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

Forward oplog entries to the active oplog processor plugins #1038

Open
vigoo opened this issue Oct 28, 2024 · 0 comments · May be fixed by #1095
Open

Forward oplog entries to the active oplog processor plugins #1038

vigoo opened this issue Oct 28, 2024 · 0 comments · May be fixed by #1095
Assignees
@vigoo
Labels
worker-executor
Milestone
Golem 1.1

Comments

@vigoo
Copy link
Contributor

vigoo commented Oct 28, 2024 •
edited
Loading

Based on the work prepared in #1036, make sure that each emitted oplog entry emits a fire-and-forget worker invocation to the enabled oplog processor plugins.

  • Applies to new oplog entries created in live mode
  • No broadcast during replay
  • When a new oplog processor is added, it needs to first get the full history of the worker before it gets new entries

Make sure it is not possible to enable oplog processor plugins for oplog processor plugins.
@vigoo vigoo self-assigned this Oct 28, 2024
@vigoo vigoo added this to the Golem 1.1 milestone Oct 28, 2024
@vigoo vigoo linked a pull request Nov 30, 2024 that will close this issue
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vigoo vigoo

Labels
worker-executor
Projects
None yet
Milestone
Golem 1.1
Development

Successfully merging a pull request may close this issue.

Running oplog processor plugins, WIP golemcloud/golem
1 participant
@vigoo