Apache Cassandra supports asynchronous multi-datacenters replication and various mechanisms to repair lost data. By closely integrating Elasticsearch with Cassandra, Elassandra provides search features on many datacenters.
When it becomes necessary to increase read/write throughput, Elassandra automatically re-shards your Elasticsearch indices as new machines are added, allowing to smoothly scale-out to fit your business needs without down-time or heavy maintenance operations.
By indexing cassandra data into elasticsearch, you can provide continous and real-time data visualization for your application with Kibana.
Elassandra removes the single point of failure of Elasticsearch by using a distributed transaction to manage its configuration.
Cassandra is optimised for write-intensive workloads, therefore, Elassandra is suitable for applications where a large amount of data needs to be inserted (such as infrastructure logging, IOT, or events). Then, Elasticsearch indices can be rebuilt at any time from Cassandra tables without data duplication.
Failover-based approaches do not truly achieve high availability for write operations. By its multi-master design, Elassandra remains always available when a server/container failed or restart for a maintenance operation.
Elassandra is distributed under Apache License v2
See the Elassandra Google group.
You can also check the Q&A about using elassandra on Satck Overflow.
If you suspect that you have found a bug in Elassandra, you can report it on github.com.
Please provide as much details as you can on your issue, including your CQL schema and Elasticsearch mapping and
nodetool gossipinfo output.
Commercial support is available form Strapdata.com
Your're welcome to rise a pull request https://github.com/strapdata/elassandra/pulls.
git clone --recurse-submodules https://github.com/strapdata/elassandra
git checkout -b pull_request_branch