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

Leader recovery fails because because the logstream does not contain events from snapshot #9645

Closed
lenaschoenburg opened this issue Jun 29, 2022 · 1 comment
Assignees
Labels
kind/bug Categorizes an issue or PR as a bug support Marks an issue as related to a customer support request

Comments

@lenaschoenburg
Copy link
Member

Describe the bug

A transition to leader fails during recovery because the event with the snapshot position 1998448 was not found in the log stream.

Additionally, the error handling initiates a teardown of the stream processor which fails because closing the replay state machine causes an NPE.

To Reproduce
Unclear.

Expected behavior

As far as I understand, for leaders this is an unexpected exception that shouldn't happen.

Log/Stacktrace

Full Stacktrace

2022-06-19 14:55:10.617  INFO [zeebe-wrapper,,] 7 --- [      Thread-10] c.s.t.s.z.w.zeebe.ZeebeBrokerProcess     : java.lang.IllegalStateException: Expected to find event with the snapshot position 1998448 in log stream, but nothing was found. Failed to recover 'Broker-1-StreamProcessor-2'.
2022-06-19 14:55:10.617  INFO [zeebe-wrapper,,] 7 --- [      Thread-10] c.s.t.s.z.w.zeebe.ZeebeBrokerProcess     : 	at io.camunda.zeebe.engine.processing.streamprocessor.StreamProcessor.recoverFromSnapshot(StreamProcessor.java:287) ~[zeebe-workflow-engine-1.3.8.jar:1.3.8]
2022-06-19 14:55:10.617  INFO [zeebe-wrapper,,] 7 --- [      Thread-10] c.s.t.s.z.w.zeebe.ZeebeBrokerProcess     : 	at io.camunda.zeebe.engine.processing.streamprocessor.StreamProcessor.onActorStarted(StreamProcessor.java:124) ~[zeebe-workflow-engine-1.3.8.jar:1.3.8]
2022-06-19 14:55:10.617  INFO [zeebe-wrapper,,] 7 --- [      Thread-10] c.s.t.s.z.w.zeebe.ZeebeBrokerProcess     : 	at io.camunda.zeebe.util.sched.ActorJob.invoke(ActorJob.java:79) [zeebe-util-1.3.8.jar:1.3.8]
2022-06-19 14:55:10.617  INFO [zeebe-wrapper,,] 7 --- [      Thread-10] c.s.t.s.z.w.zeebe.ZeebeBrokerProcess     : 	at io.camunda.zeebe.util.sched.ActorJob.execute(ActorJob.java:44) [zeebe-util-1.3.8.jar:1.3.8]
2022-06-19 14:55:10.617  INFO [zeebe-wrapper,,] 7 --- [      Thread-10] c.s.t.s.z.w.zeebe.ZeebeBrokerProcess     : 	at io.camunda.zeebe.util.sched.ActorTask.execute(ActorTask.java:122) [zeebe-util-1.3.8.jar:1.3.8]
2022-06-19 14:55:10.617  INFO [zeebe-wrapper,,] 7 --- [      Thread-10] c.s.t.s.z.w.zeebe.ZeebeBrokerProcess     : 	at io.camunda.zeebe.util.sched.ActorThread.executeCurrentTask(ActorThread.java:97) [zeebe-util-1.3.8.jar:1.3.8]
2022-06-19 14:55:10.617  INFO [zeebe-wrapper,,] 7 --- [      Thread-10] c.s.t.s.z.w.zeebe.ZeebeBrokerProcess     : 	at io.camunda.zeebe.util.sched.ActorThread.doWork(ActorThread.java:80) [zeebe-util-1.3.8.jar:1.3.8]
2022-06-19 14:55:10.617  INFO [zeebe-wrapper,,] 7 --- [      Thread-10] c.s.t.s.z.w.zeebe.ZeebeBrokerProcess     : 	at io.camunda.zeebe.util.sched.ActorThread.run(ActorThread.java:189) [zeebe-util-1.3.8.jar:1.3.8]

Environment:

  • Zeebe Version: 1.3.8
@lenaschoenburg lenaschoenburg added kind/bug Categorizes an issue or PR as a bug team/distributed support Marks an issue as related to a customer support request labels Jun 29, 2022
@lenaschoenburg lenaschoenburg self-assigned this Jul 7, 2022
@lenaschoenburg
Copy link
Member Author

Closed as user error in response to an availability issue caused by #9820

@lenaschoenburg lenaschoenburg closed this as not planned Won't fix, can't repro, duplicate, stale Jul 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes an issue or PR as a bug support Marks an issue as related to a customer support request
Projects
None yet
Development

No branches or pull requests

2 participants