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

Plan (staging):

• Stop puppet agent
• Stop swh-search-journal-client@objects.service client
• Upgrade search server with python3-swh.search dependency (server: search0.staging)
• Restart gunicorn-swh-search service
• Restart swh-search-journal-client@objects.service (it does not consume origin_intrinsic topic)
• webapp.staging: Upgrade python3-swh.search dependency
• webapp.staging: restart gunicorn-swh-search
• Reset topic origin_intrinsic_metadata (storage1.staging) [2]
• Restart swh-search-journal-client@indexed.service service (search0.staging)
• Monitor consumption [3]

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

[3] https://grafana.softwareheritage.org/goto/fKzJC4f7k?orgId=1

[4] https://grafana.softwareheritage.org/goto/fKzJC4f7k?orgId=1

[5] https://grafana.softwareheritage.org/goto/qwXGmIf7z?orgId=1

[6] To check the current offset is actually moving (it does)

root@kafka1:~# /opt/kafka/bin/kafka-consumer-groups.sh --bootstrap-server $SERVER --describe --all-topics --group $GROUP_ID