Remove bbb-html5-backend log when meeting handled by other backend

This commit is contained in:
Anton Georgiev 2021-04-08 15:51:57 -04:00 committed by GitHub
parent b6a29fb56d
commit 30229cebb6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -280,7 +280,7 @@ class RedisPubSub {
parsedMessage,
});
}
} else {
} else { // backend
if (meetingIdFromMessageCoreHeader === NO_MEETING_ID) { // if this is a system message
const meetingIdFromMessageMeetingProp = parsedMessage.core.body.props?.meetingProp?.intId;
const instanceIdFromMessage = getInstanceIdFromMessage(parsedMessage);
@ -327,7 +327,9 @@ class RedisPubSub {
parsedMessage,
});
} else {
Logger.warn('Backend meeting queue had not been initialized', { eventName, meetingIdFromMessageCoreHeader })
// If we reach this line, this means that there is no existing queue for this redis "backend" message
// which means that either the meeting is fully handled by another bbb-html5-backend.
// Logger.warn('Backend meeting queue had not been initialized', { eventName, meetingIdFromMessageCoreHeader })
}
}
}