Services in a three-node spatiotemporal big data store (BDS) cluster become restricted to a single node, resulting in an index with only a single shard and no replication.

Additional Information

Workaround

Once this occurs, the index settings can be updated to remove the routing.allocation.require._name property using the following curl command:

curl --user <bds-admin-user>:<bds-admin-pass> -X PUT "http://<bds-node>:9220/<index-name>/_settings" -H "Content-Type: application/json" -d "{\"routing.allocation.require._name\": null}"

After executing this command, inspect the index properties again. The index health returns to green and the replica shards should be properly assigned again. However, the index still only has one primary shard instead of three.

Steps to Reproduce