-
1. Re: One node in two clusters?
chrismeadows Feb 21, 2007 12:47 PM (in response to chrismeadows)I've almost achieved what I need by using TcpDelegatingCacheLoaders. The configuration I have is:
Cluster 1 has two nodes A and B replicating using UDP.
Cluster 2 has two nodes C and D replicating using UDP.
A, B, C, D all use unshared cacheloaders
Clusters 1 and 2 cannot find each other
Node A has a chained TcpDelegatingCacheLoader, delegating to a TcpCacheServer that wraps node D
Node C has a chained TcpDelegatingCacheLoader, delegating to a TcpCacheServer that wraps node B
Now what happens is that a single cache change is continually propagated in a loop, typically A->C->B->D->A, because A does not know that the update incoming from D originated from A (A and D are in separate clusters).
I think I'm close to what I am trying to achieve; can anyone fill in the miss bits? Can the data packets be given UUIDs so that A can ignore packets that it created?
Also, it looks like the true tag is ignored for the TcpDelegatingCacheLoader -
2. Re: One node in two clusters?
manik Feb 22, 2007 11:06 AM (in response to chrismeadows)This is very close to what you are trying to achieve. Perhaps instead of making them unshared, you could create a singleton cache loader? This will solve the problem of "A ignoring the packets it creates", as you say?
Also, it looks like the true tag is ignored for the TcpDelegatingCacheLoader
Which true tag?