0451df0d1b
It was discovered that in some situations the same reprocessing task might be processed simultaneously by different workers, which can lead to unnecessary processing. This was happening due to the use of "current_reprocess_time" in the lock name, which would lead to different locking name for some situations; for instance, when worker start processing a brand new reprocessing task, and after reprocessing a few time frames, the "current_reprocess_time" is updated, then when other workers achieve the same locking moment, they would have a different lock name for the same scope ID, and reprocess a scope that is currently in reprocessing. Change-Id: I487d0eeb1cedc162d44f8c879a27f924b5c76206
5 lines
73 B
YAML
5 lines
73 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Fixed concurrency issues during reprocessing tasks.
|