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

Define Zeno's queuing behavior properly #115

Closed
CorentinB opened this issue Aug 4, 2024 · 2 comments · Fixed by #119
Closed

Define Zeno's queuing behavior properly #115

CorentinB opened this issue Aug 4, 2024 · 2 comments · Fixed by #119
Assignees
Labels
enhancement New feature or request internal-only This PR/Issue is reserved for the IA team P1 very high priority

Comments

@CorentinB
Copy link
Collaborator

As discussed with @equals215, Zeno's behavior in term of queuing should be as followed:

  • By default: handover + WAL writes batching
  • As an option: --disable-handover, --whatever (--whatever == a good argument name to ask for more atomicity == not use WAL batch writing)
  • When using HQ: handover++ (no queuing AT ALL)
@CorentinB CorentinB added enhancement New feature or request internal-only This PR/Issue is reserved for the IA team P1 very high priority labels Aug 4, 2024
@equals215
Copy link
Member

Options and defaults can be done in under a minute. Handover++ as you call it, can either be done on the fly or integrated to #113 in the channeling efforts, as you wish @CorentinB

@CorentinB
Copy link
Collaborator Author

I guess it should be integrated in #113.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request internal-only This PR/Issue is reserved for the IA team P1 very high priority
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants