-
Notifications
You must be signed in to change notification settings - Fork 32
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.
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
fix error when delete mgh then recreate it #1288
Conversation
Signed-off-by: root <[email protected]>
/hold |
It looks must delete data or cluster id in data when recreate kafka cluster. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: clyang82, ldpliu The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/unhold
|
/retest |
Quality Gate passedIssues Measures |
Summary
we should delete kafka pvc when delete mgh, if not, when we recreate mgh, the kafka pod can not start
(org.apache.kafka.server.log.remote.storage.RemoteLogManagerConfig) [main] Exception in thread "main" java.lang.RuntimeException: Invalid cluster.id in: /var/lib/kafka/data-0/kafka-log0/meta.properties. Expected PPAVF8rBTuq25YVTs2LT_Q, but read NCsZMgUBSwuPQDozJaC8zg at org.apache.kafka.metadata.properties.MetaPropertiesEnsemble.verify(MetaPropertiesEnsemble.java:509) at kafka.tools.StorageTool$.formatCommand(StorageTool.scala:531) at kafka.tools.StorageTool$.runFormatCommand(StorageTool.scala:140) at kafka.tools.StorageTool$.execute(StorageTool.scala:80) at kafka.tools.StorageTool$.main(StorageTool.scala:53) at kafka.tools.StorageTool.main(StorageTool.scala)
Related issue(s)
https://issues.redhat.com/browse/ACM-16507
Fixes #
Tests
make unit-tests
.make integration-test
.make e2e-test-all
.