[
https://issues.apache.org/jira/browse/KUDU-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905783#comment-15905783
]
David Alves commented on KUDU-1927:
-----------------------------------
[~adar] thanks for pointing that out, I missed it.
Tbh even if it was by design, I still think it's problematic because it's
unexpected. I've seen code (in-flight patch) that missed that subtlety.
Curious: Why not just initialized leader_status_ (maybe even both) to non-OK
until we check and make sure it's actually fine?
> Potential race handling ConnectToMaster RPCs during leader transition
> ---------------------------------------------------------------------
>
> Key: KUDU-1927
> URL: https://issues.apache.org/jira/browse/KUDU-1927
> Project: Kudu
> Issue Type: Bug
> Components: master, security
> Affects Versions: 1.3.0
> Reporter: Todd Lipcon
>
> MasterServiceImpl::ConnectToMaster currently has a TODO that there might be a
> case where a client issues the RPC exactly as a leader is becoming active.
> The worry is that it may return a response indicating LEADER status, but
> without the ability to issue a key.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
