The coordination layer nobody owns
ZooKeeper sits under Kafka, HBase, Solr and NiFi as the coordination layer. It is rarely anyone's named responsibility, and its 3.5, 3.6 and 3.7 lines are all past community end of life.
Challenge
ZooKeeper is infrastructure for other infrastructure. It gets installed once, works, and drops off the inventory -- until a CVE scan finds it, or a quorum problem takes down every service that depends on it at the same time.
Environment
ZooKeeper 3.5, 3.6 or 3.7 underneath a Kafka, Solr, NiFi or HBase deployment, past community end of life.
Approach
OSSeva treats the coordination layer as a covered runtime in its own right: CVE patches on the running ZooKeeper line, plus quorum and ensemble review before it becomes an incident.
What this delivers
A patched, owned coordination layer instead of a dependency that only gets attention when it fails.