hey all, qq - when we see logs like this (top newer than bottom), does that mean the GMS container is waiting for a message on the

DataHubUpgradeHistory_v1

kafka topic before it continues initializing? this is for 0.10.0 to 0.10.1

Hey there 👋 I'm The DataHub Community Support bot. I'm here to help make sure the community can best support you with your request. Let's double check a few things first: ✅ There's a lot of good information on our docs site: www.datahubproject.io/docs, Have you searched there for a solution? ✅ It's not uncommon that someone has run into your exact problem before in the community. Have you searched Slack for similar issues? Did you find a solution to your issue? ❌ Sorry you weren't able to find a solution. I'm sending you some tips on info you can provide to help the community troubleshoot. Whenever you feel your issue is solved, please react ✅ to your original message to let us know!

I'm not a maintainer but have you run the datahub-upgrade container and its "SystemUpdate" command? (Using the v0.10.1 tag of the datahub-upgrade container)

no, which is definitely what was missing, this is more of a "am i reading this right, and if so should a log maybe be added stating what it is waiting for"

There was when I had forgotten it, but I don't see it in your log snippet.

it wasnt, i just couldnt SS more logs easily. had a teammate get confused by why it wasnt coming online and i figured a log here might help understand since the thing that happened after this was termination due to health check failures, so the logs were confusing to look at

This is the log line I'm referring to, https://github.com/datahub-project/datahub/blob/7914e15ed4e7b315c51f2b92195e2b4ae7[…]m/linkedin/metadata/boot/kafka/DataHubUpgradeKafkaListener.java

yeah idk, thats def not logged from what im seeing

Ok. Then no clue, just wanted to mention this since I had run into it. Good luck!

yeah no i appreciate you mentioning that youve seen something like this before!

Ya, this is likely a kafka issue- do you have logs from that container?

we just ran the upgrade jobs and this cleared, there's no outstanding issue. it was just confusing to us to see the logs about joining consumer groups and then silence uuntil the health check failed. we werent sure what the container was waiting on/doing while it wasnt outputting anything and the http server hadnt started

That’s odd- might have been a bug with the container, but would make a good feature request to have better logging on the update container just in case