Alexey Serbin created KUDU-3667:
-----------------------------------
Summary: ScanTokenStaleRaftMembershipTest.TabletLeaderChange
sometimes fails
Key: KUDU-3667
URL: https://issues.apache.org/jira/browse/KUDU-3667
Project: Kudu
Issue Type: Bug
Components: test
Reporter: Alexey Serbin
Attachments: scan_token-test.txt.xz
The ScanTokenStaleRaftMembershipTest.TabletLeaderChange scenario sometimes
fails with error message like below:
{noformat}
src/kudu/client/scan_token-test.cc:1726: Failure
Expected: (new_leader_tsd->uuid()) != (leader_tsd->uuid()), actual:
"72e54c14991346fb8fa1a91a53e3bb6f" vs "72e54c14991346fb8fa1a91a53e3bb6f"
{noformat}
This seems to be a benign test-only issue manifesting itself mostly in TSAN
builds stemming from the following:
# No new leader UUID for LeaderStepDown() is given in this scenario
# In case of scheduler anomalies when the other tablet replicas aren't
responsive for quite a long time, the former tablet leader might be the first
sending out vote request even after snoozing its leader failure detector.
Full log (TSAN build) is attached.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
