KnowledgeHub
Questions
Tags
Users
Search
Alex Rivera
|
Logout
Edit Question
Title
Body
I'm currently evaluating HBase as a Datastore, but one question was left unanswered: HBase stores many copies of the same object on many nodes (aka replication). As HBase features so-called strong consistency (in constrast to eventual consistent ) it guarantees that every replica returns the same value if read. As I understood the HBase concept, when reading values, first the HBase master is queried for a (there must be more than one) RegionServer providing the data. Then I can issue read and write requests without invention of the master. How can then replication work? How does HBase provide concistency? How do write operations internally work? Do write operations block until all replicas are written (=> synchronous replication). If yes, who manages this transfer? How does HDFS come into the game? I have already read the BigTable -Paper and searched the docs, but I found no further information on the architecture of HBase. Thanks!
Tags (comma-separated)
Save Edits
Cancel