-
Notifications
You must be signed in to change notification settings - Fork 9.1k
HADOOP-19452. Client#call decrease asyncCallCounter incorrectlly when exceptions occur. #7384
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
… exceptions occur.
220e74e
to
cd3893c
Compare
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
@Hexiaoqiao @slfan1989 @KeeProMise Sir, PTAL. when you have free time, thanks a lot. |
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.
Hi, @hfutatzhanghb LGTM! thanks for your contribution!
@hfutatzhanghb Thanks for the contribution! LGTM. |
@Hexiaoqiao Sir, also cc this pr. If no more comments, please help merge it , Thanks a lot. |
@hfutatzhanghb thanks for your contribution! merged. |
Thanks @slfan1989 for reviewing~ Thanks @KeeProMise for reviewing and merging! |
… exceptions occur. (apache#7384). Contributed by hfutatzhanghb. Reviewed-by: Jian Zhang <[email protected]>
Description of PR
Consider below case:
1、We do
asyncCallCounter.incrementAndGet()
and find number of async calls > maxAsyncCalls, then we doasyncCallCounter.decrementAndGet()
andthrow new AsyncCallLimitExceededException(errMsg)
in checkAsyncCall method.2、In Client#call, we invoke releaseAsyncCall() which will do
asyncCallCounter.decrementAndGet()
again.