You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a handson tutorial at a conference (MySQLDays, a FOSDEM Fringe conf, presenting about MySQL InnoDB Cluster/ReplicaSet), I was using docker-tc to simulate network issues.
However, during the class, I found that weird things happened when I tried to network partition a single host. Other hosts seemed to be affected too.
in the examples I have a docker-tc wrapper that contains:
$ curl -sSf -X "$1" "localhost:4080/$2?$3"
Here's the state of the containers before doing anything:
Then I network partition a single container by adding loss=100%:
$ docker-tc post mysqltutorial_server_3_1 loss=100%
Set loss=100% on veth3795593
Controlling traffic of the container /mysqltutorial_server_3_1 on veth3795593
Set loss=100% on veth6015f81
Controlling traffic of the container /mysqltutorial_server_3_1 on veth6015f81
Set loss=100% on vethfeda243
Controlling traffic of the container /mysqltutorial_server_3_1 on vethfeda243
Set loss=100% on vethd9de0b8
Controlling traffic of the container /mysqltutorial_server_3_1 on vethd9de0b8
Set loss=100% on veth23ae4cf
Controlling traffic of the container /mysqltutorial_server_3_1 on veth23ae4cf
When I then look at the configuration, you can see that various other servers now also have loss=100%:
For a handson tutorial at a conference (MySQLDays, a FOSDEM Fringe conf, presenting about MySQL InnoDB Cluster/ReplicaSet), I was using
docker-tc
to simulate network issues.However, during the class, I found that weird things happened when I tried to network partition a single host. Other hosts seemed to be affected too.
in the examples I have a
docker-tc
wrapper that contains:Here's the state of the containers before doing anything:
Then I network partition a single container by adding
loss=100%
:When I then look at the configuration, you can see that various other servers now also have
loss=100%
:The text was updated successfully, but these errors were encountered: