ArangoDB 集群在一个节点故障后停止

Question

I have ArangoDB cluster with 3 nodes. First one has service.config:

> ExecStart=/usr/bin/arangodb \
        --starter.data-dir=/var/lib/arangodb3/cluster \
        --server.storage-engine=rocksdb \
        --auth.jwt-secret=/etc/arangodb3/arangodb.secret \
        --agents.agency.supervision-grace-period=30 \
        --log.file=true \
        --log.dir=/var/log/arangodb3/cluster \
        --log.verbose
TimeoutStopSec=60

and two other nodes have:

> ExecStart=/usr/bin/arangodb \
        --starter.data-dir=/var/lib/arangodb3/cluster \
        --server.storage-engine=rocksdb \
        --auth.jwt-secret=/etc/arangodb3/arangodb.secret \
        --agents.agency.supervision-grace-period=30 \
        --starter.join arangodb01.domain.com \
        --log.file=true \
        --log.dir=/var/log/arangodb3/cluster \
        --log.verbose

It works fine until any node stop. After one node stop no requests processed. I see in "[root@arangodb01 ~]# journalctl -u arangodb " only:

>We're master, try to remain it component=arangodb\
>Master changed callback from [arangobd01 IP]:57722 component=arangodb\
>Received GET /hello request from [arangobd02 IP]:38436 component=arangodb

Is is possible to work if only 2 nodes work in cluster?

UPD: I face problem with shard migrtion/ This is the problem of my cluster

Answer 1

Finally I found the reason of "bad" shards. For every collection you create in cluster check "replicationFactor" in info section of collection. By default it is 1 and if you create it with the help of API it is "replicationFactor: (cluster only)"