# apache zookeeper Published articles for apache zookeeper. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Latest Chainguard Images: FIPS, Harbor stack, Apache, and more! DevFeed: [Latest Chainguard Images: FIPS, Harbor stack, Apache, and more!]() Original publisher: [Read original article]() Published: 2024-06-20T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [container images](), [Security](), [open-source-security](), [supply-chain-security](), [airflow](), [streaming-data-processing](), [DataOps]() Tags: [airflow](), [apache](), [apache-zookeeper](), [chainguard](), [chainguard-images](), [container-image](), [container-images](), [fips](), [harbor](), [jitsu](), [open-source](), [pipelines](), [security](), [software-supply-chain](), [stream-processing](), [vulnerabilities]() ### AI overview Chainguard's monthly roundup announces 57 new hardened, minimal container images, including expanded Apache, Jitsu, and Harbor stacks. More than half of the releases are FIPS compliant, bringing the total to nearly 300 FIPS-validated Images. The article highlights security, reduced CVE exposure, software supply chain protection, and images for Apache Airflow, Superset, Zookeeper, and Nifi. ### Source excerpt Upgrade your software security with the latest Chainguard Images, featuring FIPS, Harbor, Apache, and more. Streamline your development and enhance protection. ## Chainguard Image now available for Apache Zookeeper DevFeed: [Chainguard Image now available for Apache Zookeeper]() Original publisher: [Read original article]() Published: 2023-03-20T00:00:00Z Content type: news Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [Containers](), [Security](), [vulnerability scanning](), [GitHub]() Tags: [apache-zookeeper](), [built-from-source](), [chainguard](), [chainguard-images](), [container-image](), [containers](), [cosign](), [docker-zookeeper](), [jdk](), [kafka-zookeeper](), [minimal-image](), [provenance](), [secure-images](), [vulnerability-scanning](), [wolfi](), [zookeeper-container](), [zookeeper-image]() ### AI overview Chainguard announces a new Chainguard Image for Apache Zookeeper. Built from source with Wolfi and Chainguard's OpenJDK JRE, the minimal image is hardened for non-root operation and a locked-down filesystem, and is presented as more than 50% smaller than alternatives. ### Source excerpt New Chainguard Image for Apache Zookeeper is over 50% smaller in size compared to alternatives. Powered by Wolfi, comes with our own JDK, and built from source. ## CAP: if all you have is a timeout, everything looks like a partition DevFeed: [CAP: if all you have is a timeout, everything looks like a partition]() Original publisher: [Read original article]() Author: Nicolas Liochon (noreply@blogger.com) Published: 2015-05-25T17:42:00Z Content type: article Language: en Sources: [Nicolas Liochon]() Topics: [Network](), [Hadoop](), [Processes](), [Database](), [Open Source]() Tags: [acid](), [apache](), [apache-zookeeper](), [availability](), [cap-theorem](), [consistency](), [database](), [distributed-system](), [durability](), [hadoop](), [latency](), [network](), [partition](), [process](), [synchronization](), [timeout]() ### AI overview This article distinguishes network partitions from node failures and process crashes in the CAP theorem. It examines how Apache HBase uses Apache ZooKeeper ephemeral nodes and session timeouts for failure detection, noting that timeout-based recovery affects mean time to repair across these failure scenarios. ### Source excerpt "I suppose it is tempting, if the only tool you have is a timeout, to treat everything as if it were a partition." - Abraham Maslow, quoted from memory This post is part of the CAP theorem series. You may want to start by my post on ACID vs. CAP if you have a database background but have never really been exposed to the CAP theorem. The post discussing some traps in the 'Availability' and 'Consistency' definition of CAP should also be used as an introduction if you know CAP but haven't looked at its formal definition. Partitions in the CAP theorem are network partitions, and nothing else. There're not node failure or process crash. But does this matter in real-life? Let's answer this question by looking at an optimisation implemented on Apache HBase and Apache ZooKeeper when handling process crash. This is applicable by anyone using ZooKeeper. Apache HBase, ZooKeeper and failure detection Using ZooKeeper website: "ZooKeeper is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. All of these kinds of services are used in some form or another by distributed applications." And HBase website: "Apache HBase™ is the Hadoop database, a distributed, scalable, big data store." HBase is an open source implementation of Google's Bigtable. Cluster size varies from 5 to x000 nodes. ZooKeeper is used by HBase for a few things, one of them being, like in Bigtable, detecting failures. ZooKeeper manages failures by giving the user the possibility to create "ephemeral nodes". "These znodes exist as long as the session that created the znode is active. When the session ends the znode is deleted." And then "Expirations happen when the cluster does not hear from the client within the specified session timeout period (i.e. no heartbeat). At session expiration the cluster will delete any/all ephemeral nodes owned by that session and immediately notify any/all connected clients of the change (anyone w