A complete solution for open data platforms, enterprise data catalogs, data lakes and data management. Open source, mature, fully-featured and production ready.

DataHub

Hello Everyone,
I have a custom build process for GMS and Frontend images. I don't use release tags the same as Datahub official project. Because of that, my GMS is waiting forever for the system update job (I'm using the community system update job image, which has a different deployment tag). Besides, even setting 'BOOTSTRAP_SYSTEM_UPDATE_WAIT_FOR_SYSTEM_UPDATE' environment variable to 'false', the GMS application stills wait for the system update job. Could someone please tell me how to fix this problem without rebuilding the system update image on my side?

Hey there :wave: 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: :one: There's a lot of good information on our docs site: <http://www.datahubproject.io/docs|www.datahubproject.io/docs>, Have you searched there for a solution? Yes button :two: It's not uncommon that someone has run into your exact problem before in the community. Have you searched Slack for similar issues? Yes button

Logs:
&gt; 2023-05-08 14:50:53,581 [ThreadPoolTaskExecutor-1] INFO  c.l.m.b.k.DataHubUpgradeKafkaListener:84 - Latest system update version: v0.10.2-1
&gt; 2023-05-08 14:50:53,582 [ThreadPoolTaskExecutor-1] WARN  c.l.m.b.k.DataHubUpgradeKafkaListener:88 - System version is not up to date: null-1. Waiting for datahub-upgrade to complete...

Hello <@U03MF8MU5P0> and <@U042KCFV9GX>
Could you help me here?

Even building the GMS image with the '-PreleaseVersion=0.10.0' flag, there seems to be a lack of synchronization between the update image generated by you and the GMS that I build internally.
(<https://github.com/datahub-project/datahub/blob/master/gradle/versioning/versioning.gradle>).

GMS Logs:
&gt; 2023-05-15 14:17:16,115 [ThreadPoolTaskExecutor-1] INFO  c.l.m.b.k.DataHubUpgradeKafkaListener:84 - Latest system update version: v0.10.0-1
&gt; 2023-05-15 14:17:16,115 [ThreadPoolTaskExecutor-1] WARN  c.l.m.b.k.DataHubUpgradeKafkaListener:88 - System version is not up to date: null-1. Waiting for datahub-upgrade to complete...
&gt; 2023-05-15 14:17:16,720 [R2 Nio Event Loop-1-1] WARN  c.l.r.t.h.c.c.ChannelPoolLifecycle:139 - Failed to create channel, remote=localhost/127.0.0.1:8080
&gt; io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: localhost/127.0.0.1:8080
&gt; Caused by: java.net.ConnectException: Connection refused
I was hoping that the '-PreleaseVersion=' parameter could solve the problem of the 'null' version appearing in the GMS. I made this assumption from reading this code: <https://github.com/datahub-project/datahub/blob/master/metadata-service/factories/src/main/java/com/linkedin/metadata/boot/kafka/DataHubUpgradeKafkaListener.java#L77|https://github.com/datahub-project/datahub/blob/master/metadata-service/factories/[…]m/linkedin/metadata/boot/kafka/DataHubUpgradeKafkaListener.java>

The version is from the git version gradle plugin. It adds a file `git.properties` with the version into the jar at build time.

Thank you <@U03MF8MU5P0>!
I changed the gitProperties to reflect the version tag I wanted.