[ 
https://issues.apache.org/jira/browse/KUDU-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16396330#comment-16396330
 ] 

Alexey Serbin commented on KUDU-2335:
-------------------------------------

[~tlipcon] I don't think that would lead to some inconsistency down the road in 
the code around that DCHECK, if the issue itself doesn't signal on an 
inconsistency at some other point.  So, I would not consider that DCHECK() as a 
blocker for 1.7.

> Debug assert in quorum_util.cc
> ------------------------------
>
>                 Key: KUDU-2335
>                 URL: https://issues.apache.org/jira/browse/KUDU-2335
>             Project: Kudu
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 1.7.0
>            Reporter: Alexey Serbin
>            Priority: Major
>
> The following DCHECK triggered in one of pre-commit builds with TSAN 
> configuration while running 
> {{DeleteTabletITest::TestLeaderElectionDuringDeleteTablet}} scenario:
> {noformat}
> quorum_util.cc:509] Check failed: peer_uuid != leader_uuid || healthy 
> 839fda3822054564af4a3dd547beaca1: leader reported as not healthy; config: 
> opid_index: -1 OBSOLETE_local: false peers { permanent_uuid: 
> "bb39501070104f769870f437f991970e" member_type: VOTER last_known_addr { host: 
> "127.8.86.130" port: 52021 } } peers { permanent_uuid: 
> "839fda3822054564af4a3dd547beaca1" member_type: VOTER last_known_addr { host: 
> "127.8.86.129" port: 37815 } } peers { permanent_uuid: 
> "150b2dd2788f407e8537d28a21d83a80" member_type: VOTER last_known_addr { host: 
> "127.8.86.131" port: 39431 } }{noformat}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to