[jira] [Commented] (KUDU-1584) follower memory throttling results in error log messages on the leader

["Todd Lipcon (JIRA)" <ji...@apache.org>]

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

Todd Lipcon commented on KUDU-1584:
-----------------------------------

The issue seems to be in consensus_peers.cc:

{code}
  // Pass through errors we can respond to, like not found, since in that case
  // we will need to start a Tablet Copy. TODO: Handle DELETED response once implemented.
  if ((response_.has_error() &&
       response_.error().code() != TabletServerErrorPB::TABLET_NOT_FOUND) ||
      (response_.status().has_error() &&
       response_.status().error().code() == consensus::ConsensusErrorPB::CANNOT_PREPARE)) {
    // Again, let the queue know that the remote is still responsive, since we
    // will not be sending this error response through to the queue.
    queue_->NotifyPeerIsResponsiveDespiteError(peer_pb_.permanent_uuid());
    ProcessResponseError(StatusFromPB(response_.error().status()));
    return;
  }
{code}

The ProcessResponseError call should pass response_.status().error().status() in case !response_.has_error()


> follower memory throttling results in error log messages on the leader
> ----------------------------------------------------------------------
>
>                 Key: KUDU-1584
>                 URL: https://issues.apache.org/jira/browse/KUDU-1584
>             Project: Kudu
>          Issue Type: Bug
>            Reporter: Todd Lipcon
>
> W0828 22:07:42.156687 49842 consensus_peers.cc:333] T c3810e04cd5f4ce8aa8cef40bcf15e33 P f92dc14d005d45e08ab52cf8142ea5b1 -> Peer 83e1da1e50ac4fbb9efa3310d58bb8ef (e1216.halxg.cloudera.com:7050): Couldn't send request to peer 83e1da1e50ac4fbb9efa3310d58bb8ef for tablet c3810e04cd5f4ce8aa8cef40bcf15e33. Status: Runtime error: (unknown error code). Retrying in the next heartbeat period. Already tried 8 times.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)