>From my experience with clustering that is when the connection between parts 
>of the clusters are lost and they can't agree on which one is supposed to keep 
>serving the data. The most common way around it afaik is to have a priority 
>and heartbeat between the nodes and allow them to kill each other off 
>(something like STONITH = Shoot The Other Node In The Head) or similar.
 
So, if we have two servers A and B and a heartbeat (with STONITH) between them 
and node A misses a few heartbeats (perhaps a lockup, perhaps something else), 
then node B will reset node A and take over that nodes capabilities.
 
This is without reading about Terracotta so things might be different there, 
but that's the split-brain problem from my experience.
 
Hope this helps
 
Cheers
 
Oscar

________________________________

Från: Ch Praveena [mailto:[EMAIL PROTECTED]
Skickat: ti 2008-04-08 09:30
Till: users@httpd.apache.org
Ämne: [EMAIL PROTECTED] Split-brain problem.



Hi all, 

   While going on with Terracotta article, 
-- http://www.terracotta.org/confluence/display/explore/How+Terracotta+Works,
For implementing application server clustering, I found this phrase, 
"Split-brain problem.".. 

Please let me know about this in detail.. 



Regards,

Praveena Chalamcharla,
Securview.... 

<<winmail.dat>>

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [EMAIL PROTECTED]
   "   from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to