blocking call to a view blocks the first action execution about kalix-jvm-sdk HOT 5 OPEN

Related existing issue: #1077

from kalix-jvm-sdk.

Also related: akka/akka-http#4150 (but I thought we decided to accept the cost of an additional .async for all the Kalix JVM SDK component streams instead of running them in-line)

from kalix-jvm-sdk.

No, sorry, that was probably specifically for streaming in calls so doesn't help here.

Why is that view not replying within at most two-three seconds though?

from kalix-jvm-sdk.

Why is that view not replying within at most two-three seconds though?

It's worse than that. It seems that the CompletionStage is not scheduled until the timeout in the get() happens. We change it to other values and we see it back in the logs in the runtime. If we set a timeout to 7 seconds, we see:

15:29:39.826 DEBUG kalix.proxy.Serve$ - Received gRPC request [/com.example.action.ServiceMetaDataAction/GetServiceMetaData]
15:30:06.826 DEBUG kalix.proxy.Serve$ - Received gRPC request [/com.example.view.ServiceMetaDataMappingView/GetServiceMetaData]

After that, subsequent calls works immediately.

So I suspect that we are tweaking the thread pool inside akka-grpc (java api) and this is done lazily.

I have the impression that the timeout is triggering something that is providing a thread to complete the CompletionStage (so the call is effectively done at that moment), but then the CompletionStage will fail anyway because it already timeout.

To recap, if a timeout of 20 seconds:

• call hit the runtime after 20 seconds
• call fails with timeout on sdk side

from kalix-jvm-sdk.

And another one: https://discuss.kalix.io/t/how-to-call-and-get-value-from-view-in-controller/318

from kalix-jvm-sdk.