4 ms·
This isn't truly distributed in that sense: "Instead of managing chunks, SeaweedFS manages data volumes in the master server. Each data volume is size
by sabujp 10y ago
This isn't truly distributed in that sense:
"Instead of managing chunks, SeaweedFS manages data
volumes in the master server. Each data volume is size
32GB, and can hold a lot of files. And each storage node
can have many data volumes. So the master node only needs
to store the metadata about the volumes, which is fairly
small amount of data and is generally stable."
- the_duke 10y agoSo there's no replication?
- chrislusf 10y agoThere is. I am not following your reasoning.
- sabujp 10y agoi think he's asking if there's replication for the data stored on the master in case the master goes down, i.e. can there be multiple masters?
- jusob 10y agoYou can (should) have multiple masters. But each volume has a primary master. I did see other masters loose the volume state information after the primary master has gone down and been taken out of the cluster.
- chrislusf 10y agoGood observation. I will make the recovery much faster with gRPC calls, which can detect broken network much faster than http heartbeats.
- chrislusf 10y agoThe master nodes only have soft states. All actual states are stored on volume servers, together with the actual data. If one master node goes down, the other master nodes will elect a new leader and control the system.