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

DataHub

Hey is there any chance to manually trigger this job? <https://github.com/acryldata/datahub-helm/blob/335c5812002ca8f3406725d97be47360717152cb/charts/datahub/templates/datahub-upgrade/datahub-system-update-job.yml|https://github.com/acryldata/datahub-helm/blob/335c5812002ca8f3406725d97be47360717[…]datahub/templates/datahub-upgrade/datahub-system-update-job.yml>

I’m looking to revive my GMS pod, and I’ve found that updating the Helm chart to the latest version gets it working properly. However, after 30 days, the issue resurfaces. I’m wondering if there’s a solution to this problem. For more information, please refer to the <https://datahubspace.slack.com/archives/CV2UVAPPG/p1680431357810179|link provided.>

I tried to update my Open search to the newest version
run restore indicies cronjob with this
```kubectl create job --from=cronjob/datahub-datahub-restore-indices-job-template datahub-restore-indices-adhoc```
But still Im getting this kind of the errors
```│     ... 18 common frames omitted                                                                                                                                                                                                                                             ││ 2023-05-18 08:23:34,125 [I/O dispatcher 1] ERROR c.l.m.s.e.update.BulkListener:56 - Error feeding bulk request. No retries left. Request: Failed to perform bulk request: index [graph_service_v1], optype: [UPDATE], type [_doc], id [9lX/iGM409cNTAlP0GMIyg==];Failed to p │```
<@U042KCFV9GX>

I found solution in this thread <https://datahubspace.slack.com/archives/CV2UVAPPG/p1682056207818099?thread_ts=1680528734.075169&amp;cid=CV2UVAPPG>

Steps to repair:
• update helm to `0.2.164`
• Enter to kafka pod and check retention 
```/opt/bitnami/kafka/bin/kafka-configs.sh --entity-type topics --entity-name DataHubUpgradeHistory_v1 --bootstrap-server localhost:9092 --describe --all | grep "<http://retention.ms|retention.ms>"```
• Alter it with
```/opt/bitnami/kafka/bin/kafka-configs.sh --entity-type topics --entity-name DataHubUpgradeHistory_v1 --bootstrap-server localhost:9092 --alter --add-config <http://retention.ms|retention.ms>=-1```
• Sanity check 
```/opt/bitnami/kafka/bin/kafka-configs.sh --entity-type topics --entity-name DataHubUpgradeHistory_v1 --bootstrap-server localhost:9092 --describe --all | grep "<http://retention.ms|retention.ms>"```

<https://github.com/datahub-project/datahub/blob/master/docker/kafka-setup/kafka-setup.sh#L155> - When DataHub will be released with this code people don’t gonna need to manually alter retention inside kafka pod