5 ms·

And when your journal is corrupted due to a bug in the Docker volume driver?

• jjawssd 10y ago
  Isn't it possible to stream a copy of the database out of the container and over the network to another database instance?
  • Minikloon 10y ago
    Chicken and egg. Is that other instance containerized?
    • mentat 10y ago
      Decoupled failure modes, unless you think there's a global "fail all docker data stores".
      • user5994461 10y ago
        There are major cascading failures with Docker. For starter, failure modes are not decoupled at all. If one db hits a race condition in the storage driver on one instance, it's usually 100% guarantee that all other instances are sensitive to the same bug and it will happen sooner or later. In practice, occurrences of a bug are highly correlated and usually happen in batch.
• amelius 10y ago
  Then you let Docker write to a virtual network drive, streaming the journal out of the container.
  • KaiserPro 10y ago
    I doubt thats going to be fast. However, if you are going to be running docker on real tin (because thats where the value/speed comes in, if you're on AWS thats a whole 'nother issue) Then you might as well use device mapper for what it was originally designed for: mapping fibre channel. (or iscsi, or SAS [another scsi]) That is assuming you want speed, and have paid enough cash to overcome SPoF in your storage layer (it'll be cheaper and faster than trying to software your way out of it.)