Macos version database is available, but has issues. All of a sudden

Using FoundationDB Running FoundationDB
1

Hello,

I just started using foundationdb a while ago. the database has very little data. but today when i tried to run my app, i noticed it was taking time to connect to foundationdb. After running fdbcli in terminal this is what it shows.

Using cluster file `/usr/local/etc/foundationdb/fdb.cluster'.

The database is available, but has issues (type 'status' for more information).

Welcome to the fdbcli. For help, type `help'.

And after running status. here is the log.

fdb> status

WARNING: Long delay (Ctrl-C to interrupt)

Using cluster file `/usr/local/etc/foundationdb/fdb.cluster'.

Unable to start default priority transaction after 5 seconds.

Unable to start batch priority transaction after 5 seconds.

Unable to retrieve all status information.

Configuration:
  Redundancy mode        - single
  Storage engine         - memory-2
  Coordinators           - 1
  Usable Regions         - 1

Cluster:
  FoundationDB processes - 1
  Zones                  - 1
  Machines               - 1
  Memory availability    - 8.0 GB per process on machine with least available
  Fault Tolerance        - 0 machines
  Server time            - 04/26/23 20:28:52

Data:
  Replication health     - Healthy
  Moving data            - 0.000 GB
  Sum of key-value sizes - 3 MB
  Disk space used        - 138 MB

Operating space:
  Storage server         - 1.0 GB free on most full server
  Log server             - 0.0 GB free on most full server

Workload:
  Read rate              - 4 Hz
  Write rate             - 0 Hz
  Transactions started   - 1 Hz
  Transactions committed - 0 Hz
  Conflict rate          - 0 Hz
  Performance limited by server d59ab0d668aa7250: Log server MVCC memory.

Backup and DR:
  Running backups        - 0
  Running DRs            - 0

Client time: 04/26/23 20:28:44

how can i resolve this ? Thank you

2

The database is unavailable, probably because of Ratekeeper is throttling due to space issue:

  Storage server         - 1.0 GB free on most full server
  Log server             - 0.0 GB free on most full server

You can try adding more disk space and also check MasterRecoveryState event in the log, which should be 14, i.e., fully_recovered state.

3

i have added 4GB but still the same.

Operating space:
  Storage server         - 4.1 GB free on most full server
  Log server             - 0.0 GB free on most full server

Workload:
  Read rate              - 19 Hz
  Write rate             - 0 Hz
  Transactions started   - 6 Hz
  Transactions committed - 0 Hz
  Conflict rate          - 0 Hz
  Performance limited by server 8111c7049481eb8c: Log server MVCC memory.
4

Note ratekeeper now throttles due to TLog write bandwidth issue:

Performance limited by server 8111c7049481eb8c: Log server MVCC memory.
5

how can i increase the log server space ? i tried editing the conf

 memory = 8GiB
 storage_memory = 8GiB
 cache_memory = 8GiB

but still the warning doesnt go away.