[FIXED] JetStream: interest across gateways #2750
Merged
Conversation
This file contains 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
If the interest existed prior to the initial creation of the consumer, the gateway "watcher" would not be started, which means that interest moving across the super-cluster after that would not be detected. The watcher runs every second and not sure if this is costly or not, so we may want to go a different approach of having a separate interest change channel that would be specific to gateways. But this means adding a new sublist where the interest would be registered and that sublist would need to be updated when processing GW RSub and RUnsub? Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
|
Could this scheme at a server be inverted (eval on SUB/UNSUB at the server) to solve the general case of alerting on foreign-account interest changes? |
|
On SUB/UNSUB can we follow the current export/import maps in reverse? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If the interest existed prior to the initial creation of the
consumer, the gateway "watcher" would not be started, which means
that interest moving across the super-cluster after that would
not be detected.
The watcher runs every second and not sure if this is costly or
not, so we may want to go a different approach of having a separate
interest change channel that would be specific to gateways. But this
means adding a new sublist where the interest would be registered
and that sublist would need to be updated when processing GW RSub
and RUnsub?
Resolves #2745
Signed-off-by: Ivan Kozlovic ivan@synadia.com