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

DataHub

```Type     Reason       Age    From               Message
  ----     ------       ----   ----               -------
  Normal   Scheduled    9m48s  default-scheduler  Successfully assigned default/datahub-datahub-mce-consumer-5775f5c487-8z9dr to minikube
  Warning  FailedMount  9m48s  kubelet            MountVolume.SetUp failed for volume "datahub-datahub-mce-consumer-token-8s9sh" : failed to sync secret cache: timed out waiting for the condition
  Normal   Pulling      9m47s  kubelet            Pulling image "linkedin/datahub-mce-consumer:v0.8.6"
  Normal   Pulled       8m29s  kubelet            Successfully pulled image "linkedin/datahub-mce-consumer:v0.8.6" in 1m18.086509993s
  Normal   Created      8m29s  kubelet            Created container datahub-mce-consumer
  Normal   Started      8m28s  kubelet            Started container datahub-mce-consumer```


Hey <@U026P1R6BS8> - mce consumer should not be dependent on the graph service- it should not be waiting on either neo4j or elastic to start

Mae consumer is running and has status of ready

```NAME                                               READY   STATUS      RESTARTS   AGE
datahub-datahub-frontend-77797bc7bf-twjbm          1/1     Running     0          2m37s
datahub-datahub-gms-79bb9bf665-jr8mg               1/1     Running     0          2m37s
datahub-datahub-mae-consumer-85d5c4b5dc-rfnb8      1/1     Running     0          2m37s
datahub-datahub-mce-consumer-5775f5c487-8z9dr      0/1     Running     0          2m37s
datahub-datahub-upgrade-job-df9m6                  0/1     Error       0          2m37s
datahub-datahub-upgrade-job-h94f2                  0/1     Completed   0          53s
datahub-elasticsearch-setup-job-zndvb              0/1     Completed   0          3m15s
datahub-kafka-setup-job-cs86x                      0/1     Completed   0          3m10s
datahub-mysql-setup-job-xv4xq                      0/1     Completed   0          2m42s
elasticsearch-master-0                             1/1     Running     0          5m22s
elasticsearch-master-1                             1/1     Running     0          5m22s
elasticsearch-master-2                             1/1     Running     0          5m21s
prerequisites-cp-schema-registry-cf79bfccf-2tnzf   2/2     Running     1          5m22s
prerequisites-kafka-0                              1/1     Running     1          5m22s
prerequisites-mysql-0                              1/1     Running     0          5m22s
prerequisites-neo4j-community-0                    1/1     Running     0          5m22s
prerequisites-zookeeper-0                          1/1     Running     0          5m22s```


Have you replicated the mce consumer issue multiple times?

I suspect that is unrelated to neo4j vs elastic

Is there something wrong with our system ?

I’d also be interested if this persists if you restart docker

`kubectl logs datahub-datahub-mce-consumer-5775f5c487-8z9dr`  should give you more information about what is going on in that pod