Activate loader-metadata in production
1 unresolved thread
1 unresolved thread
To be merged once the necessary checks on the staging dataset is done (next monday).
Refs. swh/infra/sysadm-environment#4794 (closed)
cc @vlorentz (jsyk)
Merge request reports
Activity
mentioned in issue swh/infra/sysadm-environment#4794 (closed)
- Resolved by Antoine R. Dumont
added 7 commits
-
aa53b311...4ba124fa - 6 commits from branch
production
- fd061022 - Activate loader-metadata in production
-
aa53b311...4ba124fa - 6 commits from branch
91 91 # See https://gitlab.softwareheritage.org/swh/meta/-/issues/4949 92 92 sentrySwhPackage: swh.loader.cvs 93 93 94 loader_metadata: 95 enabled: true 96 storage: 97 host: saam.internal.softwareheritage.org 98 port: 5002 99 scheduler: 100 host: saatchi.internal.softwareheritage.org 101 port: 5008 102 consumerGroup: swh.loader_metadata.journal_client looks like the consumer group is not prefixed by the user name
Edited by Vincent SellierI recall it's the chart that does the proper naming when using authentication (always now). I'll double check.
^ yes, that's it!
group_id: {{ $journalUser }}-{{ $consumerGroup }}
Edited by Antoine R. Dumontchanged this line in version 4 of the diff
.
- [ ] staging: loader-metadata [0/6] - [ ] swh-charts: Rename consumer group loader_metadata.journal_client - [ ] Stop journal clients - [ ] Export the offsets of the current consumer group - [ ] Import them into the new name - [ ] Then restart the clients with the new name - [ ] Finally clean up the old consumer group
- Resolved by Vincent Sellier
- Resolved by Antoine R. Dumont
Please register or sign in to reply