Split Brain (English: divided brain) marks an absolutely unwanted condition of a computer cluster. It results from the simultaneous interruption of all intermediate connections between the cluster parts.
In principle one differentiates between
For the co-ordination of the transactions in the cluster i.d.R. a cluster Interconnect or a quorum is used - depending upon assigned technology. If the connection is interrupted between one or more parts of the cluster over this way, none can still differentiate between whether it itself around a partial loss or a separation acts. All of these (now isolated) cluster fragments continue working for itself, in order to maintain the supply of the service ("service"). Since still under normal conditions the network binding functions into the public net (thus toward user), problems result:
The Grundproblem of Split Brain is the circumstance that at least two parts still, however no co-ordination between them function is more possible. While this seems not yet directly problematic with pure read accesses, a write access leads to substantial conflicts: The recording procedures distribute themselves over (functioning however from each other isolated) the parts of the cluster, whereby however the Middle animal and/or the user nothing unusual noticed (the cluster behaves in the normal operation from user view directly). However written block cannot be read by knots/part B by the interrupted intermediate connection by knots/part A (and in reverse).
The data conditions therefore run out one that which are not consistency of the data no more ensured. A Recovery from this situation is feasiblly or completely impossible under normal conditions only under indiskutablem expenditure of time.
The basis of all counter measures is the simultaneous employment of quorum and cluster Interconnect: The separation of one of the two co-ordination possibilities permits still the distinction between division and partial loss.
The cover of parallel losses (pointer of loss of several operatingcritical parts) increases the expenditure enormously - in case of Split Brain preventing intercepts for example the use of several quorums and the employment more parallelisierter/bonded Interconnects the loss of Interconnect and a STORAGE.
In interaction between quorums and Interconnect reliably automated decision making is necessary, then for example with Oracle cluster commodity the decision is met as follows:
It survives after the loss of the Interconnects (sequence considered):
In order not to repeat the problem solved allegedly evenly by several quorums (I see two quorums, you see two quorums, but we unfortunately see two different pairs!) uses Oracle an odd number of these quorums. All knots in the quorum meet, must see itself also in the Interconnect. If this is not the case, the reading and the topology information decide in the Voting disk on lives and death of the knot. The decision list evenly specified is extended:
We found here 4 related websites.
Index | Privacy | Terms Of Use | Sitemap | Feedback