Task #1718
Story #1388: implement MN-MN replication manager in CN stack
Create Hazelcast replication configuration that uses TCP vs multicast
Start date:
2011-08-25
Due date:
% Done:
100%
Milestone:
CCI-0.6.4
Product Version:
*
Story Points:
Sprint:
Description
For distributed replication queues, we'll need to configure the Hazelcast queues on initialization to use TCP rather than multicast, which will require that we know the IP addresses of all CNs. Also, change the backup policy to 3, and configure the merge policy such that we add all unique tasks back into the queue in the event of all CNs going down.
History
#1 Updated by Chris Jones about 13 years ago
- Subject changed from Create Hazelcast configuration that uses TCP vs multicast to Create Hazelcast replication configuration that uses TCP vs multicast
#2 Updated by Chris Jones about 13 years ago
- Assignee set to Chris Jones
#3 Updated by Chris Jones about 13 years ago
- Status changed from New to Closed
d1_replication has a hazelcast.xml file in the classpath now. This may need to be refactored to be a centralized configuration in a d1_hazelcast component or something similar.
