Project

General

Profile

Task #2221

Story #2067: Refactor the index task generator and processor to improve scalability and performance

Update Task Generation to act only on 'update' events

Added by Skye Roseboom almost 13 years ago. Updated almost 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Skye Roseboom
Category:
d1_indexer
Start date:
2012-01-12
Due date:
% Done:

100%

Milestone:
CCI-1.0.0
Product Version:
*
Story Points:
Sprint:

Description

Related to how hzcast generates map added events for items that have previously been in the map, but evicted. When the item is re-added to distributed map, and 'add' event is called.

Only listen for update events on the system metadata map.

This change mean the IndexTask priority between add/update is no longer useful. Remove/update priority handling logic - no longer can tell and add form and update.

History

#1 Updated by Skye Roseboom almost 13 years ago

  • Status changed from New to In Progress

#2 Updated by Skye Roseboom almost 13 years ago

Changing strategy to account for previously evicted items being re-added to system metadata map:

on add event, check the serial version - if greater than 1 - this not a true add, should represent an item re-added to map after eviction.

#3 Updated by Skye Roseboom almost 13 years ago

added serial version check to add event handling logic. Add event is ignored if systemMetadata.serialVersion > 1. When the value is greater than 1, this indicates an add event generated when a previously evicted entry is added back into the distributed map.

#4 Updated by Skye Roseboom almost 13 years ago

  • Status changed from In Progress to Closed

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)