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

[Bug]: Cluster scope limiter rate cannot be update to proxies when proxy number updates #35496

Closed
1 task done
congqixia opened this issue Aug 15, 2024 · 1 comment
Closed
1 task done

[Bug]: Cluster scope limiter rate cannot be update to proxies when proxy number updates #35496

congqixia opened this issue Aug 15, 2024 · 1 comment
Assignees
@congqixia
Labels
kind/bug Issues or changes related a bug stale indicates no udpates for 30 days triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@congqixia
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: b4b1ed6 & 2.4.8
- Deployment mode(standalone or cluster):
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

Cluster scope quota rate cannot be update to proxy when proxy number updates

Expected Behavior

Rootcoord shall update rate & quota correctly

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response
@congqixia congqixia added kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Aug 15, 2024
@congqixia congqixia self-assigned this Aug 15, 2024
congqixia added a commit to congqixia/milvus that referenced this issue Aug 15, 2024
@congqixia
fix: Reset cluster scope rate with paramtable values and force update it
528becf 
See also milvus-io#35496

Signed-off-by: Congqi Xia <[email protected]>
@congqixia congqixia mentioned this issue Aug 15, 2024
Closed
@stale Stale
Copy link

stale bot commented Sep 14, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.

@stale stale bot added the stale indicates no udpates for 30 days label Sep 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@congqixia congqixia

Labels
kind/bug Issues or changes related a bug stale indicates no udpates for 30 days triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@congqixia