allegro / allegro/consul-recipes
Watches: Document races on worker pool
Open
- Dominant language
- Java
- Stars
- 12
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Even if events are properly ordered from Consul. We can still process them in a different order. When we've got multiple threads of worker pool and synchronized operation of consuming events, the thread that got second event can run before the thread that got first event.
We should recommend for users that they either should use single threaded worker pool or save last consumed index.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.