Thanks for the incredibly fast reply, It has however raised a couple of other questions (as answers usually do :) )
When you say "A state transfer will time out unless it can acquire all locks on the oldest member" I assume this means that, in effect, this locks the whole cluster for the duration, as a transaction would need to update every member? Are these locks only for writing, and you can still read? Assuming each node is locked individually (I assume a lot :) ), are all the locks kept for the duration of the transfer to the new member, or released as each node is transfered? (we cache a lot of large objects, so the transfer could take some time - I havent got as far as investigating transfer speed yet but read some posts saying it can be quite slow) Would I be right in thinking that because of the locking, you should therefore only add 1 cache at a time or is there something to handle this case (so if we restarted all the servers in a cluster at the same time and the transfer took say 1 minute possibly all but the first one in might fail ? ) Will the transfer always be an all or nothing thing? (so its safe to assume if you can't read a node you *know* should be there - the transfer failed) or is there a better/proper way of telling it failed to get the state correctly? Sorry for the rapid fire questions, and thanks again for your time << JOC >> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3900250#3900250 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3900250 ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
