[jira] [Assigned] (IMPALA-3978) Reword datastream timeout error message to highlight situations where changing the timeout makes sense

["Michael Smith (Jira)" <ji...@apache.org>]

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

Michael Smith reassigned IMPALA-3978:
-------------------------------------

    Assignee: Michael Smith  (was: Henry Robinson)

> Reword datastream timeout error message to highlight situations where changing the timeout makes sense
> ------------------------------------------------------------------------------------------------------
>
>                 Key: IMPALA-3978
>                 URL: https://issues.apache.org/jira/browse/IMPALA-3978
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Distributed Exec
>    Affects Versions: Impala 2.7.0
>            Reporter: Henry Robinson
>            Assignee: Michael Smith
>            Priority: Major
>
> This error message:
> {quote}
> Datastream sender timed-out waiting for recvr for fragment instance: 9f4cdc5cf9c63511:3ad1e5076f9a41e2 (time-out was: 2m). 
> Increase --datastream_sender_timeout_ms if you see this message frequently.
> {quote}
> is printed out no matter what the cause of the timeout. However, increasing the timeout only really makes sense if the system is overloaded, i.e. fragments are being started but they're taking a very long time. We should reword the message to make the clearer, so when timeouts are being hit due to failures, users don't think they have to reconfigure the system.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org