|
| 1 | +## Chaos kill-couchbase command |
| 2 | + |
| 3 | +Cbdinocluster provides a way to kill couchbase service running |
| 4 | +on a docker container by using `chaos kill-couchbase` command. |
| 5 | +This method is used to simulate a stop and restart of the couchbase server. |
| 6 | + |
| 7 | +### What it does |
| 8 | + |
| 9 | +If no nodeId is provided, the command will terminate the Couchbase service on all nodes in the cluster. |
| 10 | +If a nodeId is specified, only the Couchbase service on the specified node will be terminated. |
| 11 | +The command should first gather information about the nodes, including the containers on which they are running, |
| 12 | +And it should then simply exec into a Docker container and run `pkill -f couchbase-server` |
| 13 | +to terminate the Couchbase service. |
| 14 | + |
| 15 | +The `runSv` supervisor will automatically restart couchbase-server within a few seconds. |
| 16 | + |
| 17 | +### Usage |
| 18 | + |
| 19 | +This command is useful in case where a Couchbase server may be unexpectedly stopped and restarted. |
| 20 | +It allows observing behavior during the transition period when the server is restarting, |
| 21 | +which can reveal issues with connection handling, retries, and error recovery. |
| 22 | + |
| 23 | +``` |
| 24 | +
|
| 25 | +### Kill Couchbase Service |
| 26 | +
|
| 27 | +``` |
| 28 | +cbdinocluster chaos kill-couchbase <clusterId> [nodeId] |
| 29 | +``` |
| 30 | +
|
| 31 | +### Supported Deployers |
| 32 | +
|
| 33 | +| Deployer | Supported | Notes | |
| 34 | +|----------|-----------|-------------------------| |
| 35 | +| DOCKER | Yes | Supported for Docker | |
| 36 | +| LOCAL | No | Not supported for local | |
| 37 | +| CAO | No | Not supported for cao | |
| 38 | +| CLOUD | No | Not supported for cloud | |
0 commit comments