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

Deadlock when starting Zeebe with only one CPU thread #8992

Closed
npepinpe opened this issue Mar 25, 2022 · 0 comments · Fixed by #8993
Closed

Deadlock when starting Zeebe with only one CPU thread #8992

npepinpe opened this issue Mar 25, 2022 · 0 comments · Fixed by #8993
Assignees
@romansmirnov
Labels
kind/bug Categorizes an issue or PR as a bug severity/high Marks a bug as having a noticeable impact on the user with no known workaround version:8.1.0-alpha1 Marks an issue as being completely or in parts released in 8.1.0-alpha1 version:8.1.0 Marks an issue as being completely or in parts released in 8.1.0

Comments

@npepinpe
Copy link
Member

Describe the bug

The broker will not start when starting with the embedded gateway and only one CPU thread. It will start with more, or without the embedded gateway.

To Reproduce

docker run --rm -p 26500:26500 -e ZEEBE_BROKER_THREADS_CPUTHREADCOUNT=1 -e ZEEBE_BROKER_NETWORK_HOST=0.0.0.0 camunda/zeebe:SNAPSHOT

Expected behavior

The broker can start with the embedded gateway and only one CPU thread count.

Environment:

  • OS: Linux
  • Zeebe Version: 1.4.0-SNAPSHOT
  • Configuration: ZEEBE_BROKER_THREADS_CPUTHREADCOUNT=1
@npepinpe npepinpe added the kind/bug Categorizes an issue or PR as a bug label Mar 25, 2022
@npepinpe npepinpe added the severity/high Marks a bug as having a noticeable impact on the user with no known workaround label Mar 25, 2022
@romansmirnov romansmirnov mentioned this issue Mar 25, 2022
Merged
10 tasks
zeebe-bors-camunda bot added a commit that referenced this issue Mar 28, 2022
@zeebe-bors-camunda @romansmirnov
merge: #8993
51df528 
8993: fix: don't wait for actor being submitted r=oleschoenburg a=romansmirnov

## Description

* Ensures that the activate jobs handler actor is submitted to the actor scheduler without blocking the actor thread
* This requires the usage of `CompletableFuture` to get notified when the handler has been scheduled successfully
* That way, the implementation works in case of an embedded and standalone gateway
* Adjust test cases to avoid potential race conditions

<!-- Please explain the changes you made here. -->

## Related issues

<!-- Which issues are closed by this PR or are related -->

closes #8992



Co-authored-by: Roman <roman.smirnov@camunda.com>
@deepthidevaki deepthidevaki added the version:8.1.0-alpha1 Marks an issue as being completely or in parts released in 8.1.0-alpha1 label May 3, 2022
@Zelldon Zelldon added the version:8.1.0 Marks an issue as being completely or in parts released in 8.1.0 label Oct 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@romansmirnov romansmirnov

Labels
kind/bug Categorizes an issue or PR as a bug severity/high Marks a bug as having a noticeable impact on the user with no known workaround version:8.1.0-alpha1 Marks an issue as being completely or in parts released in 8.1.0-alpha1 version:8.1.0 Marks an issue as being completely or in parts released in 8.1.0
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: don't wait for actor being submitted camunda/camunda
4 participants
@npepinpe @deepthidevaki @romansmirnov @Zelldon