I can see, from the logs, many errors like this one:

10:28:53.812 [pool-9-thread-1] INFO  c.l.m.filter.RestliLoggingFilter - POST /usageStats?action=queryRange - queryRange - 200 - 356ms
10:29:17.224 [qtp544724190-11718] INFO  c.l.m.r.entity.EntityResource - LIST URNS for dataHubPolicy with start 0 and count 30
10:29:27.224 [pool-17-thread-1] ERROR c.d.m.a.AuthorizationManager - Failed to retrieve policy urns! Skipping updating policy cache until next refresh. start: 0, count: 30
com.linkedin.r2.RemoteInvocationException: com.linkedin.r2.RemoteInvocationException: Failed to get response from server for URI <http://localhost:8080/entities>
	at com.linkedin.restli.internal.client.ExceptionUtil.wrapThrowable(ExceptionUtil.java:135)
	at com.linkedin.restli.internal.client.ResponseFutureImpl.getResponseImpl(ResponseFutureImpl.java:130)
	at com.linkedin.restli.internal.client.ResponseFutureImpl.getResponse(ResponseFutureImpl.java:94)
	at com.linkedin.common.client.BaseClient.sendClientRequest(BaseClient.java:28)
	at com.linkedin.entity.client.RestliEntityClient.listUrns(RestliEntityClient.java:390)
	at com.datahub.metadata.authorization.AuthorizationManager$PolicyRefreshRunnable.run(AuthorizationManager.java:186)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: com.linkedin.r2.RemoteInvocationException: Failed to get response from server for URI <http://localhost:8080/entities>
	at com.linkedin.r2.transport.http.common.HttpBridge$1.onResponse(HttpBridge.java:67)
	at com.linkedin.r2.transport.http.client.rest.ExecutionCallback.lambda$onResponse$0(ExecutionCallback.java:64)
	... 3 common frames omitted
Caused by: java.util.concurrent.TimeoutException: Exceeded request timeout of 10000ms
	at com.linkedin.r2.transport.http.client.TimeoutTransportCallback$1.run(TimeoutTransportCallback.java:69)
	at com.linkedin.r2.util.Timeout.lambda$new$0(Timeout.java:77)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	... 3 common frames omitted
10:31:17.225 [qtp544724190-7234] INFO  c.l.m.r.enti

Do this affected the UI or any other code functionality of Datahub?

Hi @kind-psychiatrist-76973 which container are you seeing these logs in? And how are you running that container, via Gradle or Docker?

It’s kubernetes in production, the pod is datahub-gms. I am using the official HELM chart (

"datahub/datahub"

), version

"0.2.34"

Yeah this should be okay. Once the pod is fully up, you don’t see these error msgs any more right?

no, unfortunately these error happens very ofter

Ah the list urns function is taking too long. So we fixed this issue in a latest PR, so it will be released in the next release. It was using mysql to fetch all policies before, and we saw latency issues with that approach, so we switched it to use search instead, and saw a much more reasonable latency.

Thank you that’s really useful, we’ll test the upcoming release to see if these errors will be gone.