WangXiang
WangXiang
Using Chaosd to inject a fault into a JVM application, Chaosd runs success but can see errors below in application's log: 
create PhysicalMachineChaos in Chaos Mesh, the YAML config is below: ```YAML kind: PhysicalMachineChaos apiVersion: chaos-mesh.org/v1alpha1 metadata: namespace: default name: write-payload spec: action: disk-write-payload address: - http://172.16.112.130:31767 uid: c11fa67a-ee03-4fab-9e85-77fdece0b1ff disk-write-payload: size:...
When the user enters ctrl-c when executing chaosd, the status of the experiment will be `created`, and can never be recovered. Should support force recover.
 Maybe we can watch the free space on disk, and left some space to save the experiment's status.
according to https://github.com/chaos-mesh/rfcs/blob/main/text/2021-12-09-logging.md
according to https://github.com/chaos-mesh/rfcs/blob/main/text/2021-09-27-refine-error-handling.md
`direction` can only be set to `from` or `to`, need to support `both`, to support bidirectional network partition.
include: - fail to receive publisher's message - fail to update config - fail to notify the update
include: - high payload - message queue is full - can't write into
use `ifdown` command to down the network device.