FDB cluster with three_datacenter mode becomes unavailable if one of three DCs has network card failure

I have a FDB cluster in three_datacenter mode. Each DC has 6 machines.

I found that the cluster becomes unavailable if I randomly down the machines’ public network interface (ifdown bond1) in the primary DC (fdbcli --exec ‘status json’ | jq .cluster.active_primary_dc).

The problem is hard to recur.

Any advice to address this?

Start by examining the three_datacenter failure scenario described: take down bond1 on machines in the primary DC and query fdbcli with “status json”, checking cluster.active_primary_dc. No source files or tests are identified. Done means producing a reliable reproduction, identifying why the cluster becomes unavailable, and documenting an actionable mitigation.

Written by the indexing model from the issue text.