CDV ❯ common locks for timestamp entry

• Type: Bug
• Status: Closed
• Priority: 2 Major
• Resolution: Fixed
• Component/s:
• Labels:

• Assignee: kkannaiy
• Reporter: nelrahma
• Created: May 22, 2009
• Votes: 0
• Watchers: 2
• Updated:

  February 12, 2013
• Resolved:

  May 26, 2009

Attachments

• nelrahma (4.00 k) text/plain share_key_patch.txt

Description

In tim-map-evictor, there is a time stamp entry class that updated it’s timestamp using a concurrent lock. we should use the same lock that is used in the csm map, so that way we don’t create a new ClientLock object to update the timstampEntry, attach is a patch that demonstrates this.

Comments

Tim Eck 2009-05-26

the lockID used for the timestamp update should now be identical to the one used in the underlying CSM

Kalai Kannaiyan 2009-08-13

unable to verify the changes -> tim-map-evictor branch does not exist (moved as tim-distributed-cache).