[
https://issues.apache.org/jira/browse/IMPALA-8121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong updated IMPALA-8121:
----------------------------------
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.
h2. Metadata V2 Flags
Catalogd:
--catalog_topic_mode=minimal
Impalad:
--use_local_catalog=true
I think we *may* also want to configure automatic invalidations of tables from
the catalogd so that changes to the underlying storage cluster are eventually
reflected in the compute cluster. There's a better solution in the pipeline
that uses HMS notifications
(https://issues.apache.org/jira/browse/IMPALA-7970), but in the meantime
invalidation is time-based.
Catalogd:
--invalidate_tables_timeout_s=3600
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
We may want to have an I/O cache enabled
was:
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.
h2. Metadata V2 Flags
Catalogd:
--catalog_topic_mode=minimal
Impalad:
--use_local_catalog=true
I think we *may* also want to configure automatic invalidations of tables from
the catalogd so that changes to the underlying storage cluster are eventually
reflected in the compute cluster. There's a better solution in the pipeline
that uses HMS notifications
(https://issues.apache.org/jira/browse/IMPALA-7970), but in the meantime
invalidation is time-based.
Catalogd:
--invalidate_tables_timeout_s=3600
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
> Pick better default flags in containers
> ---------------------------------------
>
> Key: IMPALA-8121
> URL: https://issues.apache.org/jira/browse/IMPALA-8121
> Project: IMPALA
> Issue Type: Sub-task
> Components: Infrastructure
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Major
>
> 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.
> h2. Metadata V2 Flags
> Catalogd:
> --catalog_topic_mode=minimal
> Impalad:
> --use_local_catalog=true
> I think we *may* also want to configure automatic invalidations of tables
> from the catalogd so that changes to the underlying storage cluster are
> eventually reflected in the compute cluster. There's a better solution in the
> pipeline that uses HMS notifications
> (https://issues.apache.org/jira/browse/IMPALA-7970), but in the meantime
> invalidation is time-based.
> Catalogd:
> --invalidate_tables_timeout_s=3600
> 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
> We may want to have an I/O cache enabled
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
