irairdon opened a new issue #7059:
URL: https://github.com/apache/pulsar/issues/7059
When running pulsar on Kubernetes if you reboot a Kubernetes node any client
producing will hand and be unable to produce new messages.
**To Reproduce**
Steps to reproduce the behavior:
1. Install helm chart for Pulsar on kubernetes
2. Use pulsar-perf tool to start producing messages on a single topic.
3. reboot one of the kubernetes nodes.
4. I have not found errors listed but the pulsar-perf tool will start
showing 0 messages produced.
5. If you kill the broker pods one at a time eventually the producer will
start producing messages again.
**Expected behavior**
I expect pulsar not to hang if a kuberentes node reboots.
**Desktop (please complete the following information):**
- Pulsar 2.5.2
- Kubernetes 1.13
**Additional context**
I haven't been able to reproduce be restarting individual services. It only
occurs in a node restart. When the current producer is hung you can still
create new topics and new producers that will not see the hang so it is related
only to existing active topics.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
