Can we keep two different clusters data in synch.

Question

i have 10 coherence servers in newyork all forming clusterA and i do have 10 coherence servers in charlotte forming clusterB ,i wish to keep the data between cluster A and cluster B in synch.
Q1: is there any possible/configurable way to achive this.
Note: I dont want all the 20 coherence servers(newyork and charlotte) forming the same cluster.
Q2:Incase if all the 20 servers are forming the same cluster how would the read/write response times vary for the coherence clientapplications which are running in charlotte and newyork ,Asuuming i have 50 Apps running in charlotte and the same 50 apps(DR COPY) running in newyork.i am trying to achieve the best read/write performance.
Q3: is read/write performance vary only based on the cache type irrespective of network/location of coherence servers?
Thanks Much
Edited by: goodboy626696 on May 28, 2009 2:19 PM

Answer 1

On the remote site, something similar cache config (have proxy-scheme):
<cache-config>
<caching-scheme-mapping>
<cache-mapping>
<cache-name>my-cache</cache-name>
<scheme-name>distributed-scheme</scheme-name>
</cache-mapping>
</caching-scheme-mapping>
<caching-schemes>
<distributed-scheme>
<scheme-name>distributed-scheme</scheme-name>
..... Define a backing map and a listener here .....
</distributed-scheme>
<proxy-scheme>
<service-name>ExtendTcpProxyService</service-name>
<thread-count>50</thread-count>
<acceptor-config>
<tcp-acceptor>
<local-address>
<address>localhost</address>
<port system-property="tangosol.coherence.acceptor.port">32000</port>
<reusable>true</reusable>
</local-address>
</tcp-acceptor>
</acceptor-config>
<autostart>true</autostart>
</proxy-scheme>
</caching-schemes>
</cache-config>
On another site we would need a remote-cache-scheme:
<!DOCTYPE cache-config SYSTEM "cache-config.dtd">
<cache-config>
<caching-scheme-mapping>
<cache-mapping>
<cache-name>*</cache-name>
<scheme-name>distributed-scheme</scheme-name>
</cache-mapping>
</caching-scheme-mapping>
<caching-schemes>
<distributed-scheme>
<scheme-name>distributed-scheme</scheme-name>
<service-name>DistributedCache</service-name>
<lease-granularity>thread</lease-granularity>
<backing-map-scheme>
<local-scheme>
</local-scheme>
</backing-map-scheme>
<autostart>true</autostart>
</distributed-scheme>
<!--
remote cache scheme used to replicate data to the replicate cluster via
Extend
-->
<remote-cache-scheme>
<scheme-name>remote</scheme-name>
<service-name>ExtendTcpCacheService</service-name>
<initiator-config>
<tcp-initiator>
<remote-addresses>
<socket-address>
<address>localhost</address>
<port>32000</port>
</socket-address>
</remote-addresses>
<connect-timeout>20s</connect-timeout>
</tcp-initiator>
<outgoing-message-handler>
<request-timeout>20s</request-timeout>
</outgoing-message-handler>
</initiator-config>
</remote-cache-scheme>
</caching-schemes>
</cache-config>
And then from an active site in a BML use the code to publish the key/value to a remote cache.
Edited by: asrivast on Jun 9, 2009 10:49 PM