Skip to content

Deploy swh-search v0.13.0

No migration needed, but v0.12.0 (specifically [1]) requires the journal client to be reset on the origin_intrinsic_metadata topic.

Plan (staging):

Plan (production):

  • search1: Stop puppet agent

  • search1: Stop swh-search-journal-client@*.service client

  • search1: Upgrade python3-swh.search dependency

  • search1: Restart gunicorn-swh-search service

  • search1: Restart swh-search-journal-client@objects.service (it does not consume origin_intrinsic topic)

  • moma, webapp1: Upgrade python3-swh.search dependency

  • moma, webapp1: restart gunicorn-swh-search

  • kafka1: Reset topic origin_intrinsic_metadata [2]

  • search1: Restart swh-search-journal-client@indexed.service service

  • Monitor consumption [5]

  • [1] edb812ab4d831dfddda03d5f871d9a2f5d58b5c1

  • [2] kafka reset offset command to trigger from (storage1.staging or kafka1.prod):

SERVER=$(hostname -f):9092
GROUP_ID=swh.search.journal_client.indexed-v0.11
echo /opt/kafka/bin/kafka-consumer-groups.sh --bootstrap-server $SERVER \
  --reset-offsets --all-topics --to-earliest \
  --group $GROUP_ID \
  --execute
root@kafka1:~# /opt/kafka/bin/kafka-consumer-groups.sh --bootstrap-server $SERVER --describe --all-topics --group $GROUP_ID

Migrated from T3944 (view on Phabricator)

Edited by Antoine R. Dumont