Hello Team! We encountered an error in the GoodData sql-executor pod. Below are the details: GD Version: 2.5.1

{
  "insertId": "16ye3ud9146vihqa",
  "jsonPayload": {
    "orgId": "onefactoreal",
    "logger": "com.gooddata.tiger.sqlexecutor.db.extensions.SqlLoggingExtension",
    "ts": "2024-05-29 00:49:24.877",
    "action": "executeSql",
    "traceId": "e37baf41d10daf7c",
    "spanId": "5190ddab2a0a3221",
    "exc": "errorType=com.gooddata.tiger.grpc.client.rawcache.RawCacheStreamHandlerForStore.ServerStreamingClosedException, message=Streaming closed on server side\n\tat com.gooddata.tiger.grpc.client.rawcache.RawCacheStreamHandlerForStore.throwWhenServerInactive(RawCacheStreamHandlerForStore.kt:97)\n\tat com.gooddata.tiger.grpc.client.rawcache.RawCacheStreamHandlerForStore$onRow$2.invokeSuspend(RawCacheStreamHandlerForStore.kt:170)\n\tat com.gooddata.tiger.grpc.client.rawcache.RawCacheStreamHandlerForStore$onRow$2.invoke(RawCacheStreamHandlerForStore.kt)\n\tat com.gooddata.tiger.grpc.client.rawcache.RawCacheStreamHandlerForStore$onRow$2.invoke(RawCacheStreamHandlerForStore.kt)\n\tat com.gooddata.tiger.grpc.error.ErrorPropagationKt.clientCatching(ErrorPropagation.kt:101)\n\tat com.gooddata.tiger.grpc.client.rawcache.RawCacheStreamHandlerForStore.onRow(RawCacheStreamHandlerForStore.kt:146)\n\tat com.gooddata.tiger.sqlexecutor.messaging.StreamingSqlExecutionResultHandler.singleRowAction(ExecuteSqlMessageHandler.kt:69)\n\tat com.gooddata.tiger.sqlexecutor.messaging.StreamingSqlExecutionResultHandler.onResult(ExecuteSqlMessageHandler.kt:60)\n\tat com.gooddata.tiger.sqlexecutor.db.SQLQueryExecutor$executeFinalSqlAction$3.invokeSuspend(SQLQueryExecutor.kt:257)\n\tat com.gooddata.tiger.sqlexecutor.db.SQLQueryExecutor$executeFinalSqlAction$3.invoke(SQLQueryExecutor.kt)\n\tat com.gooddata.tiger.sqlexecutor.db.SQLQueryExecutor$executeFinalSqlAction$3.invoke(SQLQueryExecutor.kt)\n\tat com.gooddata.tiger.sqlexecutor.db.extensions.SqlLoggingExtension$logExecutionWithFetch$2.invokeSuspend(SqlLoggingExtension.kt:27)\n\tat com.gooddata.tiger.sqlexecutor.db.extensions.SqlLoggingExtension$logExecutionWithFetch$2.invoke(SqlLoggingExtension.kt)\n\tat com.gooddata.tiger.sqlexecutor.db.extensions.SqlLoggingExtension$logExecutionWithFetch$2.invoke(SqlLoggingExtension.kt)\n\tat com.gooddata.tiger.sqlexecutor.db.extensions.SqlLoggingExtension.logDataFetching(SqlLoggingExtension.kt:92)\n\tat com.gooddata.tiger.sqlexecutor.db.extensions.SqlLoggingExtension.logExecutionWithFetch(SqlLoggingExtension.kt:26)\n\tat com.gooddata.tiger.sqlexecutor.db.SQLQueryExecutor.executeFinalSqlAction(SQLQueryExecutor.kt:250)\n\tat com.gooddata.tiger.sqlexecutor.db.SQLQueryExecutor.access$executeFinalSqlAction(SQLQueryExecutor.kt:63)\n\tat com.gooddata.tiger.sqlexecutor.db.SQLQueryExecutor$executeSqlActions$2.invokeSuspend(SQLQueryExecutor.kt:241)\n\tat com.gooddata.tiger.sqlexecutor.db.SQLQueryExecutor$executeSqlActions$2.invoke(SQLQueryExecutor.kt)\n\tat com.gooddata.tiger.sqlexecutor.db.SQLQueryExecutor$executeSqlActions$2.invoke(SQLQueryExecutor.kt)\n\tat com.gooddata.tiger.sqlexecutor.db.bigquery.BigQueryConnectionService.executeAction(BigQueryConnectionService.kt:96)\n\tat com.gooddata.tiger.sqlexecutor.db.bigquery.BigQueryConnectionService.useConnection$suspendImpl(BigQueryConnectionService.kt:60)\n\tat com.gooddata.tiger.sqlexecutor.db.bigquery.BigQueryConnectionService.useConnection(BigQueryConnectionService.kt)\n\tat com.gooddata.tiger.sqlexecutor.db.SQLQueryExecutor.executeSqlActions(SQLQueryExecutor.kt:224)\n\tat com.gooddata.tiger.sqlexecutor.db.SQLQueryExecutor.access$executeSqlActions(SQLQueryExecutor.kt:63)\n\tat com.gooddata.tiger.sqlexecutor.db.SQLQueryExecutor$executeCancellableSqlRequest$2$executeSqlActionsJob$1.invokeSuspend(SQLQueryExecutor.kt:185)\n\tat kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)\n\tat kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:56)\n\tat kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:571)\n\tat kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:738)\n\tat kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678)\n\tat kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665)\n",
    "thread": "DefaultDispatcher-worker-10",
    "msg": "Unexpected exception type",
    "level": "ERROR",
    "userId": "testuser"
  },
  "resource": {
    "type": "k8s_container",
    "labels": {
      "location": "us-west1",
      "cluster_name": "fact-prod-gdcn",
      "project_id": "factoreal-gcp-prod",
      "pod_name": "gooddata-cn-sql-executor-8698fd88-vxwrl",
      "container_name": "sql-executor",
      "namespace_name": "gooddata-cn"
    }
  },
  "timestamp": "2024-05-29T00:49:24.877875092Z",
  "severity": "ERROR",
  "labels": {
    "k8s-pod/pod-template-hash": "8698fd88",
    "compute.googleapis.com/resource_name": "gke-fact-prod-gdcn-fact-prod-gdc-pool-563abf9e-o15i",
    "k8s-pod/app_kubernetes_io/instance": "gooddata-cn",
    "k8s-pod/app_kubernetes_io/name": "gooddata-cn",
    "k8s-pod/app_kubernetes_io/component": "sqlExecutor"
  },
  "logName": "projects/factoreal-gcp-prod/logs/stdout",
  "receiveTimestamp": "2024-05-29T00:49:28.153851295Z",
  "errorGroups": [
    {
      "id": "CKCHjYe-8qflcg"
    }
  ]
}

Hi @SATHISH P what is the context of this error? Did it happen during calculating results on dashboard/insight? Did you received the error one time or is it happening regularly?

Hi @Jan Kos, Got this error while calculating results for the dashboards today. I haven't received it again.

Hi Sathish, during result calculations, analytics engine as a part of the process registers raw results into result cache (Redis).. only known situation to us is that raw result TTL expired before the whole execution finished and the exception above was thrown. This should be rare race condition and subsequent calculation will be ok.