-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Fix free worker command bugs #16458
Fix free worker command bugs #16458
Conversation
This reverts commit b4c5a1f. Resume branch.
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.
It LGTM overall.
Would you like to add a space after "Worker" in L87
System.out.println("Worker" + workerName + " is not found in decommissioned worker set.");
Thanks for your comment! I have added the space. Can you take a look at Fix a bug in WorkerInfoField? Because the |
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.
LGTM
Add comments in FreeWorker command. Co-authored-by: Bowen Ding <6999708+dbw9580@users.noreply.github.com>
alluxio-bot, merge this please |
Check evaluation failed: |
All checks are green below but checks panel shows that the |
Re-opened to trigger all tests again. If the bot still doesn't recognize, i will force merge. |
alluxio-bot, merge this please |
### What changes are proposed in this pull request? Fix potential bugs in freeWorker command. ### Why are the changes needed? When a worker has been decommissioned, its metadata can not be got by calling `getWorkerInfolist()`. This method accesses `LoadingCache<String, List<WorkerInfo>> mWorkerInfoCache` in `DefaultBlockMaster.java`, which will not refresh instantly. As to method `removeDecommissionedWorker()` in `BlockMasterClientServiceHandler.java`, if we don't add FieldRanges, the list `decommissionedWorkers` would not get enough information to run the loop below successfully, though the worker has been decommissioned. ### Does this PR introduce any user facing changes? No. pr-link: Alluxio#16458 change-id: cid-101865dc9ec4f40e7561f81f38287c6efc2ae23f
### What changes are proposed in this pull request? Fix potential bugs in freeWorker command. ### Why are the changes needed? When a worker has been decommissioned, its metadata can not be got by calling `getWorkerInfolist()`. This method accesses `LoadingCache<String, List<WorkerInfo>> mWorkerInfoCache` in `DefaultBlockMaster.java`, which will not refresh instantly. As to method `removeDecommissionedWorker()` in `BlockMasterClientServiceHandler.java`, if we don't add FieldRanges, the list `decommissionedWorkers` would not get enough information to run the loop below successfully, though the worker has been decommissioned. ### Does this PR introduce any user facing changes? No. pr-link: Alluxio#16458 change-id: cid-101865dc9ec4f40e7561f81f38287c6efc2ae23f
### What changes are proposed in this pull request? Fix potential bugs in freeWorker command. ### Why are the changes needed? When a worker has been decommissioned, its metadata can not be got by calling `getWorkerInfolist()`. This method accesses `LoadingCache<String, List<WorkerInfo>> mWorkerInfoCache` in `DefaultBlockMaster.java`, which will not refresh instantly. As to method `removeDecommissionedWorker()` in `BlockMasterClientServiceHandler.java`, if we don't add FieldRanges, the list `decommissionedWorkers` would not get enough information to run the loop below successfully, though the worker has been decommissioned. ### Does this PR introduce any user facing changes? No. pr-link: Alluxio#16458 change-id: cid-101865dc9ec4f40e7561f81f38287c6efc2ae23f
What changes are proposed in this pull request?
Fix potential bugs in freeWorker command.
Why are the changes needed?
When a worker has been decommissioned, its metadata can not be got by calling
getWorkerInfolist()
. This method accessesLoadingCache<String, List<WorkerInfo>> mWorkerInfoCache
inDefaultBlockMaster.java
, which will not refresh instantly.As to method
removeDecommissionedWorker()
inBlockMasterClientServiceHandler.java
, if we don't add FieldRanges, the listdecommissionedWorkers
would not get enough information to run the loop below successfully, though the worker has been decommissioned.Does this PR introduce any user facing changes?
No.