pulsar-broker failed to start with both Liveness probe and Readiness probes failed: HTTP probe failed with statuscode: 404 about pulsar-helm-chart HOT 5 CLOSED

I tried to get into a shell into the pod while it has a short running status, and got the following
ver-nextrelease-pulsar-broker.txt

from pulsar-helm-chart.

I believe that this is fixed by #489 which is going to be released with 3.4.1 version of the chart. The release is currently in voting: https://lists.apache.org/thread/4stgyrtsnj9jhrvw0b1t8bqr4knj8bfx

from pulsar-helm-chart.

@jing-c-tyagi Pulsar Helm Chart 3.4.1 has been released. This problem should be fixed with #489 which is part of 3.4.1 release. I'll close the issue. Please reopen if the problem persists.

from pulsar-helm-chart.

Actually, now I noticed that the error message contains "Error e reading ledger - ledger=74597 - operation=Failed to read entry - entry=0" . That's a sign of a corrupted or missing ledger. You will need to repair that somehow. One solution is to accept the data loss and allow Pulsar to continue while ignoring the problem by setting autoSkipNonRecoverableData=true. That's a dangerous setting and you will face data loss.
However, in this case, since the error is about persistent://public/functions/assignments topic, that is used for Pulsar Functions coordination and the data loss isn't a problem. (You could disable Pulsar Functions completely unless you are using the feature.)

from pulsar-helm-chart.

Closing this since this isn't a pulsar-helm-chart issue.

from pulsar-helm-chart.