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

Add processor and event applier for checkpoint record #9720

Closed
Tracked by #9606
deepthidevaki opened this issue Jul 6, 2022 · 0 comments · Fixed by #9821
Closed
Tracked by #9606

Add processor and event applier for checkpoint record #9720

deepthidevaki opened this issue Jul 6, 2022 · 0 comments · Fixed by #9821
Assignees
@deepthidevaki
Labels
version:8.1.0-alpha4 version:8.1.0 Marks an issue as being completely or in parts released in 8.1.0

Comments

@deepthidevaki
Copy link
Contributor

deepthidevaki commented Jul 6, 2022 •
edited
Loading

Depends on #9613 #9719

  • Define db states for checkpoint info - checkpointId and checkpointPostition.
  • Add a processor that can process checkpoint:create command. Use the backup manager to trigger the backup. Taking the backup is asynchronous. So the processor can trigger and continue without waiting. Write follow up event checkpoint:created if the backup is triggered. If a checkpoint with this id or higher already exists then it doesn't trigger a new bakcup instead write follow up event checkpoint:ignored. This should also send the response back to the gateway.
  • Add a event replayer to replay checkpoint:created record. The replayer should update the checkpointId and checkpointPosition in the database.
@deepthidevaki deepthidevaki mentioned this issue Jul 6, 2022
Closed
58 tasks
This was referenced Jul 14, 2022
Closed
Closed
Closed
Merged
Merged
@deepthidevaki deepthidevaki self-assigned this Jul 15, 2022
zeebe-bors-camunda bot added a commit that referenced this issue Jul 25, 2022
@zeebe-bors-camunda @deepthidevaki
merge: #9817
9c8b886 
9817: Define state for storing checkpoint info r=deepthidevaki a=deepthidevaki

## Description

When processing checkpoint records, the processor have to store the latest checkpoint info in the state. This PR adds the necessary classes for accessing checkpoint info in ZeebeDb.

## Related issue

realted #9720 



Co-authored-by: Deepthi Devaki Akkoorath <deepthidevaki@gmail.com>
zeebe-bors-camunda bot added a commit that referenced this issue Jul 25, 2022
@zeebe-bors-camunda @deepthidevaki
merge: #9817
6610522 
9817: Define state for storing checkpoint info r=deepthidevaki a=deepthidevaki

## Description

When processing checkpoint records, the processor have to store the latest checkpoint info in the state. This PR adds the necessary classes for accessing checkpoint info in ZeebeDb.

## Related issue

realted #9720 



Co-authored-by: Deepthi Devaki Akkoorath <deepthidevaki@gmail.com>
zeebe-bors-camunda bot added a commit that referenced this issue Jul 26, 2022
@zeebe-bors-camunda @deepthidevaki
merge: #9817
77ec95b 
9817: Define state for storing checkpoint info r=deepthidevaki a=deepthidevaki

## Description

When processing checkpoint records, the processor have to store the latest checkpoint info in the state. This PR adds the necessary classes for accessing checkpoint info in ZeebeDb.

## Related issue

realted #9720 



Co-authored-by: Deepthi Devaki Akkoorath <deepthidevaki@gmail.com>
@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

@deepthidevaki deepthidevaki

Labels
version:8.1.0-alpha4 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.

Add processor to process checkpoint records camunda/camunda
4 participants
@npepinpe @menski @deepthidevaki @Zelldon