You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2018/02/09 20:06:00 UTC

[jira] [Resolved] (IMPALA-3271) Remove deprecated command-line options (including Llama)

     [ https://issues.apache.org/jira/browse/IMPALA-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Armstrong resolved IMPALA-3271.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 3.0


IMPALA-3271: organise and warn on removed startup flags

Gather all the removed flags in a single place and establish consistent
behaviour.

If the flag is set, a warning is logged. GFlags are initialised before
logging, so the warning goes to stderr instead of the WARNING log.

The affected flags are:
be_service_threads, cgroup_hierarchy_path, enable_accept_queue_server,
enable_partitioned_aggregation, enable_partitioned_hash_join,
enable_phj_probe_side_filtering, enable_rm, llama_addresses,
llama_callback_port, llama_host, llama_max_request_attempts,
llama_port, llama_registration_timeout_secs,
llama_registration_wait_secs, local_nodemanager_url,
resource_broker_cnxn_attempts, resource_broker_cnxn_retry_interval_ms,
resource_broker_recv_timeout, resource_broker_send_timeout,
rm_always_use_defaults, rm_default_cpu_vcores, rm_default_memory,
rpc_cnxn_attempts, rpc_cnxn_retry_interval_ms, staging_cgroup,
suppress_unknown_disk_id_warnings, use_statestore,

Testing:
Ran "start-impala-cluster.py --impalad_args=--enable_rm=true"
and verified that the warning appeared in
logs/cluster/impalad-error.log

Cherry-picks: not for 2.x

Change-Id: Ic9bb4792e1b18840aa85aa5d755a09f2b5461f34
Reviewed-on: http://gerrit.cloudera.org:8080/9173
Reviewed-by: Tim Armstrong <ta...@cloudera.com>
Tested-by: Impala Public Jenkins
---

> Remove deprecated command-line options (including Llama)
> --------------------------------------------------------
>
>                 Key: IMPALA-3271
>                 URL: https://issues.apache.org/jira/browse/IMPALA-3271
>             Project: IMPALA
>          Issue Type: Task
>          Components: Backend
>    Affects Versions: Impala 2.3.0
>            Reporter: Matthew Jacobs
>            Assignee: Tim Armstrong
>            Priority: Minor
>              Labels: llama, resource-management
>             Fix For: Impala 3.0
>
>
> Llama has been unsupported as of Impala 2.3 (CDH 5.5), but it is still possible to start Impala with Llama integration enabled. For Impala 3.0 we can remove this support from the product. This will involve removing user-facing configurations (and related plumbing) that enables Llama to be used as it was before Impala 2.3.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)