impala-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henry Robinson (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (IMPALA-5345) Under stress, some TransmitData() RPCs are not responded to
Date Sat, 10 Jun 2017 05:06:20 GMT

     [ https://issues.apache.org/jira/browse/IMPALA-5345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Henry Robinson resolved IMPALA-5345.
------------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 2.10.0

Can't reproduce this on either a 20-node or 140-node cluster since I fixed KUDU-2041. My guess
is that connection deadlock looked like a half-complete RPC failure. Have to run stress as
well to confirm, but current indication is that this is fixed.

> Under stress, some TransmitData() RPCs are not responded to
> -----------------------------------------------------------
>
>                 Key: IMPALA-5345
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5345
>             Project: IMPALA
>          Issue Type: Sub-task
>    Affects Versions: Impala 2.10.0
>            Reporter: Henry Robinson
>            Assignee: Henry Robinson
>            Priority: Critical
>             Fix For: Impala 2.10.0
>
>
> Under stress conditions on two separate clusters (one secure, one not), I've seen some
{{TransmitData()}} RPCs stay unresponded to forever, blocking the query's completion. The
RPCs are seen by the recipient, but are not in the pending sender list.
> Need to test further to see if this is related to the fix for IMPALA-5093 or if a response
is dropped on some path if an row batch is 'retried' from the pending sender list. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message