[IMPALA-8627] Re-enable catalog v2 in containers

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Impala 3.3.0
• Fix Version/s: Impala 3.3.0
• Component/s: Infrastructure
• Labels: catalog-v2
• Target Version: Impala 3.3.0
• Epic Color: ghx-label-3
• Assignee: Vihang Karajgaonkar
• Reporter: Tim Armstrong
• Created: 05/Jun/19 22:22
• Updated: 23/Sep/19 08:54
• Resolved: 08/Aug/19 18:28

Description

We also need to set --invalidate_tables_on_memory_pressure on the impalads for that to be fully effective - the impalads send table usage info to the catalogd

Issue Links

• depends upon: IMPALA-7534 Handle invalidation races in CatalogdMetaProvider cache
• depends upon: IMPALA-8633 Insert event should not error when table does not exists
• depends upon: IMPALA-8715 Test failures when catalogv2 is enabled
• depends upon: IMPALA-8906 TestObservability.test_query_profile_contains_query_compilation_metadata_load_events is flaky
• is depended upon by: IMPALA-8822 No metadata loading information in query profile when Catalog V2 enabled
• is duplicated by: IMPALA-8660 Enable Event processing by default Impala e2e tests
• relates to: IMPALA-8567 Many random catalog consistency issues with catalog v2/event processor