Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Hazelcast failover and backups

The hazelcast documentation states that

If a member goes down, its backup replica that also holds the same data, will dynamically redistribute the data including the ownership and locks on them to remaining live nodes. As a result, no data will get lost.

Few questions

a) If a backup of 1 is configured for a member in the cluster then does that imply that there is only 1 more member in the cluster which has the backup for that member ? Or is there a backup of the backup ?

b) So given a) if both the member and its backup go down then would there be data loss ?

c) If there is a write through strategy in place and both the member and its backup go down and there is data loss then is there a mechanism in place to restore the data dynamically (using the write through mechanism or something else ) ?

Thanks in advance

like image 338
sunny Avatar asked Oct 02 '22 07:10

sunny


1 Answers

A few answers:

a) backups are configured on a data-structure level. So you could say: this map has 1 synchronous backups... and that map zero.. or 2 or...

Backups can be synchronous (meaning that there is a write through of the change to the backup) or it can be a write behind (so at some point in time the backups is done). Asynchronous and synchronous backups are configured independently on the data-structure level.

b) yes. That is why you can configure more than 1 backup if you have such high availability requirements.

c) some of the datastructures (e.g. map/queue) can be configured with a maploader/mapstore strategy; which makes it possible to e.g. write your changes to disk/database etc.

like image 86
pveentjer Avatar answered Oct 07 '22 18:10

pveentjer