You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Xu Shao Hong (Jira)" <ji...@apache.org> on 2021/11/29 06:07:00 UTC

[jira] [Created] (RATIS-1446) should avoid NPE in yieldLeaderToHigherPriorityPeer

Xu Shao Hong created RATIS-1446:
-----------------------------------

             Summary: should avoid NPE in yieldLeaderToHigherPriorityPeer
                 Key: RATIS-1446
                 URL: https://issues.apache.org/jira/browse/RATIS-1446
             Project: Ratis
          Issue Type: Bug
            Reporter: Xu Shao Hong


 
{code:java}
1private void yieldLeaderToHigherPriorityPeer() {
2  if (!server.getInfo().isLeader()) {
3    return;
4  }

5  final RaftConfigurationImpl conf = server.getRaftConf();
6  int leaderPriority = conf.getPeer(server.getId()).getPriority(); {code}
During my test in k8s env, I met the corner case where the ozone progress met NPE and was shut down. The log shows it is thrown at line 6. It is possible in some cases configuration may not include the server itself. The case happened when bootstrapping the second SCM. Thus there should have a null check before getPriority.

 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)