[jira] [Updated] (AMBARI-21722) Begin Using Service Versions In Python stack_feature Code
[
https://issues.apache.org/jira/browse/AMBARI-21722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21722:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Begin Using Service Versions In Python stack_feature Code
> -
>
> Key: AMBARI-21722
> URL: https://issues.apache.org/jira/browse/AMBARI-21722
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21722.patch
>
>
> The command generators in Ambari are sending down the
> {{KeyName.CURRENT_VERSION}} ({{current_version}}) property in the JSON to the
> agents. This is being used to determine the "current cluster version" which
> doesn't really exist anymore:
> {code:title=stack_features.py}
> # something like 2.4.0.0-1234
> # (or None if this is a cluster install and it hasn't been calculated yet)
> current_cluster_version = default("/hostLevelParams/current_version", None)
> {code}
> This really needs to be calculated from the service's repository version
> instead.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21045) Enable Storm's AutoTGT configs in secure mode
[ https://issues.apache.org/jira/browse/AMBARI-21045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128182#comment-16128182 ] Hudson commented on AMBARI-21045: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1811 (See [https://builds.apache.org/job/Ambari-branch-2.5/1811/]) AMBARI-21045. Enable Storm's AutoTGT configs in secure mode (Sriharsha (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d7b2d856632fa2614ba2d2b153c8717ed4390d66]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/stack_advisor.py * (delete) ambari-server/src/main/resources/common-services/STORM/1.1.0/configuration/storm-site.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml * (add) ambari-server/src/main/resources/common-services/STORM/1.1.0/configuration/storm-env.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml > Enable Storm's AutoTGT configs in secure mode > - > > Key: AMBARI-21045 > URL: https://issues.apache.org/jira/browse/AMBARI-21045 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21045-2.5-maint.patch, > AMBARI-21045.branch-2.5.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21723) Redundant type arguments (Java 8)
[
https://issues.apache.org/jira/browse/AMBARI-21723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128161#comment-16128161
]
Hadoop QA commented on AMBARI-21723:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12881930/AMBARI-21723.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 188
new or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12000//console
This message is automatically generated.
> Redundant type arguments (Java 8)
> -
>
> Key: AMBARI-21723
> URL: https://issues.apache.org/jira/browse/AMBARI-21723
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-21723.patch
>
>
> Ambari Server is now built with Java 8, which can infer more type arguments
> than Java 7.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21045) Enable Storm's AutoTGT configs in secure mode
[ https://issues.apache.org/jira/browse/AMBARI-21045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128156#comment-16128156 ] Hudson commented on AMBARI-21045: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1810 (See [https://builds.apache.org/job/Ambari-branch-2.5/1810/]) Revert "AMBARI-21045. AMBARI-21045. Enable Storm's AutoTGT configs in (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=96e5ea566037e7874e815000966495145974f69c]) * (delete) ambari-server/src/main/resources/common-services/STORM/1.1.0/configuration/storm-env.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog251.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml * (add) ambari-server/src/main/resources/common-services/STORM/1.1.0/configuration/storm-site.xml * (edit) ambari-server/src/main/resources/stacks/stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml > Enable Storm's AutoTGT configs in secure mode > - > > Key: AMBARI-21045 > URL: https://issues.apache.org/jira/browse/AMBARI-21045 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21045-2.5-maint.patch, > AMBARI-21045.branch-2.5.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21728) Service and Patch Upgrade Catalog Changes for 2.6 - additional fixes
[
https://issues.apache.org/jira/browse/AMBARI-21728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128104#comment-16128104
]
Hadoop QA commented on AMBARI-21728:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12881941/AMBARI-21728.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11999//console
This message is automatically generated.
> Service and Patch Upgrade Catalog Changes for 2.6 - additional fixes
> -
>
> Key: AMBARI-21728
> URL: https://issues.apache.org/jira/browse/AMBARI-21728
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21728.patch
>
>
> Things missing:
> - Address Jonathan's comment at https://reviews.apache.org/r/61503/
> - Oracle DB support
> - Test coverage for AMBARI-21169
> - Prepare patch for trunk (forward-port an upgrade catalog)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21729) Owner of yarn.include stays to be root:root where as dfs.include gets changed to the correct one upon restart services
[
https://issues.apache.org/jira/browse/AMBARI-21729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128101#comment-16128101
]
Hadoop QA commented on AMBARI-21729:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12881948/AMBARI-21729.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/11998//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11998//console
This message is automatically generated.
> Owner of yarn.include stays to be root:root where as dfs.include gets changed
> to the correct one upon restart services
> --
>
> Key: AMBARI-21729
> URL: https://issues.apache.org/jira/browse/AMBARI-21729
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin
>Affects Versions: 2.5.2
>Reporter: Dhanya Balasundaran
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21729.patch
>
>
> - After deployment, create dfs.include and yarn.include in /etc/hadoop/conf
> as root user itself. - Set manage.include.files to true for HDFS and YARN and
> update dfs.hosts and yarn.resourcemanager.nodes.include-path properties
> - Restart services
> - After services are restrated dfs.include gets the right owner
> (:hadoop) where as yarn.include still has root:root
> - Noticed that owner of dfs.include is updated during Namenode restart but
> yarn.include is not updated after restart of all services that had stale
> configs
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21325) Ability to switch Quick Links to use Service URL through Knox or given proxy
[
https://issues.apache.org/jira/browse/AMBARI-21325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128054#comment-16128054
]
Hadoop QA commented on AMBARI-21325:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12881859/AMBARI-21325.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server ambari-web:
org.apache.ambari.server.state.UpgradeHelperTest
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11997//console
This message is automatically generated.
> Ability to switch Quick Links to use Service URL through Knox or given proxy
>
>
> Key: AMBARI-21325
> URL: https://issues.apache.org/jira/browse/AMBARI-21325
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: trunk, 2.5.2, 2.5.3
>Reporter: Jeffrey E Rodriguez
>Assignee: Chandana Mirashi
> Attachments: AMBARI-21325.patch
>
> Original Estimate: 336h
> Remaining Estimate: 336h
>
> Knox has the ability to proxy Hadoop user interfaces URL. Having the ability
> to setup Quicklinks through Knox so instead of for example going to "Hbase
> Master UI" directly we can proxy through Knox for example:
> http://hdpjeff1.fyre.ibm.com:16010/master-status
> can be instead go through:
> https://hdpjeff1.fyre.ibm.com:8443/gateway/default/hbase/hbaseui/master-status
> Here https://hdpjeff1.fyre.ibm.com:8443/gateway is the Knox gateway URL.
> This will bring authentication to the UI access and would secure the UI
> access.
> Ideally this behavior can be set as secure going through proxy by default or
> it can be turn off to go directly by Ambari Admin.
> Changes added:
> 1. Add new json properties knox_url, knox_path, supports_knox
>a. knox_url: template to be used for urls that are proxied through Knox
>b. knox_path: Knox gateway path that will be added to the proxy url.
>c. supports_knox: whether link will be redirected through Knox
> 2. Add above json properties to quicklinks.json
> 3. Add HDFSUI & DATANODE,YARNUI & NODEUI, JOBHISTORYUI, HBASEUI, OOZIEUI,
> SPARKUI services to Knox topology template.
> 4. Automate protocol and port added to Knox topology file. Based on whether
> SSL is enabled for the services listed above, the port and protocol in
> params_linux.py will be updated.
> 5. Update quick_view_link_view.js so that when Knox is installed and
> support_knox is true, quicklink url follows knox url template specified in
> the quicklinks.json for the service/component.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21045) Enable Storm's AutoTGT configs in secure mode
[ https://issues.apache.org/jira/browse/AMBARI-21045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128053#comment-16128053 ] Hudson commented on AMBARI-21045: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1809 (See [https://builds.apache.org/job/Ambari-branch-2.5/1809/]) AMBARI-21045. AMBARI-21045. Enable Storm's AutoTGT configs in secure (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3d07ec5a091de3735e63c5500c380612e6533baa]) * (add) ambari-server/src/main/resources/common-services/STORM/1.1.0/configuration/storm-env.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/config-upgrade.xml * (delete) ambari-server/src/main/resources/common-services/STORM/1.1.0/configuration/storm-site.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/stack_advisor.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog251.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/stack_advisor.py > Enable Storm's AutoTGT configs in secure mode > - > > Key: AMBARI-21045 > URL: https://issues.apache.org/jira/browse/AMBARI-21045 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21045-2.5-maint.patch, > AMBARI-21045.branch-2.5.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21045) Enable Storm's AutoTGT configs in secure mode
[ https://issues.apache.org/jira/browse/AMBARI-21045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128016#comment-16128016 ] Sumit Mohanty commented on AMBARI-21045: https://issues.apache.org/jira/secure/attachment/12882035/AMBARI-21045-2.5-maint.patch is good for backport +1 > Enable Storm's AutoTGT configs in secure mode > - > > Key: AMBARI-21045 > URL: https://issues.apache.org/jira/browse/AMBARI-21045 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21045-2.5-maint.patch, > AMBARI-21045.branch-2.5.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21045) Enable Storm's AutoTGT configs in secure mode
[ https://issues.apache.org/jira/browse/AMBARI-21045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-21045: Attachment: AMBARI-21045-2.5-maint.patch > Enable Storm's AutoTGT configs in secure mode > - > > Key: AMBARI-21045 > URL: https://issues.apache.org/jira/browse/AMBARI-21045 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21045-2.5-maint.patch, > AMBARI-21045.branch-2.5.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21722) Begin Using Service Versions In Python stack_feature Code
[
https://issues.apache.org/jira/browse/AMBARI-21722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127992#comment-16127992
]
Hadoop QA commented on AMBARI-21722:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12882009/AMBARI-21722.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11996//console
This message is automatically generated.
> Begin Using Service Versions In Python stack_feature Code
> -
>
> Key: AMBARI-21722
> URL: https://issues.apache.org/jira/browse/AMBARI-21722
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21722.patch
>
>
> The command generators in Ambari are sending down the
> {{KeyName.CURRENT_VERSION}} ({{current_version}}) property in the JSON to the
> agents. This is being used to determine the "current cluster version" which
> doesn't really exist anymore:
> {code:title=stack_features.py}
> # something like 2.4.0.0-1234
> # (or None if this is a cluster install and it hasn't been calculated yet)
> current_cluster_version = default("/hostLevelParams/current_version", None)
> {code}
> This really needs to be calculated from the service's repository version
> instead.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21657) Ambari does not display metric data on widgets when the JMX path contains the '-' character.
[
https://issues.apache.org/jira/browse/AMBARI-21657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127966#comment-16127966
]
Hudson commented on AMBARI-21657:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7889 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7889/])
AMBARI-21657 : Ambari does not display metric data on widgets when the
(avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=78793366447c59db8c6deac3c1ce3b69da8ed268])
* (edit) ambari-web/app/mixins/common/widgets/widget_mixin.js
> Ambari does not display metric data on widgets when the JMX path contains the
> '-' character.
>
>
> Key: AMBARI-21657
> URL: https://issues.apache.org/jira/browse/AMBARI-21657
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.6.0
>
> Attachments: AMBARI-21657.patch
>
>
> {code}
> "name" : "Hadoop:service=azure-file-system,name=AzureFileSystemMetrics4",
> "modelerType" : "AzureFileSystemMetrics4",
> "tag.Context" : "azureFileSystem",
> "tag.wasbFileSystemId" : "24f05882-a63a-43d4-9dec-eff23f9fcfa0",
> "tag.accountName" : "<>",
> "tag.containerName" : "xhdinsight-2017-07-24t21-26-36-619z",
> "tag.Hostname" : "zk2-xhdins",
> "wasb_web_responses" : 87824,
> "wasb_files_created" : 8
> {code}
> For example, the above metrics cannot be displayed on widgets due to the '-'
> in *Hadoop:service=azure-file-system,name=AzureFileSystemMetrics4*.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21657) Ambari does not display metric data on widgets when the JMX path contains the '-' character.
[
https://issues.apache.org/jira/browse/AMBARI-21657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127952#comment-16127952
]
Hudson commented on AMBARI-21657:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #13 (See
[https://builds.apache.org/job/Ambari-branch-2.6/13/])
AMBARI-21657 : Ambari does not display metric data on widgets when the
(avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2d1af8e4fe0158a38c0c77e92330e266fd44ba84])
* (edit) ambari-web/app/mixins/common/widgets/widget_mixin.js
> Ambari does not display metric data on widgets when the JMX path contains the
> '-' character.
>
>
> Key: AMBARI-21657
> URL: https://issues.apache.org/jira/browse/AMBARI-21657
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.6.0
>
> Attachments: AMBARI-21657.patch
>
>
> {code}
> "name" : "Hadoop:service=azure-file-system,name=AzureFileSystemMetrics4",
> "modelerType" : "AzureFileSystemMetrics4",
> "tag.Context" : "azureFileSystem",
> "tag.wasbFileSystemId" : "24f05882-a63a-43d4-9dec-eff23f9fcfa0",
> "tag.accountName" : "<>",
> "tag.containerName" : "xhdinsight-2017-07-24t21-26-36-619z",
> "tag.Hostname" : "zk2-xhdins",
> "wasb_web_responses" : 87824,
> "wasb_files_created" : 8
> {code}
> For example, the above metrics cannot be displayed on widgets due to the '-'
> in *Hadoop:service=azure-file-system,name=AzureFileSystemMetrics4*.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-21657) Ambari does not display metric data on widgets when the JMX path contains the '-' character.
[
https://issues.apache.org/jira/browse/AMBARI-21657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan resolved AMBARI-21657.
Resolution: Fixed
Pushed to branch-2.6 and trunk.
> Ambari does not display metric data on widgets when the JMX path contains the
> '-' character.
>
>
> Key: AMBARI-21657
> URL: https://issues.apache.org/jira/browse/AMBARI-21657
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.6.0
>
> Attachments: AMBARI-21657.patch
>
>
> {code}
> "name" : "Hadoop:service=azure-file-system,name=AzureFileSystemMetrics4",
> "modelerType" : "AzureFileSystemMetrics4",
> "tag.Context" : "azureFileSystem",
> "tag.wasbFileSystemId" : "24f05882-a63a-43d4-9dec-eff23f9fcfa0",
> "tag.accountName" : "<>",
> "tag.containerName" : "xhdinsight-2017-07-24t21-26-36-619z",
> "tag.Hostname" : "zk2-xhdins",
> "wasb_web_responses" : 87824,
> "wasb_files_created" : 8
> {code}
> For example, the above metrics cannot be displayed on widgets due to the '-'
> in *Hadoop:service=azure-file-system,name=AzureFileSystemMetrics4*.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21722) Begin Using Service Versions In Python stack_feature Code
[
https://issues.apache.org/jira/browse/AMBARI-21722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21722:
-
Attachment: AMBARI-21722.patch
> Begin Using Service Versions In Python stack_feature Code
> -
>
> Key: AMBARI-21722
> URL: https://issues.apache.org/jira/browse/AMBARI-21722
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21722.patch
>
>
> The command generators in Ambari are sending down the
> {{KeyName.CURRENT_VERSION}} ({{current_version}}) property in the JSON to the
> agents. This is being used to determine the "current cluster version" which
> doesn't really exist anymore:
> {code:title=stack_features.py}
> # something like 2.4.0.0-1234
> # (or None if this is a cluster install and it hasn't been calculated yet)
> current_cluster_version = default("/hostLevelParams/current_version", None)
> {code}
> This really needs to be calculated from the service's repository version
> instead.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21722) Begin Using Service Versions In Python stack_feature Code
[
https://issues.apache.org/jira/browse/AMBARI-21722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21722:
-
Status: Patch Available (was: Open)
> Begin Using Service Versions In Python stack_feature Code
> -
>
> Key: AMBARI-21722
> URL: https://issues.apache.org/jira/browse/AMBARI-21722
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21722.patch
>
>
> The command generators in Ambari are sending down the
> {{KeyName.CURRENT_VERSION}} ({{current_version}}) property in the JSON to the
> agents. This is being used to determine the "current cluster version" which
> doesn't really exist anymore:
> {code:title=stack_features.py}
> # something like 2.4.0.0-1234
> # (or None if this is a cluster install and it hasn't been calculated yet)
> current_cluster_version = default("/hostLevelParams/current_version", None)
> {code}
> This really needs to be calculated from the service's repository version
> instead.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21730) Default of hive.llap.execution.mode=only on Hive Interactive breaks StorageHandler tables.
[
https://issues.apache.org/jira/browse/AMBARI-21730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127849#comment-16127849
]
Xabriel J Collazo Mojica commented on AMBARI-21730:
---
A quote from the Hive Jira in which folks point to {{auto}} as the mode to use
when a user is not sure whether LLAP can be leveraged or not:
bq. If the user is not sure if they can run in llap, they need to use mode =
auto. The mode = all behavior only prevents further checking on the query if it
can be run in llap. If under mode all, query cannot be run in llap because some
parts of the plan cannot be run in it, it makes sense to stop the user from
proceeding.
Source:
https://issues.apache.org/jira/browse/HIVE-13342?focusedCommentId=15230950=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15230950
> Default of hive.llap.execution.mode=only on Hive Interactive breaks
> StorageHandler tables.
> --
>
> Key: AMBARI-21730
> URL: https://issues.apache.org/jira/browse/AMBARI-21730
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0, 2.5.1
>Reporter: Xabriel J Collazo Mojica
>
> Ambari 2.5+ sets the following Hive Interactive flag by default to:
> {{hive.llap.execution.mode=only}}
> This mode breaks compatibility with StorageHander based tables. For example,
> HBase tables like these fail:
> CREATE TABLE hbase_table_1(key int, value string)
> STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
> WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:val")
> TBLPROPERTIES ("hbase.table.name" = "xyz",
> "hbase.mapred.output.outputtable" = "xyz");
> With a stack trace like:
> 0: jdbc:hive2://intel68bvt2.fyre.ibm.com:2181> INSERT OVERWRITE TABLE
> hbase_table_1 SELECT * FROM hbase_table_1;
> INFO : Compiling
> command(queryId=hive_20170814172300_b01cbd64-f790-468b-855c-2ff8224f4fc0):
> INSERT OVERWRITE TABLE hbase_table_1 SELECT * FROM hbase_table_1
>
> INFO : Dag name: INSERT OVERWRITE TABLE hbase...hbase_table_1(Stage-3)
> INFO : Dag submit failed due to There is conflicting local resource
> (guava-14.0.1.jar) between dag local resource and vertex Map 1 local
> resource.
> Resource of dag : resource { scheme: "hdfs" host:
> "intel68bvt1.fyre.ibm.com" port: 8020 file:
> "/tmp/hive/hive/0ccc7843-8d48-474a-888a-96bea2fcc1cd/hive_2017-08-14_17-23-00_028_5196182473716985960-6/hive/_tez_scratch_dir/guava-14.0.1.jar"
> } size: 2189117 timestamp: 1502756584191 type: FILE visibility: PRIVATE
> Resource of vertex: resource { scheme: "hdfs" host:
> "intel68bvt1.fyre.ibm.com" port: 8020 file:
> "/tmp/hive/hive/_tez_session_dir/de9aa10e-39a4-4d76-a0d8-55493fc6ba00/guava-14.0.1.jar"
> }
> *When this flag is set to: {{hive.llap.execution.mode=auto}}, the issue is
> not seen anymore.*
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21325) Ability to switch Quick Links to use Service URL through Knox or given proxy
[ https://issues.apache.org/jira/browse/AMBARI-21325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandana Mirashi updated AMBARI-21325: -- Status: Patch Available (was: Open) > Ability to switch Quick Links to use Service URL through Knox or given proxy > > > Key: AMBARI-21325 > URL: https://issues.apache.org/jira/browse/AMBARI-21325 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk, 2.5.2, 2.5.3 >Reporter: Jeffrey E Rodriguez >Assignee: Chandana Mirashi > Attachments: AMBARI-21325.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > Knox has the ability to proxy Hadoop user interfaces URL. Having the ability > to setup Quicklinks through Knox so instead of for example going to "Hbase > Master UI" directly we can proxy through Knox for example: > http://hdpjeff1.fyre.ibm.com:16010/master-status > can be instead go through: > https://hdpjeff1.fyre.ibm.com:8443/gateway/default/hbase/hbaseui/master-status > Here https://hdpjeff1.fyre.ibm.com:8443/gateway is the Knox gateway URL. > This will bring authentication to the UI access and would secure the UI > access. > Ideally this behavior can be set as secure going through proxy by default or > it can be turn off to go directly by Ambari Admin. > Changes added: > 1. Add new json properties knox_url, knox_path, supports_knox >a. knox_url: template to be used for urls that are proxied through Knox >b. knox_path: Knox gateway path that will be added to the proxy url. >c. supports_knox: whether link will be redirected through Knox > 2. Add above json properties to quicklinks.json > 3. Add HDFSUI & DATANODE,YARNUI & NODEUI, JOBHISTORYUI, HBASEUI, OOZIEUI, > SPARKUI services to Knox topology template. > 4. Automate protocol and port added to Knox topology file. Based on whether > SSL is enabled for the services listed above, the port and protocol in > params_linux.py will be updated. > 5. Update quick_view_link_view.js so that when Knox is installed and > support_knox is true, quicklink url follows knox url template specified in > the quicklinks.json for the service/component. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21730) Default of hive.llap.execution.mode=only on Hive Interactive breaks StorageHandler tables.
[
https://issues.apache.org/jira/browse/AMBARI-21730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xabriel J Collazo Mojica updated AMBARI-21730:
--
Description:
Ambari 2.5+ sets the following Hive Interactive flag by default to:
{{hive.llap.execution.mode=only}}
This mode breaks compatibility with StorageHander based tables. For example,
HBase tables like these fail:
CREATE TABLE hbase_table_1(key int, value string)
STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:val")
TBLPROPERTIES ("hbase.table.name" = "xyz",
"hbase.mapred.output.outputtable" = "xyz");
With a stack trace like:
0: jdbc:hive2://intel68bvt2.fyre.ibm.com:2181> INSERT OVERWRITE TABLE
hbase_table_1 SELECT * FROM hbase_table_1;
INFO : Compiling
command(queryId=hive_20170814172300_b01cbd64-f790-468b-855c-2ff8224f4fc0):
INSERT OVERWRITE TABLE hbase_table_1 SELECT * FROM hbase_table_1
INFO : Dag name: INSERT OVERWRITE TABLE hbase...hbase_table_1(Stage-3)
INFO : Dag submit failed due to There is conflicting local resource
(guava-14.0.1.jar) between dag local resource and vertex Map 1 local resource.
Resource of dag : resource { scheme: "hdfs" host:
"intel68bvt1.fyre.ibm.com" port: 8020 file:
"/tmp/hive/hive/0ccc7843-8d48-474a-888a-96bea2fcc1cd/hive_2017-08-14_17-23-00_028_5196182473716985960-6/hive/_tez_scratch_dir/guava-14.0.1.jar"
} size: 2189117 timestamp: 1502756584191 type: FILE visibility: PRIVATE
Resource of vertex: resource { scheme: "hdfs" host:
"intel68bvt1.fyre.ibm.com" port: 8020 file:
"/tmp/hive/hive/_tez_session_dir/de9aa10e-39a4-4d76-a0d8-55493fc6ba00/guava-14.0.1.jar"
}
*When this flag is set to: {{hive.llap.execution.mode=auto}}, the issue is not
seen anymore.*
was:
Ambari 2.5+ sets the following Hive Interactive flag by default to:
{{hive.llap.execution.mode=only}}
This mode breaks compatibility with StorageHander based tables. For example,
HBase tables like these fail:
CREATE TABLE hbase_table_1(key int, value string)
STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:val")
TBLPROPERTIES ("hbase.table.name" = "xyz",
"hbase.mapred.output.outputtable" = "xyz");
With a stack trace like:
0: jdbc:hive2://intel68bvt2.fyre.ibm.com:2181> INSERT OVERWRITE TABLE
hbase_table_1 SELECT * FROM hbase_table_1;
INFO : Compiling
command(queryId=hive_20170814172300_b01cbd64-f790-468b-855c-2ff8224f4fc0):
INSERT OVERWRITE TABLE hbase_table_1 SELECT * FROM hbase_table_1
INFO : Dag name: INSERT OVERWRITE TABLE hbase...hbase_table_1(Stage-3)
INFO : Dag submit failed due to There is conflicting local resource
(guava-14.0.1.jar) between dag local resource and vertex Map 1 local resource.
Resource of dag : resource { scheme: "hdfs" host:
"intel68bvt1.fyre.ibm.com" port: 8020 file:
"/tmp/hive/hive/0ccc7843-8d48-474a-888a-96bea2fcc1cd/hive_2017-08-14_17-23-00_028_5196182473716985960-6/hive/_tez_scratch_dir/guava-14.0.1.jar"
} size: 2189117 timestamp: 1502756584191 type: FILE visibility: PRIVATE
Resource of vertex: resource { scheme: "hdfs" host:
"intel68bvt1.fyre.ibm.com" port: 8020 file:
"/tmp/hive/hive/_tez_session_dir/de9aa10e-39a4-4d76-a0d8-55493fc6ba00/guava-14.0.1.jar"
}
When this flag is set to: {{hive.llap.execution.mode=auto}}, the issue is not
seen anymore.
> Default of hive.llap.execution.mode=only on Hive Interactive breaks
> StorageHandler tables.
> --
>
> Key: AMBARI-21730
> URL: https://issues.apache.org/jira/browse/AMBARI-21730
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0, 2.5.1
>Reporter: Xabriel J Collazo Mojica
>
> Ambari 2.5+ sets the following Hive Interactive flag by default to:
> {{hive.llap.execution.mode=only}}
> This mode breaks compatibility with StorageHander based tables. For example,
> HBase tables like these fail:
> CREATE TABLE hbase_table_1(key int, value string)
> STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
> WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:val")
> TBLPROPERTIES ("hbase.table.name" = "xyz",
> "hbase.mapred.output.outputtable" = "xyz");
> With a stack trace like:
> 0: jdbc:hive2://intel68bvt2.fyre.ibm.com:2181> INSERT OVERWRITE TABLE
> hbase_table_1 SELECT * FROM hbase_table_1;
> INFO : Compiling
> command(queryId=hive_20170814172300_b01cbd64-f790-468b-855c-2ff8224f4fc0):
> INSERT OVERWRITE TABLE hbase_table_1 SELECT * FROM hbase_table_1
>
> INFO : Dag name: INSERT OVERWRITE TABLE hbase...hbase_table_1(Stage-3)
> INFO : Dag submit failed due to There is conflicting local resource
> (guava-14.0.1.jar) between dag local
[jira] [Updated] (AMBARI-21729) Owner of yarn.include stays to be root:root where as dfs.include gets changed to the correct one upon restart services
[ https://issues.apache.org/jira/browse/AMBARI-21729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-21729: --- Priority: Blocker (was: Major) > Owner of yarn.include stays to be root:root where as dfs.include gets changed > to the correct one upon restart services > -- > > Key: AMBARI-21729 > URL: https://issues.apache.org/jira/browse/AMBARI-21729 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.5.2 >Reporter: Dhanya Balasundaran >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 2.5.2 > > Attachments: AMBARI-21729.patch > > > - After deployment, create dfs.include and yarn.include in /etc/hadoop/conf > as root user itself. - Set manage.include.files to true for HDFS and YARN and > update dfs.hosts and yarn.resourcemanager.nodes.include-path properties > - Restart services > - After services are restrated dfs.include gets the right owner > (:hadoop) where as yarn.include still has root:root > - Noticed that owner of dfs.include is updated during Namenode restart but > yarn.include is not updated after restart of all services that had stale > configs -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21730) Default of hive.llap.execution.mode=only on Hive Interactive breaks StorageHandler tables.
[
https://issues.apache.org/jira/browse/AMBARI-21730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xabriel J Collazo Mojica updated AMBARI-21730:
--
Description:
Ambari 2.5+ sets the following Hive Interactive flag by default to:
{{hive.llap.execution.mode=only}}
This mode breaks compatibility with StorageHander based tables. For example,
HBase tables like these fail:
CREATE TABLE hbase_table_1(key int, value string)
STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:val")
TBLPROPERTIES ("hbase.table.name" = "xyz",
"hbase.mapred.output.outputtable" = "xyz");
With a stack trace like:
0: jdbc:hive2://intel68bvt2.fyre.ibm.com:2181> INSERT OVERWRITE TABLE
hbase_table_1 SELECT * FROM hbase_table_1;
INFO : Compiling
command(queryId=hive_20170814172300_b01cbd64-f790-468b-855c-2ff8224f4fc0):
INSERT OVERWRITE TABLE hbase_table_1 SELECT * FROM hbase_table_1
INFO : Dag name: INSERT OVERWRITE TABLE hbase...hbase_table_1(Stage-3)
INFO : Dag submit failed due to There is conflicting local resource
(guava-14.0.1.jar) between dag local resource and vertex Map 1 local resource.
Resource of dag : resource { scheme: "hdfs" host:
"intel68bvt1.fyre.ibm.com" port: 8020 file:
"/tmp/hive/hive/0ccc7843-8d48-474a-888a-96bea2fcc1cd/hive_2017-08-14_17-23-00_028_5196182473716985960-6/hive/_tez_scratch_dir/guava-14.0.1.jar"
} size: 2189117 timestamp: 1502756584191 type: FILE visibility: PRIVATE
Resource of vertex: resource { scheme: "hdfs" host:
"intel68bvt1.fyre.ibm.com" port: 8020 file:
"/tmp/hive/hive/_tez_session_dir/de9aa10e-39a4-4d76-a0d8-55493fc6ba00/guava-14.0.1.jar"
}
When this flag is set to: {{hive.llap.execution.mode=auto}}, the issue is not
seen anymore.
was:
Ambari 2.5+ sets the following Hive Interactive flag by default to:
{{hive.llap.execution.mode=only}}
This mode breaks compatibility with StorageHander based tables. For example,
HBase tables like these fail:
{{CREATE TABLE hbase_table_1(key int, value string)
STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:val")
TBLPROPERTIES ("hbase.table.name" = "xyz",
"hbase.mapred.output.outputtable" = "xyz");
}}
With a stack trace like:
{{0: jdbc:hive2://intel68bvt2.fyre.ibm.com:2181> INSERT OVERWRITE TABLE
hbase_table_1 SELECT * FROM hbase_table_1;
INFO : Compiling
command(queryId=hive_20170814172300_b01cbd64-f790-468b-855c-2ff8224f4fc0):
INSERT OVERWRITE TABLE hbase_table_1 SELECT * FROM hbase_table_1
INFO : Dag name: INSERT OVERWRITE TABLE hbase...hbase_table_1(Stage-3)
INFO : Dag submit failed due to There is conflicting local resource
(guava-14.0.1.jar) between dag local resource and vertex Map 1 local resource.
Resource of dag : resource { scheme: "hdfs" host:
"intel68bvt1.fyre.ibm.com" port: 8020 file:
"/tmp/hive/hive/0ccc7843-8d48-474a-888a-96bea2fcc1cd/hive_2017-08-14_17-23-00_028_5196182473716985960-6/hive/_tez_scratch_dir/guava-14.0.1.jar"
} size: 2189117 timestamp: 1502756584191 type: FILE visibility: PRIVATE
Resource of vertex: resource { scheme: "hdfs" host:
"intel68bvt1.fyre.ibm.com" port: 8020 file:
"/tmp/hive/hive/_tez_session_dir/de9aa10e-39a4-4d76-a0d8-55493fc6ba00/guava-14.0.1.jar"
}
}}
When this flag is set to: {{hive.llap.execution.mode=auto}}, the issue is not
seen anymore.
> Default of hive.llap.execution.mode=only on Hive Interactive breaks
> StorageHandler tables.
> --
>
> Key: AMBARI-21730
> URL: https://issues.apache.org/jira/browse/AMBARI-21730
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0, 2.5.1
>Reporter: Xabriel J Collazo Mojica
>
> Ambari 2.5+ sets the following Hive Interactive flag by default to:
> {{hive.llap.execution.mode=only}}
> This mode breaks compatibility with StorageHander based tables. For example,
> HBase tables like these fail:
> CREATE TABLE hbase_table_1(key int, value string)
> STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
> WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:val")
> TBLPROPERTIES ("hbase.table.name" = "xyz",
> "hbase.mapred.output.outputtable" = "xyz");
> With a stack trace like:
> 0: jdbc:hive2://intel68bvt2.fyre.ibm.com:2181> INSERT OVERWRITE TABLE
> hbase_table_1 SELECT * FROM hbase_table_1;
> INFO : Compiling
> command(queryId=hive_20170814172300_b01cbd64-f790-468b-855c-2ff8224f4fc0):
> INSERT OVERWRITE TABLE hbase_table_1 SELECT * FROM hbase_table_1
>
> INFO : Dag name: INSERT OVERWRITE TABLE hbase...hbase_table_1(Stage-3)
> INFO : Dag submit failed due to There is conflicting local resource
> (guava-14.0.1.jar) between dag
[jira] [Updated] (AMBARI-21730) Default of hive.llap.execution.mode=only on Hive Interactive breaks StorageHandler tables.
[
https://issues.apache.org/jira/browse/AMBARI-21730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xabriel J Collazo Mojica updated AMBARI-21730:
--
Description:
Ambari 2.5+ sets the following Hive Interactive flag by default to:
{{hive.llap.execution.mode=only}}
This mode breaks compatibility with StorageHander based tables. For example,
HBase tables like these fail:
{{CREATE TABLE hbase_table_1(key int, value string)
STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:val")
TBLPROPERTIES ("hbase.table.name" = "xyz",
"hbase.mapred.output.outputtable" = "xyz");
}}
With a stack trace like:
{{0: jdbc:hive2://intel68bvt2.fyre.ibm.com:2181> INSERT OVERWRITE TABLE
hbase_table_1 SELECT * FROM hbase_table_1;
INFO : Compiling
command(queryId=hive_20170814172300_b01cbd64-f790-468b-855c-2ff8224f4fc0):
INSERT OVERWRITE TABLE hbase_table_1 SELECT * FROM hbase_table_1
INFO : Dag name: INSERT OVERWRITE TABLE hbase...hbase_table_1(Stage-3)
INFO : Dag submit failed due to There is conflicting local resource
(guava-14.0.1.jar) between dag local resource and vertex Map 1 local resource.
Resource of dag : resource { scheme: "hdfs" host:
"intel68bvt1.fyre.ibm.com" port: 8020 file:
"/tmp/hive/hive/0ccc7843-8d48-474a-888a-96bea2fcc1cd/hive_2017-08-14_17-23-00_028_5196182473716985960-6/hive/_tez_scratch_dir/guava-14.0.1.jar"
} size: 2189117 timestamp: 1502756584191 type: FILE visibility: PRIVATE
Resource of vertex: resource { scheme: "hdfs" host:
"intel68bvt1.fyre.ibm.com" port: 8020 file:
"/tmp/hive/hive/_tez_session_dir/de9aa10e-39a4-4d76-a0d8-55493fc6ba00/guava-14.0.1.jar"
}
}}
When this flag is set to: {{hive.llap.execution.mode=auto}}, the issue is not
seen anymore.
was:
Ambari 2.5+ sets the following Hive Interactive flag by default to:
{{hive.llap.execution.mode=only}}
This mode breaks compatibility with StorageHander based tables. For example,
HBase tables like these fail:
{{ CREATE TABLE hbase_table_1(key int, value string)
STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:val")
TBLPROPERTIES ("hbase.table.name" = "xyz",
"hbase.mapred.output.outputtable" = "xyz");
}}
With a stack trace like:
{{0: jdbc:hive2://intel68bvt2.fyre.ibm.com:2181> INSERT OVERWRITE TABLE
hbase_table_1 SELECT * FROM hbase_table_1;
INFO : Compiling
command(queryId=hive_20170814172300_b01cbd64-f790-468b-855c-2ff8224f4fc0):
INSERT OVERWRITE TABLE hbase_table_1 SELECT * FROM hbase_table_1
INFO : Dag name: INSERT OVERWRITE TABLE hbase...hbase_table_1(Stage-3)
INFO : Dag submit failed due to There is conflicting local resource
(guava-14.0.1.jar) between dag local resource and vertex Map 1 local resource.
Resource of dag : resource { scheme: "hdfs" host:
"intel68bvt1.fyre.ibm.com" port: 8020 file:
"/tmp/hive/hive/0ccc7843-8d48-474a-888a-96bea2fcc1cd/hive_2017-08-14_17-23-00_028_5196182473716985960-6/hive/_tez_scratch_dir/guava-14.0.1.jar"
} size: 2189117 timestamp: 1502756584191 type: FILE visibility: PRIVATE
Resource of vertex: resource { scheme: "hdfs" host:
"intel68bvt1.fyre.ibm.com" port: 8020 file:
"/tmp/hive/hive/_tez_session_dir/de9aa10e-39a4-4d76-a0d8-55493fc6ba00/guava-14.0.1.jar"
}
}}
When this flag is set to: {{hive.llap.execution.mode=auto}}, the issue is not
seen anymore.
> Default of hive.llap.execution.mode=only on Hive Interactive breaks
> StorageHandler tables.
> --
>
> Key: AMBARI-21730
> URL: https://issues.apache.org/jira/browse/AMBARI-21730
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0, 2.5.1
>Reporter: Xabriel J Collazo Mojica
>
> Ambari 2.5+ sets the following Hive Interactive flag by default to:
> {{hive.llap.execution.mode=only}}
> This mode breaks compatibility with StorageHander based tables. For example,
> HBase tables like these fail:
> {{CREATE TABLE hbase_table_1(key int, value string)
> STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
> WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:val")
> TBLPROPERTIES ("hbase.table.name" = "xyz",
> "hbase.mapred.output.outputtable" = "xyz");
> }}
> With a stack trace like:
> {{0: jdbc:hive2://intel68bvt2.fyre.ibm.com:2181> INSERT OVERWRITE TABLE
> hbase_table_1 SELECT * FROM hbase_table_1;
> INFO : Compiling
> command(queryId=hive_20170814172300_b01cbd64-f790-468b-855c-2ff8224f4fc0):
> INSERT OVERWRITE TABLE hbase_table_1 SELECT * FROM hbase_table_1
>
> INFO : Dag name: INSERT OVERWRITE TABLE hbase...hbase_table_1(Stage-3)
> INFO : Dag submit failed due to There is conflicting local resource
>
[jira] [Updated] (AMBARI-21730) Default of hive.llap.execution.mode=only on Hive Interactive breaks StorageHandler tables.
[
https://issues.apache.org/jira/browse/AMBARI-21730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xabriel J Collazo Mojica updated AMBARI-21730:
--
Description:
Ambari 2.5+ sets the following Hive Interactive flag by default to:
{{hive.llap.execution.mode=only}}
This mode breaks compatibility with StorageHander based tables. For example,
HBase tables like these fail:
{{ CREATE TABLE hbase_table_1(key int, value string)
STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:val")
TBLPROPERTIES ("hbase.table.name" = "xyz",
"hbase.mapred.output.outputtable" = "xyz");
}}
With a stack trace like:
{{0: jdbc:hive2://intel68bvt2.fyre.ibm.com:2181> INSERT OVERWRITE TABLE
hbase_table_1 SELECT * FROM hbase_table_1;
INFO : Compiling
command(queryId=hive_20170814172300_b01cbd64-f790-468b-855c-2ff8224f4fc0):
INSERT OVERWRITE TABLE hbase_table_1 SELECT * FROM hbase_table_1
INFO : Dag name: INSERT OVERWRITE TABLE hbase...hbase_table_1(Stage-3)
INFO : Dag submit failed due to There is conflicting local resource
(guava-14.0.1.jar) between dag local resource and vertex Map 1 local resource.
Resource of dag : resource { scheme: "hdfs" host:
"intel68bvt1.fyre.ibm.com" port: 8020 file:
"/tmp/hive/hive/0ccc7843-8d48-474a-888a-96bea2fcc1cd/hive_2017-08-14_17-23-00_028_5196182473716985960-6/hive/_tez_scratch_dir/guava-14.0.1.jar"
} size: 2189117 timestamp: 1502756584191 type: FILE visibility: PRIVATE
Resource of vertex: resource { scheme: "hdfs" host:
"intel68bvt1.fyre.ibm.com" port: 8020 file:
"/tmp/hive/hive/_tez_session_dir/de9aa10e-39a4-4d76-a0d8-55493fc6ba00/guava-14.0.1.jar"
}
}}
When this flag is set to: {{hive.llap.execution.mode=auto}}, the issue is not
seen anymore.
was:
Ambari 2.5+ sets the following Hive Interactive flag by default to:
{{hive.llap.execution.mode=only}}
This mode breaks compatibility with StorageHander based tables. For example,
HBase tables like these fail:
{{CREATE TABLE hbase_table_1(key int, value string)
STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:val")
TBLPROPERTIES ("hbase.table.name" = "xyz",
"hbase.mapred.output.outputtable" = "xyz");
0: jdbc:hive2://intel68bvt2.fyre.ibm.com:2181> INSERT OVERWRITE TABLE
hbase_table_1 SELECT * FROM hbase_table_1;
INFO : Compiling
command(queryId=hive_20170814172300_b01cbd64-f790-468b-855c-2ff8224f4fc0):
INSERT OVERWRITE TABLE hbase_table_1 SELECT * FROM hbase_table_1
INFO : Dag name: INSERT OVERWRITE TABLE hbase...hbase_table_1(Stage-3)
INFO : Dag submit failed due to There is conflicting local resource
(guava-14.0.1.jar) between dag local resource and vertex Map 1 local resource.
Resource of dag : resource { scheme: "hdfs" host:
"intel68bvt1.fyre.ibm.com" port: 8020 file:
"/tmp/hive/hive/0ccc7843-8d48-474a-888a-96bea2fcc1cd/hive_2017-08-14_17-23-00_028_5196182473716985960-6/hive/_tez_scratch_dir/guava-14.0.1.jar"
} size: 2189117 timestamp: 1502756584191 type: FILE visibility: PRIVATE
Resource of vertex: resource { scheme: "hdfs" host:
"intel68bvt1.fyre.ibm.com" port: 8020 file:
"/tmp/hive/hive/_tez_session_dir/de9aa10e-39a4-4d76-a0d8-55493fc6ba00/guava-14.0.1.jar"
} }}
When this flag is set to: {{hive.llap.execution.mode=auto}}, the issue is not
seen anymore.
> Default of hive.llap.execution.mode=only on Hive Interactive breaks
> StorageHandler tables.
> --
>
> Key: AMBARI-21730
> URL: https://issues.apache.org/jira/browse/AMBARI-21730
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0, 2.5.1
>Reporter: Xabriel J Collazo Mojica
>
> Ambari 2.5+ sets the following Hive Interactive flag by default to:
> {{hive.llap.execution.mode=only}}
> This mode breaks compatibility with StorageHander based tables. For example,
> HBase tables like these fail:
> {{ CREATE TABLE hbase_table_1(key int, value string)
> STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
> WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:val")
> TBLPROPERTIES ("hbase.table.name" = "xyz",
> "hbase.mapred.output.outputtable" = "xyz");
> }}
> With a stack trace like:
> {{0: jdbc:hive2://intel68bvt2.fyre.ibm.com:2181> INSERT OVERWRITE TABLE
> hbase_table_1 SELECT * FROM hbase_table_1;
> INFO : Compiling
> command(queryId=hive_20170814172300_b01cbd64-f790-468b-855c-2ff8224f4fc0):
> INSERT OVERWRITE TABLE hbase_table_1 SELECT * FROM hbase_table_1
>
> INFO : Dag name: INSERT OVERWRITE TABLE hbase...hbase_table_1(Stage-3)
> INFO : Dag submit failed due to There is conflicting local resource
> (guava-14.0.1.jar) between
[jira] [Created] (AMBARI-21730) Default of hive.llap.execution.mode=only on Hive Interactive breaks StorageHandler tables.
Xabriel J Collazo Mojica created AMBARI-21730:
-
Summary: Default of hive.llap.execution.mode=only on Hive
Interactive breaks StorageHandler tables.
Key: AMBARI-21730
URL: https://issues.apache.org/jira/browse/AMBARI-21730
Project: Ambari
Issue Type: Bug
Affects Versions: 2.5.0, 2.5.1
Reporter: Xabriel J Collazo Mojica
Ambari 2.5+ sets the following Hive Interactive flag by default to:
{{hive.llap.execution.mode=only}}
This mode breaks compatibility with StorageHander based tables. For example,
HBase tables like these fail:
{{CREATE TABLE hbase_table_1(key int, value string)
STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:val")
TBLPROPERTIES ("hbase.table.name" = "xyz",
"hbase.mapred.output.outputtable" = "xyz");
0: jdbc:hive2://intel68bvt2.fyre.ibm.com:2181> INSERT OVERWRITE TABLE
hbase_table_1 SELECT * FROM hbase_table_1;
INFO : Compiling
command(queryId=hive_20170814172300_b01cbd64-f790-468b-855c-2ff8224f4fc0):
INSERT OVERWRITE TABLE hbase_table_1 SELECT * FROM hbase_table_1
INFO : Dag name: INSERT OVERWRITE TABLE hbase...hbase_table_1(Stage-3)
INFO : Dag submit failed due to There is conflicting local resource
(guava-14.0.1.jar) between dag local resource and vertex Map 1 local resource.
Resource of dag : resource { scheme: "hdfs" host:
"intel68bvt1.fyre.ibm.com" port: 8020 file:
"/tmp/hive/hive/0ccc7843-8d48-474a-888a-96bea2fcc1cd/hive_2017-08-14_17-23-00_028_5196182473716985960-6/hive/_tez_scratch_dir/guava-14.0.1.jar"
} size: 2189117 timestamp: 1502756584191 type: FILE visibility: PRIVATE
Resource of vertex: resource { scheme: "hdfs" host:
"intel68bvt1.fyre.ibm.com" port: 8020 file:
"/tmp/hive/hive/_tez_session_dir/de9aa10e-39a4-4d76-a0d8-55493fc6ba00/guava-14.0.1.jar"
} }}
When this flag is set to: {{hive.llap.execution.mode=auto}}, the issue is not
seen anymore.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21729) Owner of yarn.include stays to be root:root where as dfs.include gets changed to the correct one upon restart services
[
https://issues.apache.org/jira/browse/AMBARI-21729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127425#comment-16127425
]
Hadoop QA commented on AMBARI-21729:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12881948/AMBARI-21729.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/11995//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11995//console
This message is automatically generated.
> Owner of yarn.include stays to be root:root where as dfs.include gets changed
> to the correct one upon restart services
> --
>
> Key: AMBARI-21729
> URL: https://issues.apache.org/jira/browse/AMBARI-21729
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin
>Affects Versions: 2.5.2
>Reporter: Dhanya Balasundaran
>Assignee: Dmytro Sen
> Fix For: 2.5.2
>
> Attachments: AMBARI-21729.patch
>
>
> - After deployment, create dfs.include and yarn.include in /etc/hadoop/conf
> as root user itself. - Set manage.include.files to true for HDFS and YARN and
> update dfs.hosts and yarn.resourcemanager.nodes.include-path properties
> - Restart services
> - After services are restrated dfs.include gets the right owner
> (:hadoop) where as yarn.include still has root:root
> - Noticed that owner of dfs.include is updated during Namenode restart but
> yarn.include is not updated after restart of all services that had stale
> configs
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21729) Owner of yarn.include stays to be root:root where as dfs.include gets changed to the correct one upon restart services
[ https://issues.apache.org/jira/browse/AMBARI-21729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-21729: Attachment: AMBARI-21729.patch > Owner of yarn.include stays to be root:root where as dfs.include gets changed > to the correct one upon restart services > -- > > Key: AMBARI-21729 > URL: https://issues.apache.org/jira/browse/AMBARI-21729 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.5.2 >Reporter: Dhanya Balasundaran >Assignee: Dmytro Sen > Fix For: 2.5.2 > > Attachments: AMBARI-21729.patch > > > - After deployment, create dfs.include and yarn.include in /etc/hadoop/conf > as root user itself. - Set manage.include.files to true for HDFS and YARN and > update dfs.hosts and yarn.resourcemanager.nodes.include-path properties > - Restart services > - After services are restrated dfs.include gets the right owner > (:hadoop) where as yarn.include still has root:root > - Noticed that owner of dfs.include is updated during Namenode restart but > yarn.include is not updated after restart of all services that had stale > configs -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21729) Owner of yarn.include stays to be root:root where as dfs.include gets changed to the correct one upon restart services
[ https://issues.apache.org/jira/browse/AMBARI-21729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-21729: Status: Patch Available (was: In Progress) > Owner of yarn.include stays to be root:root where as dfs.include gets changed > to the correct one upon restart services > -- > > Key: AMBARI-21729 > URL: https://issues.apache.org/jira/browse/AMBARI-21729 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.5.2 >Reporter: Dhanya Balasundaran >Assignee: Dmytro Sen > Fix For: 2.5.2 > > Attachments: AMBARI-21729.patch > > > - After deployment, create dfs.include and yarn.include in /etc/hadoop/conf > as root user itself. - Set manage.include.files to true for HDFS and YARN and > update dfs.hosts and yarn.resourcemanager.nodes.include-path properties > - Restart services > - After services are restrated dfs.include gets the right owner > (:hadoop) where as yarn.include still has root:root > - Noticed that owner of dfs.include is updated during Namenode restart but > yarn.include is not updated after restart of all services that had stale > configs -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-21729) Owner of yarn.include stays to be root:root where as dfs.include gets changed to the correct one upon restart services
[ https://issues.apache.org/jira/browse/AMBARI-21729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen reassigned AMBARI-21729: --- Assignee: Dmytro Sen > Owner of yarn.include stays to be root:root where as dfs.include gets changed > to the correct one upon restart services > -- > > Key: AMBARI-21729 > URL: https://issues.apache.org/jira/browse/AMBARI-21729 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.5.2 >Reporter: Dhanya Balasundaran >Assignee: Dmytro Sen > Fix For: 2.5.2 > > Attachments: AMBARI-21729.patch > > > - After deployment, create dfs.include and yarn.include in /etc/hadoop/conf > as root user itself. - Set manage.include.files to true for HDFS and YARN and > update dfs.hosts and yarn.resourcemanager.nodes.include-path properties > - Restart services > - After services are restrated dfs.include gets the right owner > (:hadoop) where as yarn.include still has root:root > - Noticed that owner of dfs.include is updated during Namenode restart but > yarn.include is not updated after restart of all services that had stale > configs -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-21608) Spark shell is not working after upgrade
[
https://issues.apache.org/jira/browse/AMBARI-21608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang resolved AMBARI-21608.
Resolution: Implemented
The root cause is that Hive code can not locate jar files on
HIVE_AUX_JARS_PATH. Hive code throws a write error which gets interpreted as
permission denied. This issue is resolved by fixing AMBARI-21607.
> Spark shell is not working after upgrade
>
>
> Key: AMBARI-21608
> URL: https://issues.apache.org/jira/browse/AMBARI-21608
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Eric Yang
> Fix For: 2.5.2
>
>
> Spark shell does not work after IOP to HDP upgrade. This error message shows
> up when running spark-shell:
> {code}
> 17/07/28 20:50:46 INFO Datastore: The class
> "org.apache.hadoop.hive.metastore.model.MResourceUri" is tagged as
> "embedded-only" so does not have its own datastore table.
> 17/07/28 20:50:46 INFO SessionState: Created local directory:
> /tmp/cedf0cab-747a-45e8-8c36-53a304027587_resources
> 17/07/28 20:50:46 INFO SessionState: Created HDFS directory:
> /tmp/hive/spark/cedf0cab-747a-45e8-8c36-53a304027587
> 17/07/28 20:50:46 INFO SessionState: Created local directory:
> /tmp/spark/cedf0cab-747a-45e8-8c36-53a304027587
> 17/07/28 20:50:46 INFO SessionState: Created HDFS directory:
> /tmp/hive/spark/cedf0cab-747a-45e8-8c36-53a304027587/_tmp_space.db
> java.lang.RuntimeException: java.lang.RuntimeException: java.io.IOException:
> Permission denied
> at
> org.apache.hadoop.hive.ql.session.SessionState.start(SessionState.java:522)
> at
> org.apache.spark.sql.hive.client.ClientWrapper.(ClientWrapper.scala:209)
> at
> org.apache.spark.sql.hive.client.IsolatedClientLoader.createClient(IsolatedClientLoader.scala:238)
> at
> org.apache.spark.sql.hive.HiveContext.executionHive$lzycompute(HiveContext.scala:225)
> at
> org.apache.spark.sql.hive.HiveContext.executionHive(HiveContext.scala:215)
> at
> org.apache.spark.sql.hive.HiveContext.functionRegistry$lzycompute(HiveContext.scala:480)
> at
> org.apache.spark.sql.hive.HiveContext.functionRegistry(HiveContext.scala:479)
> at org.apache.spark.sql.UDFRegistration.(UDFRegistration.scala:40)
> at org.apache.spark.sql.SQLContext.(SQLContext.scala:330)
> at org.apache.spark.sql.hive.HiveContext.(HiveContext.scala:90)
> at org.apache.spark.sql.hive.HiveContext.(HiveContext.scala:101)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.spark.repl.SparkILoop.createSQLContext(SparkILoop.scala:1028)
> at $iwC$$iwC.(:15)
> at $iwC.(:24)
> at (:26)
> at .(:30)
> at .()
> at .(:7)
> at .()
> at $print()
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.spark.repl.SparkIMain$ReadEvalPrint.call(SparkIMain.scala:1065)
> at
> org.apache.spark.repl.SparkIMain$Request.loadAndRun(SparkIMain.scala:1346)
> at
> org.apache.spark.repl.SparkIMain.loadAndRunReq$1(SparkIMain.scala:840)
> at org.apache.spark.repl.SparkIMain.interpret(SparkIMain.scala:871)
> at org.apache.spark.repl.SparkIMain.interpret(SparkIMain.scala:819)
> at
> org.apache.spark.repl.SparkILoop.reallyInterpret$1(SparkILoop.scala:857)
> at
> org.apache.spark.repl.SparkILoop.interpretStartingWith(SparkILoop.scala:902)
> at org.apache.spark.repl.SparkILoop.command(SparkILoop.scala:814)
> at
> org.apache.spark.repl.SparkILoopInit$$anonfun$initializeSpark$1.apply(SparkILoopInit.scala:132)
> at
> org.apache.spark.repl.SparkILoopInit$$anonfun$initializeSpark$1.apply(SparkILoopInit.scala:124)
> at org.apache.spark.repl.SparkIMain.beQuietDuring(SparkIMain.scala:324)
> at
> org.apache.spark.repl.SparkILoopInit$class.initializeSpark(SparkILoopInit.scala:124)
> at org.apache.spark.repl.SparkILoop.initializeSpark(SparkILoop.scala:64)
> at
> org.apache.spark.repl.SparkILoop$$anonfun$org$apache$spark$repl$SparkILoop$$process$1$$anonfun$apply$mcZ$sp$5.apply$mcV$sp(SparkILoop.scala:974)
> at
> org.apache.spark.repl.SparkILoopInit$class.runThunks(SparkILoopInit.scala:159)
> at
[jira] [Updated] (AMBARI-21724) Hosts filters work incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-21724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21724: -- Status: Open (was: Patch Available) > Hosts filters work incorrectly > -- > > Key: AMBARI-21724 > URL: https://issues.apache.org/jira/browse/AMBARI-21724 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.5.2 > > Attachments: AMBARI-21724.patch, Screenshot from 2017-08-11 > 11-58-27.png > > > Hosts filters work incorrectly > STR: > 1)Apply filter with absent of hosts result > 2)After few seconds appear unsuitable host > 3)After few seconds in disappear > Firstly this issue occurs in ambari-2.5.2.0-241 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21729) Owner of yarn.include stays to be root:root where as dfs.include gets changed to the correct one upon restart services
Dhanya Balasundaran created AMBARI-21729: Summary: Owner of yarn.include stays to be root:root where as dfs.include gets changed to the correct one upon restart services Key: AMBARI-21729 URL: https://issues.apache.org/jira/browse/AMBARI-21729 Project: Ambari Issue Type: Bug Components: ambari-admin Affects Versions: 2.5.2 Reporter: Dhanya Balasundaran Fix For: 2.5.2 - After deployment, create dfs.include and yarn.include in /etc/hadoop/conf as root user itself. - Set manage.include.files to true for HDFS and YARN and update dfs.hosts and yarn.resourcemanager.nodes.include-path properties - Restart services - After services are restrated dfs.include gets the right owner (:hadoop) where as yarn.include still has root:root - Noticed that owner of dfs.include is updated during Namenode restart but yarn.include is not updated after restart of all services that had stale configs -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21713) Python tests started under uid=0 and uid > 0 works differently
[ https://issues.apache.org/jira/browse/AMBARI-21713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127317#comment-16127317 ] Hudson commented on AMBARI-21713: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #12 (See [https://builds.apache.org/job/Ambari-branch-2.6/12/]) AMBARI-21713 Python tests started under uid=0 and uid > 0 works (hapylestat: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=15bf0fa27d7bf85729c75d3d8ee6b29c6372bc4b]) * (edit) ambari-server/src/test/python/stacks/utils/RMFTestCase.py * (edit) ambari-common/src/main/python/resource_management/libraries/functions/packages_analyzer.py * (edit) ambari-server/src/test/python/TestMpacks.py > Python tests started under uid=0 and uid > 0 works differently > -- > > Key: AMBARI-21713 > URL: https://issues.apache.org/jira/browse/AMBARI-21713 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: trunk > > > The cause is sudo.py and same meaning modules, which implements different > logic depends on user uid. Coz of that us tests covering only uid > 0 logic > and starting them from root (on VM or docker) causing them to fail -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21728) Service and Patch Upgrade Catalog Changes for 2.6 - additional fixes
[ https://issues.apache.org/jira/browse/AMBARI-21728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-21728: Fix Version/s: 2.6.0 > Service and Patch Upgrade Catalog Changes for 2.6 - additional fixes > - > > Key: AMBARI-21728 > URL: https://issues.apache.org/jira/browse/AMBARI-21728 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21728.patch > > > Things missing: > - Address Jonathan's comment at https://reviews.apache.org/r/61503/ > - Oracle DB support > - Test coverage for AMBARI-21169 > - Prepare patch for trunk (forward-port an upgrade catalog) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21728) Service and Patch Upgrade Catalog Changes for 2.6 - additional fixes
[ https://issues.apache.org/jira/browse/AMBARI-21728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-21728: Affects Version/s: 2.6.0 > Service and Patch Upgrade Catalog Changes for 2.6 - additional fixes > - > > Key: AMBARI-21728 > URL: https://issues.apache.org/jira/browse/AMBARI-21728 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21728.patch > > > Things missing: > - Address Jonathan's comment at https://reviews.apache.org/r/61503/ > - Oracle DB support > - Test coverage for AMBARI-21169 > - Prepare patch for trunk (forward-port an upgrade catalog) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-21726) Log Search UI: columns set for logs list should be customized by user
[ https://issues.apache.org/jira/browse/AMBARI-21726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk resolved AMBARI-21726. --- Resolution: Fixed Committed to branch-feature-logsearch-ui > Log Search UI: columns set for logs list should be customized by user > - > > Key: AMBARI-21726 > URL: https://issues.apache.org/jira/browse/AMBARI-21726 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-21726.patch > > > Add combobox control with list of available columns for display inside logs > list. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-21727) Log Search UI: fix typos in license
[ https://issues.apache.org/jira/browse/AMBARI-21727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk resolved AMBARI-21727. --- Resolution: Fixed Committed to branch-feature-logsearch-ui > Log Search UI: fix typos in license > --- > > Key: AMBARI-21727 > URL: https://issues.apache.org/jira/browse/AMBARI-21727 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-21727.patch > > > Correct typo in link to Apache license. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21728) Service and Patch Upgrade Catalog Changes for 2.6 - additional fixes
[ https://issues.apache.org/jira/browse/AMBARI-21728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-21728: Status: Patch Available (was: Open) > Service and Patch Upgrade Catalog Changes for 2.6 - additional fixes > - > > Key: AMBARI-21728 > URL: https://issues.apache.org/jira/browse/AMBARI-21728 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Critical > Attachments: AMBARI-21728.patch > > > Things missing: > - Address Jonathan's comment at https://reviews.apache.org/r/61503/ > - Oracle DB support > - Test coverage for AMBARI-21169 > - Prepare patch for trunk (forward-port an upgrade catalog) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21728) Service and Patch Upgrade Catalog Changes for 2.6 - additional fixes
[ https://issues.apache.org/jira/browse/AMBARI-21728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-21728: Attachment: AMBARI-21728.patch > Service and Patch Upgrade Catalog Changes for 2.6 - additional fixes > - > > Key: AMBARI-21728 > URL: https://issues.apache.org/jira/browse/AMBARI-21728 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Critical > Attachments: AMBARI-21728.patch > > > Things missing: > - Address Jonathan's comment at https://reviews.apache.org/r/61503/ > - Oracle DB support > - Test coverage for AMBARI-21169 > - Prepare patch for trunk (forward-port an upgrade catalog) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21728) Service and Patch Upgrade Catalog Changes for 2.6 - additional fixes
Dmitry Lysnichenko created AMBARI-21728: --- Summary: Service and Patch Upgrade Catalog Changes for 2.6 - additional fixes Key: AMBARI-21728 URL: https://issues.apache.org/jira/browse/AMBARI-21728 Project: Ambari Issue Type: Task Reporter: Dmitry Lysnichenko Assignee: Dmitry Lysnichenko Priority: Critical Things missing: - Address Jonathan's comment at https://reviews.apache.org/r/61503/ - Oracle DB support - Test coverage for AMBARI-21169 - Prepare patch for trunk (forward-port an upgrade catalog) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21728) Service and Patch Upgrade Catalog Changes for 2.6 - additional fixes
[ https://issues.apache.org/jira/browse/AMBARI-21728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-21728: Component/s: ambari-server > Service and Patch Upgrade Catalog Changes for 2.6 - additional fixes > - > > Key: AMBARI-21728 > URL: https://issues.apache.org/jira/browse/AMBARI-21728 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Critical > Attachments: AMBARI-21728.patch > > > Things missing: > - Address Jonathan's comment at https://reviews.apache.org/r/61503/ > - Oracle DB support > - Test coverage for AMBARI-21169 > - Prepare patch for trunk (forward-port an upgrade catalog) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21727) Log Search UI: fix typos in license
[ https://issues.apache.org/jira/browse/AMBARI-21727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-21727: -- Attachment: AMBARI-21727.patch > Log Search UI: fix typos in license > --- > > Key: AMBARI-21727 > URL: https://issues.apache.org/jira/browse/AMBARI-21727 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-21727.patch > > > Correct typo in link to Apache license. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21727) Log Search UI: fix typos in license
Andrii Babiichuk created AMBARI-21727: - Summary: Log Search UI: fix typos in license Key: AMBARI-21727 URL: https://issues.apache.org/jira/browse/AMBARI-21727 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 3.0.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Fix For: 3.0.0 Correct typo in link to Apache license. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21724) Hosts filters work incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-21724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21724: -- Attachment: AMBARI-21724.patch > Hosts filters work incorrectly > -- > > Key: AMBARI-21724 > URL: https://issues.apache.org/jira/browse/AMBARI-21724 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.5.2 > > Attachments: AMBARI-21724.patch, Screenshot from 2017-08-11 > 11-58-27.png > > > Hosts filters work incorrectly > STR: > 1)Apply filter with absent of hosts result > 2)After few seconds appear unsuitable host > 3)After few seconds in disappear > Firstly this issue occurs in ambari-2.5.2.0-241 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21724) Hosts filters work incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-21724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21724: -- Attachment: (was: AMBARI-21724.patch) > Hosts filters work incorrectly > -- > > Key: AMBARI-21724 > URL: https://issues.apache.org/jira/browse/AMBARI-21724 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.5.2 > > Attachments: Screenshot from 2017-08-11 11-58-27.png > > > Hosts filters work incorrectly > STR: > 1)Apply filter with absent of hosts result > 2)After few seconds appear unsuitable host > 3)After few seconds in disappear > Firstly this issue occurs in ambari-2.5.2.0-241 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21726) Log Search UI: columns set for logs list should be customized by user
[ https://issues.apache.org/jira/browse/AMBARI-21726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-21726: -- Attachment: AMBARI-21726.patch > Log Search UI: columns set for logs list should be customized by user > - > > Key: AMBARI-21726 > URL: https://issues.apache.org/jira/browse/AMBARI-21726 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-21726.patch > > > Add combobox control with list of available columns for display inside logs > list. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21726) Log Search UI: columns set for logs list should be customized by user
Andrii Babiichuk created AMBARI-21726: - Summary: Log Search UI: columns set for logs list should be customized by user Key: AMBARI-21726 URL: https://issues.apache.org/jira/browse/AMBARI-21726 Project: Ambari Issue Type: Task Components: ambari-logsearch Affects Versions: 3.0.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Fix For: 3.0.0 Add combobox control with list of available columns for display inside logs list. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21725) Web Client Doesn't Display MAINT Repos Correctly
[
https://issues.apache.org/jira/browse/AMBARI-21725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonenko Alexander updated AMBARI-21725:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Web Client Doesn't Display MAINT Repos Correctly
>
>
> Key: AMBARI-21725
> URL: https://issues.apache.org/jira/browse/AMBARI-21725
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.3
>Reporter: Antonenko Alexander
> Fix For: 2.5.3
>
> Attachments: AMBARI-21725.patch
>
>
> The web client currently doesn't understand {{MAINT}} repositories. When you
> register one it doesn't show the repo differently or identify it as a
> {{MAINT}} repo.
> After applying an upgrade which is a {{MAINT}} upgrade, the upgrade history
> also should indicate that it was a {{MAINT}} style.
> {{MAINT}} is a peer to {{PATCH}} upgrades, so anywhere we have special
> display/text for patches, we should also have the same for maintenance
> repos/upgrades.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21725) Web Client Doesn't Display MAINT Repos Correctly
[
https://issues.apache.org/jira/browse/AMBARI-21725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127259#comment-16127259
]
Antonenko Alexander commented on AMBARI-21725:
--
committed to branch-feature-AMBARI-21450
> Web Client Doesn't Display MAINT Repos Correctly
>
>
> Key: AMBARI-21725
> URL: https://issues.apache.org/jira/browse/AMBARI-21725
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.3
>Reporter: Antonenko Alexander
> Fix For: 2.5.3
>
> Attachments: AMBARI-21725.patch
>
>
> The web client currently doesn't understand {{MAINT}} repositories. When you
> register one it doesn't show the repo differently or identify it as a
> {{MAINT}} repo.
> After applying an upgrade which is a {{MAINT}} upgrade, the upgrade history
> also should indicate that it was a {{MAINT}} style.
> {{MAINT}} is a peer to {{PATCH}} upgrades, so anywhere we have special
> display/text for patches, we should also have the same for maintenance
> repos/upgrades.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21725) Web Client Doesn't Display MAINT Repos Correctly
[
https://issues.apache.org/jira/browse/AMBARI-21725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127256#comment-16127256
]
Antonenko Alexander commented on AMBARI-21725:
--
PATCH APPLICATION FAILED
as it was applied against trunk.
manually tested.
> Web Client Doesn't Display MAINT Repos Correctly
>
>
> Key: AMBARI-21725
> URL: https://issues.apache.org/jira/browse/AMBARI-21725
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.3
>Reporter: Antonenko Alexander
> Fix For: 2.5.3
>
> Attachments: AMBARI-21725.patch
>
>
> The web client currently doesn't understand {{MAINT}} repositories. When you
> register one it doesn't show the repo differently or identify it as a
> {{MAINT}} repo.
> After applying an upgrade which is a {{MAINT}} upgrade, the upgrade history
> also should indicate that it was a {{MAINT}} style.
> {{MAINT}} is a peer to {{PATCH}} upgrades, so anywhere we have special
> display/text for patches, we should also have the same for maintenance
> repos/upgrades.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21724) Hosts filters work incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-21724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127253#comment-16127253 ] Andrii Babiichuk commented on AMBARI-21724: --- +1 for the patch > Hosts filters work incorrectly > -- > > Key: AMBARI-21724 > URL: https://issues.apache.org/jira/browse/AMBARI-21724 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.5.2 > > Attachments: AMBARI-21724.patch, Screenshot from 2017-08-11 > 11-58-27.png > > > Hosts filters work incorrectly > STR: > 1)Apply filter with absent of hosts result > 2)After few seconds appear unsuitable host > 3)After few seconds in disappear > Firstly this issue occurs in ambari-2.5.2.0-241 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21721) Blueprint deployments failing without version string
[ https://issues.apache.org/jira/browse/AMBARI-21721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127241#comment-16127241 ] Hudson commented on AMBARI-21721: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7888 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7888/]) AMBARI-21721. Blueprint deployments failing without version string (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c802a29814e9911b337c1dbb8804839575b0a838]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/topology/AmbariContextTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/AmbariContext.java > Blueprint deployments failing without version string > > > Key: AMBARI-21721 > URL: https://issues.apache.org/jira/browse/AMBARI-21721 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21721.patch > > > When deploying blueprints without a version specified, try to find a > best-matching repository. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21721) Blueprint deployments failing without version string
[ https://issues.apache.org/jira/browse/AMBARI-21721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127239#comment-16127239 ] Hudson commented on AMBARI-21721: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #11 (See [https://builds.apache.org/job/Ambari-branch-2.6/11/]) AMBARI-21721. Blueprint deployments failing without version string (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=297704d99ad51be7a9152b931d736eeae24dc851]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/AmbariContext.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/topology/AmbariContextTest.java > Blueprint deployments failing without version string > > > Key: AMBARI-21721 > URL: https://issues.apache.org/jira/browse/AMBARI-21721 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21721.patch > > > When deploying blueprints without a version specified, try to find a > best-matching repository. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21725) Web Client Doesn't Display MAINT Repos Correctly
[
https://issues.apache.org/jira/browse/AMBARI-21725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127214#comment-16127214
]
Andrii Tkach commented on AMBARI-21725:
---
+1 for the patch
> Web Client Doesn't Display MAINT Repos Correctly
>
>
> Key: AMBARI-21725
> URL: https://issues.apache.org/jira/browse/AMBARI-21725
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.3
>Reporter: Antonenko Alexander
> Fix For: 2.5.3
>
> Attachments: AMBARI-21725.patch
>
>
> The web client currently doesn't understand {{MAINT}} repositories. When you
> register one it doesn't show the repo differently or identify it as a
> {{MAINT}} repo.
> After applying an upgrade which is a {{MAINT}} upgrade, the upgrade history
> also should indicate that it was a {{MAINT}} style.
> {{MAINT}} is a peer to {{PATCH}} upgrades, so anywhere we have special
> display/text for patches, we should also have the same for maintenance
> repos/upgrades.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21725) Web Client Doesn't Display MAINT Repos Correctly
[
https://issues.apache.org/jira/browse/AMBARI-21725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127213#comment-16127213
]
Hadoop QA commented on AMBARI-21725:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12881932/AMBARI-21725.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11994//console
This message is automatically generated.
> Web Client Doesn't Display MAINT Repos Correctly
>
>
> Key: AMBARI-21725
> URL: https://issues.apache.org/jira/browse/AMBARI-21725
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.3
>Reporter: Antonenko Alexander
> Fix For: 2.5.3
>
> Attachments: AMBARI-21725.patch
>
>
> The web client currently doesn't understand {{MAINT}} repositories. When you
> register one it doesn't show the repo differently or identify it as a
> {{MAINT}} repo.
> After applying an upgrade which is a {{MAINT}} upgrade, the upgrade history
> also should indicate that it was a {{MAINT}} style.
> {{MAINT}} is a peer to {{PATCH}} upgrades, so anywhere we have special
> display/text for patches, we should also have the same for maintenance
> repos/upgrades.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21725) Web Client Doesn't Display MAINT Repos Correctly
[
https://issues.apache.org/jira/browse/AMBARI-21725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonenko Alexander updated AMBARI-21725:
-
Status: Patch Available (was: Open)
> Web Client Doesn't Display MAINT Repos Correctly
>
>
> Key: AMBARI-21725
> URL: https://issues.apache.org/jira/browse/AMBARI-21725
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.3
>Reporter: Antonenko Alexander
> Fix For: 2.5.3
>
> Attachments: AMBARI-21725.patch
>
>
> The web client currently doesn't understand {{MAINT}} repositories. When you
> register one it doesn't show the repo differently or identify it as a
> {{MAINT}} repo.
> After applying an upgrade which is a {{MAINT}} upgrade, the upgrade history
> also should indicate that it was a {{MAINT}} style.
> {{MAINT}} is a peer to {{PATCH}} upgrades, so anywhere we have special
> display/text for patches, we should also have the same for maintenance
> repos/upgrades.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21725) Web Client Doesn't Display MAINT Repos Correctly
[
https://issues.apache.org/jira/browse/AMBARI-21725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonenko Alexander updated AMBARI-21725:
-
Attachment: AMBARI-21725.patch
> Web Client Doesn't Display MAINT Repos Correctly
>
>
> Key: AMBARI-21725
> URL: https://issues.apache.org/jira/browse/AMBARI-21725
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.3
>Reporter: Antonenko Alexander
> Fix For: 2.5.3
>
> Attachments: AMBARI-21725.patch
>
>
> The web client currently doesn't understand {{MAINT}} repositories. When you
> register one it doesn't show the repo differently or identify it as a
> {{MAINT}} repo.
> After applying an upgrade which is a {{MAINT}} upgrade, the upgrade history
> also should indicate that it was a {{MAINT}} style.
> {{MAINT}} is a peer to {{PATCH}} upgrades, so anywhere we have special
> display/text for patches, we should also have the same for maintenance
> repos/upgrades.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21725) Web Client Doesn't Display MAINT Repos Correctly
Antonenko Alexander created AMBARI-21725:
Summary: Web Client Doesn't Display MAINT Repos Correctly
Key: AMBARI-21725
URL: https://issues.apache.org/jira/browse/AMBARI-21725
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.5.3
Reporter: Antonenko Alexander
Fix For: 2.5.3
The web client currently doesn't understand {{MAINT}} repositories. When you
register one it doesn't show the repo differently or identify it as a {{MAINT}}
repo.
After applying an upgrade which is a {{MAINT}} upgrade, the upgrade history
also should indicate that it was a {{MAINT}} style.
{{MAINT}} is a peer to {{PATCH}} upgrades, so anywhere we have special
display/text for patches, we should also have the same for maintenance
repos/upgrades.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21724) Hosts filters work incorrectly
[
https://issues.apache.org/jira/browse/AMBARI-21724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127208#comment-16127208
]
Hadoop QA commented on AMBARI-21724:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12881919/AMBARI-21724.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11993//console
This message is automatically generated.
> Hosts filters work incorrectly
> --
>
> Key: AMBARI-21724
> URL: https://issues.apache.org/jira/browse/AMBARI-21724
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21724.patch, Screenshot from 2017-08-11
> 11-58-27.png
>
>
> Hosts filters work incorrectly
> STR:
> 1)Apply filter with absent of hosts result
> 2)After few seconds appear unsuitable host
> 3)After few seconds in disappear
> Firstly this issue occurs in ambari-2.5.2.0-241
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21723) Redundant type arguments (Java 8)
[ https://issues.apache.org/jira/browse/AMBARI-21723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-21723: --- Attachment: AMBARI-21723.patch > Redundant type arguments (Java 8) > - > > Key: AMBARI-21723 > URL: https://issues.apache.org/jira/browse/AMBARI-21723 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila > Fix For: 3.0.0 > > Attachments: AMBARI-21723.patch > > > Ambari Server is now built with Java 8, which can infer more type arguments > than Java 7. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21723) Redundant type arguments (Java 8)
[ https://issues.apache.org/jira/browse/AMBARI-21723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-21723: --- Status: Patch Available (was: Open) > Redundant type arguments (Java 8) > - > > Key: AMBARI-21723 > URL: https://issues.apache.org/jira/browse/AMBARI-21723 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila > Fix For: 3.0.0 > > Attachments: AMBARI-21723.patch > > > Ambari Server is now built with Java 8, which can infer more type arguments > than Java 7. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21723) Redundant type arguments (Java 8)
[ https://issues.apache.org/jira/browse/AMBARI-21723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-21723: --- Status: Open (was: Patch Available) > Redundant type arguments (Java 8) > - > > Key: AMBARI-21723 > URL: https://issues.apache.org/jira/browse/AMBARI-21723 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila > Fix For: 3.0.0 > > > Ambari Server is now built with Java 8, which can infer more type arguments > than Java 7. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21723) Redundant type arguments (Java 8)
[ https://issues.apache.org/jira/browse/AMBARI-21723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-21723: --- Attachment: (was: AMBARI-21723.patch) > Redundant type arguments (Java 8) > - > > Key: AMBARI-21723 > URL: https://issues.apache.org/jira/browse/AMBARI-21723 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila > Fix For: 3.0.0 > > > Ambari Server is now built with Java 8, which can infer more type arguments > than Java 7. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21721) Blueprint deployments failing without version string
[ https://issues.apache.org/jira/browse/AMBARI-21721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-21721: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Blueprint deployments failing without version string > > > Key: AMBARI-21721 > URL: https://issues.apache.org/jira/browse/AMBARI-21721 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21721.patch > > > When deploying blueprints without a version specified, try to find a > best-matching repository. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21634) Make sure Ambari also considers NIS users
[
https://issues.apache.org/jira/browse/AMBARI-21634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127187#comment-16127187
]
Hadoop QA commented on AMBARI-21634:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12881897/AMBARI-21634_branch-2.5.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-agent|https://builds.apache.org/job/Ambari-trunk-test-patch/11992//artifact/patch-work/testrun_ambari-agent.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11992//console
This message is automatically generated.
> Make sure Ambari also considers NIS users
> --
>
> Key: AMBARI-21634
> URL: https://issues.apache.org/jira/browse/AMBARI-21634
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.5.1
>Reporter: Aman Poonia
>Assignee: Aman Poonia
> Fix For: trunk, 2.5.2
>
> Attachments: AMBARI-21634_branch-2.5.patch, AMBARI-21634.patch
>
>
> Make sure Ambari also considers NIS users while reporting for the users if
> they are present or not.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21723) Redundant type arguments (Java 8)
[
https://issues.apache.org/jira/browse/AMBARI-21723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127164#comment-16127164
]
Hadoop QA commented on AMBARI-21723:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12881902/AMBARI-21723.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 96 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11991//console
This message is automatically generated.
> Redundant type arguments (Java 8)
> -
>
> Key: AMBARI-21723
> URL: https://issues.apache.org/jira/browse/AMBARI-21723
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-21723.patch
>
>
> Ambari Server is now built with Java 8, which can infer more type arguments
> than Java 7.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21713) Python tests started under uid=0 and uid > 0 works differently
[ https://issues.apache.org/jira/browse/AMBARI-21713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127159#comment-16127159 ] Hudson commented on AMBARI-21713: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7887 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7887/]) AMBARI-21713 Python tests started under uid=0 and uid > 0 works (hapylestat: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=12b6caad612b6389aeef256b5bbbaae6d65cc588]) * (edit) ambari-server/src/test/python/stacks/utils/RMFTestCase.py * (edit) ambari-common/src/main/python/resource_management/libraries/functions/packages_analyzer.py * (edit) ambari-server/src/test/python/TestMpacks.py > Python tests started under uid=0 and uid > 0 works differently > -- > > Key: AMBARI-21713 > URL: https://issues.apache.org/jira/browse/AMBARI-21713 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: trunk > > > The cause is sudo.py and same meaning modules, which implements different > logic depends on user uid. Coz of that us tests covering only uid > 0 logic > and starting them from root (on VM or docker) causing them to fail -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21724) Hosts filters work incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-21724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127126#comment-16127126 ] Andrii Tkach commented on AMBARI-21724: --- branch-2.5: 30441 passing (27s) 157 pending > Hosts filters work incorrectly > -- > > Key: AMBARI-21724 > URL: https://issues.apache.org/jira/browse/AMBARI-21724 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.5.2 > > Attachments: AMBARI-21724.patch, Screenshot from 2017-08-11 > 11-58-27.png > > > Hosts filters work incorrectly > STR: > 1)Apply filter with absent of hosts result > 2)After few seconds appear unsuitable host > 3)After few seconds in disappear > Firstly this issue occurs in ambari-2.5.2.0-241 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21724) Hosts filters work incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-21724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21724: -- Status: Patch Available (was: Open) > Hosts filters work incorrectly > -- > > Key: AMBARI-21724 > URL: https://issues.apache.org/jira/browse/AMBARI-21724 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.5.2 > > Attachments: AMBARI-21724.patch, Screenshot from 2017-08-11 > 11-58-27.png > > > Hosts filters work incorrectly > STR: > 1)Apply filter with absent of hosts result > 2)After few seconds appear unsuitable host > 3)After few seconds in disappear > Firstly this issue occurs in ambari-2.5.2.0-241 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21713) Python tests started under uid=0 and uid > 0 works differently
[ https://issues.apache.org/jira/browse/AMBARI-21713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127121#comment-16127121 ] Dmytro Grinenko commented on AMBARI-21713: -- Committed: bbd751130f..845aaa3f0c branch-feature-AMBARI-21450 -> branch-feature-AMBARI-21450 f206e95711..12b6caad61 trunk -> trunk > Python tests started under uid=0 and uid > 0 works differently > -- > > Key: AMBARI-21713 > URL: https://issues.apache.org/jira/browse/AMBARI-21713 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: trunk > > > The cause is sudo.py and same meaning modules, which implements different > logic depends on user uid. Coz of that us tests covering only uid > 0 logic > and starting them from root (on VM or docker) causing them to fail -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21724) Hosts filters work incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-21724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21724: -- Attachment: AMBARI-21724.patch > Hosts filters work incorrectly > -- > > Key: AMBARI-21724 > URL: https://issues.apache.org/jira/browse/AMBARI-21724 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.5.2 > > Attachments: AMBARI-21724.patch, Screenshot from 2017-08-11 > 11-58-27.png > > > Hosts filters work incorrectly > STR: > 1)Apply filter with absent of hosts result > 2)After few seconds appear unsuitable host > 3)After few seconds in disappear > Firstly this issue occurs in ambari-2.5.2.0-241 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-21713) Python tests started under uid=0 and uid > 0 works differently
[ https://issues.apache.org/jira/browse/AMBARI-21713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko resolved AMBARI-21713. -- Resolution: Fixed > Python tests started under uid=0 and uid > 0 works differently > -- > > Key: AMBARI-21713 > URL: https://issues.apache.org/jira/browse/AMBARI-21713 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: trunk > > > The cause is sudo.py and same meaning modules, which implements different > logic depends on user uid. Coz of that us tests covering only uid > 0 logic > and starting them from root (on VM or docker) causing them to fail -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21724) Hosts filters work incorrectly
Andrii Tkach created AMBARI-21724: - Summary: Hosts filters work incorrectly Key: AMBARI-21724 URL: https://issues.apache.org/jira/browse/AMBARI-21724 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.2 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Blocker Fix For: 2.5.2 Hosts filters work incorrectly STR: 1)Apply filter with absent of hosts result 2)After few seconds appear unsuitable host 3)After few seconds in disappear Firstly this issue occurs in ambari-2.5.2.0-241 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21724) Hosts filters work incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-21724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21724: -- Attachment: Screenshot from 2017-08-11 11-58-27.png > Hosts filters work incorrectly > -- > > Key: AMBARI-21724 > URL: https://issues.apache.org/jira/browse/AMBARI-21724 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.5.2 > > Attachments: Screenshot from 2017-08-11 11-58-27.png > > > Hosts filters work incorrectly > STR: > 1)Apply filter with absent of hosts result > 2)After few seconds appear unsuitable host > 3)After few seconds in disappear > Firstly this issue occurs in ambari-2.5.2.0-241 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-21565) RU: Hive service check was failed during RU
[ https://issues.apache.org/jira/browse/AMBARI-21565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk resolved AMBARI-21565. -- Resolution: Duplicate AMBARI-21566 > RU: Hive service check was failed during RU > --- > > Key: AMBARI-21565 > URL: https://issues.apache.org/jira/browse/AMBARI-21565 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > > Std.err > > > > Exception in thread Thread-4: > Traceback (most recent call last): > File "/usr/lib64/python2.6/threading.py", line 532, in __bootstrap_inner > self.run() > File "/usr/lib64/python2.6/threading.py", line 736, in run > self.function(*self.args, **self.kwargs) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 383, in _on_timeout > terminate_process(proc, terminate_strategy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/signal_utils.py", > line 48, in terminate_process > kill_process_tree(proc) > File > "/usr/lib/python2.6/site-packages/resource_management/core/signal_utils.py", > line 91, in kill_process_tree > shell.checked_call(["bash", kill_tree_script, str(proc.pid), > str(signal.SIGKILL)]) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 72, in inner > result = function(command, **kwargs) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 102, in checked_call > tries=tries, try_sleep=try_sleep, > timeout_kill_strategy=timeout_kill_strategy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 150, in _call_wrapper > result = _call(command, **kwargs_copy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 303, in _call > raise ExecutionFailed(err_msg, code, out, err) > ExecutionFailed: Execution of 'bash > /usr/lib/python2.6/site-packages/resource_management/core/files/killtree.sh > 6363 9' returned 1. kill: top: invalid signal > Try `kill --help' for more information. > > Exception in thread Thread-5: > Traceback (most recent call last): > File "/usr/lib64/python2.6/threading.py", line 532, in __bootstrap_inner > self.run() > File "/usr/lib64/python2.6/threading.py", line 736, in run > self.function(*self.args, **self.kwargs) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 383, in _on_timeout > terminate_process(proc, terminate_strategy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/signal_utils.py", > line 48, in terminate_process > kill_process_tree(proc) > File > "/usr/lib/python2.6/site-packages/resource_management/core/signal_utils.py", > line 91, in kill_process_tree > shell.checked_call(["bash", kill_tree_script, str(proc.pid), > str(signal.SIGKILL)]) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 72, in inner > result = function(command, **kwargs) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 102, in checked_call > tries=tries, try_sleep=try_sleep, > timeout_kill_strategy=timeout_kill_strategy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 150, in _call_wrapper > result = _call(command, **kwargs_copy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 303, in _call > raise ExecutionFailed(err_msg, code, out, err) > ExecutionFailed: Execution of 'bash > /usr/lib/python2.6/site-packages/resource_management/core/files/killtree.sh > 8306 9' returned 1. kill: top: invalid signal > Try `kill --help' for more information. > > Exception in thread Thread-6: > Traceback (most recent call last): > File "/usr/lib64/python2.6/threading.py", line 532, in __bootstrap_inner > self.run() > File "/usr/lib64/python2.6/threading.py", line 736, in run > self.function(*self.args, **self.kwargs) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 383, in _on_timeout > terminate_process(proc, terminate_strategy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/signal_utils.py", > line 48, in terminate_process > kill_process_tree(proc) > File > "/usr/lib/python2.6/site-packages/resource_management/core/signal_utils.py", > line 91, in kill_process_tree > shell.checked_call(["bash", kill_tree_script, str(proc.pid), >
[jira] [Updated] (AMBARI-21723) Redundant type arguments (Java 8)
[ https://issues.apache.org/jira/browse/AMBARI-21723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-21723: --- Status: Patch Available (was: Open) > Redundant type arguments (Java 8) > - > > Key: AMBARI-21723 > URL: https://issues.apache.org/jira/browse/AMBARI-21723 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila > Fix For: 3.0.0 > > Attachments: AMBARI-21723.patch > > > Ambari Server is now built with Java 8, which can infer more type arguments > than Java 7. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21723) Redundant type arguments (Java 8)
[ https://issues.apache.org/jira/browse/AMBARI-21723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-21723: --- Status: Open (was: Patch Available) > Redundant type arguments (Java 8) > - > > Key: AMBARI-21723 > URL: https://issues.apache.org/jira/browse/AMBARI-21723 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila > Fix For: 3.0.0 > > Attachments: AMBARI-21723.patch > > > Ambari Server is now built with Java 8, which can infer more type arguments > than Java 7. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21723) Redundant type arguments (Java 8)
[ https://issues.apache.org/jira/browse/AMBARI-21723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-21723: --- Attachment: (was: AMBARI-21723.patch) > Redundant type arguments (Java 8) > - > > Key: AMBARI-21723 > URL: https://issues.apache.org/jira/browse/AMBARI-21723 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila > Fix For: 3.0.0 > > Attachments: AMBARI-21723.patch > > > Ambari Server is now built with Java 8, which can infer more type arguments > than Java 7. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21723) Redundant type arguments (Java 8)
[ https://issues.apache.org/jira/browse/AMBARI-21723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-21723: --- Attachment: AMBARI-21723.patch > Redundant type arguments (Java 8) > - > > Key: AMBARI-21723 > URL: https://issues.apache.org/jira/browse/AMBARI-21723 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila > Fix For: 3.0.0 > > Attachments: AMBARI-21723.patch > > > Ambari Server is now built with Java 8, which can infer more type arguments > than Java 7. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21364) DB consistency checker throws errors for missing 'parquet-logging' and 'product-info' configs after Ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-21364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127017#comment-16127017
]
Dmitry Lysnichenko commented on AMBARI-21364:
-
[~mattwuenschel],
This jira targets Ambari upgrade, not stack upgrade. Could you please open a
new jira and describe your issue? Thanks
> DB consistency checker throws errors for missing 'parquet-logging' and
> 'product-info' configs after Ambari upgrade
> --
>
> Key: AMBARI-21364
> URL: https://issues.apache.org/jira/browse/AMBARI-21364
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Vivek Sharma
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Labels: upgrade
> Fix For: 2.5.2
>
> Attachments: AMBARI-21364.patch, AMBARI-21364.trunk.patch,
> AMBARI-21364.trunk.patch
>
>
> *STR*
> # Deployed cluster with Ambari version: 2.5.1.0-159 and HDP version:
> 2.6.1.0-129
> # Upgrade Ambari to 2.5.2.0-74 (hash:
> fd30644590991deb41241454d6e9091ed7a38e92)
> # Run "ambari-server start"
> {code}
> root@ctr-e133-1493418528701-156570-01-05:/hwqe/hadoopqe# ambari-server
> restart
> Using python /usr/bin/python
> Restarting ambari-server
> Waiting for server stop...
> Ambari Server stopped
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server start..
> DB configs consistency check failed. Run "ambari-server start
> --skip-database-check" to skip. You may try --auto-fix-database flag to
> attempt to fix issues automatically. If you use this "--skip-database-check"
> option, do not make any changes to your cluster topology or perform a cluster
> upgrade until you correct the database consistency issues. See
> /var/log/ambari-server/ambari-server-check-database.log for more details on
> the consistency issues.
> ERROR: Exiting with exit code -1.
> REASON: Ambari Server java process has stopped. Please check the logs for
> more information.
> {code}
> DB log: ambari-server-check-database.log
> {code}
> 2017-06-27 13:51:38,743 INFO - Executing query 'GET_SERVICES_WITH_CONFIGS'
> 2017-06-27 13:51:38,748 INFO - Comparing service configs from stack with
> configs that we got from db
> 2017-06-27 13:51:38,748 INFO - Getting services from metainfo
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / KAFKA
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / PIG
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / ZEPPELIN
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / LOGSEARCH
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / MAPREDUCE2
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / SLIDER
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / HIVE
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / TEZ
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / HBASE
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / OOZIE
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / FLUME
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / MAHOUT
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / HDFS
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / DRUID
> 2017-06-27 13:51:38,748 INFO - Processing HDP-2.6 / AMBARI_METRICS
> 2017-06-27 13:51:38,749 INFO - Processing HDP-2.6 / SPARK
> 2017-06-27 13:51:38,749 INFO - Processing HDP-2.6 / SMARTSENSE
> 2017-06-27 13:51:38,749 INFO - Processing HDP-2.6 / AMBARI_INFRA
> 2017-06-27 13:51:38,749 INFO - Processing HDP-2.6 / YARN
> 2017-06-27 13:51:38,749 INFO - Processing HDP-2.6 / FALCON
> 2017-06-27 13:51:38,749 INFO - Processing HDP-2.6 / SPARK2
> 2017-06-27 13:51:38,749 INFO - Processing HDP-2.6 / ZOOKEEPER
> 2017-06-27 13:51:38,749 INFO - Processing HDP-2.6 / ATLAS
> 2017-06-27 13:51:38,749 INFO - Processing HDP-2.6 / SQOOP
> 2017-06-27 13:51:38,749 INFO - Processing HDP-2.6 / STORM
> 2017-06-27 13:51:38,749 INFO - Processing HDP-2.6 / KNOX
> 2017-06-27 13:51:38,749 INFO - Processing HDP-2.6 / KERBEROS
> 2017-06-27 13:51:38,749 INFO - Comparing required service configs from stack
> with mapped service configs from db
> 2017-06-27 13:51:38,751 ERROR - Required config(s): product-info is(are) not
> available for service SMARTSENSE with service config version 2 in cluster cl1
> 2017-06-27 13:51:38,751 ERROR - Required config(s): parquet-logging is(are)
> not available for service HIVE with service config version 7 in cluster cl1
> 2017-06-27
[jira] [Updated] (AMBARI-21723) Redundant type arguments (Java 8)
[ https://issues.apache.org/jira/browse/AMBARI-21723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-21723: --- Status: Patch Available (was: Open) > Redundant type arguments (Java 8) > - > > Key: AMBARI-21723 > URL: https://issues.apache.org/jira/browse/AMBARI-21723 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila > Fix For: 3.0.0 > > Attachments: AMBARI-21723.patch > > > Ambari Server is now built with Java 8, which can infer more type arguments > than Java 7. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21723) Redundant type arguments (Java 8)
[ https://issues.apache.org/jira/browse/AMBARI-21723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-21723: --- Attachment: AMBARI-21723.patch > Redundant type arguments (Java 8) > - > > Key: AMBARI-21723 > URL: https://issues.apache.org/jira/browse/AMBARI-21723 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila > Fix For: 3.0.0 > > Attachments: AMBARI-21723.patch > > > Ambari Server is now built with Java 8, which can infer more type arguments > than Java 7. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21723) Redundant type arguments (Java 8)
[ https://issues.apache.org/jira/browse/AMBARI-21723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-21723: --- Issue Type: Improvement (was: Bug) > Redundant type arguments (Java 8) > - > > Key: AMBARI-21723 > URL: https://issues.apache.org/jira/browse/AMBARI-21723 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila > Fix For: 3.0.0 > > > Ambari Server is now built with Java 8, which can infer more type arguments > than Java 7. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21723) Redundant type arguments (Java 8)
Doroszlai, Attila created AMBARI-21723: -- Summary: Redundant type arguments (Java 8) Key: AMBARI-21723 URL: https://issues.apache.org/jira/browse/AMBARI-21723 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Doroszlai, Attila Assignee: Doroszlai, Attila Fix For: 3.0.0 Ambari Server is now built with Java 8, which can infer more type arguments than Java 7. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21634) Make sure Ambari also considers NIS users
[ https://issues.apache.org/jira/browse/AMBARI-21634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Poonia updated AMBARI-21634: - Attachment: AMBARI-21634_branch-2.5.patch > Make sure Ambari also considers NIS users > -- > > Key: AMBARI-21634 > URL: https://issues.apache.org/jira/browse/AMBARI-21634 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.5.1 >Reporter: Aman Poonia >Assignee: Aman Poonia > Fix For: trunk, 2.5.2 > > Attachments: AMBARI-21634_branch-2.5.patch, AMBARI-21634.patch > > > Make sure Ambari also considers NIS users while reporting for the users if > they are present or not. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21634) Make sure Ambari also considers NIS users
[ https://issues.apache.org/jira/browse/AMBARI-21634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Poonia updated AMBARI-21634: - Status: Patch Available (was: Open) > Make sure Ambari also considers NIS users > -- > > Key: AMBARI-21634 > URL: https://issues.apache.org/jira/browse/AMBARI-21634 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.5.1 >Reporter: Aman Poonia >Assignee: Aman Poonia > Fix For: trunk, 2.5.2 > > Attachments: AMBARI-21634_branch-2.5.patch, AMBARI-21634.patch > > > Make sure Ambari also considers NIS users while reporting for the users if > they are present or not. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21634) Make sure Ambari also considers NIS users
[ https://issues.apache.org/jira/browse/AMBARI-21634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Poonia updated AMBARI-21634: - Fix Version/s: 2.5.2 > Make sure Ambari also considers NIS users > -- > > Key: AMBARI-21634 > URL: https://issues.apache.org/jira/browse/AMBARI-21634 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.5.1 >Reporter: Aman Poonia >Assignee: Aman Poonia > Fix For: trunk, 2.5.2 > > Attachments: AMBARI-21634.patch > > > Make sure Ambari also considers NIS users while reporting for the users if > they are present or not. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21634) Make sure Ambari also considers NIS users
[ https://issues.apache.org/jira/browse/AMBARI-21634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Poonia updated AMBARI-21634: - Status: Open (was: Patch Available) > Make sure Ambari also considers NIS users > -- > > Key: AMBARI-21634 > URL: https://issues.apache.org/jira/browse/AMBARI-21634 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.5.1 >Reporter: Aman Poonia >Assignee: Aman Poonia > Fix For: trunk > > Attachments: AMBARI-21634.patch > > > Make sure Ambari also considers NIS users while reporting for the users if > they are present or not. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
