-
1. Problem with persistence cache in 1.1
prese Sep 15, 2004 4:37 AM (in response to prese)hi,
I'm trying to get the persistence cache working. The problem I am encountering is the JBossCache seem to be in a endless loop when trying to archive 160k+ instances of a simple object containing a few attributes. The data size for the 160k+ objects is about 10mb as CSV, but in the archive form as persisted by the CacheLoader it just keep growing. I've tried both the FileCacheLoader & BdbjeCacheLoader, they both shows the same behaviour.
eddie -
2. Re: Cache reconciliation
belaban Sep 15, 2004 5:08 AM (in response to prese)If you use FD.shun=true and GMS.shun=true, then the following will happen:
- C is disconnected
- C will form a view {C}
- A and B will form a view {A,B}
- When you reconnect, both partitions will shun each other, causing them to leave and rejoin. There is *never* a merge going on !
When you disable shun=true, the partitions {C} and {A,B} will merge back into {A,B,C}, so there you *will* get a MergeView.
Bela -
3. Re: Cache reconciliation
prese Sep 15, 2004 6:38 AM (in response to prese)Hi Bela,
Thanks for the answer, but i still have some problems :((..
Node C is the coordinator.
If I remove B when I reconnect back B I have the following situation:
- node A and B received a merge view with members A, B
- node C is declared as suspect and does not receive any view ...
I put it on shun=false both the GMS and FD.
I´m using for Cluster Partition on channel configuration and for Cache clustering a different channnel configuration ... can be this the cause for the problem ?
What other cluster parameters should I check?
Thanks
Sebi -
4. Re: Cache reconciliation
belaban Sep 15, 2004 8:47 AM (in response to prese)You have to use the exact same config for A, B and C.
I don't understand the rest of your post...
Bela -
5. Re: Cache reconciliation
prese Sep 15, 2004 9:08 AM (in response to prese)I´m using exactlly the same cluster configuration for all the nodes but I still have the problem:
Consider the following:
- node A is the coordinator of the clustered cache
- there are also node B and C on the cluster
- the node B is disconnected for a while
- I reconnect it back
- I receive merge view only on nodes B and C ... the merge view contains those 2 nodes
- Node A (the old coordinator) is declared as suspected and he does not receive any merge view ....
I´m using the shun=false for both GMS and FD.
I have no idea why the node A is declared as suspected and why the mergeing view does not contain all the nodes? ...
Thanks
Sebi