-
Notifications
You must be signed in to change notification settings - Fork 897
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
put S3 refresh in a separate worker #17704
Conversation
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 don't think we have specs for this file
@Ladas we moved the child managers into a single worker because of races with targeted refresh right? Is that not a concern with the S3 manager? |
@agrare should not be, S3 entities are not connected to anything from the other managers, nor there is a targeted refresh for it. (I believe it was the targeted refresh doing the race, since it would be 2 workers saving the same records) |
@agrare Yeah should be ok :) |
Okay thanks guys, I'm good with this then. I assume this has to be merged right before the amazon PR. When you two approve it I'll merge both together. |
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
f7f09a8
to
0c82f49
Compare
Checked commit AlexanderZagaynov@0c82f49 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
put S3 refresh in a separate worker
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1541435
Put S3 refresh in a separate worker, as it can contain too many objects, which blocks other data refresh.
Coupled PR: ManageIQ/manageiq-providers-amazon#461