known issue for events in 1.19 and 1.20 #849
Open
Conversation
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
Vercel Previews Deployed
|
Broken Link CheckerNo broken links found! 🎉 |
…ue-two-event-clients
…ue-two-event-clients
…ue-two-event-clients
…ue-two-event-clients
|
@tvoran The update text looks good. Please also add an entry to the summary tables for 1.19 and 1.20 under |
schavis
requested changes
Sep 4, 2025
github-actions
bot
added
the
Vault IC
schavis
requested changes
Sep 9, 2025
Comment on lines
+477
to
+480
| Users may miss events if two or more event clients subscribe to the same | ||
| performance standby node in a cluster, and each client specifies the same | ||
| namespace and event type filters. If one client disconnects, the other(s) will | ||
| no longer receive events. |
There was a problem hiding this comment.
Suggested change
| Users may miss events if two or more event clients subscribe to the same | |
| performance standby node in a cluster, and each client specifies the same | |
| namespace and event type filters. If one client disconnects, the other(s) will | |
| no longer receive events. | |
| Users may miss events when multiple clients subscribe to the same performance | |
| standby node in a cluster with the same namespace and event type filters because | |
| one client disconnecting unsubscribes the remaining clients who no longer | |
| receive events. |
Style correction: write in active voice
Comment on lines
+484
to
+486
| If there are multiple event subscribers with the same namespace and event type | ||
| filters, spread them out among the nodes of the Vault cluster, or only subscribe | ||
| to events on the active node of the cluster. |
There was a problem hiding this comment.
Suggested change
| If there are multiple event subscribers with the same namespace and event type | |
| filters, spread them out among the nodes of the Vault cluster, or only subscribe | |
| to events on the active node of the cluster. | |
| If you have multiple event subscribers with the same namespace and event type | |
| filters you have two options: | |
| 1. Spread them out among the nodes of the Vault cluster. | |
| 1. Only subscribe to events on the active node of the cluster. |
Comment on lines
+369
to
+371
| If there are multiple event subscribers with the same namespace and event type | ||
| filters, spread them out among the nodes of the Vault cluster, or only subscribe | ||
| to events on the active node of the cluster. |
There was a problem hiding this comment.
Suggested change
| If there are multiple event subscribers with the same namespace and event type | |
| filters, spread them out among the nodes of the Vault cluster, or only subscribe | |
| to events on the active node of the cluster. | |
| If you have multiple event subscribers with the same namespace and event type | |
| filters you have two options: | |
| 1. Spread them out among the nodes of the Vault cluster. | |
| 1. Only subscribe to events on the active node of the cluster. |
Edited to match 1.19.x language
Comment on lines
+362
to
+365
| Users may miss events if two or more event clients subscribe to the same | ||
| performance standby node in a cluster, and each client specifies the same | ||
| namespace and event type filters. If one client disconnects, the other(s) will | ||
| no longer receive events. |
There was a problem hiding this comment.
Suggested change
| Users may miss events if two or more event clients subscribe to the same | |
| performance standby node in a cluster, and each client specifies the same | |
| namespace and event type filters. If one client disconnects, the other(s) will | |
| no longer receive events. | |
| Users may miss events when multiple clients subscribe to the same performance | |
| standby node in a cluster with the same namespace and event type filters because | |
| one client disconnecting unsubscribes the remaining clients who no longer | |
| receive events. |
Edited to match 1.19.x language
|
|
||
| | Change | Affected version | Fixed version | ||
| | ------------ | ---------------------- | -------------------- | ||
| | Known issue | 1.20.x+ent, 1.19.x+ent | None |
There was a problem hiding this comment.
Suggested change
| | Known issue | 1.20.x+ent, 1.19.x+ent | None | |
| | Known issue | 1.20.0+ent | None |
We should note the specific version where the problem appears. I'm assuming if we're using ".x" that means it's been there since 1.20.0?
|
|
||
| | Change | Affected version | Fixed version | ||
| | ------------ | ---------------------- | -------------------- | ||
| | Known issue | 1.20.x+ent, 1.19.x+ent | None |
There was a problem hiding this comment.
Suggested change
| | Known issue | 1.20.x+ent, 1.19.x+ent | None | |
| | Known issue | 1.19.0+ent | None |
We should note the specific version where the problem appears. I'm assuming if we're using ".x" that means it's been there since 1.19.0?
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.
Adding a known issue with event subscriptions in Vault 1.19 and 1.20 ENT.