This is also implemented by the use of strategies, but unlike in the case of replication that is a guest agent strategy alone, the strategy for clustering comprises a strategy for trove-api, trove-taskmanager, and trove-guestagent.
This is due to the contrast among different database engines in the way they implement clustering. Having said that, Trove in this case also is purely an enabler and the database engine itself has to support clustering for Trove to even consider implementing a strategy.
The Juno release brought clustering to MongoDB, and now with the current release, we have clustering enabled for the following data stores and the associated actions that are supported:
|
Data store name |
Cluster actions supported |
|---|---|
|
MongoDB |
Create/add shards/grow/shrink/delete |
|
PXC |
Create/delete/grow/shrink |
|
Redis |
Create/delete |
|
Vertica |
Create/delete |
As we can see, MongoDB has more features when it comes to clustering in Trove compared to its counterparts...