-
Notifications
You must be signed in to change notification settings - Fork 898
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
Delegate queue_name for refresh to parent manager instead of queue_name arrays #20345
Conversation
bff6497
to
ea51528
Compare
Are we still storing JSON in the column, then or will there be a data migration? Since it's using the parent's queue name, how do we report that in |
Yeah, this would break evm:status since we use worker.queue_name... EDIT: well, it could break it, depending on what |
Sorry might be missing something but why would it break evm:status? |
|
cool! Yeah, I changed my comment afterwards... it wouldn't definitely break it... if it returns a queue_name format that was previously supported, it would work |
ea51528
to
2ddba64
Compare
@agrare it says it depends on the other PRs, do they need to be merged first? If so, can you mark this WIP and ping me when they're merged? |
Oh I think "not WIP" implies ready to review not ready to merge, I'll mark it WIP if that's how most people use it |
2ddba64
to
99610f8
Compare
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.
Looks good.
I think we may have this as a static method to get away from having to create an ems object for every queue.
But looking at the original code in ems_refresh.rb
it looks like that wasn't the intent here.
I remember getting a big performance gain in MiqQueue.put
by avoiding the queue lookup.
Maybe something to file away in our minds for future work
I'm going to un-WIP this because it is ready for review, just has an associated schema change. @jrafanie please review |
99610f8
to
387abe2
Compare
Checked commit agrare@387abe2 with ruby 2.6.3, rubocop 0.69.0, haml-lint 0.28.0, and yamllint |
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
@Fryguy are you good with this PR and the associated migration (ManageIQ/manageiq-schema#496)? |
ManageIQ/manageiq#20345 dropped combined child manager queue names
ManageIQ/manageiq#20345 dropped combined child manager queue names
ManageIQ/manageiq#20345 dropped combined child manager queue names
ManageIQ/manageiq#20345 dropped combined child manager queue names
ems_id comes from ems_id_from_queue_name which as of [1] can only ever return an integer or nil from parse_ems_id. [1] ManageIQ#20345
ems_id comes from ems_id_from_queue_name which as of [1] can only ever return an integer or nil from parse_ems_id. [1] ManageIQ#20345
ems_id comes from ems_id_from_queue_name which as of [1] can only ever return an integer or nil from parse_ems_id. [1] ManageIQ#20345
ems_id comes from ems_id_from_queue_name which as of [1] can only ever return an integer or nil from parse_ems_id. [1] ManageIQ#20345
ems_id comes from ems_id_from_queue_name which as of [1] can only ever return an integer or nil from parse_ems_id. [1] ManageIQ#20345
Instead of changing the worker queue_name to allow for arrays which has been problematic we could simply delegate the queue_name for refresh to the parent manager if the child managers are targeted and leave the parent manager's RefreshWorker queue_name alone.
Depends on:
Dependent:
Fixes #20307