[jira] [Commented] (AMBARI-15775) Integrate Red Hat Satellite option in Ambari Admin
[
https://issues.apache.org/jira/browse/AMBARI-15775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231666#comment-15231666
]
Hadoop QA commented on AMBARI-15775:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797645/AMBARI-15775.v2.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 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-admin.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6301//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6301//console
This message is automatically generated.
> Integrate Red Hat Satellite option in Ambari Admin
> --
>
> Key: AMBARI-15775
> URL: https://issues.apache.org/jira/browse/AMBARI-15775
> Project: Ambari
> Issue Type: Task
> Components: ambari-admin
>Affects Versions: 2.4.0
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: 2.4.0
>
> Attachments: AMBARI-15775.v0.patch, AMBARI-15775.v1.patch,
> AMBARI-15775.v2.patch
>
>
> Provide RedHat satellite option. It can be used wherever we show redhat6
> urls, and applicable to redhat6/redhat7. For example, registering repos, etc.
> The API call to update links when using VDF can specify the new property. In
> order to make it more generic (and default {{true}}), it is called
> "{{ambari_managed_repositories}}". API looks like:
> {noformat}
> PUT /api/v1/stacks/HDP/versions/2.3/repository_versions/2
> {
> "RepositoryVersions" : {
> "id" : 2
> },
> "operating_systems" : [
> {
> "OperatingSystems" : {
> "ambari_managed_repositories": false,
> "os_type" : "redhat6",
> "repository_version_id" : 2,
> "stack_name" : "HDP",
> "stack_version" : "2.3"
> },
> "repositories" : [
> {
> "Repositories" : {
> "base_url" : "http://repos.ambari.apache.org/hdp/HDP-2.3.4.14-4;,
> "repo_id" : "HDP-2.3",
> "repo_name" : "HDP"
> }
> },
> {
> "Repositories" : {
> "base_url" :
> "http://repos.ambari.apache.org/hdp/HDP-UTILS-1.1.0.20;,
> "repo_id" : "HDP-UTILS-1.1.0.20",
> "repo_name" : "HDP-UTILS"
> }
> }
> ]
> }
> ]
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15768) Ambari Widget should display metrics for available metrics even if some of the metrics it expects are not returned by API
[ https://issues.apache.org/jira/browse/AMBARI-15768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231553#comment-15231553 ] Hudson commented on AMBARI-15768: - ABORTED: Integrated in Ambari-trunk-Commit #4616 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4616/]) AMBARI-15768. Ambari Widget should display metrics for available metrics (yusaku: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e3edcf574c387aa8d4f16a07ae97d268a105247e]) * ambari-web/app/mixins/common/widgets/widget_mixin.js * ambari-web/test/mixins/common/widget_mixin_test.js > Ambari Widget should display metrics for available metrics even if some of > the metrics it expects are not returned by API > - > > Key: AMBARI-15768 > URL: https://issues.apache.org/jira/browse/AMBARI-15768 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15768.patch, AMBARI-15768_2.2.2.patch, Screen > Shot 2016-04-06 at 2.53.23 PM.png > > > For example, Namenode RPC widget requests 5 metrics from the backend. 2 of > the metrics' availability depends on a Namenode config to be present. In such > a case, the widget should display whatever metrics that are available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15635) Storm & Kafka should've default nproc ,nofile values
[ https://issues.apache.org/jira/browse/AMBARI-15635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231555#comment-15231555 ] Hudson commented on AMBARI-15635: - ABORTED: Integrated in Ambari-trunk-Commit #4616 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4616/]) AMBARI-15635. ambari is setting very small limits for kafka causing (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=71a1f7e0e5985b1a77bf09b976ebda3ab3fdbbf5]) * ambari-server/src/main/resources/common-services/KAFKA/0.8.1.2.2/configuration/kafka-env.xml * ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/package/templates/storm.conf.j2 * ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/configuration/storm-env.xml * ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/package/scripts/params_linux.py > Storm & Kafka should've default nproc ,nofile values > - > > Key: AMBARI-15635 > URL: https://issues.apache.org/jira/browse/AMBARI-15635 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani > Attachments: AMBARI-15635.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15577) Stack Featurize Hive Service
[
https://issues.apache.org/jira/browse/AMBARI-15577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231533#comment-15231533
]
Hadoop QA commented on AMBARI-15577:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797565/AMBARI-15577.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 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6299//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6299//console
This message is automatically generated.
> Stack Featurize Hive Service
>
>
> Key: AMBARI-15577
> URL: https://issues.apache.org/jira/browse/AMBARI-15577
> Project: Ambari
> Issue Type: Technical task
> Components: stacks
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Jayush Luniya
>Assignee: Juanjo Marron
> Fix For: 2.4.0
>
> Attachments: AMBARI-15577.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15741) Remove PHD references from HAWQ
[ https://issues.apache.org/jira/browse/AMBARI-15741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt updated AMBARI-15741: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Remove PHD references from HAWQ > --- > > Key: AMBARI-15741 > URL: https://issues.apache.org/jira/browse/AMBARI-15741 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.2.0 >Reporter: Lav Jain >Assignee: Lav Jain >Priority: Minor > Fix For: 2.3.0, 2.2.2 > > Attachments: AMBARI-15741.branch22.patch, AMBARI-15741.patch > > > Remove any reference to PHD (pivotal) stack in HAWQ codebase as it has been > obsoleted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15724) Integrate Version Registration in Select Stack Page
[ https://issues.apache.org/jira/browse/AMBARI-15724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231507#comment-15231507 ] Xi Wang commented on AMBARI-15724: -- 25612 tests complete (25 seconds) 154 tests pending > Integrate Version Registration in Select Stack Page > --- > > Key: AMBARI-15724 > URL: https://issues.apache.org/jira/browse/AMBARI-15724 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Xi Wang >Assignee: Xi Wang >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15724.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15766) Create a new alert type that is based on timeseries metrics
[
https://issues.apache.org/jira/browse/AMBARI-15766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231509#comment-15231509
]
Hadoop QA commented on AMBARI-15766:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797534/AMBARI-15766-trunk_1.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 4 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6298//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6298//console
This message is automatically generated.
> Create a new alert type that is based on timeseries metrics
> ---
>
> Key: AMBARI-15766
> URL: https://issues.apache.org/jira/browse/AMBARI-15766
> Project: Ambari
> Issue Type: Task
> Components: alerts, ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15766-trunk_1.patch
>
>
> There are a few requirements around creating alerts based on the time-series
> data stored in AMS. They fall in the the general category of:
> identify a metrics (name of the metrics, app name)
> - identify a window (e.g. last 10 minutes, last 1 day)
> - get the data points
> - add them up, or
> - compute average, or
> - compute standard deviations, or
> ...
> - compare the value to a threshold
> - emit an alert if needed (WARN, CRITICAL, etc)
> We should also allow for alerts based on multiple metrics but there is no ask
> for such a capability. Just something to keep in mind while designing.
> It seems general enough that we should define an alert type that can be
> instantiated by services to define specific alerts. Users can add additional
> alerts if they so choose.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15635) Storm & Kafka should've default nproc ,nofile values
[ https://issues.apache.org/jira/browse/AMBARI-15635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231469#comment-15231469 ] Hudson commented on AMBARI-15635: - FAILURE: Integrated in Ambari-branch-2.2 #610 (See [https://builds.apache.org/job/Ambari-branch-2.2/610/]) AMBARI-15635. ambari is setting very small limits for kafka causing (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=61fa49bbf1758537906db8c9e2fee6a3da2cf95b]) * ambari-server/src/main/resources/common-services/KAFKA/0.8.1.2.2/configuration/kafka-env.xml * ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/package/templates/storm.conf.j2 * ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/package/scripts/params_linux.py * ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/configuration/storm-env.xml > Storm & Kafka should've default nproc ,nofile values > - > > Key: AMBARI-15635 > URL: https://issues.apache.org/jira/browse/AMBARI-15635 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani > Attachments: AMBARI-15635.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15773) Password must not by displayed by UpgradeItem and Stage resources in the API
[
https://issues.apache.org/jira/browse/AMBARI-15773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231468#comment-15231468
]
Hudson commented on AMBARI-15773:
-
FAILURE: Integrated in Ambari-branch-2.2 #610 (See
[https://builds.apache.org/job/Ambari-branch-2.2/610/])
AMBARI-15773. Password must not by displayed by UpgradeItem and Stage
(afernandez:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ed29d1cd1fa7db50bed2ed12352120f3a7a03475])
*
ambari-server/src/main/java/org/apache/ambari/server/utils/SecretReference.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeItemResourceProvider.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StageResourceProvider.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClientConfigResourceProvider.java
> Password must not by displayed by UpgradeItem and Stage resources in the API
>
>
> Key: AMBARI-15773
> URL: https://issues.apache.org/jira/browse/AMBARI-15773
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Fix For: 2.2.2
>
> Attachments: AMBARI-15773.branch-2.2.patch, AMBARI-15773.trunk.patch
>
>
> STR:
> * Install ambari-server-2.2.2.0-391 (ambari-server --hash:
> 8b49b71d5ef602e1252049fbc970958fbe05806e)
> * Install HDP 2.3 or 2.4
> * Install another version in order to perform RU or EU
> * Use the API to navigate to
> http://server:8080/api/v1/clusters/cl1/upgrades/##/upgrade_groups/1/upgrade_items/1
> Notice that the output contains the ambari_db_rca_password in plaintext,
> {code}
> "host_params" :
> "{\"agent_stack_retry_count\":\"5\",\"agent_stack_retry_on_unavailability\":\"false\",\"ambari_db_rca_driver\":\"org.postgresql.Driver\",\"ambari_db_rca_password\":\"bigdatacustom\",\"ambari_db_rca_url\":\"jdbc:postgresql://172.22.117.211:5432/ambaricustom\",\"ambari_db_rca_username\":\"ambaricustomuser\",\"current_version\":\"2.4.0.0-169\",\"db_driver_filename\":\"mysql-connector-java.jar\",\"db_name\":\"ambaricustom\",\"host_sys_prepped\":\"false\",\"java_home\":\"/usr/jdk64/jdk1.8.0_60\",\"java_version\":\"8\",\"jdk_location\":\"http://os-s11-4-snjlmu-ambari-se-eu-3-5.novalocal:8080/resources/\",\"mysql_jdbc_url\":\"http://os-s11-4-snjlmu-ambari-se-eu-3-5.novalocal:8080/resources//mysql-connector-java.jar\",\"not_managed_hdfs_path_list\":\"[\\\"/apps/hive/warehouse\\\",\\\"/apps/falcon\\\",\\\"/mr-history/done\\\",\\\"/app-logs\\\",\\\"/tmp\\\"]\",\"oracle_jdbc_url\":\"http://os-s11-4-snjlmu-ambari-se-eu-3-5.novalocal:8080/resources//ojdbc6.jar\",\"stack_name\":\"HDP\",\"stack_version\":\"2.4\"};,
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15768) Ambari Widget should display metrics for available metrics even if some of the metrics it expects are not returned by API
[ https://issues.apache.org/jira/browse/AMBARI-15768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231467#comment-15231467 ] Hudson commented on AMBARI-15768: - FAILURE: Integrated in Ambari-branch-2.2 #610 (See [https://builds.apache.org/job/Ambari-branch-2.2/610/]) AMBARI-15768. Ambari Widget should display metrics for available metrics (yusaku: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=38ad05bda646c636dd0fc841ee0044a2411431b9]) * ambari-web/test/mixins/common/widget_mixin_test.js * ambari-web/app/mixins/common/widgets/widget_mixin.js > Ambari Widget should display metrics for available metrics even if some of > the metrics it expects are not returned by API > - > > Key: AMBARI-15768 > URL: https://issues.apache.org/jira/browse/AMBARI-15768 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15768.patch, AMBARI-15768_2.2.2.patch, Screen > Shot 2016-04-06 at 2.53.23 PM.png > > > For example, Namenode RPC widget requests 5 metrics from the backend. 2 of > the metrics' availability depends on a Namenode config to be present. In such > a case, the widget should display whatever metrics that are available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-13240) Kerberos: Allow multiple KDC hosts to be set while enabling Kerberos
[
https://issues.apache.org/jira/browse/AMBARI-13240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-13240:
--
Status: Patch Available (was: Open)
> Kerberos: Allow multiple KDC hosts to be set while enabling Kerberos
>
>
> Key: AMBARI-13240
> URL: https://issues.apache.org/jira/browse/AMBARI-13240
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server, ambari-web
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Minor
> Labels: kerberos
> Fix For: 2.3.0
>
> Attachments: AMBARI-13240_trunk_01.patch
>
>
> Because multiple KDCs may exist for an installation (failover, high
> availability, etc...), Ambari should allow a user to specify multiple KDC
> hosts to be set while enabling Kerberos and updating the Kerberos service's
> configuration.
> This should be done by allowing {{kerberos-env/kdc_host}} to accept a
> (comma-)delimited list of hosts and then parsing that list properly when
> building the krb5.conf file where each {{kdc_host}} item generates an entry
> in the relevant realm block. For example:
> {noformat:title=kerberos-env}
> {
> ...
> "kdc_hosts" : "kdc1.example.com, kdc2.example.com"
> ...
> }
> {noformat}
> {noformat:title=krb5.conf}
> [realms]
> EXAMPLE.COM = {
> ...
> kdc = kdc1.example.com
> kdc = kdc2.example.com
> ...
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-13240) Kerberos: Allow multiple KDC hosts to be set while enabling Kerberos
[
https://issues.apache.org/jira/browse/AMBARI-13240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-13240:
--
Attachment: AMBARI-13240_trunk_01.patch
> Kerberos: Allow multiple KDC hosts to be set while enabling Kerberos
>
>
> Key: AMBARI-13240
> URL: https://issues.apache.org/jira/browse/AMBARI-13240
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server, ambari-web
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Minor
> Labels: kerberos
> Fix For: 2.3.0
>
> Attachments: AMBARI-13240_trunk_01.patch
>
>
> Because multiple KDCs may exist for an installation (failover, high
> availability, etc...), Ambari should allow a user to specify multiple KDC
> hosts to be set while enabling Kerberos and updating the Kerberos service's
> configuration.
> This should be done by allowing {{kerberos-env/kdc_host}} to accept a
> (comma-)delimited list of hosts and then parsing that list properly when
> building the krb5.conf file where each {{kdc_host}} item generates an entry
> in the relevant realm block. For example:
> {noformat:title=kerberos-env}
> {
> ...
> "kdc_hosts" : "kdc1.example.com, kdc2.example.com"
> ...
> }
> {noformat}
> {noformat:title=krb5.conf}
> [realms]
> EXAMPLE.COM = {
> ...
> kdc = kdc1.example.com
> kdc = kdc2.example.com
> ...
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15775) Integrate Red Hat Satellite option in Ambari Admin
[
https://issues.apache.org/jira/browse/AMBARI-15775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhe (Joe) Wang updated AMBARI-15775:
Attachment: AMBARI-15775.v1.patch
ambari-admin:
Executed 64 of 64 SUCCESS (0.08 secs / 0.298 secs)
Manual testing done.
> Integrate Red Hat Satellite option in Ambari Admin
> --
>
> Key: AMBARI-15775
> URL: https://issues.apache.org/jira/browse/AMBARI-15775
> Project: Ambari
> Issue Type: Task
> Components: ambari-admin
>Affects Versions: 2.4.0
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: 2.4.0
>
> Attachments: AMBARI-15775.v0.patch, AMBARI-15775.v1.patch
>
>
> Provide RedHat satellite option. It can be used wherever we show redhat6
> urls, and applicable to redhat6/redhat7. For example, registering repos, etc.
> The API call to update links when using VDF can specify the new property. In
> order to make it more generic (and default {{true}}), it is called
> "{{ambari_managed_repositories}}". API looks like:
> {noformat}
> PUT /api/v1/stacks/HDP/versions/2.3/repository_versions/2
> {
> "RepositoryVersions" : {
> "id" : 2
> },
> "operating_systems" : [
> {
> "OperatingSystems" : {
> "ambari_managed_repositories": false,
> "os_type" : "redhat6",
> "repository_version_id" : 2,
> "stack_name" : "HDP",
> "stack_version" : "2.3"
> },
> "repositories" : [
> {
> "Repositories" : {
> "base_url" : "http://repos.ambari.apache.org/hdp/HDP-2.3.4.14-4;,
> "repo_id" : "HDP-2.3",
> "repo_name" : "HDP"
> }
> },
> {
> "Repositories" : {
> "base_url" :
> "http://repos.ambari.apache.org/hdp/HDP-UTILS-1.1.0.20;,
> "repo_id" : "HDP-UTILS-1.1.0.20",
> "repo_name" : "HDP-UTILS"
> }
> }
> ]
> }
> ]
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15700) Stack advisor: Component layout recommendation needs support for avoiding hosts in maintenance mode
[ https://issues.apache.org/jira/browse/AMBARI-15700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-15700: --- Attachment: rb45713.patch > Stack advisor: Component layout recommendation needs support for avoiding > hosts in maintenance mode > --- > > Key: AMBARI-15700 > URL: https://issues.apache.org/jira/browse/AMBARI-15700 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.4.0 > > Attachments: rb45713.patch > > > Include maintenance_state in hosts JSON so that the stack advisor can use it > when performing an action like component layout recommendation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15741) Remove PHD references from HAWQ
[
https://issues.apache.org/jira/browse/AMBARI-15741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231369#comment-15231369
]
Hadoop QA commented on AMBARI-15741:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797556/AMBARI-15741.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 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6296//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6296//console
This message is automatically generated.
> Remove PHD references from HAWQ
> ---
>
> Key: AMBARI-15741
> URL: https://issues.apache.org/jira/browse/AMBARI-15741
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk, 2.2.0
>Reporter: Lav Jain
>Assignee: Lav Jain
>Priority: Minor
> Fix For: 2.3.0, 2.2.2
>
> Attachments: AMBARI-15741.branch22.patch, AMBARI-15741.patch
>
>
> Remove any reference to PHD (pivotal) stack in HAWQ codebase as it has been
> obsoleted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15764) Add "services" element to compatible_repository_versions endpoint
[ https://issues.apache.org/jira/browse/AMBARI-15764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-15764: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Add "services" element to compatible_repository_versions endpoint > - > > Key: AMBARI-15764 > URL: https://issues.apache.org/jira/browse/AMBARI-15764 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15764.patch > > > The services/stack_services elements should be added to the endpoint to > reduce calls to the backend. > Also fixed issues where the compatible endpoint would not return correctly > with a user predicate. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15745) Create Alert For Reporting Potential Issues With Slow REST Responses
[
https://issues.apache.org/jira/browse/AMBARI-15745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231316#comment-15231316
]
Hudson commented on AMBARI-15745:
-
ABORTED: Integrated in Ambari-trunk-Commit #4615 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4615/])
AMBARI-15745 - Create Alert For Reporting Potential Issues With Slow (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=28f1a958d09216e7a69d42ef3b0796c90cdcc0c4])
*
ambari-server/src/test/java/org/apache/ambari/server/api/services/AmbariMetaInfoTest.java
* ambari-server/src/main/java/org/apache/ambari/server/alerts/AlertRunnable.java
*
ambari-server/src/test/java/org/apache/ambari/server/alerts/StaleAlertRunnableTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/alerts/StaleAlertRunnable.java
*
ambari-server/src/main/java/org/apache/ambari/server/alerts/AgentHeartbeatAlertRunnable.java
*
ambari-server/src/test/java/org/apache/ambari/server/metadata/AgentAlertDefinitionsTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/alerts/AmbariPerformanceRunnable.java
*
ambari-server/src/main/java/org/apache/ambari/server/state/alert/ParameterizedSource.java
*
ambari-server/src/main/java/org/apache/ambari/server/state/alert/ScriptSource.java
*
ambari-server/src/main/java/org/apache/ambari/server/state/alert/ServerSource.java
*
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionManager.java
*
ambari-server/src/main/java/org/apache/ambari/server/state/services/AmbariServerAlertService.java
*
ambari-server/src/test/java/org/apache/ambari/server/alerts/AmbariPerformanceRunnableTest.java
*
ambari-server/src/test/java/org/apache/ambari/server/alerts/AgentHeartbeatAlertRunnableTest.java
* ambari-server/src/main/resources/alerts.json
> Create Alert For Reporting Potential Issues With Slow REST Responses
>
>
> Key: AMBARI-15745
> URL: https://issues.apache.org/jira/browse/AMBARI-15745
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15745.patch
>
>
> There are many factors which can influence the response rate of the REST API
> when the web client polls various endpoints:
> - Database access problems
> - Federated PropertyProvider delays
> - Serialization Time of JSON
> If the response rate of the REST API is poor, this can affect the overall UX
> of the product and produce a situation where Ambari doesn't seem to be
> responding.
> There should be an alert which provides queries into various parts of Ambari
> in order to determine if response times are acceptable.
> - This should be a {{SERVER}} side task
> - If possible, the query should be made directly through the ResourceProvider
> framework to simulate a REST request. It should be made against the cluster
> endpoint since that's what is most likely polled.
> - The alert should have configurable values for the threshold settings.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15646) Audit Log Code Cleanup & Safety
[ https://issues.apache.org/jira/browse/AMBARI-15646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231319#comment-15231319 ] Hudson commented on AMBARI-15646: - ABORTED: Integrated in Ambari-trunk-Commit #4615 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4615/]) AMBARI-15646. Audit Log Code Cleanup & Safety. (Daniel Gergely via (stoader: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6320d589f942b41cdab34c1de241423ccb5b4752]) * ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostComponentResourceProvider.java * ambari-server/src/main/java/org/apache/ambari/server/cleanup/ClasspathScannerUtils.java * ambari-server/src/main/java/org/apache/ambari/server/security/authorization/PermissionHelper.java * ambari-server/src/main/java/org/apache/ambari/server/notifications/dispatchers/EmailDispatcher.java * ambari-server/src/test/java/org/apache/ambari/server/audit/request/AbstractBaseCreator.java * ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertTargetResourceProvider.java * ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionDBAccessorImpl.java * ambari-server/src/main/java/org/apache/ambari/server/audit/event/OperationStatusAuditEvent.java * ambari-server/src/test/java/org/apache/ambari/server/security/authentication/AmbariAuthenticationFilterTest.java * ambari-server/src/main/java/org/apache/ambari/server/audit/event/request/StartOperationRequestAuditEvent.java * ambari-server/src/main/java/org/apache/ambari/server/audit/request/eventcreator/MemberEventCreator.java * ambari-server/src/main/java/org/apache/ambari/server/audit/request/eventcreator/ServiceEventCreator.java * ambari-server/src/main/java/org/apache/ambari/server/audit/request/eventcreator/ViewPrivilegeEventCreator.java * ambari-server/src/main/java/org/apache/ambari/server/audit/event/TaskStatusAuditEvent.java * ambari-server/src/main/java/org/apache/ambari/server/audit/request/eventcreator/UpgradeEventCreator.java * ambari-server/src/main/java/org/apache/ambari/server/audit/request/eventcreator/GroupEventCreator.java * ambari-server/src/main/java/org/apache/ambari/server/audit/request/RequestAuditLoggerImpl.java * ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UpgradeResourceProviderTest.java * ambari-server/src/main/java/org/apache/ambari/server/audit/request/eventcreator/BlueprintExportEventCreator.java * ambari-server/src/main/java/org/apache/ambari/server/audit/request/eventcreator/ServiceConfigDownloadEventCreator.java * ambari-server/src/main/java/org/apache/ambari/server/audit/request/eventcreator/RecommendationIgnoreEventCreator.java * ambari-server/src/main/java/org/apache/ambari/server/api/services/BaseService.java * ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UserResourceProvider.java * ambari-server/src/main/java/org/apache/ambari/server/audit/AuditLoggerDefaultImpl.java * ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java * ambari-server/src/main/java/org/apache/ambari/server/audit/request/eventcreator/RequestAuditEventCreatorHelper.java * ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariAuthorizationFilterTest.java * ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerTest.java * ambari-server/src/main/java/org/apache/ambari/server/audit/request/eventcreator/AlertTargetEventCreator.java * ambari-server/src/main/java/org/apache/ambari/server/controller/internal/GroupResourceProvider.java * ambari-server/src/main/java/org/apache/ambari/server/api/services/LogoutService.java * ambari-server/src/main/java/org/apache/ambari/server/audit/event/request/MembershipChangeRequestAuditEvent.java * ambari-server/src/main/java/org/apache/ambari/server/security/authentication/AmbariAuthenticationFilter.java * ambari-server/src/test/java/org/apache/ambari/server/audit/OperationStatusAuditEventTest.java * ambari-server/src/main/java/org/apache/ambari/server/audit/request/eventcreator/RepositoryEventCreator.java * ambari-server/src/main/java/org/apache/ambari/server/audit/request/RequestAuditEventCreator.java * ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeItemResourceProvider.java * ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariAuthorizationFilter.java * ambari-server/src/test/java/org/apache/ambari/server/agent/TestHeartbeatHandler.java * ambari-server/src/main/java/org/apache/ambari/server/audit/request/eventcreator/ComponentEventCreator.java * ambari-server/src/main/java/org/apache/ambari/server/audit/request/eventcreator/ConfigurationChangeEventCreator.java * ambari-server/src/main/java/org/apache/ambari/server/state/services/AlertNoticeDispatchService.java *
[jira] [Commented] (AMBARI-15762) Component install post processing can not be run in parallel
[
https://issues.apache.org/jira/browse/AMBARI-15762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231318#comment-15231318
]
Hudson commented on AMBARI-15762:
-
ABORTED: Integrated in Ambari-trunk-Commit #4615 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4615/])
AMBARI-15762. Component install post processing can not be run in (aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5f0a09690310fee76c4cab3639c1c4ec08ecca8a])
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/shared_initialization.py
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/params.py
*
ambari-common/src/main/python/resource_management/libraries/functions/file_based_process_lock.py
* ambari-agent/src/test/python/resource_management/TestFileBasedProcessLock.py
> Component install post processing can not be run in parallel
>
>
> Key: AMBARI-15762
> URL: https://issues.apache.org/jira/browse/AMBARI-15762
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.2.2
>
> Attachments: AMBARI-15762.patch
>
>
> **Problem**
> Ambari executes component installs in parallel on a host. Each install process
> in the post-install phase executes certain shared/common configuration
> directory related steps (stacks/HDP/2.0.6/hooks/after-
> INSTALL/scripts/shared_initialization.py:link_configs() -> ... -> /resource_ma
> nagement/libraries/functions/conf_select.py:convert_conf_directories_to_symlin
> ks() ) on the directories listed in conf_select.py:PACKAGE_DIRS
> The common configuration directory related processing fail in they are kicked
> of in the same time for the same directory.
> In the case the following code snippet is executed in the same time by
> multiple component installs
> each will see the `backup_dir` as non existent and will try to execute the
> "cp" command. One will succeed while the others fail.
>
>
>
> Execute(("cp", "-R", "-p", old_conf, backup_dir), not_if = format("test
> -e {backup_dir}"), sudo = True)
>
> Similar behaviour is seen for the following code snippet:
>
>
>
> Execute(as_sudo(["cp", "-R", "-p", os.path.join(old_conf, "*"),
> versioned_conf], auto_escape=False), only_if = format("ls -d {old_conf}/*"))
>
> **Possible solution**
> Use the linux "lockfile" command or "mkdir /var/lock/mylock" (see example of
> the mkdir solution here: )
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15738) Descriptions for HAWQ sysctl params mention incorrect default values
[ https://issues.apache.org/jira/browse/AMBARI-15738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231317#comment-15231317 ] Hudson commented on AMBARI-15738: - ABORTED: Integrated in Ambari-trunk-Commit #4615 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4615/]) AMBARI-15738: Descriptions for HAWQ sysctl params mention incorrect (matt: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f0645b68abdcc61876313fd2e9aa5fec552a566e]) * ambari-server/src/main/resources/common-services/HAWQ/2.0.0/configuration/hawq-sysctl-env.xml > Descriptions for HAWQ sysctl params mention incorrect default values > > > Key: AMBARI-15738 > URL: https://issues.apache.org/jira/browse/AMBARI-15738 > Project: Ambari > Issue Type: Bug >Reporter: Alexander Denissov >Assignee: Alexander Denissov >Priority: Minor > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15738.branch22.patch > > > kernel.shmmax and net.ipv4.ip_local_port_range have incorrect default values > in their descriptions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15770) HAWQ fails to connect to YARN in HA+SEC mode
[ https://issues.apache.org/jira/browse/AMBARI-15770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Denissov updated AMBARI-15770: Status: Patch Available (was: Open) > HAWQ fails to connect to YARN in HA+SEC mode > > > Key: AMBARI-15770 > URL: https://issues.apache.org/jira/browse/AMBARI-15770 > Project: Ambari > Issue Type: Bug >Reporter: Alexander Denissov >Assignee: Alexander Denissov > Fix For: 2.2.2 > > > When HAWQ is in the cluster with YARN HA and Kerberos enabled, the segments > are down as they cannot connect to YARN RM. > The following updates are required: > 1. add hadoop.security.authentication = kerberos in yarn-client.xml > 2. add 2 properties to core-site.xml: > >hadoop.proxyuser.postgres.hosts >* > > >hadoop.proxyuser.postgres.groups >hadoop > > 3. on every node: > sudo useradd postgres > sudo usermod -a -G hadoop postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15770) HAWQ fails to connect to YARN in HA+SEC mode
[ https://issues.apache.org/jira/browse/AMBARI-15770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Denissov updated AMBARI-15770: Attachment: AMBARI-15770.branch22.patch The same patch applies to trunk. Tested manually and updates python tests: -- Ran 246 tests in 7.061s OK -- Total run:923 Total errors:0 Total failures:0 > HAWQ fails to connect to YARN in HA+SEC mode > > > Key: AMBARI-15770 > URL: https://issues.apache.org/jira/browse/AMBARI-15770 > Project: Ambari > Issue Type: Bug >Reporter: Alexander Denissov >Assignee: Alexander Denissov > Fix For: 2.2.2 > > Attachments: AMBARI-15770.branch22.patch > > > When HAWQ is in the cluster with YARN HA and Kerberos enabled, the segments > are down as they cannot connect to YARN RM. > The following updates are required: > 1. add hadoop.security.authentication = kerberos in yarn-client.xml > 2. add 2 properties to core-site.xml: > >hadoop.proxyuser.postgres.hosts >* > > >hadoop.proxyuser.postgres.groups >hadoop > > 3. on every node: > sudo useradd postgres > sudo usermod -a -G hadoop postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15774) Ambari upgrade fails with MySQL DB and enforce gtid enabled
[
https://issues.apache.org/jira/browse/AMBARI-15774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle updated AMBARI-15774:
-
Status: Patch Available (was: Open)
> Ambari upgrade fails with MySQL DB and enforce gtid enabled
> ---
>
> Key: AMBARI-15774
> URL: https://issues.apache.org/jira/browse/AMBARI-15774
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15774.patch
>
>
> Issue: Ambari upgrade is failing from 2.2.0 to 2.2.1.1 with below error:
> {code}
> mbari-server upgrade
> Using python /usr/bin/python
> Upgrading ambari-server
> Updating properties in ambari.properties ...
> WARNING: Can not find ambari.properties.rpmsave file from previous version,
> skipping import of settings
> WARNING: Can not find ambari-env.sh.rpmsave file from previous version,
> skipping restore of environment settings
> Fixing database objects owner
> Ambari Server configured for MySQL. Confirm you have made a backup of the
> Ambari Server database [y/n] (y)? y
> Upgrading database schema
> Error output from schema upgrade command:
> Exception in thread "main" org.apache.ambari.server.AmbariException:
> Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.5.2.v20140319-9ad6abd):
> org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception:
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
> 'ambari.TL_alert_notice' doesn't exist
> Error Code: 1146
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15774) Ambari upgrade fails with MySQL DB and enforce gtid enabled
[
https://issues.apache.org/jira/browse/AMBARI-15774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle updated AMBARI-15774:
-
Attachment: AMBARI-15774.patch
> Ambari upgrade fails with MySQL DB and enforce gtid enabled
> ---
>
> Key: AMBARI-15774
> URL: https://issues.apache.org/jira/browse/AMBARI-15774
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15774.patch
>
>
> Issue: Ambari upgrade is failing from 2.2.0 to 2.2.1.1 with below error:
> {code}
> mbari-server upgrade
> Using python /usr/bin/python
> Upgrading ambari-server
> Updating properties in ambari.properties ...
> WARNING: Can not find ambari.properties.rpmsave file from previous version,
> skipping import of settings
> WARNING: Can not find ambari-env.sh.rpmsave file from previous version,
> skipping restore of environment settings
> Fixing database objects owner
> Ambari Server configured for MySQL. Confirm you have made a backup of the
> Ambari Server database [y/n] (y)? y
> Upgrading database schema
> Error output from schema upgrade command:
> Exception in thread "main" org.apache.ambari.server.AmbariException:
> Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.5.2.v20140319-9ad6abd):
> org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception:
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
> 'ambari.TL_alert_notice' doesn't exist
> Error Code: 1146
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15775) Integrate Red Hat Satellite option in Ambari Admin
[
https://issues.apache.org/jira/browse/AMBARI-15775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhe (Joe) Wang updated AMBARI-15775:
Status: Patch Available (was: Open)
> Integrate Red Hat Satellite option in Ambari Admin
> --
>
> Key: AMBARI-15775
> URL: https://issues.apache.org/jira/browse/AMBARI-15775
> Project: Ambari
> Issue Type: Task
> Components: ambari-admin
>Affects Versions: 2.4.0
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: 2.4.0
>
> Attachments: AMBARI-15775.v0.patch
>
>
> Provide RedHat satellite option. It can be used wherever we show redhat6
> urls, and applicable to redhat6/redhat7. For example, registering repos, etc.
> The API call to update links when using VDF can specify the new property. In
> order to make it more generic (and default {{true}}), it is called
> "{{ambari_managed_repositories}}". API looks like:
> {noformat}
> PUT /api/v1/stacks/HDP/versions/2.3/repository_versions/2
> {
> "RepositoryVersions" : {
> "id" : 2
> },
> "operating_systems" : [
> {
> "OperatingSystems" : {
> "ambari_managed_repositories": false,
> "os_type" : "redhat6",
> "repository_version_id" : 2,
> "stack_name" : "HDP",
> "stack_version" : "2.3"
> },
> "repositories" : [
> {
> "Repositories" : {
> "base_url" : "http://repos.ambari.apache.org/hdp/HDP-2.3.4.14-4;,
> "repo_id" : "HDP-2.3",
> "repo_name" : "HDP"
> }
> },
> {
> "Repositories" : {
> "base_url" :
> "http://repos.ambari.apache.org/hdp/HDP-UTILS-1.1.0.20;,
> "repo_id" : "HDP-UTILS-1.1.0.20",
> "repo_name" : "HDP-UTILS"
> }
> }
> ]
> }
> ]
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15775) Integrate Red Hat Satellite option in Ambari Admin
[
https://issues.apache.org/jira/browse/AMBARI-15775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhe (Joe) Wang updated AMBARI-15775:
Attachment: AMBARI-15775.v0.patch
ambari-admin:
Executed 64 of 64 SUCCESS (0.048 secs / 0.299 secs)
Manual testing done.
> Integrate Red Hat Satellite option in Ambari Admin
> --
>
> Key: AMBARI-15775
> URL: https://issues.apache.org/jira/browse/AMBARI-15775
> Project: Ambari
> Issue Type: Task
> Components: ambari-admin
>Affects Versions: 2.4.0
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: 2.4.0
>
> Attachments: AMBARI-15775.v0.patch
>
>
> Provide RedHat satellite option. It can be used wherever we show redhat6
> urls, and applicable to redhat6/redhat7. For example, registering repos, etc.
> The API call to update links when using VDF can specify the new property. In
> order to make it more generic (and default {{true}}), it is called
> "{{ambari_managed_repositories}}". API looks like:
> {noformat}
> PUT /api/v1/stacks/HDP/versions/2.3/repository_versions/2
> {
> "RepositoryVersions" : {
> "id" : 2
> },
> "operating_systems" : [
> {
> "OperatingSystems" : {
> "ambari_managed_repositories": false,
> "os_type" : "redhat6",
> "repository_version_id" : 2,
> "stack_name" : "HDP",
> "stack_version" : "2.3"
> },
> "repositories" : [
> {
> "Repositories" : {
> "base_url" : "http://repos.ambari.apache.org/hdp/HDP-2.3.4.14-4;,
> "repo_id" : "HDP-2.3",
> "repo_name" : "HDP"
> }
> },
> {
> "Repositories" : {
> "base_url" :
> "http://repos.ambari.apache.org/hdp/HDP-UTILS-1.1.0.20;,
> "repo_id" : "HDP-UTILS-1.1.0.20",
> "repo_name" : "HDP-UTILS"
> }
> }
> ]
> }
> ]
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-15775) Integrate Red Hat Satellite option in Ambari Admin
Zhe (Joe) Wang created AMBARI-15775:
---
Summary: Integrate Red Hat Satellite option in Ambari Admin
Key: AMBARI-15775
URL: https://issues.apache.org/jira/browse/AMBARI-15775
Project: Ambari
Issue Type: Task
Components: ambari-admin
Affects Versions: 2.4.0
Reporter: Zhe (Joe) Wang
Assignee: Zhe (Joe) Wang
Fix For: 2.4.0
Provide RedHat satellite option. It can be used wherever we show redhat6 urls,
and applicable to redhat6/redhat7. For example, registering repos, etc.
The API call to update links when using VDF can specify the new property. In
order to make it more generic (and default {{true}}), it is called
"{{ambari_managed_repositories}}". API looks like:
{noformat}
PUT /api/v1/stacks/HDP/versions/2.3/repository_versions/2
{
"RepositoryVersions" : {
"id" : 2
},
"operating_systems" : [
{
"OperatingSystems" : {
"ambari_managed_repositories": false,
"os_type" : "redhat6",
"repository_version_id" : 2,
"stack_name" : "HDP",
"stack_version" : "2.3"
},
"repositories" : [
{
"Repositories" : {
"base_url" : "http://repos.ambari.apache.org/hdp/HDP-2.3.4.14-4;,
"repo_id" : "HDP-2.3",
"repo_name" : "HDP"
}
},
{
"Repositories" : {
"base_url" :
"http://repos.ambari.apache.org/hdp/HDP-UTILS-1.1.0.20;,
"repo_id" : "HDP-UTILS-1.1.0.20",
"repo_name" : "HDP-UTILS"
}
}
]
}
]
}
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15738) Descriptions for HAWQ sysctl params mention incorrect default values
[ https://issues.apache.org/jira/browse/AMBARI-15738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231239#comment-15231239 ] Hudson commented on AMBARI-15738: - SUCCESS: Integrated in Ambari-branch-2.2 #609 (See [https://builds.apache.org/job/Ambari-branch-2.2/609/]) AMBARI-15738: Descriptions for HAWQ sysctl params mention incorrect (matt: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=41f14c7221bc7d71fafb70ab9abebff7786e8583]) * ambari-server/src/main/resources/common-services/HAWQ/2.0.0/configuration/hawq-sysctl-env.xml > Descriptions for HAWQ sysctl params mention incorrect default values > > > Key: AMBARI-15738 > URL: https://issues.apache.org/jira/browse/AMBARI-15738 > Project: Ambari > Issue Type: Bug >Reporter: Alexander Denissov >Assignee: Alexander Denissov >Priority: Minor > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15738.branch22.patch > > > kernel.shmmax and net.ipv4.ip_local_port_range have incorrect default values > in their descriptions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15762) Component install post processing can not be run in parallel
[
https://issues.apache.org/jira/browse/AMBARI-15762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231240#comment-15231240
]
Hudson commented on AMBARI-15762:
-
SUCCESS: Integrated in Ambari-branch-2.2 #609 (See
[https://builds.apache.org/job/Ambari-branch-2.2/609/])
AMBARI-15762. Component install post processing can not be run in (aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9b86d41e197adc31ab29c1bc71a578a7d4b5da81])
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/shared_initialization.py
*
ambari-common/src/main/python/resource_management/libraries/functions/file_based_process_lock.py
* ambari-agent/src/test/python/resource_management/TestFileBasedProcessLock.py
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/params.py
> Component install post processing can not be run in parallel
>
>
> Key: AMBARI-15762
> URL: https://issues.apache.org/jira/browse/AMBARI-15762
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.2.2
>
> Attachments: AMBARI-15762.patch
>
>
> **Problem**
> Ambari executes component installs in parallel on a host. Each install process
> in the post-install phase executes certain shared/common configuration
> directory related steps (stacks/HDP/2.0.6/hooks/after-
> INSTALL/scripts/shared_initialization.py:link_configs() -> ... -> /resource_ma
> nagement/libraries/functions/conf_select.py:convert_conf_directories_to_symlin
> ks() ) on the directories listed in conf_select.py:PACKAGE_DIRS
> The common configuration directory related processing fail in they are kicked
> of in the same time for the same directory.
> In the case the following code snippet is executed in the same time by
> multiple component installs
> each will see the `backup_dir` as non existent and will try to execute the
> "cp" command. One will succeed while the others fail.
>
>
>
> Execute(("cp", "-R", "-p", old_conf, backup_dir), not_if = format("test
> -e {backup_dir}"), sudo = True)
>
> Similar behaviour is seen for the following code snippet:
>
>
>
> Execute(as_sudo(["cp", "-R", "-p", os.path.join(old_conf, "*"),
> versioned_conf], auto_escape=False), only_if = format("ls -d {old_conf}/*"))
>
> **Possible solution**
> Use the linux "lockfile" command or "mkdir /var/lock/mylock" (see example of
> the mkdir solution here: )
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-15774) Ambari upgrade fails with MySQL DB and enforce gtid enabled
Siddharth Wagle created AMBARI-15774:
Summary: Ambari upgrade fails with MySQL DB and enforce gtid
enabled
Key: AMBARI-15774
URL: https://issues.apache.org/jira/browse/AMBARI-15774
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.2.0
Reporter: Siddharth Wagle
Assignee: Siddharth Wagle
Priority: Critical
Fix For: 2.2.2
Issue: Ambari upgrade is failing from 2.2.0 to 2.2.1.1 with below error:
{code}
mbari-server upgrade
Using python /usr/bin/python
Upgrading ambari-server
Updating properties in ambari.properties ...
WARNING: Can not find ambari.properties.rpmsave file from previous version,
skipping import of settings
WARNING: Can not find ambari-env.sh.rpmsave file from previous version,
skipping restore of environment settings
Fixing database objects owner
Ambari Server configured for MySQL. Confirm you have made a backup of the
Ambari Server database [y/n] (y)? y
Upgrading database schema
Error output from schema upgrade command:
Exception in thread "main" org.apache.ambari.server.AmbariException: Exception
[EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd):
org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException:
Table 'ambari.TL_alert_notice' doesn't exist
Error Code: 1146
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15774) Ambari upgrade fails with MySQL DB and enforce gtid enabled
[
https://issues.apache.org/jira/browse/AMBARI-15774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231224#comment-15231224
]
Siddharth Wagle commented on AMBARI-15774:
--
The GTID consistency error is rather strange.
http://dev.mysql.com/doc/refman/5.6/en/replication-gtids-restrictions.html
Temporary tables. CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE
statements are not supported inside transactions when using GTIDs (that is,
when the server was started with the --enforce-gtid-consistency option). It is
possible to use these statements with GTIDs enabled, but only outside of any
transaction, and only with autocommit=1.
> Ambari upgrade fails with MySQL DB and enforce gtid enabled
> ---
>
> Key: AMBARI-15774
> URL: https://issues.apache.org/jira/browse/AMBARI-15774
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.2.2
>
>
> Issue: Ambari upgrade is failing from 2.2.0 to 2.2.1.1 with below error:
> {code}
> mbari-server upgrade
> Using python /usr/bin/python
> Upgrading ambari-server
> Updating properties in ambari.properties ...
> WARNING: Can not find ambari.properties.rpmsave file from previous version,
> skipping import of settings
> WARNING: Can not find ambari-env.sh.rpmsave file from previous version,
> skipping restore of environment settings
> Fixing database objects owner
> Ambari Server configured for MySQL. Confirm you have made a backup of the
> Ambari Server database [y/n] (y)? y
> Upgrading database schema
> Error output from schema upgrade command:
> Exception in thread "main" org.apache.ambari.server.AmbariException:
> Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.5.2.v20140319-9ad6abd):
> org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception:
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
> 'ambari.TL_alert_notice' doesn't exist
> Error Code: 1146
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15771) After enabling NN HA with HAWQ installed, duplicate properties are seen on HAWQ config tab
[ https://issues.apache.org/jira/browse/AMBARI-15771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Goutam Tadi updated AMBARI-15771: - Attachment: AMBARI-15771-branch-2.2-orig.patch > After enabling NN HA with HAWQ installed, duplicate properties are seen on > HAWQ config tab > -- > > Key: AMBARI-15771 > URL: https://issues.apache.org/jira/browse/AMBARI-15771 > Project: Ambari > Issue Type: Bug >Reporter: Matt >Assignee: Goutam Tadi > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15771-branch-2.2-orig.patch > > > Steps to reproduce: > - Install a cluster with HDFS and HAWQ > - Enable Namenode HA (hawq_dfs_url should get updated here) > After enabling Namenode HA, a duplicate hawq_dfs_url along with other > properties from hawq-site are shown in Configs page of HAWQ service. > This issue happens quite often, but not every time. More investigation is > required. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15771) After enabling NN HA with HAWQ installed, duplicate properties are seen on HAWQ config tab
[ https://issues.apache.org/jira/browse/AMBARI-15771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Goutam Tadi updated AMBARI-15771: - Status: Patch Available (was: Open) > After enabling NN HA with HAWQ installed, duplicate properties are seen on > HAWQ config tab > -- > > Key: AMBARI-15771 > URL: https://issues.apache.org/jira/browse/AMBARI-15771 > Project: Ambari > Issue Type: Bug >Reporter: Matt >Assignee: Goutam Tadi > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15771-branch-2.2-orig.patch > > > Steps to reproduce: > - Install a cluster with HDFS and HAWQ > - Enable Namenode HA (hawq_dfs_url should get updated here) > After enabling Namenode HA, a duplicate hawq_dfs_url along with other > properties from hawq-site are shown in Configs page of HAWQ service. > This issue happens quite often, but not every time. More investigation is > required. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15719) Make list of reassignable components stack driven instead of hardcoding them in the UI code
[
https://issues.apache.org/jira/browse/AMBARI-15719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Di Li updated AMBARI-15719:
---
Attachment: AMBARI-15719.patch
> Make list of reassignable components stack driven instead of hardcoding them
> in the UI code
> ---
>
> Key: AMBARI-15719
> URL: https://issues.apache.org/jira/browse/AMBARI-15719
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server, ambari-web
>Affects Versions: trunk
>Reporter: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-15719.patch
>
>
> When a component is reassignable, the Ambari web UI adds the "Move" menu item
> to the component menu on the host page.
> The logic on whether a component should be displayed with the "Move" menu
> item is currently controlled by the following hardcoded list.
> /** @property {Boolean} isReassignable - component supports reassign action
> **/
> isReassignable: function() {
> return ['NAMENODE', 'SECONDARY_NAMENODE', 'JOBTRACKER',
> 'RESOURCEMANAGER', 'APP_TIMELINE_SERVER', 'OOZIE_SERVER', 'WEBHCAT_SERVER',
> 'HIVE_SERVER', 'HIVE_METASTORE', 'MYSQL_SERVER',
> 'METRICS_COLLECTOR'].contains(this.get('componentName'));
> }.property('componentName'),
> We should make the list stack driven by specify whether a component is
> reassignable via a flag in the metainfo.xml.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (AMBARI-15719) Make list of reassignable components stack driven instead of hardcoding them in the UI code
[
https://issues.apache.org/jira/browse/AMBARI-15719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Di Li reassigned AMBARI-15719:
--
Assignee: Di Li
> Make list of reassignable components stack driven instead of hardcoding them
> in the UI code
> ---
>
> Key: AMBARI-15719
> URL: https://issues.apache.org/jira/browse/AMBARI-15719
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server, ambari-web
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-15719.patch
>
>
> When a component is reassignable, the Ambari web UI adds the "Move" menu item
> to the component menu on the host page.
> The logic on whether a component should be displayed with the "Move" menu
> item is currently controlled by the following hardcoded list.
> /** @property {Boolean} isReassignable - component supports reassign action
> **/
> isReassignable: function() {
> return ['NAMENODE', 'SECONDARY_NAMENODE', 'JOBTRACKER',
> 'RESOURCEMANAGER', 'APP_TIMELINE_SERVER', 'OOZIE_SERVER', 'WEBHCAT_SERVER',
> 'HIVE_SERVER', 'HIVE_METASTORE', 'MYSQL_SERVER',
> 'METRICS_COLLECTOR'].contains(this.get('componentName'));
> }.property('componentName'),
> We should make the list stack driven by specify whether a component is
> reassignable via a flag in the metainfo.xml.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15719) Make list of reassignable components stack driven instead of hardcoding them in the UI code
[
https://issues.apache.org/jira/browse/AMBARI-15719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Di Li updated AMBARI-15719:
---
Status: Patch Available (was: Open)
> Make list of reassignable components stack driven instead of hardcoding them
> in the UI code
> ---
>
> Key: AMBARI-15719
> URL: https://issues.apache.org/jira/browse/AMBARI-15719
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server, ambari-web
>Affects Versions: trunk
>Reporter: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-15719.patch
>
>
> When a component is reassignable, the Ambari web UI adds the "Move" menu item
> to the component menu on the host page.
> The logic on whether a component should be displayed with the "Move" menu
> item is currently controlled by the following hardcoded list.
> /** @property {Boolean} isReassignable - component supports reassign action
> **/
> isReassignable: function() {
> return ['NAMENODE', 'SECONDARY_NAMENODE', 'JOBTRACKER',
> 'RESOURCEMANAGER', 'APP_TIMELINE_SERVER', 'OOZIE_SERVER', 'WEBHCAT_SERVER',
> 'HIVE_SERVER', 'HIVE_METASTORE', 'MYSQL_SERVER',
> 'METRICS_COLLECTOR'].contains(this.get('componentName'));
> }.property('componentName'),
> We should make the list stack driven by specify whether a component is
> reassignable via a flag in the metainfo.xml.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15751) RU/EU PreCheck to ensure dfs.client.retry.policy.enable is set to false
[ https://issues.apache.org/jira/browse/AMBARI-15751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-15751: - Status: Patch Available (was: Open) > RU/EU PreCheck to ensure dfs.client.retry.policy.enable is set to false > --- > > Key: AMBARI-15751 > URL: https://issues.apache.org/jira/browse/AMBARI-15751 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.4.0 > > Attachments: AMBARI-15751.trunk.patch > > > Ambari used to have a PreCheck to ensure that certain client retries were > enabled. > This check should be required in all RU/EUs > hdfs-site: "dfs.client.retry.policy.enabled" must be false > hive-site: "hive.metastore.failure.retries"must be greater than 0 > oozie-env: "-Doozie.connection.retry.count" must be present in the "content" > param > Right now, this check is disabled and there hdfs-site property is not checked. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15751) RU/EU PreCheck to ensure dfs.client.retry.policy.enable is set to false
[ https://issues.apache.org/jira/browse/AMBARI-15751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-15751: - Attachment: (was: AMBARI-15751.trunk.patch) > RU/EU PreCheck to ensure dfs.client.retry.policy.enable is set to false > --- > > Key: AMBARI-15751 > URL: https://issues.apache.org/jira/browse/AMBARI-15751 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.4.0 > > Attachments: AMBARI-15751.trunk.patch > > > Ambari used to have a PreCheck to ensure that certain client retries were > enabled. > This check should be required in all RU/EUs > hdfs-site: "dfs.client.retry.policy.enabled" must be false > hive-site: "hive.metastore.failure.retries"must be greater than 0 > oozie-env: "-Doozie.connection.retry.count" must be present in the "content" > param > Right now, this check is disabled and there hdfs-site property is not checked. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15733) Atlas Integration : Support Atlas HA
[ https://issues.apache.org/jira/browse/AMBARI-15733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Beerbower updated AMBARI-15733: --- Summary: Atlas Integration : Support Atlas HA (was: Atlas Integration : Support enable Atlas HA) > Atlas Integration : Support Atlas HA > > > Key: AMBARI-15733 > URL: https://issues.apache.org/jira/browse/AMBARI-15733 > Project: Ambari > Issue Type: Bug >Reporter: Tom Beerbower >Assignee: Tom Beerbower > > # set cardinality to 1+ in Atlas stack definition > # expose Atlas configuration to enable HA (atlas.server.ha.enabled) > # set Atlas configuration for server id list (atlas.server.ids) > # set Atlas configuration properties for hosts (atlas.server.host.id1, ...) > # expose Atlas host component ha_state property in Ambari REST API. > # Update Ambari quick link definition in Atlas stack definition to show > ha_state. (See Yarn RM quick links) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15773) Password must not by displayed by UpgradeItem and Stage resources in the API
[
https://issues.apache.org/jira/browse/AMBARI-15773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-15773:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to trunk: commit 7c211e3ee365889bf1e38f392f5f5adafe41e4a5
branch-2.2: commit ed29d1cd1fa7db50bed2ed12352120f3a7a03475
> Password must not by displayed by UpgradeItem and Stage resources in the API
>
>
> Key: AMBARI-15773
> URL: https://issues.apache.org/jira/browse/AMBARI-15773
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Fix For: 2.2.2
>
> Attachments: AMBARI-15773.branch-2.2.patch, AMBARI-15773.trunk.patch
>
>
> STR:
> * Install ambari-server-2.2.2.0-391 (ambari-server --hash:
> 8b49b71d5ef602e1252049fbc970958fbe05806e)
> * Install HDP 2.3 or 2.4
> * Install another version in order to perform RU or EU
> * Use the API to navigate to
> http://server:8080/api/v1/clusters/cl1/upgrades/##/upgrade_groups/1/upgrade_items/1
> Notice that the output contains the ambari_db_rca_password in plaintext,
> {code}
> "host_params" :
> "{\"agent_stack_retry_count\":\"5\",\"agent_stack_retry_on_unavailability\":\"false\",\"ambari_db_rca_driver\":\"org.postgresql.Driver\",\"ambari_db_rca_password\":\"bigdatacustom\",\"ambari_db_rca_url\":\"jdbc:postgresql://172.22.117.211:5432/ambaricustom\",\"ambari_db_rca_username\":\"ambaricustomuser\",\"current_version\":\"2.4.0.0-169\",\"db_driver_filename\":\"mysql-connector-java.jar\",\"db_name\":\"ambaricustom\",\"host_sys_prepped\":\"false\",\"java_home\":\"/usr/jdk64/jdk1.8.0_60\",\"java_version\":\"8\",\"jdk_location\":\"http://os-s11-4-snjlmu-ambari-se-eu-3-5.novalocal:8080/resources/\",\"mysql_jdbc_url\":\"http://os-s11-4-snjlmu-ambari-se-eu-3-5.novalocal:8080/resources//mysql-connector-java.jar\",\"not_managed_hdfs_path_list\":\"[\\\"/apps/hive/warehouse\\\",\\\"/apps/falcon\\\",\\\"/mr-history/done\\\",\\\"/app-logs\\\",\\\"/tmp\\\"]\",\"oracle_jdbc_url\":\"http://os-s11-4-snjlmu-ambari-se-eu-3-5.novalocal:8080/resources//ojdbc6.jar\",\"stack_name\":\"HDP\",\"stack_version\":\"2.4\"};,
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15768) Ambari Widget should display metrics for available metrics even if some of the metrics it expects are not returned by API
[ https://issues.apache.org/jira/browse/AMBARI-15768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-15768: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.2. > Ambari Widget should display metrics for available metrics even if some of > the metrics it expects are not returned by API > - > > Key: AMBARI-15768 > URL: https://issues.apache.org/jira/browse/AMBARI-15768 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15768.patch, AMBARI-15768_2.2.2.patch, Screen > Shot 2016-04-06 at 2.53.23 PM.png > > > For example, Namenode RPC widget requests 5 metrics from the backend. 2 of > the metrics' availability depends on a Namenode config to be present. In such > a case, the widget should display whatever metrics that are available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15773) Password must not by displayed by UpgradeItem and Stage resources in the API
[
https://issues.apache.org/jira/browse/AMBARI-15773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-15773:
-
Attachment: (was: AMBARI-15773.trunk.patch)
> Password must not by displayed by UpgradeItem and Stage resources in the API
>
>
> Key: AMBARI-15773
> URL: https://issues.apache.org/jira/browse/AMBARI-15773
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Fix For: 2.2.2
>
> Attachments: AMBARI-15773.branch-2.2.patch, AMBARI-15773.trunk.patch
>
>
> STR:
> * Install ambari-server-2.2.2.0-391 (ambari-server --hash:
> 8b49b71d5ef602e1252049fbc970958fbe05806e)
> * Install HDP 2.3 or 2.4
> * Install another version in order to perform RU or EU
> * Use the API to navigate to
> http://server:8080/api/v1/clusters/cl1/upgrades/##/upgrade_groups/1/upgrade_items/1
> Notice that the output contains the ambari_db_rca_password in plaintext,
> {code}
> "host_params" :
> "{\"agent_stack_retry_count\":\"5\",\"agent_stack_retry_on_unavailability\":\"false\",\"ambari_db_rca_driver\":\"org.postgresql.Driver\",\"ambari_db_rca_password\":\"bigdatacustom\",\"ambari_db_rca_url\":\"jdbc:postgresql://172.22.117.211:5432/ambaricustom\",\"ambari_db_rca_username\":\"ambaricustomuser\",\"current_version\":\"2.4.0.0-169\",\"db_driver_filename\":\"mysql-connector-java.jar\",\"db_name\":\"ambaricustom\",\"host_sys_prepped\":\"false\",\"java_home\":\"/usr/jdk64/jdk1.8.0_60\",\"java_version\":\"8\",\"jdk_location\":\"http://os-s11-4-snjlmu-ambari-se-eu-3-5.novalocal:8080/resources/\",\"mysql_jdbc_url\":\"http://os-s11-4-snjlmu-ambari-se-eu-3-5.novalocal:8080/resources//mysql-connector-java.jar\",\"not_managed_hdfs_path_list\":\"[\\\"/apps/hive/warehouse\\\",\\\"/apps/falcon\\\",\\\"/mr-history/done\\\",\\\"/app-logs\\\",\\\"/tmp\\\"]\",\"oracle_jdbc_url\":\"http://os-s11-4-snjlmu-ambari-se-eu-3-5.novalocal:8080/resources//ojdbc6.jar\",\"stack_name\":\"HDP\",\"stack_version\":\"2.4\"};,
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15773) Password must not by displayed by UpgradeItem and Stage resources in the API
[
https://issues.apache.org/jira/browse/AMBARI-15773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-15773:
-
Attachment: (was: AMBARI-15773.branch-2.2.patch)
> Password must not by displayed by UpgradeItem and Stage resources in the API
>
>
> Key: AMBARI-15773
> URL: https://issues.apache.org/jira/browse/AMBARI-15773
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Fix For: 2.2.2
>
> Attachments: AMBARI-15773.branch-2.2.patch, AMBARI-15773.trunk.patch
>
>
> STR:
> * Install ambari-server-2.2.2.0-391 (ambari-server --hash:
> 8b49b71d5ef602e1252049fbc970958fbe05806e)
> * Install HDP 2.3 or 2.4
> * Install another version in order to perform RU or EU
> * Use the API to navigate to
> http://server:8080/api/v1/clusters/cl1/upgrades/##/upgrade_groups/1/upgrade_items/1
> Notice that the output contains the ambari_db_rca_password in plaintext,
> {code}
> "host_params" :
> "{\"agent_stack_retry_count\":\"5\",\"agent_stack_retry_on_unavailability\":\"false\",\"ambari_db_rca_driver\":\"org.postgresql.Driver\",\"ambari_db_rca_password\":\"bigdatacustom\",\"ambari_db_rca_url\":\"jdbc:postgresql://172.22.117.211:5432/ambaricustom\",\"ambari_db_rca_username\":\"ambaricustomuser\",\"current_version\":\"2.4.0.0-169\",\"db_driver_filename\":\"mysql-connector-java.jar\",\"db_name\":\"ambaricustom\",\"host_sys_prepped\":\"false\",\"java_home\":\"/usr/jdk64/jdk1.8.0_60\",\"java_version\":\"8\",\"jdk_location\":\"http://os-s11-4-snjlmu-ambari-se-eu-3-5.novalocal:8080/resources/\",\"mysql_jdbc_url\":\"http://os-s11-4-snjlmu-ambari-se-eu-3-5.novalocal:8080/resources//mysql-connector-java.jar\",\"not_managed_hdfs_path_list\":\"[\\\"/apps/hive/warehouse\\\",\\\"/apps/falcon\\\",\\\"/mr-history/done\\\",\\\"/app-logs\\\",\\\"/tmp\\\"]\",\"oracle_jdbc_url\":\"http://os-s11-4-snjlmu-ambari-se-eu-3-5.novalocal:8080/resources//ojdbc6.jar\",\"stack_name\":\"HDP\",\"stack_version\":\"2.4\"};,
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15773) Password must not by displayed by UpgradeItem and Stage resources in the API
[
https://issues.apache.org/jira/browse/AMBARI-15773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-15773:
-
Attachment: AMBARI-15773.branch-2.2.patch
AMBARI-15773.trunk.patch
> Password must not by displayed by UpgradeItem and Stage resources in the API
>
>
> Key: AMBARI-15773
> URL: https://issues.apache.org/jira/browse/AMBARI-15773
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Fix For: 2.2.2
>
> Attachments: AMBARI-15773.branch-2.2.patch, AMBARI-15773.trunk.patch
>
>
> STR:
> * Install ambari-server-2.2.2.0-391 (ambari-server --hash:
> 8b49b71d5ef602e1252049fbc970958fbe05806e)
> * Install HDP 2.3 or 2.4
> * Install another version in order to perform RU or EU
> * Use the API to navigate to
> http://server:8080/api/v1/clusters/cl1/upgrades/##/upgrade_groups/1/upgrade_items/1
> Notice that the output contains the ambari_db_rca_password in plaintext,
> {code}
> "host_params" :
> "{\"agent_stack_retry_count\":\"5\",\"agent_stack_retry_on_unavailability\":\"false\",\"ambari_db_rca_driver\":\"org.postgresql.Driver\",\"ambari_db_rca_password\":\"bigdatacustom\",\"ambari_db_rca_url\":\"jdbc:postgresql://172.22.117.211:5432/ambaricustom\",\"ambari_db_rca_username\":\"ambaricustomuser\",\"current_version\":\"2.4.0.0-169\",\"db_driver_filename\":\"mysql-connector-java.jar\",\"db_name\":\"ambaricustom\",\"host_sys_prepped\":\"false\",\"java_home\":\"/usr/jdk64/jdk1.8.0_60\",\"java_version\":\"8\",\"jdk_location\":\"http://os-s11-4-snjlmu-ambari-se-eu-3-5.novalocal:8080/resources/\",\"mysql_jdbc_url\":\"http://os-s11-4-snjlmu-ambari-se-eu-3-5.novalocal:8080/resources//mysql-connector-java.jar\",\"not_managed_hdfs_path_list\":\"[\\\"/apps/hive/warehouse\\\",\\\"/apps/falcon\\\",\\\"/mr-history/done\\\",\\\"/app-logs\\\",\\\"/tmp\\\"]\",\"oracle_jdbc_url\":\"http://os-s11-4-snjlmu-ambari-se-eu-3-5.novalocal:8080/resources//ojdbc6.jar\",\"stack_name\":\"HDP\",\"stack_version\":\"2.4\"};,
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15768) Ambari Widget should display metrics for available metrics even if some of the metrics it expects are not returned by API
[
https://issues.apache.org/jira/browse/AMBARI-15768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231018#comment-15231018
]
Hadoop QA commented on AMBARI-15768:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797548/AMBARI-15768.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 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6294//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6294//console
This message is automatically generated.
> Ambari Widget should display metrics for available metrics even if some of
> the metrics it expects are not returned by API
> -
>
> Key: AMBARI-15768
> URL: https://issues.apache.org/jira/browse/AMBARI-15768
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15768.patch, AMBARI-15768_2.2.2.patch, Screen
> Shot 2016-04-06 at 2.53.23 PM.png
>
>
> For example, Namenode RPC widget requests 5 metrics from the backend. 2 of
> the metrics' availability depends on a Namenode config to be present. In such
> a case, the widget should display whatever metrics that are available.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15679) Initial commit for LogSearch service definition
[ https://issues.apache.org/jira/browse/AMBARI-15679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231016#comment-15231016 ] Olivér Szabó commented on AMBARI-15679: --- Patch is too big, review board patch not contains ambari/ambari-logsearch/ambari-logearch-portal/src/main/webapps/libs folder (12 MB) > Initial commit for LogSearch service definition > --- > > Key: AMBARI-15679 > URL: https://issues.apache.org/jira/browse/AMBARI-15679 > Project: Ambari > Issue Type: Technical task > Components: stacks >Affects Versions: 2.4.0 >Reporter: Sumit Mohanty >Assignee: Olivér Szabó > Fix For: 2.4.0 > > Attachments: AMBARI-15679.patch > > > LogSearch service includes three major components: > * A Solr cloud to store logs and query > * Log collectors/feeders that consume log files being generated by the > services > * Log search service that provides REST API and UI front end > The above components are managed by Ambari through a stack definition. The > stack definition provides the mechanism to have the LogSearch service > configured to read log files created by other services, including Ambari > Server. This integration allows customizing log locations and letting > LogSearch service be aware of the locations. > Final peace is to provide an integration from the Ambari UI to LogSearch > service so that the logs for a service is easily accessible from the service > dashboards. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15646) Audit Log Code Cleanup & Safety
[
https://issues.apache.org/jira/browse/AMBARI-15646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230982#comment-15230982
]
Hadoop QA commented on AMBARI-15646:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797529/AMBARI-15646.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 10 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.state.alerts.AlertReceivedListenerTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6292//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6292//console
This message is automatically generated.
> Audit Log Code Cleanup & Safety
> ---
>
> Key: AMBARI-15646
> URL: https://issues.apache.org/jira/browse/AMBARI-15646
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Daniel Gergely
>Assignee: Daniel Gergely
> Attachments: AMBARI-15646.patch
>
>
> As a follow-up to AMBARI-15241, there are concerns brought up in review which
> should be addressed but didn't need to hold up the feature being committed.
> These can be further broken out to into separate Jiras if needed:
> - When initializing a ThreadLocal, you can specify an initial value. This
> code is unnecessary:
> {code}
> private ThreadLocal dateFormatThreadLocal = new ThreadLocal<>();
> if(dateFormatThreadLocal.get() == null) {
> //2016-03-11T10:42:36.376Z
> dateFormatThreadLocal.set(new
> SimpleDateFormat("-MM-dd'T'HH:mm:ss.SSSX"));
> }
> {code}
> - There are no tests for a majority of events and event creators.
> - Using a multibinder is fine to be able to inject a {{Set}}, but it's
> not clear to developers adding code that this is what must be done.
> -- We either need to document the super interface to make it clear how to
> have new creators bound
> -- Or annotate creators with an annotation which then be automatically picked
> up by the {{AuditLoggerModule}} and bound without the need to explicitly
> define each creator.
> - {code}
> // binding for audit event creators
> Multibinder auditLogEventCreatorBinder =
> Multibinder.newSetBinder(binder(), RequestAuditEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(DefaultEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(ComponentEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(ServiceEventCreator.class);
>
> auditLogEventCreatorBinder.addBinding().to(UnauthorizedEventCreator.class);
>
> auditLogEventCreatorBinder.addBinding().to(ConfigurationChangeEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(UserEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(GroupEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(MemberEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(PrivilegeEventCreator.class);
>
> auditLogEventCreatorBinder.addBinding().to(BlueprintExportEventCreator.class);
>
> auditLogEventCreatorBinder.addBinding().to(ServiceConfigDownloadEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(BlueprintEventCreator.class);
>
> auditLogEventCreatorBinder.addBinding().to(ViewInstanceEventCreator.class);
>
> auditLogEventCreatorBinder.addBinding().to(ViewPrivilegeEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(RepositoryEventCreator.class);
>
> auditLogEventCreatorBinder.addBinding().to(RepositoryVersionEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(AlertGroupEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(AlertTargetEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(HostEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(UpgradeEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(UpgradeItemEventCreator.class);
>
> auditLogEventCreatorBinder.addBinding().to(RecommendationIgnoreEventCreator.class);
>
> auditLogEventCreatorBinder.addBinding().to(ValidationIgnoreEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(CredentialEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(RequestEventCreator.class);
>
[jira] [Created] (AMBARI-15773) Password must not by displayed by UpgradeItem and Stage resources in the API
Alejandro Fernandez created AMBARI-15773:
Summary: Password must not by displayed by UpgradeItem and Stage
resources in the API
Key: AMBARI-15773
URL: https://issues.apache.org/jira/browse/AMBARI-15773
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.2.2
Reporter: Alejandro Fernandez
Assignee: Alejandro Fernandez
Priority: Blocker
Fix For: 2.2.2
STR:
* Install ambari-server-2.2.2.0-391 (ambari-server --hash:
8b49b71d5ef602e1252049fbc970958fbe05806e)
* Install HDP 2.3 or 2.4
* Install another version in order to perform RU or EU
* Use the API to navigate to
http://server:8080/api/v1/clusters/cl1/upgrades/##/upgrade_groups/1/upgrade_items/1
Notice that the output contains the ambari_db_rca_password in plaintext,
{code}
"host_params" :
"{\"agent_stack_retry_count\":\"5\",\"agent_stack_retry_on_unavailability\":\"false\",\"ambari_db_rca_driver\":\"org.postgresql.Driver\",\"ambari_db_rca_password\":\"bigdatacustom\",\"ambari_db_rca_url\":\"jdbc:postgresql://172.22.117.211:5432/ambaricustom\",\"ambari_db_rca_username\":\"ambaricustomuser\",\"current_version\":\"2.4.0.0-169\",\"db_driver_filename\":\"mysql-connector-java.jar\",\"db_name\":\"ambaricustom\",\"host_sys_prepped\":\"false\",\"java_home\":\"/usr/jdk64/jdk1.8.0_60\",\"java_version\":\"8\",\"jdk_location\":\"http://os-s11-4-snjlmu-ambari-se-eu-3-5.novalocal:8080/resources/\",\"mysql_jdbc_url\":\"http://os-s11-4-snjlmu-ambari-se-eu-3-5.novalocal:8080/resources//mysql-connector-java.jar\",\"not_managed_hdfs_path_list\":\"[\\\"/apps/hive/warehouse\\\",\\\"/apps/falcon\\\",\\\"/mr-history/done\\\",\\\"/app-logs\\\",\\\"/tmp\\\"]\",\"oracle_jdbc_url\":\"http://os-s11-4-snjlmu-ambari-se-eu-3-5.novalocal:8080/resources//ojdbc6.jar\",\"stack_name\":\"HDP\",\"stack_version\":\"2.4\"};,
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15679) Initial commit for LogSearch service definition
[ https://issues.apache.org/jira/browse/AMBARI-15679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-15679: -- Attachment: AMBARI-15679.patch > Initial commit for LogSearch service definition > --- > > Key: AMBARI-15679 > URL: https://issues.apache.org/jira/browse/AMBARI-15679 > Project: Ambari > Issue Type: Technical task > Components: stacks >Affects Versions: 2.4.0 >Reporter: Sumit Mohanty >Assignee: Olivér Szabó > Fix For: 2.4.0 > > Attachments: AMBARI-15679.patch > > > LogSearch service includes three major components: > * A Solr cloud to store logs and query > * Log collectors/feeders that consume log files being generated by the > services > * Log search service that provides REST API and UI front end > The above components are managed by Ambari through a stack definition. The > stack definition provides the mechanism to have the LogSearch service > configured to read log files created by other services, including Ambari > Server. This integration allows customizing log locations and letting > LogSearch service be aware of the locations. > Final peace is to provide an integration from the Ambari UI to LogSearch > service so that the logs for a service is easily accessible from the service > dashboards. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15679) Initial commit for LogSearch service definition
[ https://issues.apache.org/jira/browse/AMBARI-15679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-15679: -- Attachment: (was: AMBARI-15679.patch) > Initial commit for LogSearch service definition > --- > > Key: AMBARI-15679 > URL: https://issues.apache.org/jira/browse/AMBARI-15679 > Project: Ambari > Issue Type: Technical task > Components: stacks >Affects Versions: 2.4.0 >Reporter: Sumit Mohanty >Assignee: Olivér Szabó > Fix For: 2.4.0 > > > LogSearch service includes three major components: > * A Solr cloud to store logs and query > * Log collectors/feeders that consume log files being generated by the > services > * Log search service that provides REST API and UI front end > The above components are managed by Ambari through a stack definition. The > stack definition provides the mechanism to have the LogSearch service > configured to read log files created by other services, including Ambari > Server. This integration allows customizing log locations and letting > LogSearch service be aware of the locations. > Final peace is to provide an integration from the Ambari UI to LogSearch > service so that the logs for a service is easily accessible from the service > dashboards. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15772) HBase masters go offline after kerberization on 2.2.9.0
[ https://issues.apache.org/jira/browse/AMBARI-15772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-15772: - Status: Patch Available (was: Open) > HBase masters go offline after kerberization on 2.2.9.0 > --- > > Key: AMBARI-15772 > URL: https://issues.apache.org/jira/browse/AMBARI-15772 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: Dmytro Grinenko >Priority: Blocker > Fix For: 2.2.2 > > > STR: > - deploy Ambari with 2.2.9 stack (select hbase, hive and dependency) > - add ranger after > - start kerberization > Observe the status of HBase masters > All three report down -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15765) Improve config groups loading on wizard (part 2)
[ https://issues.apache.org/jira/browse/AMBARI-15765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230875#comment-15230875 ] Hudson commented on AMBARI-15765: - SUCCESS: Integrated in Ambari-trunk-Commit #4614 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4614/]) AMBARI-15765 Improve config groups loading on wizard (part 2). (ababiichuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=016a303bd8ed3fdcbb543e359a3f8acde87f5059]) * ambari-web/app/controllers/wizard/step7_controller.js * ambari-web/test/controllers/wizard/step7_test.js * ambari-web/app/utils/ajax/ajax.js > Improve config groups loading on wizard (part 2) > > > Key: AMBARI-15765 > URL: https://issues.apache.org/jira/browse/AMBARI-15765 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 2.4.0 > > Attachments: AMBARI-15765.patch > > > Use ServiceConfigGroups mapper to generate config groups on installer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-9776) Ambari server 1.7 installation issue
[ https://issues.apache.org/jira/browse/AMBARI-9776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230870#comment-15230870 ] Amanda Moran commented on AMBARI-9776: -- Faced this same issue using RHEL 7.2 on Power8. Wael Emam's method did work for me. > Ambari server 1.7 installation issue > > > Key: AMBARI-9776 > URL: https://issues.apache.org/jira/browse/AMBARI-9776 > Project: Ambari > Issue Type: Bug > Environment: RHEL 6.6 64-bit >Reporter: Wael Emam > > after installing ambari-server 1.7 on my box, for some reason I can not > access ambari's portal on 8080. My browser just keeps trying to connect. > I have no firewall or selinux running. I made sure that postgresql and > ambari-server are running. > In ambari-server.out, I can see some warning on "A HTTP GET method" > eb 24, 2015 1:06:10 PM com.sun.jersey.spi.inject.Errors processErrorMessages > WARNING: The following warnings have been detected with resource and/or > provider classes: > WARNING: A HTTP GET method, public javax.ws.rs.core.Response > org.apache.ambari.server.api.services.BlueprintService.getBlueprints(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo), > should not consume any entity. > WARNING: A HTTP GET method, public javax.ws.rs.core.Response > org.apache.ambari.server.api.services.BlueprintService.getBlueprint(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String), > should not consume any entity. > WARNING: A HTTP GET method, public javax.ws.rs.core.Response > org.apache.ambari.server.api.services.RequestService.getRequests(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo), > should not consume any entity. > WARNING: A HTTP GET method, public javax.ws.rs.core.Response > org.apache.ambari.server.api.services.RequestService.getRequest(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String), > should not consume any entity. > WARNING: A HTTP GET method, public javax.ws.rs.core.Response > org.apache.ambari.server.api.services.FeedService.getFeeds(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo), > should not consume any entity. > WARNING: A HTTP GET method, public javax.ws.rs.core.Response > org.apache.ambari.server.api.services.FeedService.getFeed(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String), > should not consume any entity. > WARNING: A HTTP GET method, public javax.ws.rs.core.Response > org.apache.ambari.server.api.services.ActionService.getActionDefinitions(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo), > should not consume any entity. > WARNING: A HTTP GET method, public javax.ws.rs.core.Response > org.apache.ambari.server.api.services.ActionService.getActionDefinition(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String), > should not consume any entity. > WARNING: A HTTP GET method, public javax.ws.rs.core.Response > org.apache.ambari.server.api.services.UserService.getUsers(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo), > should not consume any entity. > WARNING: A HTTP GET method, public javax.ws.rs.core.Response > org.apache.ambari.server.api.services.UserService.getUser(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String), > should not consume any entity. > WARNING: A HTTP GET method, public javax.ws.rs.core.Response > org.apache.ambari.server.api.services.ClusterService.getClusters(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo), > should not consume any entity. > WARNING: A HTTP GET method, public javax.ws.rs.core.Response > org.apache.ambari.server.api.services.ClusterService.getCluster(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String), > should not consume any entity. > WARNING: A HTTP GET method, public javax.ws.rs.core.Response > org.apache.ambari.server.api.services.TargetClusterService.getTargetClusters(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo), > should not consume any entity. > WARNING: A HTTP GET method, public javax.ws.rs.core.Response > org.apache.ambari.server.api.services.TargetClusterService.getTargetCluster(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String), > should not consume any entity. > WARNING: A HTTP GET method, public javax.ws.rs.core.Response > org.apache.ambari.server.api.services.RootServiceService.getServices(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo), > should not consume any entity. > WARNING: A HTTP GET method, public javax.ws.rs.core.Response >
[jira] [Commented] (AMBARI-15727) "E090 NullPointerException" when executing Hive queries with tez
[
https://issues.apache.org/jira/browse/AMBARI-15727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230877#comment-15230877
]
Hudson commented on AMBARI-15727:
-
SUCCESS: Integrated in Ambari-trunk-Commit #4614 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4614/])
AMBARI-15727. "E090 NullPointerException" when executing Hive queries
(pallav.kul:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=de09ef87cbaae7d8684f9d8931ed09111d6c0ec2])
*
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/jobs/Aggregator.java
> "E090 NullPointerException" when executing Hive queries with tez
>
>
> Key: AMBARI-15727
> URL: https://issues.apache.org/jira/browse/AMBARI-15727
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.2.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.2.2
>
> Attachments: AMBARI-15727_branch-2.2.patch
>
>
> ISSUE: Queries fail when execution engine is Tez from Hive view.
> Error :
> {code}
> java.lang.NullPointerException
> java.lang.NullPointerException
> at
> org.apache.ambari.view.hive.resources.jobs.Aggregator.saveJobInfoIfNeeded(Aggregator.java:180)
>
> at
> org.apache.ambari.view.hive.resources.jobs.Aggregator.readATSJob(Aggregator.java:133)
>
> at
> org.apache.ambari.view.hive.resources.jobs.JobService.jsonObjectFromJob(JobService.java:123)
>
> at
> org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:106)
>
> 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:497)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
>
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
>
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>
> {code}
> The same query works in the hive view if the execution engine is MR.
> Restarting Ambari did not work. Here is the tail of the ambari-server log:
> {code}
> 25 Feb 2016 13:15:21,451 INFO [qtp-ambari-client-31] Connection:497 - Hive
> session opened
> 25 Feb 2016 13:15:43,598 ERROR [qtp-ambari-client-31]
> ServiceFormattedException:96 - java.lang.NullPointerException
> java.lang.NullPointerException
> at
> org.apache.ambari.view.hive.resources.jobs.Aggregator.saveJobInfoIfNeeded(Aggregator.java:180)
>
> at
> org.apache.ambari.view.hive.resources.jobs.Aggregator.readATSJob(Aggregator.java:133)
>
> at
> org.apache.ambari.view.hive.resources.jobs.JobService.jsonObjectFromJob(JobService.java:123)
>
> at
> org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:106)
>
> 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:497)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:20
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15761) While creating WEB URLs for Alerts, if we add http/https then we should not drop the URL path past port number
[
https://issues.apache.org/jira/browse/AMBARI-15761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230879#comment-15230879
]
Hudson commented on AMBARI-15761:
-
SUCCESS: Integrated in Ambari-trunk-Commit #4614 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4614/])
AMBARI-15761. While creating WEB URLs for Alerts, if we add http/https
(aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1c737d3a29d42640cd16ffef1c179f6856a9ec76])
* ambari-agent/src/test/python/ambari_agent/TestAlerts.py
* ambari-agent/src/main/python/ambari_agent/alerts/web_alert.py
*
ambari-common/src/main/python/resource_management/libraries/functions/__init__.py
*
ambari-common/src/main/python/resource_management/libraries/functions/get_path_from_url.py
* ambari-agent/src/test/python/resource_management/TestGetPathFromUrl.py
> While creating WEB URLs for Alerts, if we add http/https then we should not
> drop the URL path past port number
> --
>
> Key: AMBARI-15761
> URL: https://issues.apache.org/jira/browse/AMBARI-15761
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.2.2
>
> Attachments: AMBARI-15761.patch
>
>
> As an example, look at the following alert:
>
>
>
> "APP_TIMELINE_SERVER": [
> {
> "name": "yarn_app_timeline_server_webui",
> "label": "App Timeline Web UI",
> "description": "This host-level alert is triggered if the App
> Timeline Server Web UI is unreachable.",
> "interval": 5,
> "scope": "ANY",
> "source": {
> "type": "WEB",
> "uri": {
> "http":
> "{{yarn-site/yarn.timeline-service.webapp.address}}/ws/v1/timeline",
> "https":
> "{{yarn-site/yarn.timeline-service.webapp.https.address}}/ws/v1/timeline",
> "https_property": "{{yarn-site/yarn.http.policy}}",
> "https_property_value": "HTTPS_ONLY",
> "kerberos_keytab":
> "{{yarn-site/yarn.timeline-service.http-authentication.kerberos.keytab}}",
> "kerberos_principal":
> "{{yarn-site/yarn.timeline-service.http-authentication.kerberos.principal}}",
> "connection_timeout": 5.0
> },
> "reporting": {
> "ok": {
> "text": "HTTP {0} response in {2:.3f}s"
> },
> "warning":{
> "text": "HTTP {0} response from {1} in {2:.3f}s ({3})"
> },
> "critical": {
> "text": "Connection failed to {1} ({3})"
> }
> }
> }
> }
> ]
> }
>
> Specifically lines:
>
>
>
> "http":
> "{{yarn-site/yarn.timeline-service.webapp.address}}/ws/v1/timeline",
> "https":
> "{{yarn-site/yarn.timeline-service.webapp.https.address}}/ws/v1/timeline",
>
> These properties e.g. `yarn-site/yarn.timeline-service.webapp.address` are of
> the form `host:port`. So the logic that adds http/https does not preserve that
> the URL has `ws/v1/timeline` at the end.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-14383) Add support for Ranger TagSync process as a component under RANGER
[ https://issues.apache.org/jira/browse/AMBARI-14383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230871#comment-15230871 ] Hudson commented on AMBARI-14383: - SUCCESS: Integrated in Ambari-trunk-Commit #4614 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4614/]) AMBARI-14383. Add support for Ranger TagSync process as a component (gautam: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b1d43fbe00e3396524f75904ace3492c44d1de2e]) * ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_service.py * ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_tagsync.py * ambari-common/src/main/python/resource_management/libraries/functions/stack_features.py * ambari-common/src/main/python/resource_management/libraries/functions/package_conditions.py * ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py * ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/status_params.py * ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py * ambari-common/src/main/python/resource_management/libraries/functions/stack_select.py * ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py * ambari-server/src/main/resources/stacks/HDP/2.6/services/RANGER/metainfo.xml * ambari-server/src/main/resources/stacks/HDP/2.5/services/RANGER/themes/theme_version_3.json * ambari-server/src/test/python/stacks/2.0.6/hooks/after-INSTALL/test_after_install.py * ambari-server/src/main/resources/stacks/HDP/2.5/services/RANGER/configuration/ranger-tagsync-site.xml * ambari-server/src/main/resources/stacks/HDP/2.5/services/RANGER/configuration/tagsync-application-properties.xml * ambari-server/src/main/resources/stacks/HDP/2.2/services/RANGER/metainfo.xml * ambari-server/src/main/resources/stacks/HDP/2.5/services/RANGER/metainfo.xml * ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_features.json * ambari-server/src/test/python/stacks/2.5/configs/default.json * ambari-common/src/main/python/resource_management/libraries/functions/constants.py * ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py > Add support for Ranger TagSync process as a component under RANGER > -- > > Key: AMBARI-14383 > URL: https://issues.apache.org/jira/browse/AMBARI-14383 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Gautam Borad >Assignee: Gautam Borad > Fix For: 2.4.0 > > Attachments: AMBARI-14383.1.patch, AMBARI-14383.2.patch, > AMBARI-14383.3.patch, AMBARI-14383.patch > > > Ranger TagSync is a separate service that will be responsible for > synchronizing the tags from Apache Atlas into Apache Ranger (db). > This jira will track changes required to install/configure TagSync from > Ambari. > * Add Ranger TagSync component under existing RANGER service. > * The component will be a master component > * Ability to start/stop the component independently of Ranger Admin. > * Ability to install the component on any host of the cluster > * Support should be available only from HDP 2.3 > * Any other changes required in Ambari stack to support such component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15767) Ambari should report about slow sudo hosts
[ https://issues.apache.org/jira/browse/AMBARI-15767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230874#comment-15230874 ] Hudson commented on AMBARI-15767: - SUCCESS: Integrated in Ambari-trunk-Commit #4614 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4614/]) AMBARI-15767. Ambari should report about slow sudo hosts (aonishuk) (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=73472dc1cea0fdf00afa88d802048269483e2f91]) * ambari-agent/src/main/python/ambari_agent/main.py * ambari-agent/src/test/python/ambari_agent/TestMain.py > Ambari should report about slow sudo hosts > -- > > Key: AMBARI-15767 > URL: https://issues.apache.org/jira/browse/AMBARI-15767 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-15767.patch > > > When a host has a slow sudo command, its very difficult to know of it till you > spend some time on the problem. It would be nice if Ambari could provide an > alert, or some other means by which user is notified of a slow sudo command -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15763) Delete service: UX edits v2
[ https://issues.apache.org/jira/browse/AMBARI-15763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230878#comment-15230878 ] Hudson commented on AMBARI-15763: - SUCCESS: Integrated in Ambari-trunk-Commit #4614 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4614/]) AMBARI-15763. Delete service: UX edits v2 (alexantonenko) (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d17ea8be32fefe83d23de94ddd18906a0fa426c3]) * ambari-web/app/messages.js > Delete service: UX edits v2 > --- > > Key: AMBARI-15763 > URL: https://issues.apache.org/jira/browse/AMBARI-15763 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-15763.patch, minor-wording (1).pptx > > > Minor text edit to dependent service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15756) File browser view should have some checks before starting similar to pig view
[ https://issues.apache.org/jira/browse/AMBARI-15756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230873#comment-15230873 ] Hudson commented on AMBARI-15756: - SUCCESS: Integrated in Ambari-trunk-Commit #4614 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4614/]) AMBARI-15756. File browser view should have some checks before starting (pallav.kul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=81497776eeefc7190645186bd20adfb50f3c7471]) * contrib/views/files/src/main/resources/ui/app/routes/index.js * contrib/views/files/src/main/resources/ui/app/controllers/splash.js * contrib/views/files/src/main/java/org/apache/ambari/view/filebrowser/HelpService.java * contrib/views/files/src/main/resources/ui/app/router.js * contrib/views/files/src/main/java/org/apache/ambari/view/filebrowser/HdfsService.java * contrib/views/files/src/main/resources/ui/app/routes/splash.js * contrib/views/files/src/main/resources/ui/app/templates/splash.hbs > File browser view should have some checks before starting similar to pig view > - > > Key: AMBARI-15756 > URL: https://issues.apache.org/jira/browse/AMBARI-15756 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.1.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha > Fix For: 2.4.0 > > Attachments: AMBARI-15756_trunk.patch > > > File browser view should have some checks before starting similar to pig view > Without this, there are times where file browser view is taking time to load, > and hence would need some type of status. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15696) BulkCommand stop NodeManagers stops the wrong component
[ https://issues.apache.org/jira/browse/AMBARI-15696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230876#comment-15230876 ] Hudson commented on AMBARI-15696: - SUCCESS: Integrated in Ambari-trunk-Commit #4614 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4614/]) AMBARI-15696: BulkCommand stop NodeManagers stops the wrong component (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=10371363d2bae1ee2c5e968afc9e94240a2ee49a]) * ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/metainfo.xml * ambari-server/src/main/java/org/apache/ambari/server/state/ComponentInfo.java > BulkCommand stop NodeManagers stops the wrong component > --- > > Key: AMBARI-15696 > URL: https://issues.apache.org/jira/browse/AMBARI-15696 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-15696.patch > > > when user clicks on the Stop command for NodeManagers, UI started the wrong > component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15772) HBase masters go offline after kerberization on 2.2.9.0
Dmytro Grinenko created AMBARI-15772: Summary: HBase masters go offline after kerberization on 2.2.9.0 Key: AMBARI-15772 URL: https://issues.apache.org/jira/browse/AMBARI-15772 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.2.2 Reporter: Dmytro Grinenko Priority: Blocker Fix For: 2.2.2 STR: - deploy Ambari with 2.2.9 stack (select hbase, hive and dependency) - add ranger after - start kerberization Observe the status of HBase masters All three report down -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15679) Initial commit for LogSearch service definition
[ https://issues.apache.org/jira/browse/AMBARI-15679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-15679: -- Status: Patch Available (was: In Progress) > Initial commit for LogSearch service definition > --- > > Key: AMBARI-15679 > URL: https://issues.apache.org/jira/browse/AMBARI-15679 > Project: Ambari > Issue Type: Technical task > Components: stacks >Affects Versions: 2.4.0 >Reporter: Sumit Mohanty >Assignee: Olivér Szabó > Fix For: 2.4.0 > > Attachments: AMBARI-15679.patch > > > LogSearch service includes three major components: > * A Solr cloud to store logs and query > * Log collectors/feeders that consume log files being generated by the > services > * Log search service that provides REST API and UI front end > The above components are managed by Ambari through a stack definition. The > stack definition provides the mechanism to have the LogSearch service > configured to read log files created by other services, including Ambari > Server. This integration allows customizing log locations and letting > LogSearch service be aware of the locations. > Final peace is to provide an integration from the Ambari UI to LogSearch > service so that the logs for a service is easily accessible from the service > dashboards. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15646) Audit Log Code Cleanup & Safety
[
https://issues.apache.org/jira/browse/AMBARI-15646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230846#comment-15230846
]
Sebastian Toader commented on AMBARI-15646:
---
Committed to trunk:
{code}
commit 6320d589f942b41cdab34c1de241423ccb5b4752
Author: Daniel Gergely
Date: Thu Apr 7 18:48:43 2016 +0200
AMBARI-15646. Audit Log Code Cleanup & Safety. (Daniel Gergely via stoader)
{code}
> Audit Log Code Cleanup & Safety
> ---
>
> Key: AMBARI-15646
> URL: https://issues.apache.org/jira/browse/AMBARI-15646
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Daniel Gergely
>Assignee: Daniel Gergely
> Attachments: AMBARI-15646.patch
>
>
> As a follow-up to AMBARI-15241, there are concerns brought up in review which
> should be addressed but didn't need to hold up the feature being committed.
> These can be further broken out to into separate Jiras if needed:
> - When initializing a ThreadLocal, you can specify an initial value. This
> code is unnecessary:
> {code}
> private ThreadLocal dateFormatThreadLocal = new ThreadLocal<>();
> if(dateFormatThreadLocal.get() == null) {
> //2016-03-11T10:42:36.376Z
> dateFormatThreadLocal.set(new
> SimpleDateFormat("-MM-dd'T'HH:mm:ss.SSSX"));
> }
> {code}
> - There are no tests for a majority of events and event creators.
> - Using a multibinder is fine to be able to inject a {{Set}}, but it's
> not clear to developers adding code that this is what must be done.
> -- We either need to document the super interface to make it clear how to
> have new creators bound
> -- Or annotate creators with an annotation which then be automatically picked
> up by the {{AuditLoggerModule}} and bound without the need to explicitly
> define each creator.
> - {code}
> // binding for audit event creators
> Multibinder auditLogEventCreatorBinder =
> Multibinder.newSetBinder(binder(), RequestAuditEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(DefaultEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(ComponentEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(ServiceEventCreator.class);
>
> auditLogEventCreatorBinder.addBinding().to(UnauthorizedEventCreator.class);
>
> auditLogEventCreatorBinder.addBinding().to(ConfigurationChangeEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(UserEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(GroupEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(MemberEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(PrivilegeEventCreator.class);
>
> auditLogEventCreatorBinder.addBinding().to(BlueprintExportEventCreator.class);
>
> auditLogEventCreatorBinder.addBinding().to(ServiceConfigDownloadEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(BlueprintEventCreator.class);
>
> auditLogEventCreatorBinder.addBinding().to(ViewInstanceEventCreator.class);
>
> auditLogEventCreatorBinder.addBinding().to(ViewPrivilegeEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(RepositoryEventCreator.class);
>
> auditLogEventCreatorBinder.addBinding().to(RepositoryVersionEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(AlertGroupEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(AlertTargetEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(HostEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(UpgradeEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(UpgradeItemEventCreator.class);
>
> auditLogEventCreatorBinder.addBinding().to(RecommendationIgnoreEventCreator.class);
>
> auditLogEventCreatorBinder.addBinding().to(ValidationIgnoreEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(CredentialEventCreator.class);
> auditLogEventCreatorBinder.addBinding().to(RequestEventCreator.class);
> bind(RequestAuditLogger.class).to(RequestAuditLoggerImpl.class);
> {code}
> - Event creators have nested invocations which is not only hard to read, but
> can potentially cause NPE's; it's a dangerous practice. As an example:
> {code:title=AlertGroupEventCreator}
> String.valueOf(request.getBody().getNamedPropertySets().iterator().next().getProperties().get(PropertyHelper.getPropertyId("AlertGroup",
> "name")));
> {code}
> -- Additionally, this references properties by building them, instead of by
> their registration in the property provider. If the property name ever
> changed, this could easily be missed.
> - Some of the {{auditLog}} methods check to ensure that the logger is enabled
> first. This is very good, as building objects which won't be logged is a
> waste
[jira] [Updated] (AMBARI-15679) Initial commit for LogSearch service definition
[ https://issues.apache.org/jira/browse/AMBARI-15679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-15679: -- Attachment: AMBARI-15679.patch > Initial commit for LogSearch service definition > --- > > Key: AMBARI-15679 > URL: https://issues.apache.org/jira/browse/AMBARI-15679 > Project: Ambari > Issue Type: Technical task > Components: stacks >Affects Versions: 2.4.0 >Reporter: Sumit Mohanty >Assignee: Olivér Szabó > Fix For: 2.4.0 > > Attachments: AMBARI-15679.patch > > > LogSearch service includes three major components: > * A Solr cloud to store logs and query > * Log collectors/feeders that consume log files being generated by the > services > * Log search service that provides REST API and UI front end > The above components are managed by Ambari through a stack definition. The > stack definition provides the mechanism to have the LogSearch service > configured to read log files created by other services, including Ambari > Server. This integration allows customizing log locations and letting > LogSearch service be aware of the locations. > Final peace is to provide an integration from the Ambari UI to LogSearch > service so that the logs for a service is easily accessible from the service > dashboards. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15738) Descriptions for HAWQ sysctl params mention incorrect default values
[ https://issues.apache.org/jira/browse/AMBARI-15738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt updated AMBARI-15738: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Descriptions for HAWQ sysctl params mention incorrect default values > > > Key: AMBARI-15738 > URL: https://issues.apache.org/jira/browse/AMBARI-15738 > Project: Ambari > Issue Type: Bug >Reporter: Alexander Denissov >Assignee: Alexander Denissov >Priority: Minor > Fix For: 2.2.2 > > Attachments: AMBARI-15738.branch22.patch > > > kernel.shmmax and net.ipv4.ip_local_port_range have incorrect default values > in their descriptions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15738) Descriptions for HAWQ sysctl params mention incorrect default values
[ https://issues.apache.org/jira/browse/AMBARI-15738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt updated AMBARI-15738: -- Fix Version/s: trunk > Descriptions for HAWQ sysctl params mention incorrect default values > > > Key: AMBARI-15738 > URL: https://issues.apache.org/jira/browse/AMBARI-15738 > Project: Ambari > Issue Type: Bug >Reporter: Alexander Denissov >Assignee: Alexander Denissov >Priority: Minor > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15738.branch22.patch > > > kernel.shmmax and net.ipv4.ip_local_port_range have incorrect default values > in their descriptions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15738) Descriptions for HAWQ sysctl params mention incorrect default values
[
https://issues.apache.org/jira/browse/AMBARI-15738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230815#comment-15230815
]
Matt commented on AMBARI-15738:
---
Committed to trunk:
{code}
author Matt
Thu, 7 Apr 2016 11:08:03 -0700 (11:08 -0700)
committer Matt
Thu, 7 Apr 2016 11:08:03 -0700 (11:08 -0700)
commit f0645b68abdcc61876313fd2e9aa5fec552a566e
{code}
Committed to branch-2.2:
{code}
author Matt
Thu, 7 Apr 2016 11:08:56 -0700 (11:08 -0700)
committer Matt
Thu, 7 Apr 2016 11:08:56 -0700 (11:08 -0700)
commit 41f14c7221bc7d71fafb70ab9abebff7786e8583
{code}
Marking as resolved.
> Descriptions for HAWQ sysctl params mention incorrect default values
>
>
> Key: AMBARI-15738
> URL: https://issues.apache.org/jira/browse/AMBARI-15738
> Project: Ambari
> Issue Type: Bug
>Reporter: Alexander Denissov
>Assignee: Alexander Denissov
>Priority: Minor
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15738.branch22.patch
>
>
> kernel.shmmax and net.ipv4.ip_local_port_range have incorrect default values
> in their descriptions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15745) Create Alert For Reporting Potential Issues With Slow REST Responses
[
https://issues.apache.org/jira/browse/AMBARI-15745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-15745:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Create Alert For Reporting Potential Issues With Slow REST Responses
>
>
> Key: AMBARI-15745
> URL: https://issues.apache.org/jira/browse/AMBARI-15745
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15745.patch
>
>
> There are many factors which can influence the response rate of the REST API
> when the web client polls various endpoints:
> - Database access problems
> - Federated PropertyProvider delays
> - Serialization Time of JSON
> If the response rate of the REST API is poor, this can affect the overall UX
> of the product and produce a situation where Ambari doesn't seem to be
> responding.
> There should be an alert which provides queries into various parts of Ambari
> in order to determine if response times are acceptable.
> - This should be a {{SERVER}} side task
> - If possible, the query should be made directly through the ResourceProvider
> framework to simulate a REST request. It should be made against the cluster
> endpoint since that's what is most likely polled.
> - The alert should have configurable values for the threshold settings.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15745) Create Alert For Reporting Potential Issues With Slow REST Responses
[
https://issues.apache.org/jira/browse/AMBARI-15745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-15745:
-
Attachment: AMBARI-15745.patch
> Create Alert For Reporting Potential Issues With Slow REST Responses
>
>
> Key: AMBARI-15745
> URL: https://issues.apache.org/jira/browse/AMBARI-15745
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15745.patch
>
>
> There are many factors which can influence the response rate of the REST API
> when the web client polls various endpoints:
> - Database access problems
> - Federated PropertyProvider delays
> - Serialization Time of JSON
> If the response rate of the REST API is poor, this can affect the overall UX
> of the product and produce a situation where Ambari doesn't seem to be
> responding.
> There should be an alert which provides queries into various parts of Ambari
> in order to determine if response times are acceptable.
> - This should be a {{SERVER}} side task
> - If possible, the query should be made directly through the ResourceProvider
> framework to simulate a REST request. It should be made against the cluster
> endpoint since that's what is most likely polled.
> - The alert should have configurable values for the threshold settings.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15745) Create Alert For Reporting Potential Issues With Slow REST Responses
[
https://issues.apache.org/jira/browse/AMBARI-15745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-15745:
-
Status: Patch Available (was: Open)
> Create Alert For Reporting Potential Issues With Slow REST Responses
>
>
> Key: AMBARI-15745
> URL: https://issues.apache.org/jira/browse/AMBARI-15745
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15745.patch
>
>
> There are many factors which can influence the response rate of the REST API
> when the web client polls various endpoints:
> - Database access problems
> - Federated PropertyProvider delays
> - Serialization Time of JSON
> If the response rate of the REST API is poor, this can affect the overall UX
> of the product and produce a situation where Ambari doesn't seem to be
> responding.
> There should be an alert which provides queries into various parts of Ambari
> in order to determine if response times are acceptable.
> - This should be a {{SERVER}} side task
> - If possible, the query should be made directly through the ResourceProvider
> framework to simulate a REST request. It should be made against the cluster
> endpoint since that's what is most likely polled.
> - The alert should have configurable values for the threshold settings.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-15771) After enabling NN HA with HAWQ installed, duplicate properties are seen on HAWQ config tab
Matt created AMBARI-15771: - Summary: After enabling NN HA with HAWQ installed, duplicate properties are seen on HAWQ config tab Key: AMBARI-15771 URL: https://issues.apache.org/jira/browse/AMBARI-15771 Project: Ambari Issue Type: Bug Reporter: Matt Assignee: Goutam Tadi Fix For: trunk, 2.2.2 Steps to reproduce: - Install a cluster with HDFS and HAWQ - Enable Namenode HA (hawq_dfs_url should get updated here) After enabling Namenode HA, a duplicate hawq_dfs_url along with other properties from hawq-site are shown in Configs page of HAWQ service. This issue happens quite often, but not every time. More investigation is required. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15766) Create a new alert type that is based on timeseries metrics
[ https://issues.apache.org/jira/browse/AMBARI-15766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-15766: Status: Patch Available (was: Open) > Create a new alert type that is based on timeseries metrics > --- > > Key: AMBARI-15766 > URL: https://issues.apache.org/jira/browse/AMBARI-15766 > Project: Ambari > Issue Type: Task > Components: alerts, ambari-metrics >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15766-trunk_1.patch > > > There are a few requirements around creating alerts based on the time-series > data stored in AMS. They fall in the the general category of: > identify a metrics (name of the metrics, app name) > - identify a window (e.g. last 10 minutes, last 1 day) > - get the data points > - add them up, or > - compute average, or > - compute standard deviations, or > ... > - compare the value to a threshold > - emit an alert if needed (WARN, CRITICAL, etc) > We should also allow for alerts based on multiple metrics but there is no ask > for such a capability. Just something to keep in mind while designing. > It seems general enough that we should define an alert type that can be > instantiated by services to define specific alerts. Users can add additional > alerts if they so choose. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15766) Create a new alert type that is based on timeseries metrics
[ https://issues.apache.org/jira/browse/AMBARI-15766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-15766: Status: Open (was: Patch Available) > Create a new alert type that is based on timeseries metrics > --- > > Key: AMBARI-15766 > URL: https://issues.apache.org/jira/browse/AMBARI-15766 > Project: Ambari > Issue Type: Task > Components: alerts, ambari-metrics >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15766-trunk_1.patch > > > There are a few requirements around creating alerts based on the time-series > data stored in AMS. They fall in the the general category of: > identify a metrics (name of the metrics, app name) > - identify a window (e.g. last 10 minutes, last 1 day) > - get the data points > - add them up, or > - compute average, or > - compute standard deviations, or > ... > - compare the value to a threshold > - emit an alert if needed (WARN, CRITICAL, etc) > We should also allow for alerts based on multiple metrics but there is no ask > for such a capability. Just something to keep in mind while designing. > It seems general enough that we should define an alert type that can be > instantiated by services to define specific alerts. Users can add additional > alerts if they so choose. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15766) Create a new alert type that is based on timeseries metrics
[
https://issues.apache.org/jira/browse/AMBARI-15766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230710#comment-15230710
]
Hadoop QA commented on AMBARI-15766:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12797534/AMBARI-15766-trunk_1.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 4 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.state.cluster.ClustersDeadlockTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6289//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6289//console
This message is automatically generated.
> Create a new alert type that is based on timeseries metrics
> ---
>
> Key: AMBARI-15766
> URL: https://issues.apache.org/jira/browse/AMBARI-15766
> Project: Ambari
> Issue Type: Task
> Components: alerts, ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15766-trunk_1.patch
>
>
> There are a few requirements around creating alerts based on the time-series
> data stored in AMS. They fall in the the general category of:
> identify a metrics (name of the metrics, app name)
> - identify a window (e.g. last 10 minutes, last 1 day)
> - get the data points
> - add them up, or
> - compute average, or
> - compute standard deviations, or
> ...
> - compare the value to a threshold
> - emit an alert if needed (WARN, CRITICAL, etc)
> We should also allow for alerts based on multiple metrics but there is no ask
> for such a capability. Just something to keep in mind while designing.
> It seems general enough that we should define an alert type that can be
> instantiated by services to define specific alerts. Users can add additional
> alerts if they so choose.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-15770) HAWQ fails to connect to YARN in HA+SEC mode
Alexander Denissov created AMBARI-15770: --- Summary: HAWQ fails to connect to YARN in HA+SEC mode Key: AMBARI-15770 URL: https://issues.apache.org/jira/browse/AMBARI-15770 Project: Ambari Issue Type: Bug Reporter: Alexander Denissov Assignee: Alexander Denissov Fix For: 2.2.2 When HAWQ is in the cluster with YARN HA and Kerberos enabled, the segments are down as they cannot connect to YARN RM. The following updates are required: 1. add hadoop.security.authentication = kerberos in yarn-client.xml 2. add 2 properties to core-site.xml: hadoop.proxyuser.postgres.hosts * hadoop.proxyuser.postgres.groups hadoop 3. on every node: sudo useradd postgres sudo usermod -a -G hadoop postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15577) Stack Featurize Hive Service
[ https://issues.apache.org/jira/browse/AMBARI-15577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-15577: --- Attachment: AMBARI-15577.patch > Stack Featurize Hive Service > > > Key: AMBARI-15577 > URL: https://issues.apache.org/jira/browse/AMBARI-15577 > Project: Ambari > Issue Type: Technical task > Components: stacks >Affects Versions: 2.1.0, 2.2.0 >Reporter: Jayush Luniya >Assignee: Juanjo Marron > Fix For: 2.4.0 > > Attachments: AMBARI-15577.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15577) Stack Featurize Hive Service
[ https://issues.apache.org/jira/browse/AMBARI-15577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-15577: --- Status: Open (was: Patch Available) > Stack Featurize Hive Service > > > Key: AMBARI-15577 > URL: https://issues.apache.org/jira/browse/AMBARI-15577 > Project: Ambari > Issue Type: Technical task > Components: stacks >Affects Versions: 2.1.0, 2.2.0 >Reporter: Jayush Luniya >Assignee: Juanjo Marron > Fix For: 2.4.0 > > Attachments: AMBARI-15577.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15577) Stack Featurize Hive Service
[ https://issues.apache.org/jira/browse/AMBARI-15577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-15577: --- Status: Patch Available (was: Open) > Stack Featurize Hive Service > > > Key: AMBARI-15577 > URL: https://issues.apache.org/jira/browse/AMBARI-15577 > Project: Ambari > Issue Type: Technical task > Components: stacks >Affects Versions: 2.1.0, 2.2.0 >Reporter: Jayush Luniya >Assignee: Juanjo Marron > Fix For: 2.4.0 > > Attachments: AMBARI-15577.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15742) Recommendations return 500 error for HIVE with
[
https://issues.apache.org/jira/browse/AMBARI-15742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230616#comment-15230616
]
Hudson commented on AMBARI-15742:
-
ABORTED: Integrated in Ambari-trunk-Commit #4613 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4613/])
AMBARI-15742. Recommendations return 500 error for HIVE with (hiveww:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=aceeacef678006493d51d7ad80cf69ab91083433])
* ambari-server/src/main/resources/stacks/HDP/2.1/services/stack_advisor.py
* ambari-server/src/test/python/stacks/2.1/common/test_stack_advisor.py
> Recommendations return 500 error for HIVE with
> --
>
> Key: AMBARI-15742
> URL: https://issues.apache.org/jira/browse/AMBARI-15742
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-15742.patch
>
>
> Select "Existing MySQL / MariaDB Database " for HIVE
> Request to {{api/v1/stacks/HDP/versions/2.5/recommendations}} returns:
> {noformat}
> {
> "status" : 500,
> "message" : "Stack Advisor reported an error: AttributeError: 'NoneType'
> object has no attribute 'format'\nStdOut file:
> /var/run/ambari-server/stack-recommendations/73/stackadvisor.out\n\nStdErr
> file: /var/run/ambari-server/stack-recommendations/73/stackadvisor.err"
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15757) Add Service step4 load step takes 20+ seconds
[ https://issues.apache.org/jira/browse/AMBARI-15757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230615#comment-15230615 ] Hudson commented on AMBARI-15757: - ABORTED: Integrated in Ambari-trunk-Commit #4613 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4613/]) AMBARI-15757. Add Service step4 load step takes 20+ seconds. (onechiporenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6568b583d6a31c0c2dcecc0a7a82def22103270f]) * ambari-web/app/controllers/wizard/step7_controller.js > Add Service step4 load step takes 20+ seconds > - > > Key: AMBARI-15757 > URL: https://issues.apache.org/jira/browse/AMBARI-15757 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 2.4.0 > > Attachments: AMBARI-15757.patch > > > * Install cluster with a few services > * Open ASW > * Select all services to add > * Proceed to step4 > * It loading takes about 20-30 seconds -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15744) Webhcat Server failed to stop while stopping all the services
[
https://issues.apache.org/jira/browse/AMBARI-15744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230614#comment-15230614
]
Hudson commented on AMBARI-15744:
-
ABORTED: Integrated in Ambari-trunk-Commit #4613 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4613/])
AMBARI-15744. Webhcat Server failed to stop while stopping all the (stoader:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0e87151795a9bf97f8b7ef8033204b03f08ab91b])
*
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat_service.py
* ambari-server/src/test/python/stacks/2.0.6/HIVE/test_webhcat_server.py
> Webhcat Server failed to stop while stopping all the services
> --
>
> Key: AMBARI-15744
> URL: https://issues.apache.org/jira/browse/AMBARI-15744
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15744.branch-2.2.v1.patch,
> AMBARI-15744.branch-2.2.v2.patch, AMBARI-15744.trunk.v1.patch,
> AMBARI-15744.trunk.v2.patch
>
>
> Stop all the services using Stop All on dashboard. Webhcat server fails to
> stop with the below error. This looks like an intermittent issue.
> {code}
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat_server.py\",
> line 155, in \nWebHCatServer().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 219, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat_server.py\",
>
> line 47, in stop\nwebhcat_service(action='stop')\n File
> \"/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py\",
> line 89, in thunk\nreturn fn(*args, **kwargs)\n File
> \"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat_service.py\",
>
> line 57, in webhcat_service\nenvironment = environ)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\",
>line 154, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
>line 158, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
>line 121, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
>
>line 238, in action_run\ntries=self.resource.tries,
> try_sleep=self.resource.try_sleep)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\",
>line 70, in inner\nresult = function(command, **kwargs)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\",
> line 92, in checked_call\ntries=tries, try_sleep=try_sleep)\n
> File \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\",
>line 140, in _call_wrapper\nresult = _call(command,
> **kwargs_copy)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\",
>line 291, in _call\nraise
> Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of
> '/usr/hdp/current/hive-webhcat/sbin/webhcat_server.sh stop' returned 1.
> webhcat: stopping
> ...\n/usr/hdp/2.4.2.0-127/hive-hcatalog/sbin/webhcat_server.sh: failed to stop
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15744) Webhcat Server failed to stop while stopping all the services
[
https://issues.apache.org/jira/browse/AMBARI-15744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230584#comment-15230584
]
Hudson commented on AMBARI-15744:
-
SUCCESS: Integrated in Ambari-branch-2.2 #607 (See
[https://builds.apache.org/job/Ambari-branch-2.2/607/])
AMBARI-15744. Webhcat Server failed to stop while stopping all the (stoader:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=86a2305c0a8456dfdbe5e80f3cedd1630cad51b1])
*
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat_service.py
* ambari-server/src/test/python/stacks/2.0.6/HIVE/test_webhcat_server.py
> Webhcat Server failed to stop while stopping all the services
> --
>
> Key: AMBARI-15744
> URL: https://issues.apache.org/jira/browse/AMBARI-15744
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15744.branch-2.2.v1.patch,
> AMBARI-15744.branch-2.2.v2.patch, AMBARI-15744.trunk.v1.patch,
> AMBARI-15744.trunk.v2.patch
>
>
> Stop all the services using Stop All on dashboard. Webhcat server fails to
> stop with the below error. This looks like an intermittent issue.
> {code}
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat_server.py\",
> line 155, in \nWebHCatServer().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 219, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat_server.py\",
>
> line 47, in stop\nwebhcat_service(action='stop')\n File
> \"/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py\",
> line 89, in thunk\nreturn fn(*args, **kwargs)\n File
> \"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat_service.py\",
>
> line 57, in webhcat_service\nenvironment = environ)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\",
>line 154, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
>line 158, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
>line 121, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
>
>line 238, in action_run\ntries=self.resource.tries,
> try_sleep=self.resource.try_sleep)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\",
>line 70, in inner\nresult = function(command, **kwargs)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\",
> line 92, in checked_call\ntries=tries, try_sleep=try_sleep)\n
> File \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\",
>line 140, in _call_wrapper\nresult = _call(command,
> **kwargs_copy)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\",
>line 291, in _call\nraise
> Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of
> '/usr/hdp/current/hive-webhcat/sbin/webhcat_server.sh stop' returned 1.
> webhcat: stopping
> ...\n/usr/hdp/2.4.2.0-127/hive-hcatalog/sbin/webhcat_server.sh: failed to stop
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15727) "E090 NullPointerException" when executing Hive queries with tez
[
https://issues.apache.org/jira/browse/AMBARI-15727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230585#comment-15230585
]
Hudson commented on AMBARI-15727:
-
SUCCESS: Integrated in Ambari-branch-2.2 #607 (See
[https://builds.apache.org/job/Ambari-branch-2.2/607/])
AMBARI-15727. "E090 NullPointerException" when executing Hive queries
(pallav.kul:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9029212a7d15006b9b171a69fb20796e7253b77e])
*
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/jobs/Aggregator.java
> "E090 NullPointerException" when executing Hive queries with tez
>
>
> Key: AMBARI-15727
> URL: https://issues.apache.org/jira/browse/AMBARI-15727
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.2.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.2.2
>
> Attachments: AMBARI-15727_branch-2.2.patch
>
>
> ISSUE: Queries fail when execution engine is Tez from Hive view.
> Error :
> {code}
> java.lang.NullPointerException
> java.lang.NullPointerException
> at
> org.apache.ambari.view.hive.resources.jobs.Aggregator.saveJobInfoIfNeeded(Aggregator.java:180)
>
> at
> org.apache.ambari.view.hive.resources.jobs.Aggregator.readATSJob(Aggregator.java:133)
>
> at
> org.apache.ambari.view.hive.resources.jobs.JobService.jsonObjectFromJob(JobService.java:123)
>
> at
> org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:106)
>
> 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:497)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
>
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
>
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>
> {code}
> The same query works in the hive view if the execution engine is MR.
> Restarting Ambari did not work. Here is the tail of the ambari-server log:
> {code}
> 25 Feb 2016 13:15:21,451 INFO [qtp-ambari-client-31] Connection:497 - Hive
> session opened
> 25 Feb 2016 13:15:43,598 ERROR [qtp-ambari-client-31]
> ServiceFormattedException:96 - java.lang.NullPointerException
> java.lang.NullPointerException
> at
> org.apache.ambari.view.hive.resources.jobs.Aggregator.saveJobInfoIfNeeded(Aggregator.java:180)
>
> at
> org.apache.ambari.view.hive.resources.jobs.Aggregator.readATSJob(Aggregator.java:133)
>
> at
> org.apache.ambari.view.hive.resources.jobs.JobService.jsonObjectFromJob(JobService.java:123)
>
> at
> org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:106)
>
> 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:497)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:20
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15753) Ambari Views : Reverting the changes for separation of logs in ambari branch-2.2
[ https://issues.apache.org/jira/browse/AMBARI-15753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230586#comment-15230586 ] Hudson commented on AMBARI-15753: - SUCCESS: Integrated in Ambari-branch-2.2 #607 (See [https://builds.apache.org/job/Ambari-branch-2.2/607/]) AMBARI-15753. Ambari Views : Reverting the changes for separation of (pallav.kul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f36059e262dc62b560580c5e98af0323f44be4d4]) * contrib/views/files/src/main/resources/view.log4j.properties * contrib/views/jobs/pom.xml * contrib/views/pig/pom.xml * contrib/views/slider/src/main/resources/view.log4j.properties * contrib/views/capacity-scheduler/pom.xml * contrib/views/hive/src/main/resources/view.log4j.properties * contrib/views/hive/pom.xml * contrib/views/jobs/src/main/resources/view.log4j.properties * contrib/views/capacity-scheduler/src/main/resources/view.log4j.properties * contrib/views/slider/pom.xml * ambari-server/src/main/java/org/apache/ambari/server/view/ViewRegistry.java * contrib/views/tez/pom.xml * contrib/views/tez/src/main/resources/view.log4j.properties * contrib/views/storm/src/main/resources/view.log4j.properties * contrib/views/files/pom.xml * contrib/views/pig/src/main/resources/view.log4j.properties > Ambari Views : Reverting the changes for separation of logs in ambari > branch-2.2 > > > Key: AMBARI-15753 > URL: https://issues.apache.org/jira/browse/AMBARI-15753 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.2.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Attachments: AMBARI-15753_branch-2.2.patch > > > Revert changes of AMBARI-14084 from branch-2.2 as it is wrong branch for > these changes. > Create a new patch which will revert these changes and apply only to > branch-2.2 of ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15741) Remove PHD references from HAWQ
[ https://issues.apache.org/jira/browse/AMBARI-15741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lav Jain updated AMBARI-15741: -- Fix Version/s: 2.2.2 2.3.0 Status: Patch Available (was: Open) > Remove PHD references from HAWQ > --- > > Key: AMBARI-15741 > URL: https://issues.apache.org/jira/browse/AMBARI-15741 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.2.0 >Reporter: Lav Jain >Assignee: Lav Jain >Priority: Minor > Fix For: 2.3.0, 2.2.2 > > Attachments: AMBARI-15741.branch22.patch, AMBARI-15741.patch > > > Remove any reference to PHD (pivotal) stack in HAWQ codebase as it has been > obsoleted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15741) Remove PHD references from HAWQ
[ https://issues.apache.org/jira/browse/AMBARI-15741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lav Jain updated AMBARI-15741: -- Attachment: AMBARI-15741.patch > Remove PHD references from HAWQ > --- > > Key: AMBARI-15741 > URL: https://issues.apache.org/jira/browse/AMBARI-15741 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.2.0 >Reporter: Lav Jain >Assignee: Lav Jain >Priority: Minor > Fix For: 2.3.0, 2.2.2 > > Attachments: AMBARI-15741.branch22.patch, AMBARI-15741.patch > > > Remove any reference to PHD (pivotal) stack in HAWQ codebase as it has been > obsoleted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15764) Add "services" element to compatible_repository_versions endpoint
[ https://issues.apache.org/jira/browse/AMBARI-15764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-15764: --- Status: Patch Available (was: Open) > Add "services" element to compatible_repository_versions endpoint > - > > Key: AMBARI-15764 > URL: https://issues.apache.org/jira/browse/AMBARI-15764 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15764.patch > > > The services/stack_services elements should be added to the endpoint to > reduce calls to the backend. > Also fixed issues where the compatible endpoint would not return correctly > with a user predicate. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15764) Add "services" element to compatible_repository_versions endpoint
[ https://issues.apache.org/jira/browse/AMBARI-15764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-15764: --- Attachment: AMBARI-15764.patch > Add "services" element to compatible_repository_versions endpoint > - > > Key: AMBARI-15764 > URL: https://issues.apache.org/jira/browse/AMBARI-15764 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15764.patch > > > The services/stack_services elements should be added to the endpoint to > reduce calls to the backend. > Also fixed issues where the compatible endpoint would not return correctly > with a user predicate. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15765) Improve config groups loading on wizard (part 2)
[ https://issues.apache.org/jira/browse/AMBARI-15765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-15765: -- Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk > Improve config groups loading on wizard (part 2) > > > Key: AMBARI-15765 > URL: https://issues.apache.org/jira/browse/AMBARI-15765 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 2.4.0 > > Attachments: AMBARI-15765.patch > > > Use ServiceConfigGroups mapper to generate config groups on installer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15744) Webhcat Server failed to stop while stopping all the services
[
https://issues.apache.org/jira/browse/AMBARI-15744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Toader updated AMBARI-15744:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Webhcat Server failed to stop while stopping all the services
> --
>
> Key: AMBARI-15744
> URL: https://issues.apache.org/jira/browse/AMBARI-15744
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15744.branch-2.2.v1.patch,
> AMBARI-15744.branch-2.2.v2.patch, AMBARI-15744.trunk.v1.patch,
> AMBARI-15744.trunk.v2.patch
>
>
> Stop all the services using Stop All on dashboard. Webhcat server fails to
> stop with the below error. This looks like an intermittent issue.
> {code}
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat_server.py\",
> line 155, in \nWebHCatServer().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 219, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat_server.py\",
>
> line 47, in stop\nwebhcat_service(action='stop')\n File
> \"/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py\",
> line 89, in thunk\nreturn fn(*args, **kwargs)\n File
> \"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat_service.py\",
>
> line 57, in webhcat_service\nenvironment = environ)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\",
>line 154, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
>line 158, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
>line 121, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
>
>line 238, in action_run\ntries=self.resource.tries,
> try_sleep=self.resource.try_sleep)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\",
>line 70, in inner\nresult = function(command, **kwargs)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\",
> line 92, in checked_call\ntries=tries, try_sleep=try_sleep)\n
> File \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\",
>line 140, in _call_wrapper\nresult = _call(command,
> **kwargs_copy)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\",
>line 291, in _call\nraise
> Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of
> '/usr/hdp/current/hive-webhcat/sbin/webhcat_server.sh stop' returned 1.
> webhcat: stopping
> ...\n/usr/hdp/2.4.2.0-127/hive-hcatalog/sbin/webhcat_server.sh: failed to stop
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15768) Ambari Widget should display metrics for available metrics even if some of the metrics it expects are not returned by API
[ https://issues.apache.org/jira/browse/AMBARI-15768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230487#comment-15230487 ] Aleksandr Kovalenko commented on AMBARI-15768: -- +1 for the patch > Ambari Widget should display metrics for available metrics even if some of > the metrics it expects are not returned by API > - > > Key: AMBARI-15768 > URL: https://issues.apache.org/jira/browse/AMBARI-15768 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15768.patch, AMBARI-15768_2.2.2.patch, Screen > Shot 2016-04-06 at 2.53.23 PM.png > > > For example, Namenode RPC widget requests 5 metrics from the backend. 2 of > the metrics' availability depends on a Namenode config to be present. In such > a case, the widget should display whatever metrics that are available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15768) Ambari Widget should display metrics for available metrics even if some of the metrics it expects are not returned by API
[ https://issues.apache.org/jira/browse/AMBARI-15768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-15768: -- Status: Patch Available (was: Open) > Ambari Widget should display metrics for available metrics even if some of > the metrics it expects are not returned by API > - > > Key: AMBARI-15768 > URL: https://issues.apache.org/jira/browse/AMBARI-15768 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15768.patch, AMBARI-15768_2.2.2.patch, Screen > Shot 2016-04-06 at 2.53.23 PM.png > > > For example, Namenode RPC widget requests 5 metrics from the backend. 2 of > the metrics' availability depends on a Namenode config to be present. In such > a case, the widget should display whatever metrics that are available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15768) Ambari Widget should display metrics for available metrics even if some of the metrics it expects are not returned by API
[ https://issues.apache.org/jira/browse/AMBARI-15768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230485#comment-15230485 ] Andrii Tkach commented on AMBARI-15768: --- 25646 tests complete (25 seconds) 154 tests pending > Ambari Widget should display metrics for available metrics even if some of > the metrics it expects are not returned by API > - > > Key: AMBARI-15768 > URL: https://issues.apache.org/jira/browse/AMBARI-15768 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15768.patch, AMBARI-15768_2.2.2.patch, Screen > Shot 2016-04-06 at 2.53.23 PM.png > > > For example, Namenode RPC widget requests 5 metrics from the backend. 2 of > the metrics' availability depends on a Namenode config to be present. In such > a case, the widget should display whatever metrics that are available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15768) Ambari Widget should display metrics for available metrics even if some of the metrics it expects are not returned by API
[ https://issues.apache.org/jira/browse/AMBARI-15768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-15768: -- Attachment: AMBARI-15768_2.2.2.patch > Ambari Widget should display metrics for available metrics even if some of > the metrics it expects are not returned by API > - > > Key: AMBARI-15768 > URL: https://issues.apache.org/jira/browse/AMBARI-15768 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15768.patch, AMBARI-15768_2.2.2.patch, Screen > Shot 2016-04-06 at 2.53.23 PM.png > > > For example, Namenode RPC widget requests 5 metrics from the backend. 2 of > the metrics' availability depends on a Namenode config to be present. In such > a case, the widget should display whatever metrics that are available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15768) Ambari Widget should display metrics for available metrics even if some of the metrics it expects are not returned by API
[ https://issues.apache.org/jira/browse/AMBARI-15768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-15768: -- Attachment: AMBARI-15768.patch > Ambari Widget should display metrics for available metrics even if some of > the metrics it expects are not returned by API > - > > Key: AMBARI-15768 > URL: https://issues.apache.org/jira/browse/AMBARI-15768 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15768.patch, AMBARI-15768_2.2.2.patch, Screen > Shot 2016-04-06 at 2.53.23 PM.png > > > For example, Namenode RPC widget requests 5 metrics from the backend. 2 of > the metrics' availability depends on a Namenode config to be present. In such > a case, the widget should display whatever metrics that are available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15750) [Ambari Web] "Install Packages" option not shown when a new version is registered
[ https://issues.apache.org/jira/browse/AMBARI-15750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-15750: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk. > [Ambari Web] "Install Packages" option not shown when a new version is > registered > - > > Key: AMBARI-15750 > URL: https://issues.apache.org/jira/browse/AMBARI-15750 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Xi Wang >Assignee: Xi Wang >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-15750.patch > > > ambari-server --hash > 6fe7f83277a269dc6d9634b186ff3fc05fca8505 > 1.Install Ambari from trunk (2.4.0.0) > 2.Install cluster with HDP-2.2 > 3.Register a repo HDP-2.3.4 using version definition file > 4.Register a repo HDP-2.3.2 using REST API in the old repo version format > 6.Both the registered versions do not show up in Admin>Stacks and > Versions>Versions page. > 7.Kick off Install Packages using the REST API instead. > 8.Note the new registered version shows up in the UI in "Installing" state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15750) [Ambari Web] "Install Packages" option not shown when a new version is registered
[ https://issues.apache.org/jira/browse/AMBARI-15750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230481#comment-15230481 ] Yusaku Sako commented on AMBARI-15750: -- +1 for the patch. > [Ambari Web] "Install Packages" option not shown when a new version is > registered > - > > Key: AMBARI-15750 > URL: https://issues.apache.org/jira/browse/AMBARI-15750 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Xi Wang >Assignee: Xi Wang >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-15750.patch > > > ambari-server --hash > 6fe7f83277a269dc6d9634b186ff3fc05fca8505 > 1.Install Ambari from trunk (2.4.0.0) > 2.Install cluster with HDP-2.2 > 3.Register a repo HDP-2.3.4 using version definition file > 4.Register a repo HDP-2.3.2 using REST API in the old repo version format > 6.Both the registered versions do not show up in Admin>Stacks and > Versions>Versions page. > 7.Kick off Install Packages using the REST API instead. > 8.Note the new registered version shows up in the UI in "Installing" state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15750) [Ambari Web] "Install Packages" option not shown when a new version is registered
[ https://issues.apache.org/jira/browse/AMBARI-15750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-15750: - Description: ambari-server --hash 6fe7f83277a269dc6d9634b186ff3fc05fca8505 1.Install Ambari from trunk (2.4.0.0) 2.Install cluster with HDP-2.2 3.Register a repo HDP-2.3.4 using version definition file 4.Register a repo HDP-2.3.2 using REST API in the old repo version format 6.Both the registered versions do not show up in Admin>Stacks and Versions>Versions page. 7.Kick off Install Packages using the REST API instead. 8.Note the new registered version shows up in the UI in "Installing" state. was: ambari-server --hash 6fe7f83277a269dc6d9634b186ff3fc05fca8505 1.Install Ambari from trunk (2.4.0.0) 2.Install cluster with HDP-2.2 3.Register a repo HDP-2.3.4 using version definition file 4.Register a repo HDP-2.3.2 using REST API in the old repo version format (Refer: 5.https://docs.google.com/document/d/1M9WSi7GrozYTxGaqsgCSp25aydP88h8LMgdEVZfzRDM) 6.Both the registered versions do not show up in Admin>Stacks and Versions>Versions page. 7.Kick off Install Packages using the REST API instead. 8.Note the new registered version shows up in the UI in "Installing" state. > [Ambari Web] "Install Packages" option not shown when a new version is > registered > - > > Key: AMBARI-15750 > URL: https://issues.apache.org/jira/browse/AMBARI-15750 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Xi Wang >Assignee: Xi Wang >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-15750.patch > > > ambari-server --hash > 6fe7f83277a269dc6d9634b186ff3fc05fca8505 > 1.Install Ambari from trunk (2.4.0.0) > 2.Install cluster with HDP-2.2 > 3.Register a repo HDP-2.3.4 using version definition file > 4.Register a repo HDP-2.3.2 using REST API in the old repo version format > 6.Both the registered versions do not show up in Admin>Stacks and > Versions>Versions page. > 7.Kick off Install Packages using the REST API instead. > 8.Note the new registered version shows up in the UI in "Installing" state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15769) Add Maria DB support for Ambari Server.
[ https://issues.apache.org/jira/browse/AMBARI-15769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myroslav Papirkovskyi updated AMBARI-15769: --- Attachment: AMBARI-15769.patch > Add Maria DB support for Ambari Server. > --- > > Key: AMBARI-15769 > URL: https://issues.apache.org/jira/browse/AMBARI-15769 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15769.patch > > > Ambari server should support MariaDB via mysql driver -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15769) Add Maria DB support for Ambari Server.
[ https://issues.apache.org/jira/browse/AMBARI-15769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myroslav Papirkovskyi updated AMBARI-15769: --- Status: Patch Available (was: Open) > Add Maria DB support for Ambari Server. > --- > > Key: AMBARI-15769 > URL: https://issues.apache.org/jira/browse/AMBARI-15769 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15769.patch > > > Ambari server should support MariaDB via mysql driver -- This message was sent by Atlassian JIRA (v6.3.4#6332)
