-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Fix dyn shovel child_exists check for old id format #9968
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
Because the clause `({{_, N}, _, _, _}) -> N =:= Name;` matches both new and old id format but always returns false for old id format, `child_exists` also returned false for old ids. Also rename SupId to ChildId to be pedantically correct.
I did manual testing of this patch together with #9965. Upgraded a 3-node cluster from 3.12.6 to 3.12.9. Reproduced issues and verified below worked after applying the patch
Details
Tracing - stop_child not called
Trace
Update old shovel
Tracing - stop_child called
Update new shovel
Tracing - stop_child called
|
Proposed Changes
Because the clause
({{_, N}, _, _, _}) -> N =:= Name;
matches both new and old id format but always returns false for old id format,child_exists
also returned false for old ids.Also rename SupId to ChildId to be pedantically correct.
Follow-up of #9965
Types of Changes
What types of changes does your code introduce to this project?
Put an
x
in the boxes that applyChecklist
Put an
x
in the boxes that apply.You can also fill these out after creating the PR.
If you're unsure about any of them, don't hesitate to ask on the mailing list.
We're here to help!
This is simply a reminder of what we are going to look for before merging your code.
CONTRIBUTING.md
documentFurther Comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc.