title: How does Hadoop's HDFS High Availability feature affects the CAP Theorem?
body: <p>According to everything I've read so far about the CAP Theorem, no distributed system can provide all three of: Availability, Consistency and Partition Tolerance.</p>
  
  <p>Now, Hadoop 2.x introduced a new feature, which can be configured in order to remove the single point of failure that the hadoop clusters had (the single namenode). With that, the cluster becomes highly available, consistent and partition tolerant.
  Am I right? Or am I missing something? According to CAP, if the system tries to provide all three features, it should pay the price in latency, does the new feature add this latency to the cluster? Or has Hadoop cracked the CAP Theorem?</p>