[ 
https://issues.apache.org/jira/browse/IMPALA-14616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18045748#comment-18045748
 ] 

ASF subversion and git services commented on IMPALA-14616:
----------------------------------------------------------

Commit 7bf9ba38eb3aae1bb310f0bfd74e00e787ac3106 in impala's branch 
refs/heads/master from Sai Hemanth Gantasala
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=7bf9ba38e ]

IMPALA-14616: Skip checking batch event processing metrics in
test_event_processor_status

When hierarchical event processing is enabled, there is no info about
the current event batch shown in the /events page. Note that event
batches are dispatched and processed later in parallel. The current
event batch info is actually showing the current batch that is being
dispatched which won't take long.

This patch skips checking the current event batch info when hierarchical
event processing is enabled.

Tests
 - Verified that test runs fine locally.

Change-Id: I2df24d2fd3b028a84d557e70141e68aa234908d4
Reviewed-on: http://gerrit.cloudera.org:8080/23790
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> TestWebPage.test_event_processor_status is failing
> --------------------------------------------------
>
>                 Key: IMPALA-14616
>                 URL: https://issues.apache.org/jira/browse/IMPALA-14616
>             Project: IMPALA
>          Issue Type: Bug
>            Reporter: Surya Hebbar
>            Assignee: Sai Hemanth Gantasala
>            Priority: Major
>
> h3. Error Message
> {code}
> Failed: Timeout >7200s
> {code}
> h3. Stacktrace
> {code}
> custom_cluster/test_web_pages.py:457: in test_event_processor_status
>     time.sleep(1)
> E   Failed: Timeout >7200s
> {code}
> The error might be stemming for the same reason as IMPALA-14615.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to