HBase failure scenarios

2013-06-10 Thread Lucas Stanley
Hi, In the Strata 2013 training lectures, Jonathan Hsieh from Cloudera said something about HBase syncs which I'm trying to understand further. He said that HBase sync guarantees only that a write goes to the local disk on the region server responsible for that region and in-memory copies go on 2

Re: HBase failure scenarios

2013-06-10 Thread Azuryy Yu
yes. datanode write is pipeline. and only if pipeline writing finished, dn return ok. --Send from my Sony mobile. On Jun 11, 2013 8:27 AM, "Lucas Stanley" wrote: > Hi, > > In the Strata 2013 training lectures, Jonathan Hsieh from Cloudera said > something about HBase syncs which I'm trying to un

Re: HBase failure scenarios

2013-06-10 Thread Lucas Stanley
Thanks Azuryy! So, when a write is successful to the WAL on the responsible region server, in fact that means that the write was committed to 3 total DataNodes, correct? On Mon, Jun 10, 2013 at 5:37 PM, Azuryy Yu wrote: > yes. datanode write is pipeline. and only if pipeline writing finished,

Re: HBase failure scenarios

2013-06-10 Thread yonghu
Hi Lucas, First, the write request for HBase consists of two parts: 1. Write into WAL; 2. Write into Memstore, when Memstore reaches the threshold, the data in Memstore will be flushed into disk. In my understanding, there are two data synchronization points: The first one is write to WAL. As WA

Re: HBase failure scenarios

2013-06-11 Thread Azuryy Yu
yes, when a write is successful to the WAL on the responsible region server, in fact that means that the write was committed to 3 total DataNodes --Send from my Sony mobile. On Jun 11, 2013 8:40 AM, "Lucas Stanley" wrote: > Thanks Azuryy! > > So, when a write is successful to the WAL on the resp