[ https://issues.apache.org/jira/browse/IMPALA-4063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Ho resolved IMPALA-4063. -------------------------------- Resolution: Fixed Fix Version/s: Impala 3.2.0 The proposed release of Impala 3.1.0 will not include the fix of IMPALA-7213 which the fix of this Jira is dependent on. So marking the fix version as 3.2.0 for now. > Make fragment instance reports per-query (or per-host) instead of > per-fragment instance. > ---------------------------------------------------------------------------------------- > > Key: IMPALA-4063 > URL: https://issues.apache.org/jira/browse/IMPALA-4063 > Project: IMPALA > Issue Type: Sub-task > Components: Distributed Exec > Affects Versions: Impala 2.7.0 > Reporter: Sailesh Mukil > Assignee: Michael Ho > Priority: Major > Labels: impala-scalability-sprint-08-13-2018, performance > Fix For: Impala 3.2.0 > > > Currently we send a report per-fragment instance to the coordinator every 5 > seconds (by default; modifiable via query option 'status_report_interval'). > For queries with a large number of fragment instances, this generates > tremendous amounts of network traffic to the coordinator, which will only be > aggravated with higher a DOP. > We should instead queue per-fragment instance reports and send out a > per-query report to the coordinator instead. > For code references, see: > PlanFragmentExecutor:: ReportProfile() > PlanFragmentExecutor:: SendReport() > FragmentExecState:: ReportStatusCb() -- This message was sent by Atlassian JIRA (v7.6.3#76005)