HBASE-22857 Fix the failed ut TestHRegion and TestHRegionWithInMemoryFlush (#495)
Signed-off-by: Peter Somogyi psomogyi@apache.org Signed-off-by: stack stack@apache.org
This commit is contained in:
parent
6f9db4660a
commit
76a68bd27c
|
@ -1242,15 +1242,6 @@ public class TestHRegion {
|
||||||
HConstants.EMPTY_END_ROW, false, Durability.USE_DEFAULT, wal, family);
|
HConstants.EMPTY_END_ROW, false, Durability.USE_DEFAULT, wal, family);
|
||||||
region.put(put);
|
region.put(put);
|
||||||
|
|
||||||
// 2. Test case where START_FLUSH succeeds but COMMIT_FLUSH will throw exception
|
|
||||||
wal.flushActions = new FlushAction [] {FlushAction.COMMIT_FLUSH};
|
|
||||||
wal = new FailAppendFlushMarkerWAL(FileSystem.get(walConf), FSUtils.getRootDir(walConf),
|
|
||||||
method, walConf);
|
|
||||||
|
|
||||||
this.region = initHRegion(tableName, HConstants.EMPTY_START_ROW,
|
|
||||||
HConstants.EMPTY_END_ROW, false, Durability.USE_DEFAULT, wal, family);
|
|
||||||
region.put(put);
|
|
||||||
|
|
||||||
// 3. Test case where ABORT_FLUSH will throw exception.
|
// 3. Test case where ABORT_FLUSH will throw exception.
|
||||||
// Even if ABORT_FLUSH throws exception, we should not fail with IOE, but continue with
|
// Even if ABORT_FLUSH throws exception, we should not fail with IOE, but continue with
|
||||||
// DroppedSnapshotException. Below COMMMIT_FLUSH will cause flush to abort
|
// DroppedSnapshotException. Below COMMMIT_FLUSH will cause flush to abort
|
||||||
|
|
Loading…
Reference in New Issue