apache/curator

Apache Curator

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 40 minutes ago
Added to GitGenius on September 21st, 2026
Created on March 3rd, 2014
Open Issues & Pull Requests: 134 (+0)
GitHub issues: Enabled
Number of forks: 1,248
Total Stargazers: 3,170 (+0)
Total Subscribers: 153 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 24.9 days
Mean response time: 401.6 days
90th percentile: 1916.3 days
Tracked items: 63

How this project is maintained

95% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 93% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 20
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,012 days
Stale 30+ days: 19
Stale 90+ days: 16

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • imported-jira-issue (46)
  • bug (23)
  • rfe (22)
  • Imported Jira Issue (3)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Apache Curator is a Java client library that simplifies interaction with Apache ZooKeeper.

ZooKeeper provides distributed coordination and consensus capabilities but exposes a low-level API that requires developers to handle complex state management, connection recovery, and retry logic manually. Curator abstracts away these complexities by providing higher-level recipes and utilities built on top of ZooKeeper's core functionality. It handles connection management, automatic reconnection, and common distributed patterns so developers can focus on their application logic rather than ZooKeeper protocol details.

Curator is well-suited for teams building distributed systems that need reliable coordination primitives such as leader election, distributed locks, barriers, or queues. It works best in Java-based architectures where ZooKeeper is already part of the infrastructure. The library is particularly valuable when you need to implement consensus-based features without reimplementing error handling and recovery mechanisms. Organizations already committed to ZooKeeper as their coordination layer will find Curator significantly reduces development time and improves reliability compared to using ZooKeeper's raw client API.

The project maintains steady development activity with regular updates and bug fixes. The codebase shows consistent attention to stability and backward compatibility. Contributions are reviewed and integrated on an ongoing basis, indicating active maintenance. The project benefits from being part of the Apache ecosystem, which provides governance and long-term sustainability. Documentation and examples are maintained alongside code changes to help users understand and adopt new features.