2 - this is my deployment did i miss some compone...
# all-things-deployment
m
2 - this is my deployment did i miss some component
Copy code
NAME                                                READY   STATUS      RESTARTS   AGE
datahub-datahub-frontend-866cb6c97b-tss6f           1/1     Running     0          110s
datahub-datahub-gms-84d8f8599b-9l7pn                1/1     Running     0          110s
datahub-datahub-upgrade-job-6ktd7                   1/1     Running     0          18s
datahub-elasticsearch-setup-job-gxv6d               0/1     Completed   0          108s
datahub-kafka-setup-job-97jfc                       0/1     Completed   0          106s
datahub-mysql-setup-job-w6jdt                       0/1     Completed   0          110s
elasticsearch-master-0                              1/1     Running     0          21m
elasticsearch-master-1                              1/1     Running     0          21m
elasticsearch-master-2                              1/1     Running     0          21m
flux-68bdf85d98-gmblt                               1/1     Running     0          15h
prerequisites-cp-schema-registry-598fd5876b-lrjcq   2/2     Running     1          21m
prerequisites-kafka-0                               1/1     Running     1          21m
prerequisites-neo4j-community-0                     1/1     Running     0          21m
prerequisites-zookeeper-0                           1/1     Running     0          21m
e
Can you set global.datahub_standalone_consumers_enabled to true? https://github.com/linkedin/datahub/blob/master/datahub-kubernetes/datahub/values.yaml#L63
m
yes sure , i'll do
@early-lamp-41924 what did this parametres please , can you send me a link or a doc to read
Done ,
Copy code
datahub-datahub-frontend-85fbbf7d7-5lxnj            1/1     Running     0          3m31s
datahub-datahub-gms-75b5d8986c-w9c6l                1/1     Running     0          3m31s
datahub-datahub-mae-consumer-b47c85d7f-22ngc        1/1     Running     0          12m
datahub-datahub-mce-consumer-7ddc6d8d45-9fqzf       1/1     Running     0          12m
datahub-datahub-upgrade-job-vrwdc                   1/1     Running     0          3m31s
datahub-elasticsearch-setup-job-s5hjb               0/1     Completed   0          3m31s
datahub-kafka-setup-job-ppvsq                       0/1     Completed   0          3m31s
datahub-mysql-setup-job-c9gtk                       0/1     Completed   0          3m28s
elasticsearch-master-0                              1/1     Running     0          3h8m
elasticsearch-master-1                              1/1     Running     0          3h8m
elasticsearch-master-2                              1/1     Running     0          3h8m
flux-68bdf85d98-gmblt                               1/1     Running     0          18h
prerequisites-cp-schema-registry-598fd5876b-lrjcq   2/2     Running     1          3h8m
prerequisites-kafka-0                               1/1     Running     1          3h8m
prerequisites-neo4j-community-0                     1/1     Running     0          3h8m
prerequisites-zookeeper-0                           1/1     Running     0          3h8m
l
@early-lamp-41924 ^
e
We recently made a change that combines gms/mae/mce-consumer into one node. However, this change came after v0.8.1, so the necessary code changes to support this is not in that version. We are releasing a new version v0.8.2 today. With that you don’t have to set this parameter any mroe!
m
ah ok , btw , i'm using the v0.8.0
because of this bug
@early-lamp-41924
i got the same error with v0.8.1
l
@green-football-43791 @big-carpet-38439 ^ have you seen this bug after the upgrade?
e
Hmn upgrade job should be a no-op
m
@loud-island-88694 i can reproduce if you want
e
Since you didnt have anything running pre v0.8
m
i confirm that when downgrading to v0.8.0 the bug was fixed
e
What is the exact bug? You couldn't access the user page?
m
From datahub-upgrade-job
Copy code
2021-06-17T14:31:48.873793757Z ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console...
e
Upgrade job having the same msg as described in the issue is working as expected
@miniature-airport-96424 would you be open to hop on a quick call to resolve this issue?
What actually happens when you deploy v0.8.1 ignoring datahub-upgrade-job? That is working as expected. Is ingest failing or any frontend components failing?
m
@early-lamp-41924, except datahub-upgrade-job ,all works fine
e
ah yes
so that is working as expected.
It is there for folks who installed datahub before the latest breaking changes and migrate the storage layer to the new format. If you installed v0.8.1 directly, this job shouldn’t do anything. We will improve logging to make this more clear