You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 5, 2023. It is now read-only.
We have stopOnKafkaFailure = true in the config, however the see this in the log:
[2021-09-18|18:10:52.881] failed to publish, tring to log essential message module=pub topic=orders msg="ExecutionResult at height: 190325426, numOfMsgs: 0" err="dial tcp: lookup kafka-2.kafka-headless.kafka.svc.cluster.local on
?????:53: no such host"
E[2021-09-18|18:10:56.913] failed to publish, tring to log essential message module=pub topic=block msg="Block: blockHash: 06ee93729edfcbfe579be757e5ed1cac095160801f4397e42839a0755d86329e, blockHeihgt: 190325426, numofTx: 0" err="
kafka server: In the middle of a leadership election, there is currently no leader for this partition and hence it is unavailable for writes."
and the node did not stop, just proceeded with the chain as if nothing happened.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have
stopOnKafkaFailure = true
in the config, however the see this in the log:and the node did not stop, just proceeded with the chain as if nothing happened.
The text was updated successfully, but these errors were encountered: