[NXP-21707] RedisWorkManager should not run concurrently works sharing the same id - Nuxeo Issue Tracker

XML

Word

Printable

Details

Type: Bug
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: 8.10, 9.1-SNAPSHOT
Fix Version/s: 8.10-HF03, 9.1
Component/s: Events / Works, Redis, Renditions

Tags:
Backlog priority:
800
Sprint:
nxcore 9.1.2, nxcore 9.1.3
Story Points:
3

Description

When a work is running, if another work with the same id is scheduled it should not be run until the first one is completed.
First there is no interest to run concurrently the same work,
second the underlying queue implementation are not able to run 2 works with the same id, the work data and state being indexed with the job id.

Attachments

Issue Links

is related to

NXP-21255 redis works popping should run atomically

Resolved

NXP-21939 Create reliable unit test work

Open

NXP-21734 Fix failure of Redis work done cleanup on duplicate job

Resolved

NXP-25619 Coalescing Work with StreamWorkManager implementation

Resolved

Activity

People

Assignee:

Benoit Delbosc

Reporter:

Frantz Fischer

Participants:

Anahide Tchertchian, Benoit Delbosc, Frantz Fischer, Jenkins

Votes:

0 Vote for this issue

Watchers:

6 Start watching this issue

Dates

Created:

2017-02-23 16:32

Updated:

2018-08-27 13:36

Resolved:

2017-03-16 13:06

Time Tracking

Estimated:

Not Specified

Remaining:

Logged: