Move ProcessClass and ClusterRole out of fdbrpc#13399
Conversation
…e-process-class # Conflicts: # fdbrpc/Locality.cpp
Result of foundationdb-pr-clang-ide on Linux RHEL 9
|
Result of foundationdb-pr-macos-m1 on macOS 14.x
|
Result of foundationdb-pr-clang-arm on Linux RHEL 9
|
Result of foundationdb-pr-clang on Linux RHEL 9
|
Result of foundationdb-pr-macos on macOS 14.x
|
Result of foundationdb-pr on Linux RHEL 9
|
Result of foundationdb-pr-cluster-tests on Linux RHEL 9
|
gxglass
left a comment
There was a problem hiding this comment.
Local AI is saying a rebase is needed
…e-process-class # Conflicts: # fdbrpc/include/fdbrpc/Locality.h # fdbserver/clustercontroller/ClusterController.h # fdbserver/core/LeaderElection.cpp
Result of foundationdb-pr-clang-ide on Linux RHEL 9
|
Result of foundationdb-pr-clang-arm on Linux RHEL 9
|
Result of foundationdb-pr-macos-m1 on macOS 14.x
|
Result of foundationdb-pr on Linux RHEL 9
|
Result of foundationdb-pr-macos on macOS 14.x
|
Result of foundationdb-pr-clang on Linux RHEL 9
|
Result of foundationdb-pr-cluster-tests on Linux RHEL 9
|
Result of foundationdb-pr-clang-ide on Linux RHEL 9
|
Result of foundationdb-pr-macos-m1 on macOS 14.x
|
Result of foundationdb-pr-clang-arm on Linux RHEL 9
|
Result of foundationdb-pr on Linux RHEL 9
|
Result of foundationdb-pr-clang on Linux RHEL 9
|
Result of foundationdb-pr-cluster-tests on Linux RHEL 9
summary / time infofor f in fdb-kubernetes-/logs/.log); do check all fail typesfail_test=false Check for test failures where one or more tests have failed for a test suite.if grep -q -- "--- FAIL:" fdb-kubernetes-/logs/.log ; then Check for all tests that have not finished e.g. because they timed out or they paniced during the execution.for f in $(grep -L -- "SUCCESS! --" fdb-kubernetes-/logs/.log); do
|
Result of foundationdb-pr-macos on macOS 14.x
|
This PR builds on previous PRs to shrink
fdbrpcby extracting FDB-specific logic. This makes the library more generic and improves compilation times.The PR moves
ProcessClassintofdbclient, moves simulator-only process metadata intofdbserver/core, and places recruitment policy (ClusterRole,Fitness, andmachineClassFitness) infdbserver/core. This leavesfdbclientwith only the serialized process-class representation while removing FDB-specific server and simulation concepts fromfdbrpc.