killProcess_internal assumes that we've already checked and won't attempt to kill
a protected process. It's up to killProcess and killInterface, which are invoked
externally from simulated workloads, to enforce that constraint.
Explore all combinations where the server and the client
each takes one of the following TLS/cert-chain configuration:
No TLS, no chain, valid chain, expired chain, valid self-signed, expired self-signed
Negative cases are indirectly tested using timeouts:
i.e. if it times out, it means it's not connecting
+ Fix TSAN data race error in original test
(Calling FlowTransport::bind() with an active network thread running in background)
+ Properly redirect-and-capture subprocess stdout instead of just printing
(CTest tends to truncate subprocess console outputs)
* Recruit new singleton for consistency checker.
* Recruit the consistency checker only if enabled.
* Add a yield in monitorConsistencyChecker().
* Minor fixes.
* Consistency check workload enhancements.
* Minor fixes and clarifications.
* clang format
* Clang format.
* Minor fixes, cleanup, debug tracing.
* Misc.
* Move the consistency scan information from dbconfig to a key backed object.
* Move consistency scan config out of db cofig to a state object and feature rename.
* ConsistencyCheck workload refactor.
* devFormat
* Update fdbcli/ConsistencyScanCommand.actor.cpp
* Review Comments.
Co-authored-by: negoyal <neelam.goyal@gmail.com>
Co-authored-by: Ata E Husain Bohra <ata.husain@snowflake.com>
Configuration database data lives on the coordinators. When a change
coordinators command is issued, the data must be sent to the new
coordinators to keep the database consistent.
- Revert JWT timestamp from double back to uint64_t
- Describe in comment the need for wait loop at the beginning of watchPublicKeyJwksFile()
- Revert CLI args definition in fdbserver.actor.cpp that was
incorrectly tabbed with a bad clang-format run
fdb_find_sources CMake command adds all sources directly under fdbrpc/,
which would end up embedding the test binary into libfdbrpc.a
Avoid this by placing the test binary under subdirectory fdbrpc/tests/
* Update network address in trace logs; Add system monitor for flowprocess
* Create a new trace file with the correct process address for flowprocess
* Remove unused debugging traces
* Add a new error lock_file_failure; Change please_reboot_remote_kv_store to please_reboot_kv_store; Add the code to only reboot the kv store but not the worker; Remove some unnecessay traces
* Add error handling for file_not_found in handleIOErrors
* Format worker.actor.cpp file