Tech highlights
Distributions
- Elasticsearch
- Operating system provided repository
- Custom repository binaries
Replication types
- In-sync replica copies
Top features
- Secure communication
- Scalability
- Snapshot backups
Features list
Licenses | |
Open Source | |
Cluster management | |
Deploy cluster | |
Add / duplicate / remove / decommission node | |
High availability | |
Synchronous replication | |
Automated failover | |
Backup / restore | |
Incremental (snapshot) backups | |
Local / cloud backups | |
Observability | |
Infrastructure / database / query monitoring | |
Dashboarding / alerting | |
Security / compliance | |
Role-based access control | |
Key management | |
LDAP integration | |
TLS encryption | |
Reporting | |
Audit log |
Want some CC for Elasticsearch info for later?
I use Kibana with my Elasticsearch deployment for data manipulation. Does ClusterControl include that functionality too?
With ClusterControl, we focus on what we know best which is automating database provisioning and maintenance. The rest we let you decide so you can keep using Kibana as always.
Should I switch from using my PostgreSQL as a primary database deployment with ClusterControl to using Elasticsearch, as I have terabytes of data I need to go through?
In general, just keep using PostgreSQL as you do now and have a look at the available integrations for connecting with Elasticsearch, as once you’ve automated deployment with ClusterControl, the rest is just connectivity to your desire.
Given the amount of data, I don’t normally take backups for Elasticsearch. What do you recommend?
For DR and as part of a good B’n’R strategy, we highly recommend not only the use of a cluster for HA but using the Elasticsearch snapshot capability that allows you to store the backups locally or on AWS S3.