MXL Domain ID patch fix - #174
Merged
Merged
Conversation
jonathan-r-thorpe
commented
Aug 17, 2026
jonathan-r-thorpe
commented
Contributor
- When patching in a multi-node cluster environment where flows are replicated across nodes, the MXL domain a Sender writes to may be different to the MXL domain the Receiver reads from.
- For this reason it is unsafe to patch the domain id verbatim, and instead "auto" should be used
- This assumes that there is either one MXL domain per cluster node, or at most one MXL domain per media function meaning there is never ambiguity for Receiver's when selecting which MXL domain from which to read.
jonathan-r-thorpe
force-pushed
the
mxl-domain-auto
branch
from
August 17, 2026 12:47
1f2f62c to
083f24d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.