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

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

Ah, [~mpercy] has a good idea on how to address this: let's just return 
{{false}} in the condition that now is triggering that DCHECK.  I think that 
should address the issue. I believe it's kind of intermittent fluke, so it's 
not going to stay around for long.  At least, adding 'return' in that case will 
give us more consistency in the resulting code.

I think that's a good idea given our current roadmap of branding for 1.7 today.

Meanwhile, we can dig in and find the root cause of this and have a fix at our 
leisure.

> 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