A.J. Beamon

As you probably remember, there is some discussion here that talks about what the severity levels currently mean: https://forums.foundationdb.org/t/why-is-a-sev-40-if-ilistener-accept-throws-an-error/663 I agree that these should be more formally documented. Roughly, they...

Sure, mainly I'm adding this information here for the benefit of whoever does the documenting.

It seems I may have been mistaken about the Java case, where it looks like we do block on the run network call terminating in our implementation of stop network.

Or maybe the fact that we are waiting for `fdb_run_network` to stop but not actually joining the thread that it's running in is a problem.

@vishesh So are you saying that we should expose the `stopNetwork` function in Go and that's it for now?

> My plan is to start an async read request on that key, while the rest of the transaction handler is running (with potentially stale prefixes), and once it completes...

I'm not aware of anyone having done work on this yet, but I can add a few thoughts. Managing a cache in the face of simultaneous directory modifications in the...

> The easiest solution would be to add a new metadataVersion key in addition to the currently existing version key, which would be a versionstamp updated on every mutation (create,...

I also think we should consider adding something to report the presence of processes with misconfigured locality in status. Otherwise it may not be obvious that something isn't quite right.

Can you provide some example code that demonstrates the problem? I get correct behavior with the following sample that uses transactions: ``` import com.apple.foundationdb.Database; import com.apple.foundationdb.FDB; import com.apple.foundationdb.tuple.ByteArrayUtil; import com.apple.foundationdb.directory.DirectoryLayer;...