Potential: Update PipelineHooksWorker to utilize new Sidekiq readonly database replicas capabilities
With the ability to Allow Sidekiq jobs to use readonly database replicas in place, the next step will be to enable this capability for this worker.
It appears that this worker isn't entirely read-only; occasionally, we see writes being logged:
https://log.gprd.gitlab.net/goto/40c15f1a6c04291037de9a77c4c422a3
However, during that week these 85 writes only made up 0.0008% of all ~11M successful executions. It is unclear what these writes are, but it is likely safe to migrate this worker to read from replicas primarily.
Designs
- Show closed items
Is blocked by
Relates to
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Kamil Trzciński added to epic &5592 (closed)
added to epic &5592 (closed)
- Darby Frey added rapid actionshift db load from primary label
added rapid actionshift db load from primary label
- Darby Frey marked this issue as related to #322452 (closed)
marked this issue as related to #322452 (closed)
- Darby Frey added workflowblocked label
added workflowblocked label
- Nikola Milojevic changed epic to &5691 (closed)
changed epic to &5691 (closed)
- Changzheng Liu added grouppipeline execution label
added grouppipeline execution label
- Developer
@cheryl.li assign this issue to you as I understand it's owned by ~"group::continuous integration"
- Changzheng Liu added workflowready for development label and removed workflowblocked label
added workflowready for development label and removed workflowblocked label
- Changzheng Liu assigned to @cheryl.li
assigned to @cheryl.li
- Maintainer
@jreporter Another infradev follow-up from the rapid actionshift db load from primary (goal 3), now that the issue it's being blocked by is now fully deployed in Production. The work should be pretty straightforward as we would follow what we did to migrate the
BuildHooksWorker
: #324232 (closed) Collapse replies - Developer
@cheryl.li - I have triaged this for the 14.3 needs weight and scheduled for 14.4
- Cheryl Li added backend infradev severity2 workflowplanning breakdown labels and removed rapid actionshift db load from primary workflowready for development labels
added backend infradev severity2 workflowplanning breakdown labels and removed rapid actionshift db load from primary workflowready for development labels
- Cheryl Li removed the relation with #322452 (closed)
removed the relation with #322452 (closed)
- Cheryl Li marked this issue as related to #322452 (closed)
marked this issue as related to #322452 (closed)
- Cheryl Li unassigned @cheryl.li
unassigned @cheryl.li
- Maintainer
All infradev issues need to have a proper severity label, priority label label, and a milestone set. Please add those to this issue. For more details, see the handbook.
- 🤖 GitLab Bot 🤖 added automation:infradev-missing-labels label
added automation:infradev-missing-labels label
- Maintainer
Setting label(s) devopsverify sectionops based on ~"group::continuous integration".
- 🤖 GitLab Bot 🤖 added devopsverify sectionops labels
added devopsverify sectionops labels
- Changzheng Liu changed epic to &5983 (closed)
changed epic to &5983 (closed)
- Changzheng Liu mentioned in epic &5983 (closed)
mentioned in epic &5983 (closed)
- Jackie Porter changed milestone to %14.4
changed milestone to %14.4
- Jackie Porter added needs weight label
added needs weight label
- Jackie Porter added priority2 label
added priority2 label
- Jackie Porter mentioned in issue #330664 (closed)
mentioned in issue #330664 (closed)
- 🤖 GitLab Bot 🤖 removed automation:infradev-missing-labels label
removed automation:infradev-missing-labels label
- Maintainer
@changzhengliu I'm moving this issue to groupmemory per the update in the parent epic: &5983 (closed) and updated the milestone and due date to reflect the details in the epic. Please update it if it's not accurate. Thanks!
/cc @jreporter
Edited by Cheryl Li Collapse replies - Developer
Thanks @cheryl.li.
- Cheryl Li added groupcloud connector label and removed grouppipeline execution label
added groupcloud connector label and removed grouppipeline execution label
- Cheryl Li changed due date to May 31, 2021
changed due date to May 31, 2021
- Maintainer
Setting label(s) ~"Category:Memory" based on groupmemory.
- 🤖 GitLab Bot 🤖 added Category:Cloud Connector label
added Category:Cloud Connector label
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#3131 (closed)
mentioned in issue gitlab-org/quality/triage-reports#3131 (closed)
- Nikola Milojevic marked this issue as related to #330612 (closed)
marked this issue as related to #330612 (closed)
- Nikola Milojevic marked this issue as related to #330639 (closed)
marked this issue as related to #330639 (closed)
- Maintainer
I started looking at this, and noticed that this worker has
urgency: high
. Making this job delayed may interfere with the intention to execute this ASAP. Collapse replies - Maintainer
Based on a Slack convo, it is likely best to use
sticky
consistency here: https://gitlab.slack.com/archives/CGN8BUCKC/p1621330739009300
- Matthias Käppler assigned to @mkaeppler
assigned to @mkaeppler
- Matthias Käppler added cloud connectoractive workflowin dev labels and removed workflowplanning breakdown label
added cloud connectoractive workflowin dev labels and removed workflowplanning breakdown label
- Matthias Käppler mentioned in merge request !62104 (merged)
mentioned in merge request !62104 (merged)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#3222 (closed)
mentioned in issue gitlab-org/quality/triage-reports#3222 (closed)
- Changzheng Liu changed due date to June 17, 2021
changed due date to June 17, 2021
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#3294 (closed)
mentioned in issue gitlab-org/quality/triage-reports#3294 (closed)
- Matthias Käppler changed the description
Compare with previous version changed the description
- Maintainer
I updated the description to point out that this worker does occasionally write to the primary, but very very rarely.
- Matthias Käppler added workflowin review label and removed workflowin dev label
added workflowin review label and removed workflowin dev label
- Matthias Käppler mentioned in issue #331424 (closed)
mentioned in issue #331424 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#3385 (closed)
mentioned in issue gitlab-org/quality/triage-reports#3385 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#3486 (closed)
mentioned in issue gitlab-org/quality/triage-reports#3486 (closed)
- Matthias Käppler marked this issue as related to #331424 (closed)
marked this issue as related to #331424 (closed)
- Matthias Käppler added workflowverification label and removed workflowin review label
added workflowverification label and removed workflowin review label
- Maintainer
The change is deployed everywhere. I intend to roll this out some time tomorrow: #331424 (closed)
Collapse replies - Maintainer
This is now rolled out.
- Maintainer
Closing this as done.
- James Heimbuck added devopssystems sectioncore platform labels and removed devopsverify sectionops labels
added devopssystems sectioncore platform labels and removed devopsverify sectionops labels
- Matthias Käppler mentioned in merge request !64107 (merged)
mentioned in merge request !64107 (merged)
- Changzheng Liu changed milestone to %14.1
changed milestone to %14.1
- Matthias Käppler closed
closed
- Matthias Käppler added Deliverable label
added Deliverable label
- Changzheng Liu removed cloud connectoractive label
removed cloud connectoractive label
- 🤖 GitLab Bot 🤖 added devopsdata stores label and removed devopssystems label
added devopsdata stores label and removed devopssystems label