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.

Sign up for GitHub

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

Jump to bottom

High CPU consumption when the connection is lost. #363

Closed
XPhilipp opened this issue Nov 22, 2021 · 1 comment · Fixed by #364
Closed

High CPU consumption when the connection is lost. #363

XPhilipp opened this issue Nov 22, 2021 · 1 comment · Fixed by #364
Assignees
@ChrisKujawa
Labels
bug Something isn't working

Comments

@XPhilipp
Copy link
Contributor

XPhilipp commented Nov 22, 2021 •
edited
Loading

Describe the bug
High CPU consumption when the connection is lost, or Zeebe is restarting.

To Reproduce
Steps to reproduce the behavior:

  1. Run zeebe-client-csharp
  2. Stop Zeebe server
  3. See error

Expected behavior
Await Pooling Interval.
Simple fix add in file JobWorker.cs after line 163:
await Task.Delay(pollInterval, cancellationToken);

Enviroment (please complete the following information):

  • OS: [e.g. iOS]
  • Version [e.g. 22]

Additional context
see pool request #364
@XPhilipp XPhilipp added the bug Something isn't working label Nov 22, 2021
@XPhilipp XPhilipp mentioned this issue Nov 22, 2021
Merged
@XPhilipp
Copy link
Contributor Author

Maybe a better way to have a dedicated "Restart Interval"?

@XPhilipp XPhilipp mentioned this issue Nov 24, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ChrisKujawa ChrisKujawa

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
2 participants
@ChrisKujawa @XPhilipp