Skip to main content
DevOps

Return to Answer

Spelling, loosing --> losing
Source Link
edit approved Oct 4, 2018 at 5:11
Cocowalla
edit approved Oct 4, 2018 at 5:11
Cocowalla
  • 153
  • 1
  • 7

I wrote about this in depth but here's the summary:

  • Preventing split brain (electing more than one master node) needs to be solved. Failure to do so can be catastrophic

  • There are no production ready shared storage solutions to enable databases to be shutdown on one instance and brought up on another without loosinglosing all your data.

I wrote about this in depth but here's the summary:

  • Preventing split brain (electing more than one master node) needs to be solved. Failure to do so can be catastrophic

  • There are no production ready shared storage solutions to enable databases to be shutdown on one instance and brought up on another without loosing all your data.

I wrote about this in depth but here's the summary:

  • Preventing split brain (electing more than one master node) needs to be solved. Failure to do so can be catastrophic

  • There are no production ready shared storage solutions to enable databases to be shutdown on one instance and brought up on another without losing all your data.

Source Link
Robo
Robo
  • 755
  • 3
  • 6

I wrote about this in depth but here's the summary:

  • Preventing split brain (electing more than one master node) needs to be solved. Failure to do so can be catastrophic

  • There are no production ready shared storage solutions to enable databases to be shutdown on one instance and brought up on another without loosing all your data.