Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add JSZ filter to return stream/consumer details only if the server is the leader #5698

Closed
bruth opened this issue Jul 24, 2024 · 0 comments · Fixed by #5704
Closed

Add JSZ filter to return stream/consumer details only if the server is the leader #5698

bruth opened this issue Jul 24, 2024 · 0 comments · Fixed by #5704
Labels
proposal Enhancement idea or proposal

Comments

@bruth
Copy link
Member

bruth commented Jul 24, 2024

Proposed change

Add a stream_leader (other names welcome) filter option to the JszOptions to reduce the data of stream_detail to only include data where the server being pinged is the leader of streams.

Use case

For systems having a lot of JetStream assets, this will reduce the overall resources use on the server as well as the data sent to the client.

Contribution

Yes

@bruth bruth added the proposal Enhancement idea or proposal label Jul 24, 2024
derekcollison added a commit that referenced this issue Jul 27, 2024
The stream state and replica info is only guaranteed to be accurate when
returned by the leader of a given stream. This new option returns stream
details only for the stream in which the server is the leader for that
stream. For systems with many streams this can significantly reduce the
amount of data returned when scraping across all servers since
non-leader details will likely be ignored.

Fix #5698
neilalexander pushed a commit that referenced this issue Jul 29, 2024
The stream state and replica info is only guaranteed to be accurate
when returned by the leader of a given stream. This new option
returns stream details only for the stream in which the server
is the leader for that stream. For systems with many streams this
can significantly reduce the amount of data returned when scraping
across all servers since non-leader details will likely be ignored.

Fix #5698

Signed-off-by: Byron Ruth <byron@nats.io>
neilalexander pushed a commit that referenced this issue Jul 29, 2024
The stream state and replica info is only guaranteed to be accurate
when returned by the leader of a given stream. This new option
returns stream details only for the stream in which the server
is the leader for that stream. For systems with many streams this
can significantly reduce the amount of data returned when scraping
across all servers since non-leader details will likely be ignored.

Fix #5698

Signed-off-by: Byron Ruth <byron@nats.io>
bruth added a commit that referenced this issue Jul 29, 2024
The stream state and replica info is only guaranteed to be accurate
when returned by the leader of a given stream. This new option
returns stream details only for the stream in which the server
is the leader for that stream. For systems with many streams this
can significantly reduce the amount of data returned when scraping
across all servers since non-leader details will likely be ignored.

Fix #5698

Signed-off-by: Byron Ruth <byron@nats.io>
bruth added a commit that referenced this issue Jul 29, 2024
The stream state and replica info is only guaranteed to be accurate
when returned by the leader of a given stream. This new option
returns stream details only for the stream in which the server
is the leader for that stream. For systems with many streams this
can significantly reduce the amount of data returned when scraping
across all servers since non-leader details will likely be ignored.

Fix #5698

Signed-off-by: Byron Ruth <byron@nats.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proposal Enhancement idea or proposal
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant