[
https://issues.apache.org/jira/browse/IMPALA-9553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17067203#comment-17067203
]
Tim Armstrong commented on IMPALA-9553:
---------------------------------------
I think this could be a manifestation of IMPALA-1995 if the number or location
of input splits is different to what we expected.
> Test flaky with HBase: PlannerTest.testResourceRequirements
> -----------------------------------------------------------
>
> Key: IMPALA-9553
> URL: https://issues.apache.org/jira/browse/IMPALA-9553
> Project: IMPALA
> Issue Type: Bug
> Reporter: Csaba Ringhofer
> Priority: Critical
> Labels: flaky-test
>
> The following test seems flaky in the last few days (since 2020.03.23):
> org.apache.impala.planner.PlannerTest.testResourceRequirements
> Section PARALLELPLANS of query:
> select * from functional_hbase.alltypessmall
> Expected:
> Max Per-Host Resource Reservation: Memory=0B Threads=2
> Actual:
> Max Per-Host Resource Reservation: Memory=0B Threads=3
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
