Hey Mike, A move is logical in terms of a region and region servers (i.e. only an ID and a command is passed around), but yes the location of blocks could impact its performance a bit (until a further compaction), but would not prevent availability.
On Mon, Dec 3, 2012 at 3:53 PM, Michel Segel <[email protected]> wrote: > He could have meant that the region was unavailable for a longer duration. > > My take is that you could have limited bandwidth, and a very large region on > the move. > While I don't imagine that it could take that long to move a region, you > never know how things are tuned and you could in theory hit a timeout. > > I also have to wonder if HBase relies on the underlying HDFS to handle the > move. > > Thoughts? > > > Sent from a remote device. Please excuse any typos... > > Mike Segel > > On Dec 3, 2012, at 3:45 AM, ramkrishna vasudevan > <[email protected]> wrote: > >> Hi Jean >> >> Incase of Puts and Scans if the split is in progress it will retry. >> Suppose before the client gets to know about the split, still if the put >> is directed with the parent region row key, internally HBase directs it to >> the correct daughter region. >> But i am not clear in what you mean by Region server down for 3 mins? You >> mean during split your RS went down? >> >> Regards >> Ram >> >> >> On Mon, Dec 3, 2012 at 8:23 AM, Jean-Marc Spaggiari <[email protected] >>> wrote: >> >>> Ok. so if on the client side I'm "simply" using Puts, scans and gets >>> fron the HTableInterface, I don't have to worry about that since it >>> will retry. >>> >>> But I still should consider catching exceptions when regions are not >>> available because the region server is down for less than 3 minutes, >>> right? >>> >>> Thanks, >>> >>> JM >>> >>> 2012/12/2, Nicolas Liochon <[email protected]>: >>>> It's not accessible, but it's more or less transparent (latency impact >>>> aside) for the end user: the hbase client will retry the operation. >>>> >>>> On Sun, Dec 2, 2012 at 11:10 PM, Jean-Marc Spaggiari < >>>> [email protected]> wrote: >>>> >>>>> ? >>> -- Harsh J
