Dapr: Dapr sidecar will stop working when input binding message processing time is longer than 60 seconds

Created on 22 Oct 2020  路  3Comments  路  Source: dapr/dapr

Release Note

RELEASE NOTE: Removed 60 seconds timeout on app channel

P1 areruntime areruntiminvoke kinbug

Most helpful comment

@Li-Yanzhi this is now fixed.

All 3 comments

This is because the 60s timeout of app channel. I think it makes sense to allows to set custom timeout. We may need to allow internal gRPC channel timeout to be configurable as well.

@yaron any thoughts?

cc/ @msfussell @yolember

This is because the 60s timeout of app channel. I think it makes sense to allows to set custom timeout. We may need to allow internal gRPC channel timeout to be configurable as well.

@yaron any thoughts?

cc/ @msfussell @yolember

Actually this is a bug the way this behaves currently. The most immediate resolution is to remove the timeout. An app can take as long as it wants. In the future we can make this configurable, this intersects with custom retries which are post RC1.0. but for now, the timeout should be removed.

@Li-Yanzhi this is now fixed.

Was this page helpful?
0 / 5 - 0 ratings