https://www.gooddata.com/ logo
Join Slack
Powered by
Hey guys, the computeValidObjects api keeps on fa...
# gooddata-cn
k
Hey guys, the computeValidObjects api keeps on failing, the only error message I can see in the log is msg: "Failed to retrieve objects valid for AFM" from logger: "com.gooddata.tiger.grpc.client.aqe.AqeClient" . Is there any way to find the root cause? We are using GoodData.cn 1.51 version on gcp.
Detail log "exc": "errorType=com.gooddata.tiger.grpc.error.GrpcPropagatedServerException, message=UNKNOWN: ,<no detail>\n\tat com.gooddata.tiger.grpc.error.ErrorPropagationKt.convertFromUnknownException(ErrorPropagation.kt:108)\n\tSuppressed: reactor.core.publisher.FluxOnAssembly$OnAssemblyException: \nError has been observed at the following site(s):\n\t|_ checkpoint ⇢ Handler com.gooddata.tiger.afm.controller.ValidObjectsController#processAfmValidObjectsQuery(String, AfmValidObjectsQuery, Continuation) [DispatcherHandler]\nStack trace:\n\t\tat com.gooddata.tiger.grpc.error.ErrorPropagationKt.convertFromUnknownException(ErrorPropagation.kt:108)\n\t\tat com.gooddata.tiger.grpc.error.ErrorPropagationKt.convertToTransferableException(ErrorPropagation.kt:98)\n\t\tat com.gooddata.tiger.grpc.error.ErrorPropagationKt.clientCatching(ErrorPropagation.kt:72)\n\t\tat com.gooddata.tiger.grpc.error.ErrorPropagationKt$clientCatching$1.invokeSuspend(ErrorPropagation.kt)\n\t\tat kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)\n\t\tat kotlinx.coroutines.DispatchedTaskKt.resume(DispatchedTask.kt:175)\n\t\tat kotlinx.coroutines.DispatchedTaskKt.resumeUnconfined(DispatchedTask.kt:137)\n\t\tat kotlinx.coroutines.DispatchedTaskKt.dispatch(DispatchedTask.kt:108)\n\t\tat kotlinx.coroutines.CancellableContinuationImpl.dispatchResume(CancellableContinuationImpl.kt:308)\n\t\tat kotlinx.coroutines.CancellableContinuationImpl.resumeImpl(CancellableContinuationImpl.kt:318)\n\t\tat kotlinx.coroutines.CancellableContinuationImpl.resumeWith(CancellableContinuationImpl.kt:250)\n\t\tat com.github.marcoferrer.krotoplus.coroutines.client.SuspendingUnaryObserver.onError(SuspendingUnaryObserver.kt:34)\n\t\tat io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:478)\n\t\tat brave.grpc.TracingClientInterceptor$TracingClientCallListener.onClose(TracingClientInterceptor.java:202)\n\t\tat io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)\n\t\tat io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)\n\t\tat io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)\n\t\tat net.devh.boot.grpc.client.metric.MetricCollectingClientCallListener.onClose(MetricCollectingClientCallListener.java:65)\n\t\tat io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:617)\n\t\tat io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:70)\n\t\tat io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:803)\n\t\tat io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:782)\n\t\tat io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)\n\t\tat io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123)\n\t\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)\n\t\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)\n\t\tat java.base/java.lang.Thread.run(Unknown Source)\n", "logger": "com.gooddata.tiger.grpc.client.aqe.AqeClient", "thread": "grpc-default-executor-134", "msg": "Failed to retrieve objects valid for AFM", "userId": "", "spanId": "184e2814eba3d7eb", "traceId": "184e2814eba3d7eb" }
j
Very old version containing "aqe" service, which was completely replaced by another service. Because we can no longer fix anything in this service, I would like to ask you for to upgrade the deployment, ideally to the latest release.
k
I understand upgrade might solve the issue. We have hard deadlines for the customer deliverables , We are not in a position to upgrade in this quarter. How to know the underlying issue? More background on the issue: The Logical data model looks good in Gooddata-cn. It only works if we have one fact table with multiple dimension tables, but it does not work with multiple fact tables with multiple dimension tables. I expect this is a basic requirement that should work in 1.5.1 version.
j
The issue happens when UI collects so called validObjects. Analytical Designer (create visualization with drag&drop) collects it to filter out entities (facts/attributes) in the left panel based on the current context (what you already drag and dropped into the visualization)
Do you use community edition (single container deployment) or helm chart deployment?
k
helm chart deployment.
j
ok, then I need logs from containers with "aqe" in their names. Most likely some nasty error is happening there.
Open in Slack
PreviousNext
Powered by