Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Enhancement] Should KafkaRebalance custom resource status `Ready` mark end of usable life?
See original GitHub issueFrom reading the documentation it was unclear that once a KafkaRebalance proposal is successful and the status turns Ready you are unable to get a new proposal from that KafkaRebalance custom resource. It was only through looking through the code that we noticed that once the status is Ready that you won’t be able to generate a new proposal from this custom resource.
This seems to be intentional but we were wondering if this should be so? We were wondering if there was any compelling reason that you shouldn’t be able to use the same custom resource for generating a new proposal? This would also make keeping a KafkaRebalance custom resource in your cluster make more sense as currently all it does is act as an old artefact of a previous rebalance.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I agree with Paolo that
Completeis a better ‘terminal’ state.I agree with Tom also that as an enhancement using a
refresh(which would initialize a new session with Cruise Control for the KafkaRebalance) on aCompleteKafkaRebalance should allow it to loop back into generating a proposal and eventuallyProposalReadyI have marked this issue as
help-wantedto allow new contributors the opportunity to enhance this behaviour.