[
https://issues.apache.org/jira/browse/IMPALA-9354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fang-Yu Rao updated IMPALA-9354:
--------------------------------
Description:
The E2E test {{test_concurrent_create_kudu_table}} seems flaky when
{{ERASURE_CODING}} is set to true. This test was recently added in the patch
for https://issues.apache.org/jira/browse/IMPALA-8984. According to the error
message, it seems that some error occurred when
[https://github.com/apache/impala/blob/master/tests/custom_cluster/test_concurrent_kudu_create.py#L62]
is called. The stacktrace is also provided in the following.
{code:java}
Stacktrace
custom_cluster/test_concurrent_kudu_create.py:62: in
test_concurrent_create_kudu_table
r3.get()
/usr/lib64/python2.7/multiprocessing/pool.py:554: in get
raise self._value
E ImpalaBeeswaxException: ImpalaBeeswaxException:
E Not connected
{code}
Since [~stigahuang] and [~vihangk1] reviewed the patch for
https://issues.apache.org/jira/browse/IMPALA-8984, maybe you could provide some
insight into this issue? The JIRA is assigned to [~stigahuang] for now, but
please re-assign it to others as appropriate. Thanks!
was:
The E2E test {{test_concurrent_create_kudu_table}} seems flaky when
{{ERASURE_CODING}} is set to true. This test was recently added in the patch
for https://issues.apache.org/jira/browse/IMPALA-8984. According to the error
message, it seems that some error occurred when executing
[https://github.com/apache/impala/blob/master/tests/custom_cluster/test_concurrent_kudu_create.py#L62].
The stacktrace is also provided in the following.
{code:java}
Stacktrace
custom_cluster/test_concurrent_kudu_create.py:62: in
test_concurrent_create_kudu_table
r3.get()
/usr/lib64/python2.7/multiprocessing/pool.py:554: in get
raise self._value
E ImpalaBeeswaxException: ImpalaBeeswaxException:
E Not connected
{code}
Since [~stigahuang] and [~vihangk1] reviewed the patch for
https://issues.apache.org/jira/browse/IMPALA-8984, maybe you could provide some
insight into this issue? The JIRA is assigned to [~stigahuang] for now, but
please re-assign it to others as appropriate. Thanks!
> The E2E test test_concurrent_create_kudu_table seems flaky when
> ERASURE_CODING is set to true
> ---------------------------------------------------------------------------------------------
>
> Key: IMPALA-9354
> URL: https://issues.apache.org/jira/browse/IMPALA-9354
> Project: IMPALA
> Issue Type: Bug
> Reporter: Fang-Yu Rao
> Assignee: Quanlong Huang
> Priority: Blocker
> Labels: broken-build
>
> The E2E test {{test_concurrent_create_kudu_table}} seems flaky when
> {{ERASURE_CODING}} is set to true. This test was recently added in the patch
> for https://issues.apache.org/jira/browse/IMPALA-8984. According to the error
> message, it seems that some error occurred when
> [https://github.com/apache/impala/blob/master/tests/custom_cluster/test_concurrent_kudu_create.py#L62]
> is called. The stacktrace is also provided in the following.
> {code:java}
> Stacktrace
> custom_cluster/test_concurrent_kudu_create.py:62: in
> test_concurrent_create_kudu_table
> r3.get()
> /usr/lib64/python2.7/multiprocessing/pool.py:554: in get
> raise self._value
> E ImpalaBeeswaxException: ImpalaBeeswaxException:
> E Not connected
> {code}
> Since [~stigahuang] and [~vihangk1] reviewed the patch for
> https://issues.apache.org/jira/browse/IMPALA-8984, maybe you could provide
> some insight into this issue? The JIRA is assigned to [~stigahuang] for now,
> but please re-assign it to others as appropriate. Thanks!
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
