You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Dan Hecht (JIRA)" <ji...@apache.org> on 2018/04/06 16:29:00 UTC

[jira] [Created] (IMPALA-6818) Rethink data-stream sender/receiver startup sequencing

Dan Hecht created IMPALA-6818:
---------------------------------

             Summary: Rethink data-stream sender/receiver startup sequencing
                 Key: IMPALA-6818
                 URL: https://issues.apache.org/jira/browse/IMPALA-6818
             Project: IMPALA
          Issue Type: Sub-task
          Components: Distributed Exec
            Reporter: Dan Hecht


IMPALA-1599 introduced parallel fragment startup, which is good for startup latency. However, it meant that data-stream senders can start before receivers, and there is a timeout to handle the case when the receiver never shows up:
{code:java}
Sender timed out waiting for receiver fragment instance{code}
We see this timeout fairly regularly. Let's rethink how this works to see if we can make it robust but being careful to not sacrifice startup time too much.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)