A.J. Beamon

The `memory` storage engine also uses disk to store data, so it needs to make sure there is sufficient space on disk when excluding something. It does seem like a...

Yes, this is a behavior change that would result in not having the finalizer available as a backstop anymore.

The choice to warn and not fail was intentional to avoid situations where an invalid knob specification brings down all of the processes in a cluster and causes an availability...

> Thanks for the explanation. Can we revisit this choice? The choice to warn has led to an actual cluster-wide unavailability. The other choice has also led to cluster unavailabilities,...

Is the concern here that the process is encountering an error in `fdb_setup_network` but not generating any trace logs? Unfortunately, this is the current behavior of the client because it...

This is related to #4693 (see in particular https://github.com/apple/foundationdb/issues/4693#issuecomment-823579455)

I think you have to be careful about dividing by `total_bytes`. At the very least, you'll need to account for the possibility that storage servers are sharing disks or that...

I think we need to use something more like: ``` 1 - sum(kvstore_used_bytes, all processes) / (sum(kvstore_used_bytes, non-excluded processes) + sum(kvstore_free_bytes, non-excluded disks)) ``` Using total bytes has problems with...

Looking at the Python documentation for `multiprocessing.Semaphore`, it seems like the implementations in `multiprocessing` and `threading` are the same except for one argument name: > A semaphore object: a close...

https://github.com/apple/foundationdb/pull/8173 was just merged that adds a latency sample for range reads measured in the same way as the existing read latency sample. Does that supersede this?