feat: add reference count to subscription table #1143
+393
−595
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.
Description
Previously, when multiple consumers within a session subscribed to the same name, each subscription would send a separate subscribe message to the data plane. Similarly, each unsubscribe would send an unsubscribe message. This lead to issues where a subscription was removed from the data plane while other consumers still needed it.
This PR implements reference counting in the subscription table to prevent this problem. It also removes the session route cache in the session layer as the ref count is now directly implemented in the subscription table.
Ref: #1138
Type of Change
Checklist