generated from amazon-archives/__template_Apache-2.0
-
Notifications
You must be signed in to change notification settings - Fork 274
Closed
Labels
Type: EnhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomersstalebot-ignoreTo NOT let the stalebot update or close the Issue / PRTo NOT let the stalebot update or close the Issue / PR
Description
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, eilonmonday and phijojo
Metadata
Metadata
Assignees
Labels
Type: EnhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomersstalebot-ignoreTo NOT let the stalebot update or close the Issue / PRTo NOT let the stalebot update or close the Issue / PR