4 ms·

You can change schemas on the fly. But no one does it in their application except part of Admin. Two-phased commits are when you write a partial record to the

You can change schemas on the fly. But no one does it in their application except part of Admin. Two-phased commits are when you write a partial record to the DB and then cleanup the transaction. When they complete succesfully, they are a complete transaction, but during a failure they are not atomic through the database because it takes extra application logic to cleanup. Partition tolerance is not when one node goes offline, it is when critical nodes (master) or up to n/2 fail. For CAP, you can optimize for just Consistancy, Availabilty, or Partition tolerance. But you can also pick two - you just can not do all three. I did not know Facebook went to Hbase and why it do so - can you provide a link?

jaylevitt 15y ago
It looks like different people use different definitions of partition tolerance; the original meaning was: "The network will be allowed to lose arbitrarily many messages sent from one node to another." Which means that, if you have a network, you have partition tolerance, period. But Stonebraker defines it differently: "If there is a network failure that splits the processing nodes into two groups that cannot talk to each other, then the goal would be to allow processing to continue in both subgroups." Great article here: http://www.cloudera.com/blog/2010/04/cap-confusion-problems-with-partition-tolerance/ http://www.cloudera.com/blog/2010/04/cap-confusion-problems-... As for two-phase commits, I'm not sure what system you've used that requires app knowledge, but (for instance) PostgreSQL does them automagically; you just do PREPARE TRANSACTION and COMMIT PREPARED, and if the transaction fails you need app-level error handling - but presumably you have that error handling even without two-phase commits. Here's an article on Facebook's move to HBase: http://www.facebook.com/note.php?note_id=454991608919 http://www.facebook.com/note.php?note_id=454991608919

jaylevitt 15y ago

It looks like different people use different definitions of partition tolerance; the original meaning was: "The network will be allowed to lose arbitrarily many messages sent from one node to another." Which means that, if you have a network, you have partition tolerance, period. But Stonebraker defines it differently: "If there is a network failure that splits the processing nodes into two groups that cannot talk to each other, then the goal would be to allow processing to continue in both subgroups." Great article here: http://www.cloudera.com/blog/2010/04/cap-confusion-problems-with-partition-tolerance/ http://www.cloudera.com/blog/2010/04/cap-confusion-problems-... As for two-phase commits, I'm not sure what system you've used that requires app knowledge, but (for instance) PostgreSQL does them automagically; you just do PREPARE TRANSACTION and COMMIT PREPARED, and if the transaction fails you need app-level error handling - but presumably you have that error handling even without two-phase commits. Here's an article on Facebook's move to HBase: http://www.facebook.com/note.php?note_id=454991608919 http://www.facebook.com/note.php?note_id=454991608919