[ https://issues.apache.org/jira/browse/IMPALA-6818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Ho reassigned IMPALA-6818: ---------------------------------- Assignee: Michael Ho > 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 > Assignee: Michael Ho > Priority: Major > > 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 (e.g. when a host has a spike in load > and does not process the exec rpc for a while). 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) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org