You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hbase.apache.org by bu...@apache.org on 2019/06/03 16:02:29 UTC

[hbase-filesystem] 02/02: HBASE-22515 HBOSS: Document test cases known to fail under Null lock implementation

This is an automated email from the ASF dual-hosted git repository.

busbey pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/hbase-filesystem.git

commit aba8da248c4fa0c52459db3ad4d1ffad73ab0a34
Author: Wellington Chevreuil <we...@gmail.com>
AuthorDate: Mon Jun 3 16:23:35 2019 +0100

    HBASE-22515 HBOSS: Document test cases known to fail under Null lock implementation
    
    Signed-off-by: Sean Busbey <bu...@apache.org>
---
 hbase-oss/README.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/hbase-oss/README.md b/hbase-oss/README.md
index ec433d9..4755143 100644
--- a/hbase-oss/README.md
+++ b/hbase-oss/README.md
@@ -43,6 +43,10 @@ below:
 The null implementation just provides no-op methods instead of actual locking
 operations. This functions as an easy way to verify that a test case has
 successfully reproduced a problem that is hidden by the other implementations.
+Notice this implementation should consistently fail tests enforcing atomicity,
+such as TestAtomicRename and TestCreateNonRecursive. Additional tests may
+eventually fail due to unpredictable race conditions, since no lock behaviour
+is being implemented.
 
 ### Local Implementation (org.apache.hadoop.hbase.oss.sync.LocalTreeLockManager)