Task #2180
Story #2166: Hazelcast cluster errors need to be isolated
Coordinate d1_replication locks in the process cluster
Status:
Closed
Priority:
Normal
Assignee:
Category:
d1_replication
Target version:
Start date:
2012-01-09
Due date:
% Done:
100%
Milestone:
CCI-1.0.0
Product Version:
*
Story Points:
Sprint:
Description
Instead of directly locking the pid of an object in the storage cluster to coordinate among processing components, instead create the lock in the Hazelcast process cluster. This should reduce contention on the hzSystemMetadata map calls, but will still allow synchronization, replication, and indexing to coordinate process timing.
History
#1 Updated by Chris Jones over 12 years ago
- Status changed from New to Closed
Locks are now called using HazelcastInstance rather than HazelcastClient
