[IMPALA-12832] EventProcessor shouldn't stop for failures in single-table event

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: Impala 4.4.0
• Component/s: Catalog
• Epic Link: event-processor-completeness
• Epic Color: ghx-label-11
• Assignee: Venugopal Reddy K
• Reporter: Quanlong Huang
• Created: 22/Feb/24 04:02
• Updated: 21/Mar/24 11:16
• Resolved: 08/Mar/24 16:24

Description

EventProcessor goes into the ERROR/NEEDS_INVALIDATE state when it hits unexpected failures in processing an event. The cause are usually bugs. When it stops, all tables that need sync will be impacted. However, the event might just a single-table event (in contrast to multi-table events like RenameTable, DropDatabaseCascade, CommitTxn, AbortTxn). We can consider skipping the event and just invalidating the table.

Issue Links

• causes: IMPALA-12916 TestEventProcessingError.test_event_processor_error_global_invalidate fails in some builds
• causes: IMPALA-12917 Several tests in TestEventProcessingError fail