You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The operator searches statefulsets across the entire cluster. It seam it is not impacting the drainer as it only performs the logic when the STS comes from a broker, but it has some penalties:
Performance: clusters with high number of STS could return a lot members to search within.
API calls: it can cause a lot of api calls, as it has to get complimentary information from some STSs that should are not needed (like PVCs).
To Reproduce
When deploying the operator and a new set of brokers is created with persistence and message migration enabled, the operator searches statefulsets across the entire cluster, to find the one related with the brokers.
The text was updated successfully, but these errors were encountered:
Describe the bug
The operator searches statefulsets across the entire cluster. It seam it is not impacting the drainer as it only performs the logic when the STS comes from a broker, but it has some penalties:
To Reproduce
When deploying the operator and a new set of brokers is created with persistence and message migration enabled, the operator searches statefulsets across the entire cluster, to find the one related with the brokers.
The text was updated successfully, but these errors were encountered: