high availability SOLR

1. Performance: Monitoring and alerting can help ensure that Solr is performing optimally. By tracking metrics such as response time, query throughput, and indexing speed, administrators can identify performance bottlenecks and take action to optimize the system.
2. Availability: Solr is often used in high-traffic, mission-critical applications. Monitoring and alerting can help ensure that Solr is always available and accessible to users. By monitoring metrics such as uptime, network latency, and request errors, administrators can quickly identify and resolve any issues that may be impacting availability.
3. Capacity Planning: Monitoring and alerting can help administrators plan for future growth and capacity requirements. By tracking metrics such as index size, query volume, and storage utilization, administrators can identify when the system is nearing capacity and take action to add additional resources or optimize the system.
4. Security: Monitoring and alerting can help detect and respond to security threats. By tracking metrics such as login attempts, authentication failures, and unusual user activity, administrators can quickly identify potential security breaches and take action to mitigate the risk.

Monitoring these 4 metrics are critical to Solr health:

1.     JVM Heap Memory
2.     System Load Average
3.     Disk Space
4.     Errors of all kinds

Learn more in the 4 Critical Metrics blog post.

Apache ZooKeeper integration for cluster coordination and configuration.

When used with SolrCloud, ZooKeeper tracks each node of the cluster and the state of each core on each node. In this mode, configuration files are stored in ZooKeeper and not on the file system of each node

The retention period for Solr monitoring data varies depending on the Support Plan:

• Development Plan – data is retained for 24 hours
• Core and Enterprise Plans – data is retained for 30 to 90 days depending on the contract