Replies: 4 comments 3 replies
-
|
A good start would be to share the full logs from the operator, the full configuration of your custom resources including their |
Beta Was this translation helpful? Give feedback.
-
|
The full log is too large. Basically it repeated the foloowing |
Beta Was this translation helpful? Give feedback.
-
|
kafka CR status it has the remove_broker list at that moment |
Beta Was this translation helpful? Give feedback.
-
|
We happened to stumble upon this issue, as well. In our case, it was caused by over-restrictive network policies, so it might be worth a shot to check for this, first. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Bug Description
Steps to reproduce
Expected behavior
No response
Strimzi version
0.47.0
Kubernetes version
Client Version: v1.29.12 Server Version: v1.30.3
Installation method
argoCD
Infrastructure
kubernetes cluster
Configuration files and logs
No response
Additional context
Actually, the data was already moved out by cruise-control, but the partitions were not moved out. Later, I manually run a reassignment command to assign replicas to other brokers (0 to 9), after that, the AutoRebalance immediately remove broker 10 to 19.
Beta Was this translation helpful? Give feedback.
All reactions