Apparently, zookeeper logs were never correctly persisted. Note that this update will trigger a restart of the stack on the next install.
This issue was deduced via a separate issue noticed by @nivemaham that Kafka 2.4 would no longer start after a restart because Zookeeper did not persist its cluster ID.
Apparently, zookeeper logs were never correctly persisted. Note that this update will trigger a restart of the stack on the next install.
This issue was deduced via a separate issue noticed by @nivemaham that Kafka 2.4 would no longer start after a restart because Zookeeper did not persist its cluster ID.