-
Notifications
You must be signed in to change notification settings - Fork 9.2k
HDDS-2048: State check during container state transition in datanode should be lock protected #1375
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
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
Thanks @lokeshj1703 for the PR. |
|
@nandakumar131 The api in KeyValueContainer is currently public. Therefore I did not remove those locks. |
|
@nandakumar131 Thanks for reviewing the PR! I have updated changes as per offline discussion. |
|
💔 -1 overall
This message was automatically generated. |
nandakumar131
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.
We should do the lock/unlock with try..finally block.
|
@nandakumar131 Thanks for reviewing the changes! 3rd commit addresses your comments. There was an unlock missing for container read lock taken in BlockManagerImpl class. I have fixed it in the commit as well. |
|
💔 -1 overall
This message was automatically generated. |
…should be lock protected (apache#1375)
…should be lock protected (apache#1375)
Currently container state checks during state transition are not lock protected in KeyValueHandler. These can cause invalid state transitions.