4 ms·
These problems are a major reason why I decided to not go with the typical 1 cluster-multiple replica infrastructure. Instead I have multiple clusters, 0 repli
by AznHisoka 12y ago
These problems are a major reason why I decided to not go with the typical 1 cluster-multiple replica infrastructure.
Instead I have multiple clusters, 0 replicas, and load balance against those clusters. No split brain problem, but the same data availability benefits as having replicas. Granted, the logic is all in my app now. Now when a cluster is down, I have retry logic to keep reindexing that data to that cluster until it succeeds.
- keypusher 12y agoSplit brain problems are not related to having a replica, it can happen when any nodes in the cluster cannot talk to each other, and therefore opens the possibility of multiple masters. Having multiple clusters just means you can have multiple things in split brain, unless you have protection within your clustering stack against this outcome.
- gibrown 12y agoDoesn't that mean that you immediately lose data if a node goes down or a disk dies? FWIW the split brain problems (while not impossible) are extremely rare in ES in my experience. Seems like you've traded one potentially rare problem for a lot more complexity and other problems.
- AznHisoka 12y agoI'm using Sidekiq, a messaging queue framework to handle indexing data to my nodes/clusters. So if one goes down, it will always retry reindexing in a future time over and over until its successful. Everytime there's new data, I need to send the same data to all of the clusters.
- gibrown 12y agoInteresting. Were you actually seeing failures without running multiple clusters?