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

[Question] Several "Unable to poll" errors multiple times per day #291

Open
poblouin opened this issue Mar 19, 2024 · 0 comments
Open

[Question] Several "Unable to poll" errors multiple times per day #291

poblouin opened this issue Mar 19, 2024 · 0 comments

Comments

@poblouin
Copy link

poblouin commented Mar 19, 2024

Hey folks,

We've been using this ruby for quite a while, 1 year I would say and since then, we've been seeing a lot of "Unable to poll" errors. For example, last week, there were 700 of those for one of our service. This affects all our different using this sdk.

Unable to poll Workflow task queue

#<GRPC::Unavailable: 14:Socket closed. debug_error_string:{UNKNOWN:Error received from peer  {grpc_message:"Socket closed", grpc_status:14, created_time:"2024-03-19T14:52:38.963074635+00:00"}}>

And this

Unable to poll activity task queue

#<GRPC::Unavailable: 14:Socket closed. debug_error_string:{UNKNOWN:Error received from peer  {created_time:"2024-03-19T14:52:38.963058558+00:00", grpc_status:14, grpc_message:"Socket closed"}}>

Would someone have an idea of what might be causing those errors? Are they "normal" or expected from time to time within Temporal? We don't have a fancy configuration or anything we mostly use the default config and we use 20 as the thread pool size for both activity and workflow. I can share more relevant details if needed.

Note, this error doesn't cause any of our activities or workflows to fail, it just happens once every now and then and recovers.

temporal-ruby + grpc version

GIT
  remote: https://github.com/coinbase/temporal-ruby
  revision: 3e0dae708ec0e3eab8c44b57b64f5cd1881848e6
  
grpc (1.59.2)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant