Hi Guys! I run the datahub in Kubernetes. DataHub...
# troubleshoot
c
Hi Guys! I run the datahub in Kubernetes. DataHub CLI version: 0.8.43.5 I faced a problem when the datahub-frontend doesn’t show the changes I applied. I noticed that by checking the last ingestion date: the last one was five days ago despite the fact that it was set up at 12:00 AM every day. In addition, I tried to create a secret and I managed to but again, I can’t see it on the datahub-frontend - only in logs (trying to create the same secret once more I’m getting “This Secret already exists!” in the datahub-gms logs). Here is error I found in datahub-frontend logs:
Copy code
08:49:02 [application-akka.actor.default-dispatcher-15] WARN  o.p.o.profile.creator.TokenValidator - Preferred JWS algorithm: null not available. Using all metadata algorithms: [PS384, ES384, RS384, HS256, HS512, ES256, RS256, HS384, ES512, PS256, PS512, RS512]
08:49:02 [application-akka.actor.default-dispatcher-15] ERROR auth.sso.oidc.OidcCallbackLogic - Unable to renew the session. The session store may not support this feature
1
In datahub-gms log I’m constantly getting this:
Copy code
12:45:21.917 [I/O dispatcher 1] ERROR c.l.m.s.e.update.BulkListener:35 - Error feeding bulk request. No retries left
java.io.IOException: Unable to parse response body for Response{requestLine=POST /_bulk?timeout=1m HTTP/1.1, host=<http://elk-elasticsearch.data-elk.svc.cluster.local:9200>, response=HTTP/1.1 200 OK}
Could it be related?
b
hey Maksim! hmm this is an odd situation for sure. do you know what version of elasticsearch you're using?
c
Copy code
"version" : {
    "number" : "8.4.3",
b
ahh yes as I suspected - unfortunately we don't support elasticsearch version 8+, so I'd suggest downgrading that to a 7.x version and hopefully you'll be good to go!
c
Thanks Chris!
c
unfortunately we don't support elasticsearch version 8+
Is that findable in documentation somewhere, @bulky-soccer-26729?