-
Notifications
You must be signed in to change notification settings - Fork 3.4k
HBASE-24794 hbase.rowlock.wait.duration should not be <= 0 #2174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
to clarify, my warning about test log size is only when running the test without the new guardrail. |
|
🎊 +1 overall
This message was automatically generated. |
virajjasani
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left one nit, +1 otherwise
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
Show resolved
Hide resolved
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
virajjasani
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
|
🎊 +1 overall
This message was automatically generated. |
if hbase.rowlock.wait.duration is <=0 then log a message and treat it as a value of 1ms. Signed-off-by: Viraj Jasani <[email protected]> (cherry picked from commit 840a557)
if hbase.rowlock.wait.duration is <=0 then log a message and treat it as a value of 1ms. Signed-off-by: Viraj Jasani <[email protected]> (cherry picked from commit 840a557)
if hbase.rowlock.wait.duration is <=0 then log a message and treat it as a value of 1ms. Signed-off-by: Viraj Jasani <[email protected]> (cherry picked from commit 840a557)
|
🎊 +1 overall
This message was automatically generated. |
if hbase.rowlock.wait.duration is <=0 then log a message and treat it as a value of 1ms. amended for branches-1 Signed-off-by: Viraj Jasani <[email protected]> (cherry picked from commit 840a557)
if hbase.rowlock.wait.duration is <=0 then log a message and treat it as a value of 1ms. amended for branches-1 Signed-off-by: Viraj Jasani <[email protected]> (cherry picked from commit 840a557) (cherry picked from commit 51161b5)
if hbase.rowlock.wait.duration is <=0 then log a message and treat it as a value of 1ms. amended for branches-1 amended for branch-1.3 as test-only to verify existing behavior. Signed-off-by: Viraj Jasani <[email protected]> (cherry picked from commit 840a557) (cherry picked from commit 51161b5)
|
🎊 +1 overall
This message was automatically generated. |
if hbase.rowlock.wait.duration is <=0 then log a message and treat it as a value of 1ms. Signed-off-by: Viraj Jasani <[email protected]> (cherry picked from commit 840a557)
if hbase.rowlock.wait.duration is <=0 then log a message and treat it as a value of 1ms. Signed-off-by: Viraj Jasani <[email protected]> (cherry picked from commit 840a557) (cherry picked from commit 7607c7b) Author: Sean Busbey <[email protected]> Reason: Bug Ref: CDPD-15671 Change-Id: I51bf46cd9f0ad61a163a92dca7cd4932a20c55a8 (cherry picked from commit 0503822)
if hbase.rowlock.wait.duration is <=0 then log a message and treat it as a value of 1ms. Signed-off-by: Viraj Jasani <[email protected]> (cherry picked from commit 840a557) (cherry picked from commit 7607c7b) Change-Id: I51bf46cd9f0ad61a163a92dca7cd4932a20c55a8
if hbase.rowlock.wait.duration is <=0 then log a message and treat it as a value of 1ms. amended for branches-1 Signed-off-by: Viraj Jasani <[email protected]> (cherry picked from commit 840a557) (cherry picked from commit 51161b5)
with just the new test, things fail after spinning until timeout
warning for those looking to duplicate this, there are about 2.5 million copies of this message
and it takes a bit of room
test passes after this patch is in place, verified presence of warning in test logs. test-only backport to branch-1.3 also passes without the HRegion change.
tested out a branch-2.1 based backport on a cluster and that also worked as expected (logged a warning and then writes to meta were able to succeed)