Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] poll_workflow_task_queue retried X times needs to be an ERROR log, not WARN #704

Open
danthegoodman1 opened this issue Mar 13, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@danthegoodman1
Copy link

2024-03-13T14:27:20.049568Z  WARN temporal_client::retry: gRPC call poll_workflow_task_queue retried 16 times error=Status { code: Cancelled,
message: "Timeout expired", source: Some(tonic::transport::Error(Transport, TimeoutExpired(()))) }

This log absolutely needs to be an ERROR. Maybe after some threshold, but I've seen it get to >100 when the client was having connectivity issues to the client.

I understand metrics might solve this, but client metrics should not be required to run temporal clients reliably.

If a client is unable to get work, after a very long time of trying and failing, that should be considered an error.

@danthegoodman1 danthegoodman1 added the enhancement New feature or request label Mar 13, 2024
@jhecking
Copy link

jhecking commented May 15, 2024

We have recently observed a case where a client had retried nearly 100,000 times and still no error was reported:

temporal_client::retry: gRPC call poll_activity_task_queue retried 94372 times

Even querying the worker's state didn't indicate any problem, so the service's heartbeat (which checks worker state) also didn't fail:

{"runState":"RUNNING","numHeartbeatingActivities":0,"workflowPollerState":"SHUTDOWN","activityPollerState":"POLLING","hasOutstandingWorkflowPoll":false,"hasOutstandingActivityPoll":true,"numCachedWorkflows":0,"numInFlightWorkflowActivations":0,"numInFlightActivities":0}

(Note: This service only handles activities, so workflowPollerState SHUTDOWN was expected.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants