1. /
  2. Security Response/
  3. Glossary/
  4. network partition

Glossary

A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | _1234567890

network partition

The condition that exists after all network connections between any two groups of systems fail simultaneously. When this happens, systems on both sides of the partition can restart applications from the other side resulting in duplicate services, or split-brain. A split brain occurs when two independent systems configured in a cluster assume they have exclusive access to a given resource (usually a file system or volume). The most serious problem caused by a network partition is that it affects the data on shared disks.

See jeopardy

See seeding

If all network connections between any two groups of systems fail simultaneously, a network partition occurs. When this happens, systems on both sides of the partition can restart applications from the other side resulting in duplicate services, or "split-brain." A split brain occurs when two independent systems configured in a cluster assume they have exclusive access to a given resource (usually a file system or volume). The most serious problem caused by a network partition is that it affects the data on shared disks.

See Jeopardy and Seeding.

If all network connections between any two groups of systems fail simultaneously, a network partition occurs. When this happens, systems on both sides of the partition can restart applications from the other side, resulting in duplicate services, or split-brain. A split brain occurs when two independent systems configured in a cluster assume they have exclusive access to a given resource (usually a file system or volume). The most serious problem caused by a network partition is that it affects the data on shared disks.