zbentley opened a new issue #11842:
URL: https://github.com/apache/pulsar/issues/11842
**Describe the bug**
If I kill Pulsar standalone with SIGKILL/`kill -9` after it has been
started, the broker will not successfully start anytime thereafter unless its
data directory is removed and it is reset to initial state.
If this isn't easily fixable, please provide a workaround that I can use on
Pulsars that get into this state to bring them back without deleting all their
data (something I can do in ZK or to the BK data files short of deleting
everything that makes startup succeed).
**To Reproduce**
1. Start pulsar standalone against an empty data directory/fully clean-slate.
2. Wait for the broker to become fully available. No operations need to be
performed against it though.
3. Kill the broker with SIGKILL. I used `pkill -9 -f pulsar`.
4. Verify that the broker process is gone.
5. Attempt to start Pulsar again.
6. Observe that the broker never reaches a running state.
**Expected behavior**
Pulsar should start successfully after being brutally killed. This is an
important simulation of e.g. a server power loss/kubernetes node abrupt
termination event.
**Desktop (please complete the following information):**
- OS: MacOS 10.11
**Attachments**
- Attached are my full server output logs, containing two startup attempts:
the first successful startup, then a line I wrote into the log by hand `KILLED
HERE` indicating where I sent SIGKILL to the broker, followed by the second
(failed) startup attempt.
- Also attached is a copy of my data directory after the crash.
[error.log](https://github.com/apache/pulsar/files/7078062/error.log)
[output.log](https://github.com/apache/pulsar/files/7078063/output.log)
[standalone.zip](https://github.com/apache/pulsar/files/7078064/standalone.zip)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
