2 things: - If you kill -9 before the flush happened, data isn't persisted. It's an async operation BTW, even if you call flush and the call returns it doesn't mean the data is already on disk. - About step 5, what happens when you wait for the region to be reassigned? The default zk timeout is pretty long so that people that didn't tune their JVM settings don't run into region servers dying all the time.
J-D On Thu, May 26, 2011 at 7:43 PM, Qing Yan <[email protected]> wrote: > Hello, > I found something strange, here is the test case: > 1) Process A insert data into a particular hbase region, WAL off, AutoFlush > off > 2) Process A issues htable.flushCommits(), no exception thrown, write down > the row key. > 4) Kill the region server manually > 5) Process B query the row key, but can't find it no matter how many times > it retries. (In the meantime via > hbase UI, the region get reassigned) > Is this expected? I am using the lastest Cloudera build. > > Thank you. >
