Project

General

Profile

Story #8173

add checks for retrograde systemMetadata changes

Added by Rob Nahf about 4 years ago. Updated almost 4 years ago.

Status:
New
Priority:
High
Assignee:
Category:
d1_indexer
Target version:
Start date:
2017-09-01
Due date:
% Done:

0%

Story Points:

Description

with the ability to prioritize and the introduction of parallelized index task processing, the effective queue is not guaranteed to be time-ordered. If there are two valid system metadata changes resulting in two tasks and the second change hits the index first, the earlier task should be rejected, as its changes are out of date.


Related issues

Related to CN Index - Task #7771: Use multiple threads to index objects Closed 2016-05-04

History

#1 Updated by Rob Nahf about 4 years ago

  • Related to Task #7771: Use multiple threads to index objects added

#2 Updated by Dave Vieglais almost 4 years ago

  • Target version changed from CCI-2.3.5 to CCI-2.3.6

#3 Updated by Jing Tao almost 4 years ago

  • Target version changed from CCI-2.3.6 to CCI-2.3.7

#4 Updated by Dave Vieglais almost 4 years ago

  • Assignee changed from Rob Nahf to Jing Tao

#5 Updated by Jing Tao almost 4 years ago

  • Target version changed from CCI-2.3.7 to CCI-2.4.0

Our new hazelcast event filter has the function. But after we transfer to RabbitMQ mechanism, we will need another one. So i move it to 2.4.

#6 Updated by Dave Vieglais almost 4 years ago

  • Sprint set to Infrastructure backlog

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)