[
https://issues.apache.org/jira/browse/IMPALA-4063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16679474#comment-16679474
]
ASF subversion and git services commented on IMPALA-4063:
---------------------------------------------------------
Commit d1aa1c009f62500ae2ee8cd915751b0d42bee911 in impala's branch
refs/heads/master from Michael Ho
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=d1aa1c0 ]
IMPALA-7828: A temporary workaround for flaky UDF test (test_mem_leak())
Before IMPALA-4063, the error message detected during
FragmentInstanceState::Close() was always lost. After
IMPALA-4063, we may sometimes get the error message in
FragmentInstanceState::Close(). It's non-deterministic
as the fragment instance thread may race with the query
state thread which reports the final status. The UDF test
currently tries to handle this non-determinism by using
"row_regex:.*" in the ERRORS section but it doesn't
always seem to work.
This change workarounds the issue by commenting out the
ERRORS section in udf-no-expr-rewrite.text for now.
The actual fix will be done in IMPALA-7829.
Change-Id: I6a55d5ad1a5a7278e7390f60854a8df28c1b9f28
Reviewed-on: http://gerrit.cloudera.org:8080/11900
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
