In the concept of a horizontally distributed database, what happens when a shard becomes unavailable?
In the concept of a horizontally distributed database, what happens when a shard becomes
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In the concept of a horizontally distributed database, what happens when a shard becomes unavailable?
your question is pretty vague. In databases where you can control the replication factor and the consistency level like Cassandra or Voldemort your data should be safe (unless you mess with it).
In the other hand (but I wouldn’t call them horizontally distributed database) there are projects like memcached or redis where each shards handles a given set of data (one copy only). So in case some shard goes down that dataset will be lost (unless you use replication, or something like that…) but certainly there is not redundancy of the data in the cluster it self