-
Notifications
You must be signed in to change notification settings - Fork 3.4k
HBASE-26027 The calling of HTable.batch blocked at AsyncRequestFuture… #3419
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
…Impl.waitUntilDone caused by ArrayStoreException
|
🎊 +1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
Apache9
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.
I'm not sure how could this change solve the problem described in the issue, but FWIW, I think we should honor operation timeout.
| public void waitUntilDone() throws InterruptedIOException { | ||
| try { | ||
| waitUntilDone(Long.MAX_VALUE); | ||
| long cutoff = (EnvironmentEdgeManager.currentTime() + this.operationTimeout) * 1000L; |
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.
What if operationTimeout here is negative(which means no timeout), or Long.MAX_VALUE?
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.
What if operationTimeout here is negative(which means no timeout), or Long.MAX_VALUE?
Good point, exclude that cases seems better, will fix later, thanks.
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.
The type of operationTimeout is int, so seems no need to consider Long.MAX_VALUE case.
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
#3419) * HBASE-26027 The calling of HTable.batch blocked at AsyncRequestFutureImpl.waitUntilDone caused by ArrayStoreException (cherry picked from commit 1d6eb77)
#3419) * HBASE-26027 The calling of HTable.batch blocked at AsyncRequestFutureImpl.waitUntilDone caused by ArrayStoreException (cherry picked from commit 1d6eb77)
…Impl.waitUntilDone caused by ArrayStoreException