You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Tsz Wo Nicholas Sze (JIRA)" <ji...@apache.org> on 2017/11/11 01:35:01 UTC

[jira] [Created] (RATIS-141) In RaftClientProtocolService, the assumption of consecutive callId is invalid

Tsz Wo Nicholas Sze created RATIS-141:
-----------------------------------------

             Summary: In RaftClientProtocolService, the assumption of consecutive callId is invalid
                 Key: RATIS-141
                 URL: https://issues.apache.org/jira/browse/RATIS-141
             Project: Ratis
          Issue Type: Bug
            Reporter: Tsz Wo Nicholas Sze


{code}
//RaftClientProtocolService.AppendRequestStreamObserver.onNext(..)

              // we assume the callId is consecutive for a stream RPC call
              final PendingAppend pendingForReply = pendingList.get(
                  (int) (replySeq - headSeqNum));
{code}
Call id is used for different kinds of calls (e.g. getInfo) so that it may not be consecutive.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)