Skip to content

Document queue mode single- and multi-replica behavior #775

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

Closed
jasonstitt opened this issue Feb 5, 2023 · 1 comment
Closed

Document queue mode single- and multi-replica behavior #775

jasonstitt opened this issue Feb 5, 2023 · 1 comment
Assignees
Labels
good first issue Good for newcomers stalebot-ignore To NOT let the stalebot update or close the Issue / PR Type: Enhancement New feature or request

Comments

@jasonstitt
Copy link

Describe the feature

I've read the comment for NTH deployment replica count:

The number of replicas in the NTH deployment when using queue-processor mode (NOTE: increasing this may cause duplicate webhooks since NTH pods are stateless)

Without additional knowledge on the internal workings, this comment is difficult to interpret. It would be helpful to have documentation in the README of the implications of both single and multi replica deployments.

For example (these are made up - I'm guessing all of them, which is why I'd appreciate docs):

  • With a single replica, the draining of other nodes could be delayed if the node NTH is on is the first one terminated (?)
  • With multiple replicas, draining might take more than the 30s default visibilityTimeout of an SQS queue and therefore the messages might be picked up by another replica (?)
  • visibilityTimeout could be increased with XXX other implications (?)
@stevehipwell
Copy link
Contributor

This is related to #718.

@cjerad cjerad added Type: Enhancement New feature or request stalebot-ignore To NOT let the stalebot update or close the Issue / PR labels Mar 8, 2023
@cjerad cjerad added the good first issue Good for newcomers label Jun 20, 2023
@GavinBurris42 GavinBurris42 mentioned this issue Aug 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers stalebot-ignore To NOT let the stalebot update or close the Issue / PR Type: Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants