robertsami

Results 4 comments of robertsami

a repro test to add to `raft_consensus-test.cc` ``` TEST_F(RaftConsensusTest, TestLastLeaderReceivedNotMinimum) { SetUpConsensus(kMinimumTerm, 3); SetUpGeneralExpectations(); ConsensusBootstrapInfo info; ASSERT_OK(consensus_->Start(info)); ConsensusRequestPB request; ConsensusResponsePB response; int64_t caller_term = 0; int64_t log_index = 0; caller_term...

we should probably introduce a GUC to modulate this behavior

open question: how do we inform the user that result set was capped? maybe a NOTICE log?

FYI -- we have moved towards the nomenclature of "wait-on-conflict" (FKA pessimistic locking) vs. "fail-on-conflict" (FKA optimistic locking). Issue details have been updated accordingly