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.

Sign up for GitHub

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

Jump to bottom

Repartition with good count as max when any item has Bad_TooManyMonitoredItems status #2339

Open
Tracked by #2333
marcschier opened this issue Sep 5, 2024 · 0 comments
Open
Tracked by #2333

Repartition with good count as max when any item has Bad_TooManyMonitoredItems status #2339

marcschier opened this issue Sep 5, 2024 · 0 comments
Labels
feature request New feature or request
Milestone
2.9.12

Comments

@marcschier
Copy link
Contributor

marcschier commented Sep 5, 2024 •
edited
Loading

Add all items in the partition. Then, if any has
Bad_TooManyMonitoredItems status count the number of successful ones and set this as new maxMonitoredItem count which presumably is lower than our current max. Then, repartition the root and children subscriptions with the new number.
@marcschier marcschier added this to the Future milestone Sep 5, 2024
@marcschier marcschier added the feature request New feature or request label Sep 5, 2024
@marcschier marcschier changed the title Create new subscription when adding to current one fails due to size errors. Repartition with good count as max when any item has Bad_TooManyMonitoredItems status Sep 6, 2024
@marcschier marcschier modified the milestones: Future, 2.9.12 Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature request New feature or request
Projects
None yet
Milestone
2.9.12
Development

No branches or pull requests
1 participant
@marcschier