[
https://issues.apache.org/jira/browse/IMPALA-8278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vihang Karajgaonkar updated IMPALA-8278:
----------------------------------------
Summary: Fix MetastoreEventsProcessorTest flakiness (was: Fix
testEventProcessorFetchAfterHMSRestart)
> Fix MetastoreEventsProcessorTest flakiness
> ------------------------------------------
>
> Key: IMPALA-8278
> URL: https://issues.apache.org/jira/browse/IMPALA-8278
> Project: IMPALA
> Issue Type: Sub-task
> Reporter: Vihang Karajgaonkar
> Assignee: Vihang Karajgaonkar
> Priority: Major
>
> {{testEventProcessorFetchAfterHMSRestart}} test case in
> {{MetastoreEventsProcessorTest}} causes flakiness because it creates a new
> event processor pointing to the same the catalog instance. This means that
> all the events generated are now being processed by two events processor
> instances and they both try to modify the state of catalogd causing race
> conditions. The failures vary and depend a lot on the timing. I see the
> following exception which is related to this issue.
> Easiest way to figure out if this is a problem is to look into FeSupport logs
> of the test to confirm if a event ID is being processed twice (i.e you see to
> exactly similar logs for a given event id).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
