impala-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Brown (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (IMPALA-3121) stress test should differentiate client <-> server and server <-> server connection errors
Date Tue, 25 Jul 2017 17:34:00 GMT

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

Michael Brown resolved IMPALA-3121.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 2.7.0

Stress test bug scrub: this was fixed https://gerrit.cloudera.org/#/c/2504/

> stress test should differentiate client <-> server and server <-> server
connection errors
> ------------------------------------------------------------------------------------------
>
>                 Key: IMPALA-3121
>                 URL: https://issues.apache.org/jira/browse/IMPALA-3121
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Infrastructure
>    Affects Versions: Impala 2.5.0
>            Reporter: Dan Hecht
>            Priority: Critical
>              Labels: stress
>             Fix For: Impala 2.7.0
>
>
> The stress test means to ignore client <-> server connection problems, but is also
now ignoring server <-> server connection problems that look have status like e.g.:
> Couldn't open transport for <host>:22000 (connect() failed: Connection timed out)
> We probably shouldn't filter these out too (or we should at least count them separately).
> Note that this would have started happening at change 61b8f6a which added the second
part to that message.



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

Mime
View raw message