[msubramanyam@ip-10-174-26-45 ~]$ sudo -s
[root@ip-10-174-26-45 msubramanyam]# fdbcli
Using cluster file `/etc/foundationdb/fdb.cluster’.
The database is available, but has issues (type ‘status’ for more information).
WARNING: The cluster file is not up to date. Type ‘status’ for more information.
Welcome to the fdbcli. For help, type `help’.
fdb> status details
Using cluster file `/etc/foundationdb/fdb.cluster’.
Cluster file contents do not match current cluster connection string.
The file contains the connection string:
SharedCluster:aN43NeK4@10.174.26.22:4500
The current connection string is:
SharedCluster:B7cvX6P7P05dEcHbNVTB0rhDhmMAinUB@10.174.24.151:4500,10.174.26.22:4
500,10.174.28.171:4500
Verify the cluster file and its parent directory are writable and that the
cluster file has not been overwritten externally. To change coordinators without
manual intervention, the cluster file and its containing folder must be writable
by all servers and clients. If a majority of the coordinators referenced by the
old connection string are lost, the database will stop working until the correct
cluster file is distributed to all processes.
46 client(s) reported: Cluster file contents do not match current cluster connection string. Verify the cluster file and its parent directory are writable and that the cluster file has not been overwritten externally.
10.174.26.45:33402
10.174.26.45:38928
10.174.26.45:39352
10.174.26.45:39560
…
Configuration:
Redundancy mode - single
Storage engine - memory-2
Encryption at-rest - disabled
Coordinators - 3
Usable Regions - 1
Cluster:
FoundationDB processes - 1 (less 0 excluded; 1 with errors)
Zones - 1
Machines - 1
Memory availability - 3.7 GB per process on machine with least available
>>>>> (WARNING: 4.0 GB recommended) <<<<<
Fault Tolerance - 0 machines
Server time - 02/11/25 18:06:54
Data:
Replication health - Healthy
Moving data - 0.000 GB
Sum of key-value sizes - 1 MB
Disk space used - 117 MB
Operating space:
Storage server - 1.0 GB free on most full server
Log server - 100.8 GB free on most full server
Workload:
Read rate - 22 Hz
Write rate - 0 Hz
Transactions started - 9 Hz
Transactions committed - 0 Hz
Conflict rate - 0 Hz
Backup and DR:
Running backups - 0
Running DRs - 0
Process performance details:
10.174.26.22:4500 ( 1% cpu; 3% machine; 0.000 Gbps; 0% disk IO; 0.3 GB / 3.7 GB RAM )
Cluster file contents do not match current cluster connection string. Verify the cluster file and its parent directory are writable and that the cluster file has not been overwritten externally.
Coordination servers:
10.174.24.151:4500 (reachable)
10.174.26.22:4500 (reachable)
10.174.28.171:4500 (reachable)
Client time: 02/11/25 18:06:54
fdb> coordinators auto
Coordination state changed
fdb> configure new ssd double
ERROR: Database already exists! To change configuration, don’t say new' fdb> configure ssd double ERROR: Not enough processes exist to support the specified configuration Type configure FORCE <TOKEN…>’ to configure without this check
fdb>