root@journal0:/opt/kafka/bin# ./kafka-topics.sh --bootstrap-server 10.168.130.70:9092 --list | xargs -n1 -i{} ./kafka-run-class.sh kafka.tools.GetOffsetShell  --broker-list 10.168.130.70:9092 --topic {} | grep -v consumer
swh.journal.objects.content:0:898
swh.journal.objects.directory:0:1172
swh.journal.objects.origin:0:26
swh.journal.objects.origin_visit:0:55
swh.journal.objects.origin_visit_status:0:2
swh.journal.objects.release:0:0
swh.journal.objects.revision:0:209
swh.journal.objects.snapshot:0:1

I let the worker create the topics so there is only one partition. It will need to be adapted for the staging environment

ardumont accepted this revision.Nov 24 2020, 9:56 AM

This revision is now accepted and ready to land.Nov 24 2020, 9:56 AM

Rename the zookeper cluster to match the kafka cluster name

Harbormaster completed remote builds in B17430: Diff 16231.Nov 24 2020, 11:45 AM

precision: the tests were only done on the internal plaintext listener without sasl authentication

ardumont accepted this revision.Nov 24 2020, 11:47 AM

Closed by commit rSPSITEbf96179df42d: Ensure java is installed before trying to manipulate the java keystore (authored by vsellier). · Explain WhyNov 24 2020, 12:07 PM

This revision was automatically updated to reflect the committed changes.

vsellier added a commit: rSPSITEbf96179df42d: Ensure java is installed before trying to manipulate the java keystore.

vsellier added a commit: rSPSITE9074d87bd6dd: Configure the kafka server for staging.