[IMPALA-8121] Pick better default flags in containers

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Impala 3.3.0
• Component/s: Infrastructure
• Labels: docker
• Target Version: Impala 3.3.0
• Epic Color: ghx-label-2
• Assignee: Tim Armstrong
• Reporter: Tim Armstrong
• Created: 25/Jan/19 19:16
• Updated: 17/May/19 15:49
• Resolved: 17/May/19 15:49

Description

There are some new features of Impala that are done but disabled by default because they are not strictly better than the previous versions. E.g. the various metadata improvements. Containerised Impala is likely to be new deployments, so it is easier to make potentially disruptive changes to defaults now.

Metadata V2 Flags

Catalogd:
--catalog_topic_mode=minimal
Impalad:
--use_local_catalog=true

We want to invalidate based on HMS notifications (https://issues.apache.org/jira/browse/IMPALA-7970) and memory pressure. It's less clear if invalidating tables based on time is really useful - for large fact tables it would add a lot of unpredictability because reloading the tables is expensive.

Catalogd:
--invalidate_tables_timeout_s=???
--invalidate_tables_on_memory_pressure=true

Once IMPALA-7970 goes in, we probably also want automatic invalidation by default (TBD - how to handle older HMS that doesn't support those APIs).
Catalogd:
--hms_event_polling_interval_s=???

We probably want to enable HDFS preads for remote reads: -use_hdfs_pread - but I think this is going to be done automatically.

We may want to have an I/O cache enabled - tracked by IMPALA-8121

Issue Links

• relates to: IMPALA-5212 consider switching to pread by default