[jira] [Commented] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo
[
https://issues.apache.org/jira/browse/AMBARI-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047469#comment-16047469
]
Hadoop QA commented on AMBARI-21230:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12872810/AMBARI-21230.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-metrics/ambari-metrics-common ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11645//console
This message is automatically generated.
> Add Kerberos HTTP SPNEGO authentication support to Accumulo
> ---
>
> Key: AMBARI-21230
> URL: https://issues.apache.org/jira/browse/AMBARI-21230
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-metrics, ambari-server
>Affects Versions: 2.5.0
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
> Attachments: AMBARI-21230.patch
>
>
> This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to
> authenticate".
> In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari
> Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But
> Accumulo sinks, clients of Ambari Metrics Collector, currently do not support
> Kerberos HTTP SPNEGO authentication.
> e.g.,
> /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log:
> 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST
> metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics,
> statusCode = 401
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21227) Updating Ranger install.properties file
[ https://issues.apache.org/jira/browse/AMBARI-21227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047442#comment-16047442 ] Hudson commented on AMBARI-21227: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7618 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7618/]) AMBARI-21227 Updating Ranger install.properties file (mugdha) (mugdha: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1f19461f10a2c54d3ed81efedc3f9d3d64397700]) * (edit) ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py * (edit) ambari-server/src/test/python/stacks/2.5/RANGER/test_ranger_admin.py * (edit) ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/package/scripts/kms.py * (edit) ambari-server/src/test/python/stacks/2.6/RANGER/test_ranger_admin.py * (edit) ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/package/scripts/kms_server.py * (edit) ambari-server/src/test/python/stacks/2.5/RANGER_KMS/test_kms_server.py * (edit) ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_admin.py * (edit) ambari-server/src/test/python/stacks/2.2/RANGER/test_ranger_admin.py * (edit) ambari-common/src/main/python/resource_management/libraries/providers/modify_properties_file.py > Updating Ranger install.properties file > --- > > Key: AMBARI-21227 > URL: https://issues.apache.org/jira/browse/AMBARI-21227 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21227.patch > > > Updating Ranger and Ranger Kms services install.properties. Also backing the > files in ambari-agent tmp directory. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21227) Updating Ranger install.properties file
[ https://issues.apache.org/jira/browse/AMBARI-21227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047441#comment-16047441 ] Hudson commented on AMBARI-21227: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1591 (See [https://builds.apache.org/job/Ambari-branch-2.5/1591/]) AMBARI-21227 Updating Ranger install.properties file (mugdha) (mugdha: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=21959a49590db5f7cccfcff60f37ca12faf03bb3]) * (edit) ambari-common/src/main/python/resource_management/libraries/providers/modify_properties_file.py * (edit) ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/package/scripts/kms_server.py * (edit) ambari-server/src/test/python/stacks/2.6/RANGER/test_ranger_admin.py * (edit) ambari-server/src/test/python/stacks/2.5/RANGER/test_ranger_admin.py * (edit) ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py * (edit) ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/package/scripts/kms.py * (edit) ambari-server/src/test/python/stacks/2.5/RANGER_KMS/test_kms_server.py * (edit) ambari-server/src/test/python/stacks/2.2/RANGER/test_ranger_admin.py * (edit) ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_admin.py > Updating Ranger install.properties file > --- > > Key: AMBARI-21227 > URL: https://issues.apache.org/jira/browse/AMBARI-21227 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21227.patch > > > Updating Ranger and Ranger Kms services install.properties. Also backing the > files in ambari-agent tmp directory. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo
[ https://issues.apache.org/jira/browse/AMBARI-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21230: - Status: Patch Available (was: Open) > Add Kerberos HTTP SPNEGO authentication support to Accumulo > --- > > Key: AMBARI-21230 > URL: https://issues.apache.org/jira/browse/AMBARI-21230 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-21230.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Accumulo sinks, clients of Ambari Metrics Collector, currently do not support > Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo
[ https://issues.apache.org/jira/browse/AMBARI-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21230: - Attachment: AMBARI-21230.patch > Add Kerberos HTTP SPNEGO authentication support to Accumulo > --- > > Key: AMBARI-21230 > URL: https://issues.apache.org/jira/browse/AMBARI-21230 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-21230.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Accumulo sinks, clients of Ambari Metrics Collector, currently do not support > Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo
[ https://issues.apache.org/jira/browse/AMBARI-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21230: - Status: Open (was: Patch Available) > Add Kerberos HTTP SPNEGO authentication support to Accumulo > --- > > Key: AMBARI-21230 > URL: https://issues.apache.org/jira/browse/AMBARI-21230 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Accumulo sinks, clients of Ambari Metrics Collector, currently do not support > Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo
[ https://issues.apache.org/jira/browse/AMBARI-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21230: - Attachment: (was: AMBARI-21230.patch) > Add Kerberos HTTP SPNEGO authentication support to Accumulo > --- > > Key: AMBARI-21230 > URL: https://issues.apache.org/jira/browse/AMBARI-21230 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Accumulo sinks, clients of Ambari Metrics Collector, currently do not support > Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21227) Updating Ranger install.properties file
[ https://issues.apache.org/jira/browse/AMBARI-21227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21227: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5: [21959a49590db5f7cccfcff60f37ca12faf03bb3|https://github.com/apache/ambari/commit/21959a49590db5f7cccfcff60f37ca12faf03bb3] and trunk: [1f19461f10a2c54d3ed81efedc3f9d3d64397700|https://github.com/apache/ambari/commit/1f19461f10a2c54d3ed81efedc3f9d3d64397700] > Updating Ranger install.properties file > --- > > Key: AMBARI-21227 > URL: https://issues.apache.org/jira/browse/AMBARI-21227 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21227.patch > > > Updating Ranger and Ranger Kms services install.properties. Also backing the > files in ambari-agent tmp directory. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-20749) Ambari data purging
[ https://issues.apache.org/jira/browse/AMBARI-20749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047412#comment-16047412 ] Sebastian Toader commented on AMBARI-20749: --- Added a couple of fixes to https://issues.apache.org/jira/browse/AMBARI-20687 and renamed the db-cleanup functionality to db-purge-history > Ambari data purging > --- > > Key: AMBARI-20749 > URL: https://issues.apache.org/jira/browse/AMBARI-20749 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: amarnath reddy pappu >Assignee: Sebastian Toader >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-20749.b25.v1.patch > > > Currently there is one option to purge the old data in Ambari. > 1. db-cleanup : this sound like database clean up (or delete) , may be better > word like Purge can be used. > 2. appears like currently it purges only Alert related tables - should also > consider of other tables lie host_role_command and execution_commands and if > there is any other tables as well. > 3. I don't find any documentation on this option - some customers are trying > to hard delete entries from DB tables and ending up with some other issues. > so better documentation would help here. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-20749) Ambari data purging
[ https://issues.apache.org/jira/browse/AMBARI-20749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-20749: -- Attachment: AMBARI-20749.b25.v1.patch > Ambari data purging > --- > > Key: AMBARI-20749 > URL: https://issues.apache.org/jira/browse/AMBARI-20749 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: amarnath reddy pappu >Assignee: Sebastian Toader >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-20749.b25.v1.patch > > > Currently there is one option to purge the old data in Ambari. > 1. db-cleanup : this sound like database clean up (or delete) , may be better > word like Purge can be used. > 2. appears like currently it purges only Alert related tables - should also > consider of other tables lie host_role_command and execution_commands and if > there is any other tables as well. > 3. I don't find any documentation on this option - some customers are trying > to hard delete entries from DB tables and ending up with some other issues. > so better documentation would help here. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-20749) Ambari data purging
[ https://issues.apache.org/jira/browse/AMBARI-20749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-20749: -- Status: Patch Available (was: In Progress) > Ambari data purging > --- > > Key: AMBARI-20749 > URL: https://issues.apache.org/jira/browse/AMBARI-20749 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: amarnath reddy pappu >Assignee: Sebastian Toader >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-20749.b25.v1.patch > > > Currently there is one option to purge the old data in Ambari. > 1. db-cleanup : this sound like database clean up (or delete) , may be better > word like Purge can be used. > 2. appears like currently it purges only Alert related tables - should also > consider of other tables lie host_role_command and execution_commands and if > there is any other tables as well. > 3. I don't find any documentation on this option - some customers are trying > to hard delete entries from DB tables and ending up with some other issues. > so better documentation would help here. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-20122) Stack advisor needs to recommend dependency for slaves and masters
[ https://issues.apache.org/jira/browse/AMBARI-20122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047225#comment-16047225 ] Hudson commented on AMBARI-20122: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7617 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7617/]) Revert "AMBARI-20122 - Stack advisor needs to recommend dependency for (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=75152614e84299d16f36a6c6d7387b77a172eb96]) * (edit) ambari-server/src/test/python/stacks/2.0.6/common/test_stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/stack_advisor.py > Stack advisor needs to recommend dependency for slaves and masters > -- > > Key: AMBARI-20122 > URL: https://issues.apache.org/jira/browse/AMBARI-20122 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Jaimin Jetly >Assignee: Tim Thorpe > Fix For: 3.0.0 > > Attachments: AMBARI-20122.patch > > > After resolution of AMBARI-19685, stack advisor validates if stack defined > dependency is not satisfied but recommendation API does not account for this. > Stack defined dependencies are service/component based and has a scope > CLUSTER|HOST. > During recommendation the services to install have already been selected. We > can't really utilize the cluster scope because either the dependent service > was selected or it was not. If it was not selected it will be caught during > validation. We can only recommend based on HOST scope. > This JIRA is also limited to only handling those which don't have conditional > dependencies. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21202) YARN service advisor has spelling error in yarn-site
[
https://issues.apache.org/jira/browse/AMBARI-21202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047226#comment-16047226
]
Hudson commented on AMBARI-21202:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7617 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7617/])
Revert "AMBARI-21202 - YARN service advisor has spelling error in (jaimin:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8cdf232bde26fb3a0cd46fb178be7c517d068a0c])
* (edit)
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/service_advisor.py
> YARN service advisor has spelling error in yarn-site
>
>
> Key: AMBARI-21202
> URL: https://issues.apache.org/jira/browse/AMBARI-21202
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Tim Thorpe
>Assignee: Tim Thorpe
> Fix For: trunk
>
> Attachments: AMBARI-21202.patch
>
>
> self.validators = [("yarn-site",
> self.validateYARNSiteConfigurationsFromHDP206),
> ("yarn-site",
> self.validateYARNSiteConfigurationsFromHDP25),
> ("yarn-ste" ,
> self.validateYarnSiteConfigurationsFromHDP26),
> The HDP26 validator should be for yarn-site not yarn-ste.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21235) When trying to add a host as Cluster Administrator or Cluster Operator, Add Host Wizard keeps reloading due to permission failure
Sangeeta Ravindran created AMBARI-21235: --- Summary: When trying to add a host as Cluster Administrator or Cluster Operator, Add Host Wizard keeps reloading due to permission failure Key: AMBARI-21235 URL: https://issues.apache.org/jira/browse/AMBARI-21235 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: trunk Reporter: Sangeeta Ravindran Assignee: Sangeeta Ravindran 1. Login as a Cluster Administrator or Cluster Operator. 2. Click on Add Hosts. Enter the required details on Step 1 and click on Register and Confirm. 3. Step 2 of the wizard is displayed and because preinstalled.checks (http://host:port/api/v1/requests) call returns 403 for Cluster Operator, the error callback is called and the UI is reloaded. This causes the wizard to come back to Step 2 of Add Host Wizard and the process is repeated and the wizard keeps reloading repeatedly. According to the Role Comparison chart, Cluster Administrators and Cluster Operators should be able to add hosts. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21234) Ambari rack awareness for Kafka
[ https://issues.apache.org/jira/browse/AMBARI-21234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047184#comment-16047184 ] Ambud Sharma commented on AMBARI-21234: --- https://github.com/apache/ambari/pull/57 > Ambari rack awareness for Kafka > --- > > Key: AMBARI-21234 > URL: https://issues.apache.org/jira/browse/AMBARI-21234 > Project: Ambari > Issue Type: Improvement >Reporter: Ambud Sharma > > As an operations person it would be nice to manage Kafka rack awareness via > Ambari. Ambari allows node rack information to be configured and this > information can then be pulled in the Kafka stack and populated in the > server.properties file for Kafka. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo
[
https://issues.apache.org/jira/browse/AMBARI-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047181#comment-16047181
]
Hadoop QA commented on AMBARI-21230:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12872777/AMBARI-21230.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/11644//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11644//console
This message is automatically generated.
> Add Kerberos HTTP SPNEGO authentication support to Accumulo
> ---
>
> Key: AMBARI-21230
> URL: https://issues.apache.org/jira/browse/AMBARI-21230
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-metrics, ambari-server
>Affects Versions: 2.5.0
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
> Attachments: AMBARI-21230.patch
>
>
> This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to
> authenticate".
> In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari
> Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But
> Accumulo sinks, clients of Ambari Metrics Collector, currently do not support
> Kerberos HTTP SPNEGO authentication.
> e.g.,
> /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log:
> 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST
> metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics,
> statusCode = 401
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21234) Ambari rack awareness for Kafka
[ https://issues.apache.org/jira/browse/AMBARI-21234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047174#comment-16047174 ] ASF GitHub Bot commented on AMBARI-21234: - GitHub user ambud opened a pull request: https://github.com/apache/ambari/pull/57 Ambari rackawareness for Kafka stack AMBARI-21234 You can merge this pull request into a Git repository by running: $ git pull https://github.com/ambud/ambari trunk Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ambari/pull/57.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #57 commit b395780eaa7eff5c9492315df1d26be31b5fbf08 Author: ambud Date: 2017-06-12T22:54:31Z Ambari rackawareness for Kafka stack AMBARI-21234 > Ambari rack awareness for Kafka > --- > > Key: AMBARI-21234 > URL: https://issues.apache.org/jira/browse/AMBARI-21234 > Project: Ambari > Issue Type: Improvement >Reporter: Ambud Sharma > > As an operations person it would be nice to manage Kafka rack awareness via > Ambari. Ambari allows node rack information to be configured and this > information can then be pulled in the Kafka stack and populated in the > server.properties file for Kafka. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21234) Ambari rack awareness for Kafka
Ambud Sharma created AMBARI-21234: - Summary: Ambari rack awareness for Kafka Key: AMBARI-21234 URL: https://issues.apache.org/jira/browse/AMBARI-21234 Project: Ambari Issue Type: Improvement Reporter: Ambud Sharma As an operations person it would be nice to manage Kafka rack awareness via Ambari. Ambari allows node rack information to be configured and this information can then be pulled in the Kafka stack and populated in the server.properties file for Kafka. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21202) YARN service advisor has spelling error in yarn-site
[
https://issues.apache.org/jira/browse/AMBARI-21202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047166#comment-16047166
]
Jaimin Jetly commented on AMBARI-21202:
---
[~Tim Thorpe]
The commit has been reverted because it was blocking from deploying clusters
via ambari-web:
Selecting any partial set of service on "Select Services" page was causing
stack advisor recommendation call to fail with following error:
{code}
Traceback (most recent call last):
File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 167,
in
main(sys.argv)
File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 108,
in main
result = stackAdvisor.recommendComponentLayout(services, hosts)
File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
line 608, in recommendComponentLayout
layoutRecommendations = self.createComponentLayoutRecommendations(services,
hosts)
File
"/var/lib/ambari-server/resources/scripts/./../stacks/HDP/2.5/services/stack_advisor.py",
line 91, in createComponentLayoutRecommendations
services, hosts)
File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
line 760, in createComponentLayoutRecommendations
sortedServices = self.getServicesSortedByDependencies(services)
File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
line 886, in getServicesSortedByDependencies
self.sortServicesByDependencies(services, service, processedServices,
sortedServices)
File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
line 911, in sortServicesByDependencies
self.sortServicesByDependencies(services, requiredService,
processedServices, sortedServices)
File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
line 901, in sortServicesByDependencies
for component in service["components"]:
TypeError: 'NoneType' object is unsubscriptable
{code}
Please fix this issue and re-commit the patch
> YARN service advisor has spelling error in yarn-site
>
>
> Key: AMBARI-21202
> URL: https://issues.apache.org/jira/browse/AMBARI-21202
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Tim Thorpe
>Assignee: Tim Thorpe
> Fix For: trunk
>
> Attachments: AMBARI-21202.patch
>
>
> self.validators = [("yarn-site",
> self.validateYARNSiteConfigurationsFromHDP206),
> ("yarn-site",
> self.validateYARNSiteConfigurationsFromHDP25),
> ("yarn-ste" ,
> self.validateYarnSiteConfigurationsFromHDP26),
> The HDP26 validator should be for yarn-site not yarn-ste.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Reopened] (AMBARI-20122) Stack advisor needs to recommend dependency for slaves and masters
[
https://issues.apache.org/jira/browse/AMBARI-20122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin Jetly reopened AMBARI-20122:
---
The commit has been reverted because it was blocking from deploying clusters
via ambari-web:
Selecting any partial set of service on "Select Services" page was causing
stack advisor recommendation call to fail with following error:
{code}
Traceback (most recent call last):
File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 167,
in
main(sys.argv)
File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 108,
in main
result = stackAdvisor.recommendComponentLayout(services, hosts)
File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
line 608, in recommendComponentLayout
layoutRecommendations = self.createComponentLayoutRecommendations(services,
hosts)
File
"/var/lib/ambari-server/resources/scripts/./../stacks/HDP/2.5/services/stack_advisor.py",
line 91, in createComponentLayoutRecommendations
services, hosts)
File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
line 760, in createComponentLayoutRecommendations
sortedServices = self.getServicesSortedByDependencies(services)
File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
line 886, in getServicesSortedByDependencies
self.sortServicesByDependencies(services, service, processedServices,
sortedServices)
File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
line 911, in sortServicesByDependencies
self.sortServicesByDependencies(services, requiredService,
processedServices, sortedServices)
File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
line 901, in sortServicesByDependencies
for component in service["components"]:
TypeError: 'NoneType' object is unsubscriptable
{code}
> Stack advisor needs to recommend dependency for slaves and masters
> --
>
> Key: AMBARI-20122
> URL: https://issues.apache.org/jira/browse/AMBARI-20122
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Jaimin Jetly
>Assignee: Tim Thorpe
> Fix For: 3.0.0
>
> Attachments: AMBARI-20122.patch
>
>
> After resolution of AMBARI-19685, stack advisor validates if stack defined
> dependency is not satisfied but recommendation API does not account for this.
> Stack defined dependencies are service/component based and has a scope
> CLUSTER|HOST.
> During recommendation the services to install have already been selected. We
> can't really utilize the cluster scope because either the dependent service
> was selected or it was not. If it was not selected it will be caught during
> validation. We can only recommend based on HOST scope.
> This JIRA is also limited to only handling those which don't have conditional
> dependencies.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo
[ https://issues.apache.org/jira/browse/AMBARI-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21230: - Status: Patch Available (was: In Progress) > Add Kerberos HTTP SPNEGO authentication support to Accumulo > --- > > Key: AMBARI-21230 > URL: https://issues.apache.org/jira/browse/AMBARI-21230 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-21230.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Accumulo sinks, clients of Ambari Metrics Collector, currently do not support > Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo
[ https://issues.apache.org/jira/browse/AMBARI-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21230: - Attachment: AMBARI-21230.patch > Add Kerberos HTTP SPNEGO authentication support to Accumulo > --- > > Key: AMBARI-21230 > URL: https://issues.apache.org/jira/browse/AMBARI-21230 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-21230.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Accumulo sinks, clients of Ambari Metrics Collector, currently do not support > Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21207) Extend Swagger Maven pluging to handle nested API's
[
https://issues.apache.org/jira/browse/AMBARI-21207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Balázs Bence Sári updated AMBARI-21207:
---
Attachment: (was: nested_api_trunk_v1.patch)
> Extend Swagger Maven pluging to handle nested API's
> ---
>
> Key: AMBARI-21207
> URL: https://issues.apache.org/jira/browse/AMBARI-21207
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Balázs Bence Sári
>Assignee: Balázs Bence Sári
> Fix For: 3.0.0
>
> Attachments: nested_api_trunk_v2.patch
>
>
> A Nested API is an API that doesn't have a class level {{@Path}} annotation.
> Instances of these API classes are returned by other API's. The paths of the
> nested API methods are prefixed with the parent API method.
> Pls. see {{ClusterService#getServiceHandler()}} and {{ServiceService}} for
> example.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21207) Extend Swagger Maven pluging to handle nested API's
[
https://issues.apache.org/jira/browse/AMBARI-21207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Balázs Bence Sári updated AMBARI-21207:
---
Attachment: nested_api_trunk_v2.patch
> Extend Swagger Maven pluging to handle nested API's
> ---
>
> Key: AMBARI-21207
> URL: https://issues.apache.org/jira/browse/AMBARI-21207
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Balázs Bence Sári
>Assignee: Balázs Bence Sári
> Fix For: 3.0.0
>
> Attachments: nested_api_trunk_v2.patch
>
>
> A Nested API is an API that doesn't have a class level {{@Path}} annotation.
> Instances of these API classes are returned by other API's. The paths of the
> nested API methods are prefixed with the parent API method.
> Pls. see {{ClusterService#getServiceHandler()}} and {{ServiceService}} for
> example.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21233) ambari-web hits JS error in dev mode
Antonenko Alexander created AMBARI-21233: Summary: ambari-web hits JS error in dev mode Key: AMBARI-21233 URL: https://issues.apache.org/jira/browse/AMBARI-21233 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Antonenko Alexander Fix For: 3.0.0 http://localhost: hits JS several error and dashboard does not show up -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-20688) Supvervisord control option for Kafka broker
[ https://issues.apache.org/jira/browse/AMBARI-20688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047123#comment-16047123 ] ASF GitHub Bot commented on AMBARI-20688: - Github user ambud closed the pull request at: https://github.com/apache/ambari/pull/53 > Supvervisord control option for Kafka broker > > > Key: AMBARI-20688 > URL: https://issues.apache.org/jira/browse/AMBARI-20688 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Ambud Sharma > > Just like Storm Supervisor option in Storm Ambari stack to have Supervisord > manage the process, adding supervisord for Kafka is helpful for automated > broker recovery in case of machine reboots. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21232) Determination of defaultFS with WebHDFS enabled
[ https://issues.apache.org/jira/browse/AMBARI-21232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sridhar Sailappan updated AMBARI-21232: --- Attachment: Patch_AmbariViewUtils_WebHDFS.txt > Determination of defaultFS with WebHDFS enabled > --- > > Key: AMBARI-21232 > URL: https://issues.apache.org/jira/browse/AMBARI-21232 > Project: Ambari > Issue Type: Improvement > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Sridhar Sailappan > Attachments: Patch_AmbariViewUtils_WebHDFS.txt > > > In Ambari View Utils , the determination logic for the value of defaultFS > when WebHDFS is enabled, needs to consider the current property value of > defaultFS. Please see attached patch for the context. > If the existing configuration for the defaultFS URI already has the protocol > specified as webhdfs or swebhdfs, the URI should be used as provided and a > new value should not be constructed. Constructing a new value in a such a > scenario may lead to unexpected behavior if the Namenode has different > host-port settings for the HTTP and WebHDFS access. > The patch also addresses the following code cleanup: > 1)Fix variable names httpAddr and httpsAddr (current implementation has > the naming interchanged) > 2)Add null value check for httpAddr before assignment to hostWithPort > 3)Fix typo in variable names - DFS_NAMENODE_HTTP_ADDRESS and > DFS_NAMENODE_HTTPS_ADDRESS -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21232) Determination of defaultFS with WebHDFS enabled
Sridhar Sailappan created AMBARI-21232: -- Summary: Determination of defaultFS with WebHDFS enabled Key: AMBARI-21232 URL: https://issues.apache.org/jira/browse/AMBARI-21232 Project: Ambari Issue Type: Improvement Components: ambari-views Affects Versions: 2.4.0 Reporter: Sridhar Sailappan In Ambari View Utils , the determination logic for the value of defaultFS when WebHDFS is enabled, needs to consider the current property value of defaultFS. Please see attached patch for the context. If the existing configuration for the defaultFS URI already has the protocol specified as webhdfs or swebhdfs, the URI should be used as provided and a new value should not be constructed. Constructing a new value in a such a scenario may lead to unexpected behavior if the Namenode has different host-port settings for the HTTP and WebHDFS access. The patch also addresses the following code cleanup: 1) Fix variable names httpAddr and httpsAddr (current implementation has the naming interchanged) 2) Add null value check for httpAddr before assignment to hostWithPort 3) Fix typo in variable names - DFS_NAMENODE_HTTP_ADDRESS and DFS_NAMENODE_HTTPS_ADDRESS -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-1679) Create ambari agent scripts for Hadoop 2.0 installation, configuration and management
[ https://issues.apache.org/jira/browse/AMBARI-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-1679: --- Assignee: Siddharth Wagle > Create ambari agent scripts for Hadoop 2.0 installation, configuration and > management > - > > Key: AMBARI-1679 > URL: https://issues.apache.org/jira/browse/AMBARI-1679 > Project: Ambari > Issue Type: Sub-task > Components: ambari-agent >Affects Versions: 1.3.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle > Fix For: 1.4.0 > > Attachments: AMBARI-1679.patch > > > Create ambari agent scripts for Hadoop 2.0 installation, configuration and > management based on HDP-1.3.1 stack definition. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-10484) Expose API endpoint to expose active widget layout for a user
[ https://issues.apache.org/jira/browse/AMBARI-10484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-10484: Assignee: Ivan Kozlov > Expose API endpoint to expose active widget layout for a user > - > > Key: AMBARI-10484 > URL: https://issues.apache.org/jira/browse/AMBARI-10484 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.1.0 >Reporter: Siddharth Wagle >Assignee: Ivan Kozlov > Fix For: 2.1.0 > > > Support user endpoint to return active widget layouts for a user. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-10543) String matches does not work on metrics property of Widget response
[
https://issues.apache.org/jira/browse/AMBARI-10543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako reassigned AMBARI-10543:
Assignee: Ivan Kozlov
> String matches does not work on metrics property of Widget response
> ---
>
> Key: AMBARI-10543
> URL: https://issues.apache.org/jira/browse/AMBARI-10543
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.1.0
>Reporter: Siddharth Wagle
>Assignee: Ivan Kozlov
> Fix For: 2.1.0
>
>
> *Following API does not work*
> http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/widgets?Widgets/widget_type=HEATMAP&Widgets/metrics.matches(\"service_name\":\"HDFS\")
> *Note: Following similar API works*
> http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/widgets?Widgets/widget_type=HEATMAP&Widgets/widget_name.matches(HOST_DISK_USED)
> {code:title=Response}
> {
> "href" :
> "http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/widgets?Widgets/widget_type=HEATMAP&Widgets/widget_name.matches(HOST_DISK_USED)",
> "items" : [
> {
> "href" :
> "http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/widgets/1";,
> "Widgets" : {
> "author" : "ambari",
> "cluster_name" : "c1",
> "display_name" : "Host Disk Space Used %",
> "id" : 1,
> "scope" : "CLUSTER",
> "widget_name" : "HOST_DISK_USED",
> "widget_type" : "HEATMAP"
> }
> }
> ]
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-5637) Remove Start/Stop Hadoop Cluster Service tasks for Pig and Sqoop services
[ https://issues.apache.org/jira/browse/AMBARI-5637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-5637: --- Assignee: Anatoly Nikonorov > Remove Start/Stop Hadoop Cluster Service tasks for Pig and Sqoop services > - > > Key: AMBARI-5637 > URL: https://issues.apache.org/jira/browse/AMBARI-5637 > Project: Ambari > Issue Type: Task > Components: contrib >Reporter: Anatoly Nikonorov >Assignee: Anatoly Nikonorov > Attachments: AMBARI-5637.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (AMBARI-2341) Installation of hadoop fails when /etc/hadoop/conf is present
[
https://issues.apache.org/jira/browse/AMBARI-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako reopened AMBARI-2341:
-
> Installation of hadoop fails when /etc/hadoop/conf is present
> -
>
> Key: AMBARI-2341
> URL: https://issues.apache.org/jira/browse/AMBARI-2341
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Reporter: Alexander Alten-Lorenz
>Priority: Blocker
>
> Installation fails when the config directories are present.
> Edit to be more precise (as example):
> {code}
> notice: /Stage[2]/Hdp-hive/Anchor[hdp-hive::end]: Dependency
> File[/etc/hive/conf] has failures: true
> warning: /Stage[2]/Hdp-hive/Anchor[hdp-hive::end]: Skipping because of failed
> dependencies
> notice: /Stage[2]/Hdp-hive::Service/File[/tmp/startMetastore.sh]: Dependency
> File[/etc/hive/conf] has failures: true
> warning: /Stage[2]/Hdp-hive::Service/File[/tmp/startMetastore.sh]: Skipping
> because of failed dependencies
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-5296) update Management Pack to support Hadoop MapReduce2 and YARN services
[ https://issues.apache.org/jira/browse/AMBARI-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-5296: --- Assignee: Anatoly Nikonorov > update Management Pack to support Hadoop MapReduce2 and YARN services > - > > Key: AMBARI-5296 > URL: https://issues.apache.org/jira/browse/AMBARI-5296 > Project: Ambari > Issue Type: Task > Components: contrib >Reporter: Anatoly Nikonorov >Assignee: Anatoly Nikonorov > Attachments: AMBARI-5296.patch > > > Implement support for MapReduce2 and YARN services -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-2341) Installation of hadoop fails when /etc/hadoop/conf is present
[
https://issues.apache.org/jira/browse/AMBARI-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako resolved AMBARI-2341.
-
Resolution: Invalid
> Installation of hadoop fails when /etc/hadoop/conf is present
> -
>
> Key: AMBARI-2341
> URL: https://issues.apache.org/jira/browse/AMBARI-2341
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Reporter: Alexander Alten-Lorenz
>Priority: Blocker
>
> Installation fails when the config directories are present.
> Edit to be more precise (as example):
> {code}
> notice: /Stage[2]/Hdp-hive/Anchor[hdp-hive::end]: Dependency
> File[/etc/hive/conf] has failures: true
> warning: /Stage[2]/Hdp-hive/Anchor[hdp-hive::end]: Skipping because of failed
> dependencies
> notice: /Stage[2]/Hdp-hive::Service/File[/tmp/startMetastore.sh]: Dependency
> File[/etc/hive/conf] has failures: true
> warning: /Stage[2]/Hdp-hive::Service/File[/tmp/startMetastore.sh]: Skipping
> because of failed dependencies
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-6484) HBase RegionServer -Xmn must be configurable
[ https://issues.apache.org/jira/browse/AMBARI-6484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-6484: --- Assignee: Azwaw OUSADOU > HBase RegionServer -Xmn must be configurable > > > Key: AMBARI-6484 > URL: https://issues.apache.org/jira/browse/AMBARI-6484 > Project: Ambari > Issue Type: Bug >Affects Versions: 1.7.0 >Reporter: Azwaw OUSADOU >Assignee: Azwaw OUSADOU >Priority: Critical > Labels: features, patch > Fix For: 1.7.0 > > Attachments: AMBARI-6484.diff, AMBARI-6484.diff, > AMBARI-6484-TEST-OUTPUT.txt, MASTER-TEST-OUTPUT.txt, XMN_CONFIGURABLE.diff > > > -Xmn parameter for HBase RegionServer is calculated with hardcoded value. > This patch allows you to configure values used to calculate this parameter > (the maximum value for -Xmn and the ratio between -Xmn and -Xmx). > Without this fix HBase can be crash because of OutOfMemory when you do a YCSB > test for example. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-3412) Ambari-SCOM MSI have to perform rollback in case of interrupted installation
[ https://issues.apache.org/jira/browse/AMBARI-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-3412: --- Assignee: Tom Beerbower > Ambari-SCOM MSI have to perform rollback in case of interrupted installation > > > Key: AMBARI-3412 > URL: https://issues.apache.org/jira/browse/AMBARI-3412 > Project: Ambari > Issue Type: Improvement > Components: contrib >Reporter: Dmitriy Balykin >Assignee: Tom Beerbower > Attachments: 0001-AMBARI-3412.patch, > 0001-Moving-last-changes-to-apache.patch > > > MSI have to perform rollback in case of interrupted installation -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-3383) Installation Ambari-SCOM with incorrect DMBS credentials finishes without warning
[ https://issues.apache.org/jira/browse/AMBARI-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-3383: --- Assignee: Ivan Malamen (was: Ivan Kozlov) > Installation Ambari-SCOM with incorrect DMBS credentials finishes without > warning > - > > Key: AMBARI-3383 > URL: https://issues.apache.org/jira/browse/AMBARI-3383 > Project: Ambari > Issue Type: Bug > Components: contrib > Environment: Windows 2008 R2, MSSQL Server 2008 R2 >Reporter: Dmitriy Balykin >Assignee: Ivan Malamen > Attachments: > 0001-Ambari-SCOM-Installation-with-incorrect-DMBS-credent.patch > > > Installation Ambari-SCOM with incorrect DMBS credentials finishes without > warning. > DB for Ambari metrics and all tables didn't created, so installed Ambari > cannot work properly until it will be reinstalled with correct credentials, > or DB with all tables will created manually. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-3382) Ambari-SCOM MSI doesn't check if HDP available during installation
[ https://issues.apache.org/jira/browse/AMBARI-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-3382: --- Assignee: Ivan Malamen > Ambari-SCOM MSI doesn't check if HDP available during installation > -- > > Key: AMBARI-3382 > URL: https://issues.apache.org/jira/browse/AMBARI-3382 > Project: Ambari > Issue Type: Bug > Components: contrib > Environment: Windows 2008 R2, no HDP available on current node >Reporter: Dmitriy Balykin >Assignee: Ivan Malamen > Attachments: > 0001-Ambari-SCOM-MSI-doesn-t-check-if-HDP-available-durin.patch > > > Installation started using command line, parameter HDP_LAYOUT skipped. > Installation failed with error: > "No Ambari Properties file found, make sure the file $ENV:AMB_LAYOUT > exists and contains the current cluster layout" > This error could be not clear for user. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-3383) Installation Ambari-SCOM with incorrect DMBS credentials finishes without warning
[ https://issues.apache.org/jira/browse/AMBARI-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-3383: --- Assignee: Ivan Kozlov > Installation Ambari-SCOM with incorrect DMBS credentials finishes without > warning > - > > Key: AMBARI-3383 > URL: https://issues.apache.org/jira/browse/AMBARI-3383 > Project: Ambari > Issue Type: Bug > Components: contrib > Environment: Windows 2008 R2, MSSQL Server 2008 R2 >Reporter: Dmitriy Balykin >Assignee: Ivan Kozlov > Attachments: > 0001-Ambari-SCOM-Installation-with-incorrect-DMBS-credent.patch > > > Installation Ambari-SCOM with incorrect DMBS credentials finishes without > warning. > DB for Ambari metrics and all tables didn't created, so installed Ambari > cannot work properly until it will be reinstalled with correct credentials, > or DB with all tables will created manually. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-5792) Change the container-executor.class for Gluster
[ https://issues.apache.org/jira/browse/AMBARI-5792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-5792: --- Assignee: Erin A Boyd > Change the container-executor.class for Gluster > --- > > Key: AMBARI-5792 > URL: https://issues.apache.org/jira/browse/AMBARI-5792 > Project: Ambari > Issue Type: Bug >Affects Versions: 1.5.0, 1.6.0, 1.6.1 >Reporter: Erin A Boyd >Assignee: Erin A Boyd > Fix For: 1.6.0, 1.6.1 > > Attachments: 5792.patch > > > Update > > yarn.nodemanager.container-executor.class > from : > org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor > to: >org.apache.hadoop.yarn.server.nodemanager.GlusterContainerExecutor -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-11046) Update gluster specific fields for oozie and hive
[ https://issues.apache.org/jira/browse/AMBARI-11046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-11046: Assignee: Erin A Boyd > Update gluster specific fields for oozie and hive > - > > Key: AMBARI-11046 > URL: https://issues.apache.org/jira/browse/AMBARI-11046 > Project: Ambari > Issue Type: Bug >Reporter: Erin A Boyd >Assignee: Erin A Boyd > Fix For: 2.1.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-2405) Make non-cloud response objects optional
[ https://issues.apache.org/jira/browse/AMBARI-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-2405: --- Assignee: Tom Beerbower > Make non-cloud response objects optional > > > Key: AMBARI-2405 > URL: https://issues.apache.org/jira/browse/AMBARI-2405 > Project: Ambari > Issue Type: Improvement > Components: documentation >Reporter: Brian Swan >Assignee: Tom Beerbower >Priority: Minor > Attachments: AMBARI-2405.patch > > > Several of the Ambari API response schemas > (https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md) > list several objects as required that don't make sense when Ambari is > deployed in a cloud hosting environment. These objects should be made > optional. Specifically, the following properties should be optional (listed > by API call): > /clusters/:clusterName >* cluster_id >* requests >* configurations > /clusters/:clusterName/hosts/:hostname >* public_host_name >* rack_info >* total_mem > /clusters/:clusterName/hosts/:hostName/host_components/:componentName >* desired_stack_id >* stack_id > /clusters//hosts//host_components/datanode (also tasktracker) >* disk >* cpu >* load >* memory >* network > /clusters/:clusterName >* workflows > /clusters//hosts/ >* host_status >* host_state -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-12977) ambari-metrics fails to package from .deb on ubuntu 14.04
[ https://issues.apache.org/jira/browse/AMBARI-12977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-12977: Assignee: Canan Girgin > ambari-metrics fails to package from .deb on ubuntu 14.04 > - > > Key: AMBARI-12977 > URL: https://issues.apache.org/jira/browse/AMBARI-12977 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Canan Girgin >Assignee: Canan Girgin >Priority: Minor > Fix For: 2.3.0 > > Attachments: AMBARI-12977.patch > > > running "mvn -B clean install package jdeb:jdeb -DskipTests > -Dpython.ver="python >= 2.6" -Preplaceurl" command on ambari directory, shows > failure caused by problems during dep packaging. > if want to package only ambari-metrics and run command on ambari-metrics > directory everything is ok. > [INFO] Ambari Main ... SUCCESS [7.888s] > [INFO] Apache Ambari Project POM . SUCCESS [0.069s] > [INFO] Ambari Web SUCCESS [15.178s] > [INFO] Ambari Views .. SUCCESS [2.366s] > [INFO] Ambari Admin View . SUCCESS [24.536s] > [INFO] ambari-metrics SUCCESS [1.602s] > [INFO] Ambari Metrics Common . SUCCESS [1.215s] > [INFO] Ambari Metrics Hadoop Sink FAILURE [3.265s] > [INFO] Ambari Metrics Flume Sink . SKIPPED > [INFO] Ambari Metrics Kafka Sink . SKIPPED > [INFO] Ambari Metrics Storm Sink . SKIPPED > [INFO] Ambari Metrics Collector .. SKIPPED > [INFO] Ambari Metrics Monitor SKIPPED > [INFO] Ambari Metrics Assembly ... SKIPPED > [INFO] Ambari Server . SKIPPED > [INFO] Ambari Agent .. SKIPPED > [INFO] Ambari Client . SKIPPED > [INFO] Ambari Python Client .. SKIPPED > [INFO] Ambari Groovy Client .. SKIPPED > [INFO] Ambari Shell .. SKIPPED > [INFO] Ambari Python Shell ... SKIPPED > [INFO] Ambari Groovy Shell ... SKIPPED > [ERROR] Failed to create debian package > /home/a/repo/ambariRoot/ambari-metrics/ambari-metrics-hadoop-sink/target/ambari-metrics-hadoop-sink_2.1.0~SNAPSHOT_all.deb > org.vafer.jdeb.PackagingException: > "/home/a/repo/ambariRoot/ambari-metrics/ambari-metrics-hadoop-sink/src/main/package/deb/control" > is not a valid 'control' directory) > at org.vafer.jdeb.maven.DebMaker.makeDeb(DebMaker.java:186) > * > [ERROR] Failed to create debian package > /home/a/repo/ambari/ambari-metrics/ambari-metrics-flume-sink/target/ambari-metrics-flume-sink_2.1.0~SNAPSHOT_all.deb > org.vafer.jdeb.PackagingException: > "/home/a/repo/ambari/ambari-metrics/ambari-metrics-flume-sink/src/main/package/deb/control" > is not a valid 'control' directory) > at org.vafer.jdeb.maven.DebMaker.makeDeb(DebMaker.java:186) > * > [ERROR] Failed to create debian package > /home/a/repo/ambari/ambari-metrics/ambari-metrics-flume-sink/target/ambari-metrics-flume-sink_2.1.0~SNAPSHOT_all.deb > org.vafer.jdeb.PackagingException: > "/home/a/repo/ambari/ambari-metrics/ambari-metrics-flume-sink/src/main/package/deb/control" > is not a valid 'control' directory) > at org.vafer.jdeb.maven.DebMaker.makeDeb(DebMaker.java:186) > * > [ERROR] Failed to create debian package > /home/a/repo/ambari/ambari-metrics/ambari-metrics-kafka-sink/target/ambari-metrics-kafka-sink_2.1.0~SNAPSHOT_all.deb > org.vafer.jdeb.PackagingException: > "/home/a/repo/ambari/ambari-metrics/ambari-metrics-kafka-sink/src/main/package/deb/control" > is not a valid 'control' directory) > at org.vafer.jdeb.maven.DebMaker.makeDeb(DebMaker.java:186) > * > [ERROR] Failed to create debian package > /home/a/repo/ambari/ambari-metrics/ambari-metrics-timelineservice/target/ambari-metrics-timelineservice_2.1.0~SNAPSHOT_all.deb > org.vafer.jdeb.PackagingException: > "/home/a/repo/ambari/ambari-metrics/ambari-metrics-timelineservice/src/main/package/deb/control" > is not a valid 'control' directory) > at org.vafer.jdeb.maven.DebMaker.makeDeb(DebMaker.java:186) > * > [ERROR] Failed to create debian package > /home/a/repo/ambari/ambari-metrics/ambari-metrics-host-monitoring/target/ambari-metrics-host-monitoring_2.1.0~SNAPSHOT_all.deb > org.vafer.jdeb.PackagingException: > "/home/a/repo/ambari/ambari-metrics/ambari-metrics-host-monitoring/src/main/package/deb/control" > is not a valid
[jira] [Assigned] (AMBARI-4631) unittest PropertyFile
[ https://issues.apache.org/jira/browse/AMBARI-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-4631: --- Assignee: Iryna Kuzmenko > unittest PropertyFile > - > > Key: AMBARI-4631 > URL: https://issues.apache.org/jira/browse/AMBARI-4631 > Project: Ambari > Issue Type: Bug >Reporter: Iryna Kuzmenko >Assignee: Iryna Kuzmenko > Fix For: 1.5.0 > > Attachments: AMBARI-4631.patch > > > Files to test are in > ambari/agent/src/main/python/resource_management/libraries/providers and > ../resources > Tests are here with some examples of other resources tested: > /ambari-agent/src/test/python/resource_management > Be sure to have unnitest for every attribute of this resource. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-5631) Ambari SCOM .msi support for HDP2.1
[ https://issues.apache.org/jira/browse/AMBARI-5631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-5631: --- Assignee: Ivan Malamen > Ambari SCOM .msi support for HDP2.1 > --- > > Key: AMBARI-5631 > URL: https://issues.apache.org/jira/browse/AMBARI-5631 > Project: Ambari > Issue Type: Bug > Components: contrib >Reporter: Ivan Malamen >Assignee: Ivan Malamen >Priority: Blocker > Attachments: > 0001-AMBARI-5631-Ambari-SCOM-.msi-support-for-HDP2.1.patch > > > Comparing HDP2.0.x and HDP2.1.x, some components changed their names. As a > result, corresponding config files that should be edited on .msi installation > also changed. > For example, there are _historyserver_ and _jobhistoryserver_ services in > HDP2.1. > _historyserver_ is not more the same than in HDP2.0.x, it refers to Apache > Hadoop YARN TimelineServer, is disabled by default and shouldn't be affected > by .msi. > _jobhistoryserver_ is required, its config file > _%HADOOP_HOME%\bin\jobhistoryserver.xml_ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-5762) Remove MP msi from package
[ https://issues.apache.org/jira/browse/AMBARI-5762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-5762: --- Assignee: Ivan Malamen > Remove MP msi from package > -- > > Key: AMBARI-5762 > URL: https://issues.apache.org/jira/browse/AMBARI-5762 > Project: Ambari > Issue Type: Bug > Components: contrib >Reporter: Ivan Malamen >Assignee: Ivan Malamen > Attachments: AMBARI-5762.patch > > > Remove MSI building and copying from build scripts -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-5579) Fix build for Ambari-SCOM 2.0
[ https://issues.apache.org/jira/browse/AMBARI-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-5579: --- Assignee: Ivan Malamen > Fix build for Ambari-SCOM 2.0 > - > > Key: AMBARI-5579 > URL: https://issues.apache.org/jira/browse/AMBARI-5579 > Project: Ambari > Issue Type: Bug > Components: contrib >Reporter: Ivan Malamen >Assignee: Ivan Malamen >Priority: Blocker > Attachments: 0001-AMBARI-5579-Fix-build-for-Ambari-SCOM-2.0.patch > > > Need to fix failing build for Ambari-SCOM 2.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-5601) Ambari-SCOM build is failing
[ https://issues.apache.org/jira/browse/AMBARI-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-5601: --- Assignee: Ivan Malamen > Ambari-SCOM build is failing > > > Key: AMBARI-5601 > URL: https://issues.apache.org/jira/browse/AMBARI-5601 > Project: Ambari > Issue Type: Bug > Components: contrib >Reporter: Ivan Malamen >Assignee: Ivan Malamen >Priority: Blocker > > CoreCompile: > C:\Windows\Microsoft.NET\Framework\v4.0.30319\Csc.exe /noconfig /unsafe+ > /nowarn:1701,1702 /nostdlib+ /errorreport:prompt /warn:4 /define:TRACE > /highentropyva- /reference:"C:\Program Files (x86)\Reference > Assemblies\Microsoft\Framework\.NETFramework\v4.0\mscorlib.dll" > /reference:"C:\Program Files (x86)\Reference > Assemblies\Microsoft\Framework\.NETFramework\v4.0\System.Core.dll" > /reference:"C:\Program Files (x86)\Reference > Assemblies\Microsoft\Framework\.NETFramework\v4.0\System.Data.dll" > /reference:"C:\Program Files (x86)\Reference > Assemblies\Microsoft\Framework\.NETFramework\v4.0\System.dll" > /reference:"C:\Program Files (x86)\Reference > Assemblies\Microsoft\Framework\.NETFramework\v4.0\System.Management.dll" > /reference:"C:\Program Files (x86)\Reference > Assemblies\Microsoft\Framework\.NETFramework\v4.0\System.ServiceProcess.dll" > /reference:"C:\Program Files (x86)\Reference > Assemblies\Microsoft\Framework\.NETFramework\v4.0\System.Xml.dll" > /debug:pdbonly /filealign:512 /optimize+ /out:obj\Release\ServiceHost.exe > /target:exe /utf8output DynamicProxy.cs Main.cs Properties\AssemblyInfo.cs > Wmi.cs WmiSchema.cs > "C:\Users\jenkins\AppData\Local\Temp\.NETFramework,Version=v4.0.AssemblyAttributes.cs" > WmiSchema.cs(77,1): error CS0116: A namespace cannot directly contain members > such as fields or methods > [d:\w\ambari-scom\ambari\contrib\ambari-scom\msi\src\ServiceHost\ServiceHost.csproj] > Done Building Project > "d:\w\ambari-scom\ambari\contrib\ambari-scom\msi\src\ServiceHost\ServiceHost.csproj" > (clean;build target(s)) -- FAILED. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-5562) Ambari SCOM server should run as windows service
[ https://issues.apache.org/jira/browse/AMBARI-5562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-5562: --- Assignee: Ivan Malamen > Ambari SCOM server should run as windows service > > > Key: AMBARI-5562 > URL: https://issues.apache.org/jira/browse/AMBARI-5562 > Project: Ambari > Issue Type: Improvement > Components: contrib >Reporter: Ivan Malamen >Assignee: Ivan Malamen > Attachments: > 0001-AMBARI-5562-Ambari-SCOM-server-should-run-as-windows.patch > > > 1.We should use service name the same with name which displayed after install > of msi in Control Panel\All Control Panel Items\Programs and Features > 2.use manual start type like hadoop services > 3.think we should use OS user -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-5630) Ambari SCOM .msi should detect HDP version dynamically
[ https://issues.apache.org/jira/browse/AMBARI-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-5630: --- Assignee: Ivan Malamen > Ambari SCOM .msi should detect HDP version dynamically > -- > > Key: AMBARI-5630 > URL: https://issues.apache.org/jira/browse/AMBARI-5630 > Project: Ambari > Issue Type: Bug > Components: contrib >Reporter: Ivan Malamen >Assignee: Ivan Malamen >Priority: Blocker > Attachments: > 0001-AMBARI-5630-Ambari-SCOM-.msi-should-detect-HDP-versi.patch, > Ambari_GUI.JPG, ambariproperties.txt > > > HDP version is defined by _scom.version.id_ property in > _%AMB_DATA_DIR%\ambari-scom-server-conf\conf\ambari.properties_ file. This > version is then displayed in REST API by > _http://:8080/api/v1/clusters/_ request. > Currently it is hardcoded in .msi. We should avoid having wrong HDP version > in conf file and in API. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-5675) RECREATE_DB option is ignored by command-line .msi installation
[ https://issues.apache.org/jira/browse/AMBARI-5675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-5675: --- Assignee: Ivan Malamen > RECREATE_DB option is ignored by command-line .msi installation > --- > > Key: AMBARI-5675 > URL: https://issues.apache.org/jira/browse/AMBARI-5675 > Project: Ambari > Issue Type: Bug >Reporter: Ivan Malamen >Assignee: Ivan Malamen >Priority: Critical > Attachments: > 0001-AMBARI-5675-RECREATE_DB-option-is-ignored-by-command.patch > > > Hadoop-Metrics-SQLServer-CREATE.ddl isn't executed if .msi is installing from > command line via msiexec with _RECREATE_DB=yes_ or without _RECREATE_DB_ at > all (yes by default). > By the way, it works correctly via GUI installation both with RECREATE_DB=yes > and no. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-5550) Create MSI for Ambari-SCOM 2.0.0.0
[ https://issues.apache.org/jira/browse/AMBARI-5550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-5550: --- Assignee: Ivan Malamen > Create MSI for Ambari-SCOM 2.0.0.0 > -- > > Key: AMBARI-5550 > URL: https://issues.apache.org/jira/browse/AMBARI-5550 > Project: Ambari > Issue Type: New Feature > Components: contrib >Reporter: Ivan Malamen >Assignee: Ivan Malamen >Priority: Blocker > Attachments: 0001-AMBARI-5550-Create-MSI-for-Ambari-SCOM-2.0.0.0.patch > > > The MSI should support fresh install as well as upgrade. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-7753) DataNode decommision error in secured cluster
[
https://issues.apache.org/jira/browse/AMBARI-7753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako reassigned AMBARI-7753:
---
Assignee: jaehoon ko
> DataNode decommision error in secured cluster
> -
>
> Key: AMBARI-7753
> URL: https://issues.apache.org/jira/browse/AMBARI-7753
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
>Affects Versions: 1.6.1
> Environment: Ambari-1.6.1 with HDP-2.1.5
>Reporter: jaehoon ko
>Assignee: jaehoon ko
> Labels: patch
> Fix For: 2.0.0
>
> Attachments: AMBARI-7753.patch
>
>
> Decommissioning a DataNode from a secured cluster returns errors with the
> following messages
> {code}
> STDERR:
> 2014-10-13 10:37:31,896 - Error while executing command 'decommission':
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 111, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/namenode.py",
> line 66, in decommission
> namenode(action="decommission")
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py",
> line 70, in namenode
> decommission()
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py",
> line 145, in
> decommission
> user=hdfs_user
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 148, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 149, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 115, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 239, in action_run
> raise ex
> Fail: Execution of '/usr/bin/kinit -kt
> /etc/security/keytabs/dn.service.keytab dn/master-
> 6.amber.gbcl@amber.gbcluster.net;' returned 1. kinit: Client not found in
> Kerberos database while getting initial
> credentials
> {code}
> {code}
> STDOUT:
> 2014-10-13 10:37:31,793 - File['/etc/hadoop/conf/dfs.exclude'] {'owner':
> 'hdfs', 'content': Template
> ('exclude_hosts_list.j2'), 'group': 'hadoop'}
> 2014-10-13 10:37:31,796 - Writing File['/etc/hadoop/conf/dfs.exclude']
> because contents don't match
> 2014-10-13 10:37:31,797 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/dn.service.keytab dn/master-
> 6.amber.gbcl@amber.gbcluster.net;'] {'user': 'hdfs'}
> 2014-10-13 10:37:31,896 - Error while executing command 'decommission':
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 111, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/namenode.py",
> line 66, in decommission
> namenode(action="decommission")
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py",
> line 70, in namenode
> decommission()
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py",
> line 145, in
> decommission
> user=hdfs_user
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 148, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 149, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 115, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 239, in action_run
> raise ex
> Fail: Execution of '/usr/bin/kinit -kt
> /etc/security/keytabs/dn.service.keytab dn/master-
> 6.amber.gbcl@amber.gbcluster.net;' returned 1. kinit: Client not found in
> Kerberos database while getting initial
> credentials
> {code}
> The reason is that Ambar-agent uses DataNode principal to perform HDFS
> refresh, which should be done as NameNode. This error can be solved by
> letting Ambari-agent uses NameNode kerberos principal and keytab. Note that
> [AMBARI-5729|https://issues.apache.org/jira/browse/AMBARI-5729] solves
> similar issue for NodeManager.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-1596) Ability for Ambari Agents to run as non-root users
[ https://issues.apache.org/jira/browse/AMBARI-1596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-1596: --- Assignee: Dmitry Lysnichenko > Ability for Ambari Agents to run as non-root users > -- > > Key: AMBARI-1596 > URL: https://issues.apache.org/jira/browse/AMBARI-1596 > Project: Ambari > Issue Type: Improvement >Affects Versions: 1.2.2 >Reporter: Jeff Sposetti >Assignee: Dmitry Lysnichenko > Fix For: 2.0.0 > > > Give users the ability to have ambari-agent use a sudo account. > ambari-server non-root is supported: > https://issues.apache.org/jira/browse/AMBARI-2370 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-9608) When adding the Oozie service to a kerberized cluster OOZIE_SERVER doesn't start
[
https://issues.apache.org/jira/browse/AMBARI-9608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako reassigned AMBARI-9608:
---
Assignee: Robert Levas
> When adding the Oozie service to a kerberized cluster OOZIE_SERVER doesn't
> start
>
>
> Key: AMBARI-9608
> URL: https://issues.apache.org/jira/browse/AMBARI-9608
> Project: Ambari
> Issue Type: Bug
> Components: security
>Affects Versions: 2.0.0
>Reporter: John Speidel
>Assignee: Robert Levas
>Priority: Critical
> Labels: keberos
> Fix For: 2.0.0
>
>
> Oozie server fails to start with the error: "Fail: Configuration parameter
> 'oozie.service.HadoopAccessorService.kerberos.principal' was not found in
> configurations dictionary!"
> Steps to reproduce:
> Create a non-kerberized cluster
> I used the following blueprint
> {code}
> {
> "host_groups" : [
> {
> "name" : "host_group_1",
> "components" : [
> {
> "name" : "NODEMANAGER"
> },
> {
> "name" : "NAMENODE"
> },
> {
> "name" : "HISTORYSERVER"
> },
> {
> "name" : "ZOOKEEPER_SERVER"
> },
> {
> "name" : "SECONDARY_NAMENODE"
> },
> {
> "name" : "RESOURCEMANAGER"
> },
> {
> "name" : "APP_TIMELINE_SERVER"
> },
> {
> "name" : "DATANODE"
> },
> {
> "name" : "YARN_CLIENT"
> },
> {
> "name" : "ZOOKEEPER_CLIENT"
> },
> {
> "name" : "MAPREDUCE2_CLIENT"
> }
> ],
> "cardinality" : "1"
> }
> ],
> "Blueprints" : {
> "stack_name" : "HDP",
> "stack_version" : "2.2"
> }
> }
> {code}
> - manually unzip UnlimitedJCEPolicy
> - manually install MIT KDC
> - Using UI, kerberize the existing cluster
> - Using the UI, add the Oozie service
> OOZIE_SERVER failed to start and the above noted exception was from the log
> that is exposed via the UI for the oozie start operation.
> According to Robert Levas this property is in the kerberos descriptor it
> should be set.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-1533) Add Nagios check for ambari-agent process for each host in the cluster
[
https://issues.apache.org/jira/browse/AMBARI-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako reassigned AMBARI-1533:
---
Assignee: Sumit Mohanty
> Add Nagios check for ambari-agent process for each host in the cluster
> --
>
> Key: AMBARI-1533
> URL: https://issues.apache.org/jira/browse/AMBARI-1533
> Project: Ambari
> Issue Type: Improvement
>Reporter: Jeff Sposetti
>Assignee: Sumit Mohanty
> Attachments: AMBARI-1533.patch
>
>
> Each host in the cluster runs ambari-agent.
> There should be a Nagios alert to that watches the ambari-agent process.
> Since the system does not allow direct communication to an ambari-agent, this
> check should either a) check the process running on the host or b) ping the
> Ambari Server REST API to confirm agent is still heartbeat'ing.
> This alert should be shown with each Hosts > {host} in Ambari Web.
> Service Description: Ambari Agent (ambari-agent) process down
> Service Group: AMBARI
> Check / Retry Interval: 0.25
> Note: need to add new service group AMBARI for Nagios
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-13494) Ambari generate invalid configuration after namenode move with HA enabled
[ https://issues.apache.org/jira/browse/AMBARI-13494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-13494: Assignee: Josh Elser > Ambari generate invalid configuration after namenode move with HA enabled > - > > Key: AMBARI-13494 > URL: https://issues.apache.org/jira/browse/AMBARI-13494 > Project: Ambari > Issue Type: Bug > Components: stacks >Reporter: Josh Elser >Assignee: Josh Elser >Priority: Critical > Fix For: 2.2.0 > > Attachments: AMBARI-13494_branch-2.1.patch > > > Noticed that incorrect Accumulo configuration was generated after HA was > enabled, and then a namenode was moved. > Manually verified that, with the patch, moving a namenode with and without HA > enabled works as expected. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-5686) iptables host check warning shows on centos 5.9 even if iptables are stopped
[ https://issues.apache.org/jira/browse/AMBARI-5686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-5686: --- Assignee: Jonathan Hurley > iptables host check warning shows on centos 5.9 even if iptables are stopped > > > Key: AMBARI-5686 > URL: https://issues.apache.org/jira/browse/AMBARI-5686 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 1.6.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley > Fix For: 1.6.1 > > > While adding a host "am5-unsec-m2-4" Ambari shows firewall error even if the > firewall is stopped on that host > -- > [root@am5-unsec-m2-1 tmp]# rpm -qa | grep ambari > ambari-server-1.6.0-17 > ambari-agent-1.6.0-17 > ambari-log4j-1.6.0.17-1 > [root@am5-unsec-m2-1 tmp]# cat /etc/redhat-release > CentOS release 5.9 (Final) > -- > [root@am5-unsec-m2-4 ~]# service iptables status > Firewall is stopped. > -- -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-13889) Upgrade from 2.1.2 to 2.1.3 fails with Security enabled due to missing Accumulo configuration
[ https://issues.apache.org/jira/browse/AMBARI-13889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-13889: Assignee: Josh Elser > Upgrade from 2.1.2 to 2.1.3 fails with Security enabled due to missing > Accumulo configuration > - > > Key: AMBARI-13889 > URL: https://issues.apache.org/jira/browse/AMBARI-13889 > Project: Ambari > Issue Type: Bug > Components: ambari-upgrade >Reporter: Josh Elser >Assignee: Josh Elser >Priority: Critical > Fix For: 2.2.0 > > Attachments: AMBARI-13889.001.patch, AMBARI-13889.002.patch, > AMBARI-13889.002.trunk.patch > > > AMBARI-13295 fixed an issue where, with custom usernames/principals, the > Accumulo client was using the default principal to try to authenticate with > the Accumulo services with Kerberos enabled. This failed as the client had > incorrect information to complete the authentication handshake. > This issue still exists in 2.1.2, however, which causes an upgrade from 2.1.2 > to 2.1.3-SNAPSHOT to fail because the incorrect configuration is never > corrected. > [~rlevas] has kindly pointed that the UpgradeCatalog needs to be changed to > ensure that the configuration is updated in the upgrade path out of 2.1.2. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-13460) Accumulo start/stop checks fail when running as non-root user
[
https://issues.apache.org/jira/browse/AMBARI-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako reassigned AMBARI-13460:
Assignee: Josh Elser
> Accumulo start/stop checks fail when running as non-root user
> -
>
> Key: AMBARI-13460
> URL: https://issues.apache.org/jira/browse/AMBARI-13460
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Reporter: Josh Elser
>Assignee: Josh Elser
> Attachments: AMBARI-13460.001.patch
>
>
> Found that when installing Accumulo when Ambari isn't running as root, the
> not_if check which checks the pidfile for the give Accumulo service was
> incorrectly preventing the service from being started. It appeared that
> Ambari thought the service was already running even though the pid in the
> pidfile definitely didn't exist.
> [~billie.rinaldi] correct guessed that it was due to Ambari running as a
> different user (who didn't have permissions to read the pidfile). This stems
> from an incorrect {{not_if}} statement in the stack which caused the commands
> to check the pidfile to not be run as the Accumulo user.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-8636) Packages ambari-agent and ambari-server cannot be authenticated using ubuntu 12.04
[ https://issues.apache.org/jira/browse/AMBARI-8636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako resolved AMBARI-8636. - Resolution: Not A Problem > Packages ambari-agent and ambari-server cannot be authenticated using ubuntu > 12.04 > -- > > Key: AMBARI-8636 > URL: https://issues.apache.org/jira/browse/AMBARI-8636 > Project: Ambari > Issue Type: Bug > Components: infra >Affects Versions: 1.7.0 > Environment: ubuntu 12.04 >Reporter: Julien Pellet > > After installing the apt source according to the doc: > wget -nv http://public-repo- > 1.hortonworks.com/HDP/ubuntu12/2.x/GA/2.2.0.0/hdp.list -O > /etc/apt/sources.list.d/HDP.list > After adding the key : > apt-key adv --recv-keys --keyserver keyserver.ubuntu.com B9733A7A07513CAD > I still have a warning, preventing to install it with a configuration manager > : > root@chef:~# apt-get install ambari-agent > Reading package lists... Done > Building dependency tree > Reading state information... Done > The following NEW packages will be installed: > ambari-agent > 0 upgraded, 1 newly installed, 0 to remove and 131 not upgraded. > Need to get 0 B/2,288 kB of archives. > After this operation, 7,576 kB of additional disk space will be used. > WARNING: The following packages cannot be authenticated! > ambari-agent > Install these packages without verification [y/N]? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (AMBARI-8636) Packages ambari-agent and ambari-server cannot be authenticated using ubuntu 12.04
[ https://issues.apache.org/jira/browse/AMBARI-8636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reopened AMBARI-8636: - > Packages ambari-agent and ambari-server cannot be authenticated using ubuntu > 12.04 > -- > > Key: AMBARI-8636 > URL: https://issues.apache.org/jira/browse/AMBARI-8636 > Project: Ambari > Issue Type: Bug > Components: infra >Affects Versions: 1.7.0 > Environment: ubuntu 12.04 >Reporter: Julien Pellet > > After installing the apt source according to the doc: > wget -nv http://public-repo- > 1.hortonworks.com/HDP/ubuntu12/2.x/GA/2.2.0.0/hdp.list -O > /etc/apt/sources.list.d/HDP.list > After adding the key : > apt-key adv --recv-keys --keyserver keyserver.ubuntu.com B9733A7A07513CAD > I still have a warning, preventing to install it with a configuration manager > : > root@chef:~# apt-get install ambari-agent > Reading package lists... Done > Building dependency tree > Reading state information... Done > The following NEW packages will be installed: > ambari-agent > 0 upgraded, 1 newly installed, 0 to remove and 131 not upgraded. > Need to get 0 B/2,288 kB of archives. > After this operation, 7,576 kB of additional disk space will be used. > WARNING: The following packages cannot be authenticated! > ambari-agent > Install these packages without verification [y/N]? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-13271) Error: str() function only 1 takes parameter
[
https://issues.apache.org/jira/browse/AMBARI-13271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako reassigned AMBARI-13271:
Assignee: Kevin Vasko
> Error: str() function only 1 takes parameter
>
>
> Key: AMBARI-13271
> URL: https://issues.apache.org/jira/browse/AMBARI-13271
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.1.1
> Environment: CentOS 7.0
>Reporter: Kevin Vasko
>Assignee: Kevin Vasko
>Priority: Minor
> Fix For: 2.4.0
>
> Attachments: AMBARI-13271.2.patch, patch.diff
>
>
> In the file
> /usr/lib/python2.6/site-packages/ambari_agent/HostCleanup.py
> and in the backup_file function I was getting an error staying Error: str()
> only takes 1 parameter but 2 were passed type error.
> # Copy file and save with file.# (timestamp)
> def backup_file(filePath):
> if filePath is not None and os.path.exists(filePath):
> timestamp = datetime.datetime.now()
> format = '%Y%m%d%H%M%S'
> try:
> shutil.copyfile(filePath, filePath + "." + timestamp.strftime(format))
> except (Exception), e:
> logger.warn('Could not backup file "%s": %s' % (str(filePath, e)))
> return 0
> I do believe the exception handling line is incorrect and should be change
> from:
> logger.warn('Could not backup file "%s": %s' % (str(filePath, e)))
> to:
> logger.warn('Could not backup file "%s": %s' % (str(filePath), e))
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-13493) TEZ view throws NPE when RM HA is enabled via Blueprint deploy
[
https://issues.apache.org/jira/browse/AMBARI-13493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako reassigned AMBARI-13493:
Assignee: DIPAYAN BHOWMICK
> TEZ view throws NPE when RM HA is enabled via Blueprint deploy
> --
>
> Key: AMBARI-13493
> URL: https://issues.apache.org/jira/browse/AMBARI-13493
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.1.2
> Environment: sles11sp3
> ambari-2.1.3 (bad8603c8ad543eb0688f73bd3a6fcc159963efa)
> hdp-2.3.4.0
>Reporter: Michael Harp
>Assignee: DIPAYAN BHOWMICK
>Priority: Critical
> Fix For: 2.2.0
>
>
> Related to AMBARI-12970 which changed behavior for Tez view and RM HA.
> Steps to reproduce;
> 1. Deploy with blueprint with RM HA enabled,
> https://github.com/hortonworks/td-ape-tigereye/blob/master/hadoopBuilder/src/config/ambari/3-master-HDP-2.3.json
> 2. Select TEZ view
> {code}
> 20 Oct 2015 13:00:01,831 WARN [qtp-client-27] ServletHandler:563 -
> /api/v1/views/TEZ/versions/0.7.0.2.3.2.0-132/instances/TEZ_CLUSTER_INSTANCE/resources/status
> java.lang.NullPointerException
> at
> org.apache.ambari.view.utils.ambari.Services.getRMHAUrls(Services.java:124)
> at
> org.apache.ambari.view.utils.ambari.Services.getRMUrlFromClusterConfig(Services.java:94)
> at
> org.apache.ambari.view.utils.ambari.Services.getRMUrl(Services.java:74)
> at
> org.apache.ambari.view.tez.ViewControllerImpl.getViewStatus(ViewControllerImpl.java:60)
> at
> org.apache.ambari.view.tez.rest.ViewStatusResource.getViewStatus(ViewStatusResource.java:44)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-13361) HBase crashes after enabling Phoenix with error - Class PhoenixRpcSchedulerFactory not found
[
https://issues.apache.org/jira/browse/AMBARI-13361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako reassigned AMBARI-13361:
Assignee: Andrew Onischuk
> HBase crashes after enabling Phoenix with error - Class
> PhoenixRpcSchedulerFactory not found
>
>
> Key: AMBARI-13361
> URL: https://issues.apache.org/jira/browse/AMBARI-13361
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.1.2
>Reporter: Michael Harp
>Assignee: Andrew Onischuk
> Fix For: 2.2.0
>
>
> Enabling phoenix and accepting all default configuration recommendations
> causes hbase to crash since phoenix rpm is not installed during hbase-client
> restart. This is a regression from 2.1.0 which included phoenix rpm during
> hbase install.
> Steps to repo;
> 1. Install HBase (But not phoenix query server)
> 2. Enable phoenix, accept all defaults.
> 3. Restart all Affected
> 4. Wait a minute or two for hbase master and regionserver to crash.
> Once hbase is down starting the service does install phoenix rpm which
> restores functionality.
> {code}
> 2015-09-24 17:38:09,098 ERROR [main] master.HMasterCommandLine: Master exiting
> java.lang.RuntimeException: Failed construction of Master: class
> org.apache.hadoop.hbase.master.HMaster
> at
> org.apache.hadoop.hbase.master.HMaster.constructMaster(HMaster.java:2290)
> at
> org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:233)
> at
> org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:139)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at
> org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:126)
> at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:2304)
> Caused by: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.hbase.ipc.PhoenixRpcSchedulerFactory not found
> at
> org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2101)
> at
> org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2193)
> at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.(RSRpcServices.java:829)
> at
> org.apache.hadoop.hbase.master.MasterRpcServices.(MasterRpcServices.java:210)
> at
> org.apache.hadoop.hbase.master.HMaster.createRpcServices(HMaster.java:532)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.(HRegionServer.java:532)
> at org.apache.hadoop.hbase.master.HMaster.(HMaster.java:364)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:408)
> at
> org.apache.hadoop.hbase.master.HMaster.constructMaster(HMaster.java:2285)
> ... 5 more
> ~{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-1684) Add ability to change port numbers for mapred job submission and mapred web ui ports
[ https://issues.apache.org/jira/browse/AMBARI-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-1684: --- Assignee: Jaimin Jetly > Add ability to change port numbers for mapred job submission and mapred web > ui ports > > > Key: AMBARI-1684 > URL: https://issues.apache.org/jira/browse/AMBARI-1684 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 1.2.2 >Reporter: Pramod Thangali >Assignee: Jaimin Jetly > Fix For: 1.5.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-20853) Service Advisor - Allow Service to define its Advisor Type as Python or Java
[ https://issues.apache.org/jira/browse/AMBARI-20853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047052#comment-16047052 ] Hudson commented on AMBARI-20853: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7616 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7616/]) AMBARI-20853. Service Advisor - Allow Service to define its Advisor Type (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f1ca09c03a2fe316129aa5623c675b62d3177112]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/stackadvisor/commands/ConfigurationValidationCommand.java * (add) serviceadvisor/src/main/java/org/apache/ambari/serviceadvisor/ServiceAdvisorCommandType.java * (edit) ambari-client/groovy-client/pom.xml * (edit) ambari-logsearch/ambari-logsearch-config-zookeeper/pom.xml * (edit) ambari-server/pom.xml * (edit) contrib/views/wfmanager/pom.xml * (edit) ambari-funtest/pom.xml * (edit) ambari-server/src/test/java/org/apache/ambari/server/stack/ServiceModuleTest.java * (edit) ambari-server/checkstyle.xml * (edit) contrib/views/hive-next/pom.xml * (edit) ambari-views/examples/weather-view/pom.xml * (edit) ambari-infra/ambari-infra-solr-client/pom.xml * (edit) ambari-server/src/test/java/org/apache/ambari/server/api/services/stackadvisor/StackAdvisorHelperTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/ServiceInfo.java * (edit) ambari-metrics/ambari-metrics-timelineservice/pom.xml * (edit) ambari-project/pom.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/stackadvisor/commands/ConfigurationDependenciesRecommendationCommand.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/stackadvisor/commands/ComponentLayoutRecommendationCommand.java * (edit) pom.xml * (edit) ambari-logsearch/ambari-logsearch-logfeeder/pom.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/stackadvisor/commands/StackAdvisorCommand.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/stackadvisor/StackAdvisorRunner.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/stackadvisor/commands/ConfigurationRecommendationCommand.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/api/services/stackadvisor/StackAdvisorRunnerTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/api/services/stackadvisor/commands/StackAdvisorCommandTest.java * (add) serviceadvisor/src/main/java/org/apache/ambari/serviceadvisor/ServiceAdvisor.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/stackadvisor/commands/ComponentLayoutValidationCommand.java * (edit) contrib/views/hawq/pom.xml * (edit) contrib/views/tez/pom.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/ServiceModule.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/api/services/stackadvisor/commands/ConfigurationRecommendationCommandTest.java * (add) serviceadvisor/pom.xml * (edit) contrib/views/hive20/pom.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/stackadvisor/StackAdvisorHelper.java * (edit) ambari-logsearch/ambari-logsearch-it/pom.xml * (edit) ambari-logsearch/ambari-logsearch-config-api/pom.xml * (edit) contrib/views/pig/pom.xml > Service Advisor - Allow Service to define its Advisor Type as Python or Java > > > Key: AMBARI-20853 > URL: https://issues.apache.org/jira/browse/AMBARI-20853 > Project: Ambari > Issue Type: Story > Components: service-advisor >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: trunk > > Attachments: AMBARI-20853.trunk.patch > > > See Epic AMBARI-20852 > First step is to allow a Service's metainfo.xml file to define what type of > Service Advisor it uses, Python or Java. > For now, continue to call Python for all services since all services are not > specifying which type to use (so defaults to Python) > If set to Java, will eventually call a class to invoke the existing Service > Advisor in Python as a way to ensure compatibility. > If set to Python, continue to call the current script. > In both cases, we will continue to generate the services.json file. > Today, we call Stack Advisor on all services even if only one service is > modified, so it's ok to hardcode a service name until the UI is able to > provide that granularity. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-14717) Hive View: Hisotry filter: UI issues related to date range overlap and duration values
[ https://issues.apache.org/jira/browse/AMBARI-14717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-14717: Assignee: Rajendra Patil > Hive View: Hisotry filter: UI issues related to date range overlap and > duration values > -- > > Key: AMBARI-14717 > URL: https://issues.apache.org/jira/browse/AMBARI-14717 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.2.0 >Reporter: Rajendra Patil >Assignee: Rajendra Patil > Labels: hive-view > Fix For: 2.2.2 > > Attachments: AMBARI-14717_branch-2.2.patch, HistoryTabOverlap.png, > HistoryTabTimeslider.png > > > Hive View: Issues from User interface perspective > 1) History Tab On resizing windows Tab From and ToDate gets overlapped one > above the other. > attached screen shot (HistoryTabOverlap) > 2) History Tab Time(exec time) slider bar shows 0sec on both ends screenshot > attached(HistoryTabTimeslider) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-13306) HBase RegionServers are not being filtered properly in UI
[ https://issues.apache.org/jira/browse/AMBARI-13306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-13306: Assignee: Andrii Tkach > HBase RegionServers are not being filtered properly in UI > - > > Key: AMBARI-13306 > URL: https://issues.apache.org/jira/browse/AMBARI-13306 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.1.2 > Environment: CentOS 6.7 HDP 2.3 >Reporter: Parthiban Gunasekaran >Assignee: Andrii Tkach > > If we click the RegionServer link in HBase service page or filter by > components in host page for Regionservers, wrong hosts are being selected > which doesn't have regionservers -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-13648) Fix incorrect SPARK_CONF_DIR in Ambari stack definition
[
https://issues.apache.org/jira/browse/AMBARI-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako reassigned AMBARI-13648:
Assignee: Saisai Shao
> Fix incorrect SPARK_CONF_DIR in Ambari stack definition
> ---
>
> Key: AMBARI-13648
> URL: https://issues.apache.org/jira/browse/AMBARI-13648
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: trunk
>Reporter: Saisai Shao
>Assignee: Saisai Shao
> Fix For: 2.2.0
>
> Attachments: AMBARI-13648.patch
>
>
> What AMBARI-13584 did is not correct:
> {code}
> export SPARK_CONF_DIR=${SPARK_CONF_DIR:-{{spark_home}}}/conf
> {code}
> Which will lead to failure start up of history server, we have to change to:
> {code}
> export SPARK_CONF_DIR=${SPARK_CONF_DIR:-{{spark_home}}/conf}
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-5616) Ambari Views: Pig view
[ https://issues.apache.org/jira/browse/AMBARI-5616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-5616: --- Assignee: Roman Rader > Ambari Views: Pig view > -- > > Key: AMBARI-5616 > URL: https://issues.apache.org/jira/browse/AMBARI-5616 > Project: Ambari > Issue Type: Task >Reporter: Roman Rader >Assignee: Roman Rader > Attachments: pig.patch > > > Create back-end and front-end for Pig View -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-1391) Move JobTracker to new server
[ https://issues.apache.org/jira/browse/AMBARI-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-1391: --- Assignee: Nate Cole > Move JobTracker to new server > - > > Key: AMBARI-1391 > URL: https://issues.apache.org/jira/browse/AMBARI-1391 > Project: Ambari > Issue Type: Sub-task >Reporter: Nate Cole >Assignee: Nate Cole > Fix For: 1.4.2 > > > Move JobTracker to new server -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-13450) Bootstrap Cluster via different SSH Port Number
[ https://issues.apache.org/jira/browse/AMBARI-13450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-13450: Assignee: Selim Ozcan > Bootstrap Cluster via different SSH Port Number > --- > > Key: AMBARI-13450 > URL: https://issues.apache.org/jira/browse/AMBARI-13450 > Project: Ambari > Issue Type: Improvement > Components: ambari-server, ambari-web >Affects Versions: 2.1.0 >Reporter: Selim Ozcan >Assignee: Selim Ozcan > Labels: features, patch > Fix For: 2.3.0 > > Attachments: diff_patch2.patch > > > For the time being, bootstrapping cluster is done via default port number 22 > for SSH and SCP protocols without an option to specify the port number. > There was a need to bootstrap cluster via different port number at the > laboratory which I work at but Apache Ambari didn't have that option so we > add that functionality. It still uses the default port number 22 unless you > change it at Installer Wizard Step 2. > A Textfieldview (default written value '22' SSH Port number ) added to > installer wizard step 2, same as specifying ssh user field which is default > to 'root' user, to take the SSH port input from user. After that, Port number > is transferred to bootstrapping functions along with sshUser value. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-13903) Need a way to set "advanced" properties as optional (isRequired=false)
[ https://issues.apache.org/jira/browse/AMBARI-13903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-13903: Assignee: Jaimin Jetly > Need a way to set "advanced" properties as optional (isRequired=false) > -- > > Key: AMBARI-13903 > URL: https://issues.apache.org/jira/browse/AMBARI-13903 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: 2.1.0 >Reporter: Nathan Falk >Assignee: Jaimin Jetly > Fix For: 2.2.0 > > > The only way to let a configuration property be optional seems to be to > define it in site_properties.js. It should be possible to specify > required=false for any property in any xml file in the stack. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-13982) Bootstrap API hangs (stays in RUNNING state)
[ https://issues.apache.org/jira/browse/AMBARI-13982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-13982: Assignee: Naga Vijayapuram > Bootstrap API hangs (stays in RUNNING state) > > > Key: AMBARI-13982 > URL: https://issues.apache.org/jira/browse/AMBARI-13982 > Project: Ambari > Issue Type: Bug >Reporter: Naga Vijayapuram >Assignee: Naga Vijayapuram > > Tried Bootstrap API (curl command from Mac) pointing to Ambari Server running > on CentOS and Ubuntu boxes and landed into the same issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-16702) Zeppelin cluster deployment fails due to unavailability of zeppelin service check script
[
https://issues.apache.org/jira/browse/AMBARI-16702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako reassigned AMBARI-16702:
Assignee: Renjith Kamath
> Zeppelin cluster deployment fails due to unavailability of zeppelin service
> check script
>
>
> Key: AMBARI-16702
> URL: https://issues.apache.org/jira/browse/AMBARI-16702
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Renjith Kamath
>Assignee: Renjith Kamath
> Fix For: 2.4.0
>
> Attachments: AMBARI-16702_trunk-v1.patch
>
>
> Zeppelin cluster deployment fails due to the following error
> {code}
> 11:18:57.926 3210587 INFO - Running Service Check for Zeppelin Notebook -
> [ui.util.ServiceChecker.runServiceCheckViaAPI(ServiceChecker.java:394)]
> 11:18:57.926 3210587 INFO - executing POST
> http://c6401.ambari.apache.org:8080/api/v1/clusters/cl1/requests
> {"RequestInfo":{"command":"ZEPPELIN_SERVICE_CHECK","context":"ZEPPELIN
> Service Check "},"Requests/resource_filters": [{"service_name":"ZEPPELIN"}]}
> - [util.cluster_managers.APIManager.doPost(APIManager.java:242)]
> 11:18:57.954 3210615 ERROR - Unable to run Service check:
> ZEPPELIN_SERVICE_CHECK -
> [ui.util.ServiceChecker.runServiceCheckViaAPI(ServiceChecker.java:408)]
> 11:19:38.407 3251068 WARN - No bg counter appeared for a triggered operation
> - [monitoring.managers.BGOperations.waitForAppearing(BGOperations.java:250)]
> 11:19:38.424 3251085 INFO - Time spent on timer [install] - [3248.102] -
> [ui.util.TimerElapsed.elapsedTimeSeconds(TimerElapsed.java:37)]
> 11:19:53.304 3265965 ERROR - Failure happen: -
> [ui.util.ErrorCollectorEx.captureClusterState(ErrorCollectorEx.java:146)]
> java.io.IOException: Attempted read from closed stream.
> at
> org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:167)
> at
> org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137)
> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
> at java.io.InputStreamReader.read(InputStreamReader.java:184)
> at java.io.Reader.read(Reader.java:140)
> at org.apache.http.util.EntityUtils.toString(EntityUtils.java:244)
> at org.apache.http.util.EntityUtils.toString(EntityUtils.java:288)
> at
> com.hw.ambari.ui.util.ServiceChecker.checkForError(ServiceChecker.java:439)
> at
> com.hw.ambari.ui.util.ServiceChecker.runServiceCheckViaAPI(ServiceChecker.java:422)
> at
> com.hw.ambari.ui.tests.installer.InstallClusterUsingBlueprint.installClusterUsingBlueprint(InstallClusterUsingBlueprint.java:219)
> at
> com.hw.ambari.ui.tests.installer.InstallClusterUsingBlueprint.installClusterUsingBlueprint(InstallClusterUsingBlueprint.java:222)
> at
> com.hw.ambari.ui.tests.installer.InstallClusterUsingBlueprint.installClusterUsingBlueprint(InstallClusterUsingBlueprint.java:406)
> at
> com.hw.ambari.ui.tests.installer.InstallClusterWithDBOption.installClusterWithDBOption(InstallClusterWithDBOption.java:144)
> at
> com.hw.ambari.ui.tests.installer.InstallHadoop.install(InstallHadoop.java:259)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.Verifier$1.evaluate(Verifier.java:35)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.
[jira] [Assigned] (AMBARI-3195) WebHCat install and start fails when adding service after initial cluster install
[
https://issues.apache.org/jira/browse/AMBARI-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako reassigned AMBARI-3195:
---
Assignee: Vladimir Tkhir
> WebHCat install and start fails when adding service after initial cluster
> install
> -
>
> Key: AMBARI-3195
> URL: https://issues.apache.org/jira/browse/AMBARI-3195
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 1.4.1
>Reporter: Vladimir Tkhir
>Assignee: Vladimir Tkhir
> Fix For: 1.6.0
>
> Attachments: AMBARI-3195.patch
>
>
> Steps to reproduce:
> # install cluster HDFS and YARN(MapReduce)
> # add Hive, HCatalog, WebHCat services with following REST API calls:
> {code}
> curl -u admin:admin -X POST -d
> '[{"ServiceInfo":{"service_name":"HIVE"}},{"ServiceInfo":{"service_name":"HCATALOG"}},{"ServiceInfo":{"service_name":"WEBHCAT"}}]'
> http://host1:8080/api/v1/clusters/cl/services
> curl -u admin:admin -X PUT -d
> '{"Clusters":{"desired_configs":{"type":"global","tag":"version3","properties":{"dfs_namenode_name_dir":"/hadoop/hdfs/namenode","namenode_heapsize":"1024m","namenode_opt_newsize":"200m","dfs_namenode_checkpoint_dir":"/hadoop/hdfs/namesecondary","dfs_datanode_data_dir":"/hadoop/hdfs/data","dtnode_heapsize":"1024m","dfs_datanode_failed_volume_tolerated":"0","dfs_webhdfs_enabled":"true","hadoop_heapsize":"1024","datanode_du_reserved":"1","dfs_namenode_checkpoint_period":"21600","fs_checkpoint_size":"0.5","hdfs_log_dir_prefix":"/var/log/hadoop","hadoop_pid_dir_prefix":"/var/run/hadoop","namenode_opt_maxnewsize":"640m","dfs_exclude":"dfs.exclude","dfs_replication":"3","dfs_block_local_path_access_user":"hbase","dfs_datanode_data_dir_perm":"750","security_enabled":"false","namenode_formatted_mark_dir":"/var/run/hadoop/hdfs/namenode/formatted/","hcat_conf_dir":"","hdfs_enable_shortcircuit_read":"true","yarn_heapsize":"1024","resourcemanager_heapsize":"1024","nodemanager_heapsize":"1024","yarn_log_dir_prefix":"/var/log/hadoop-yarn","yarn_pid_dir_prefix":"/var/run/hadoop-yarn","yarn_nodemanager_local-dirs":"/hadoop/yarn","mapreduce_tasktracker_map_tasks_maximum":"4","mapreduce_map_memory_mb":"1536","mapreduce_reduce_memory_mb":"2048","mapreduce_task_io_sort_mb":"200","mapreduce_userlog_retainhours":"24","maxtasks_per_job":"-1","scheduler_name":"org.apache.hadoop.mapred.CapacityTaskScheduler","mapreduce_jobtracker_system_dir":"/mapred/system","mapred_log_dir_prefix":"/var/log/hadoop-mapreduce","mapred_pid_dir_prefix":"/var/run/hadoop-mapreduce","mapred_hosts_include":"mapred.include","task_controller":"org.apache.hadoop.mapred.DefaultTaskController","mapred_hosts_exclude":"mapred.exclude","mapred_jobstatus_dir":"file:mapred/jobstatus","hive_ambari_database":"MySQL","hive_database":"New
> MySQL
> Database","hive_hostname":"host1","hive_database_name":"hive","hive_metastore_user_name":"hive","hive_metastore_user_passwd":"test","hive_jdbc_connection_url":"jdbc:mysql://host1/hive?createDatabaseIfNotExist=true","hive_metastore_port":"9083","hive_lib":"/usr/lib/hive/lib/","hive_conf_dir":"/etc/hive/conf","hive_dbroot":"/usr/lib/hive/lib","hive_log_dir":"/var/log/hive","hive_pid_dir":"/var/run/hive","mysql_connector_url":"${download_url}/mysql-connector-java-5.1.18.zip","hive_aux_jars_path":"/usr/lib/hcatalog/share/hcatalog/hcatalog-core.jar","hcat_log_dir":"/var/log/webhcat","hcat_pid_dir":"/var/run/webhcat","hbase_conf_dir":"/etc/hbase","proxyuser_group":"users","dfs_datanode_address":"50010","dfs_datanode_http_address":"50075","gpl_artifacts_download_url":"","apache_artifacts_download_url":"","ganglia_runtime_dir":"/var/run/ganglia/hdp","java64_home":"/usr/jdk64/jdk1.6.0_31","run_dir":"/var/run/hadoop","hadoop_conf_dir":"/etc/hadoop/conf","hdfs_user":"hdfs","mapred_user":"mapred","yarn_user":"yarn","hbase_user":"hbase","hive_user":"hive","hcat_user":"hcat","webhcat_user":"hcat","oozie_user":"oozie","zk_user":"zookeeper","gmetad_user":"nobody","gmond_user":"nobody","nagios_user":"nagios","nagios_group":"nagios","smokeuser":"ambari-qa","user_group":"hadoop","rrdcached_base_dir":"/var/lib/ganglia/rrds","hive_database_type":"mysql","hive_jdbc_driver":"com.mysql.jdbc.Driver"'
> http://host1:8080/api/v1/clusters/cl
> curl -u admin:admin -X PUT -d
> '{"Clusters":{"desired_configs":{"type":"hive-site","tag":"version1","properties":{"fs.file.impl.disable.cache":"true","fs.hdfs.impl.disable.cache":"true","hadoop.clientside.fs.operations":"true","hive.auto.convert.join":"true","hive.auto.convert.join.noconditionaltask":"true","hive.auto.convert.join.noconditionaltask.size":"10","hive.auto.convert.sortmerge.join":"true","hive.auto.convert.sortmerge.join.noconditionaltask":"true","hive.enforce.bucketing":"true","hive.enforce.sorting":"true","hive.map
[jira] [Assigned] (AMBARI-5750) Ambari not configuring Ganglia/gmetad correctly, leading to log spam
[
https://issues.apache.org/jira/browse/AMBARI-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako reassigned AMBARI-5750:
---
Assignee: Andrew Onischuk
> Ambari not configuring Ganglia/gmetad correctly, leading to log spam
>
>
> Key: AMBARI-5750
> URL: https://issues.apache.org/jira/browse/AMBARI-5750
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 1.6.0
>Reporter: Sudhir Prakash
>Assignee: Andrew Onischuk
> Fix For: 1.6.1
>
>
> I performed a 2.1 stack install via Ambari GUI of all components except for
> Storm. I noticed that on my primary master node, that /var/log/messages is
> being spammed by gmetad every few seconds.
> {code}
> May 12 15:01:27 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() for
> [HDPSupervisor] failed to contact node 39.0.8.1
> May 12 15:01:27 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() got no
> answer from any [HDPSupervisor] datasource
> May 12 15:01:28 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() for
> [HDPTaskTracker] failed to contact node 39.0.8.1
> May 12 15:01:28 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() got no
> answer from any [HDPTaskTracker] datasource
> May 12 15:01:37 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() for
> [HDPJobTracker] failed to contact node 39.0.8.1
> May 12 15:01:37 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() got no
> answer from any [HDPJobTracker] datasource
> May 12 15:01:37 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() for
> [HDPFlumeServer] failed to contact node 39.0.8.1
> May 12 15:01:37 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() got no
> answer from any [HDPFlumeServer] datasource
> May 12 15:01:39 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() for
> [HDPNimbus] failed to contact node 39.0.8.1
> May 12 15:01:39 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() got no
> answer from any [HDPNimbus] datasource
> May 12 15:01:42 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() for
> [HDPSupervisor] failed to contact node 39.0.8.1
> May 12 15:01:42 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() got no
> answer from any [HDPSupervisor] datasource
> May 12 15:01:43 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() for
> [HDPTaskTracker] failed to contact node 39.0.8.1
> May 12 15:01:43 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() got no
> answer from any [HDPTaskTracker] datasource
> May 12 15:01:52 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() for
> [HDPJobTracker] failed to contact node 39.0.8.1
> May 12 15:01:52 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() got no
> answer from any [HDPJobTracker] datasource
> May 12 15:01:52 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() for
> [HDPFlumeServer] failed to contact node 39.0.8.1
> May 12 15:01:52 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() got no
> answer from any [HDPFlumeServer] datasource
> May 12 15:01:55 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() for
> [HDPNimbus] failed to contact node 39.0.8.1
> May 12 15:01:55 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() got no
> answer from any [HDPNimbus] datasource
> May 12 15:01:57 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() for
> [HDPSupervisor] failed to contact node 39.0.8.1
> May 12 15:01:57 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() got no
> answer from any [HDPSupervisor] datasource
> May 12 15:01:58 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() for
> [HDPTaskTracker] failed to contact node 39.0.8.1
> May 12 15:01:58 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() got no
> answer from any [HDPTaskTracker] datasource
> May 12 15:02:06 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() for
> [HDPFlumeServer] failed to contact node 39.0.8.1
> May 12 15:02:06 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() got no
> answer from any [HDPFlumeServer] datasource
> May 12 15:02:07 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() for
> [HDPJobTracker] failed to contact node 39.0.8.1
> May 12 15:02:07 hadoopvm1-1 /usr/sbin/gmetad[26198]: data_thread() got no
> answer from any [HDPJobTracker] datasource{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-662) Soon after a cluster was (seemingly) successfully deployed, a number of Nagios alerts were sent
[ https://issues.apache.org/jira/browse/AMBARI-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako resolved AMBARI-662. Resolution: Not A Problem > Soon after a cluster was (seemingly) successfully deployed, a number of > Nagios alerts were sent > --- > > Key: AMBARI-662 > URL: https://issues.apache.org/jira/browse/AMBARI-662 > Project: Ambari > Issue Type: Bug >Reporter: Yusaku Sako >Priority: Critical > > Below are some of the Nagios alerts that I got soon after I successfully > deployed a cluster. > During the cluster install, I did not choose to enable Kerberos Security. > Yet it seems that a check is being performed for "kinit". Also, the realm > EXAMPLE.COM is bogus. > ### > Subject: ** PROBLEM Service Alert: > domu-12-31-39-17-2e-a7.compute-1.internal/TEMPLETON::Templeton status check > is CRITICAL ** > Body: > * Nagios * > Notification Type: PROBLEM > Service: TEMPLETON::Templeton status check > Host: domu-12-31-39-17-2e-a7.compute-1.internal > Address: domu-12-31-39-17-2e-a7.compute-1.internal > State: CRITICAL > Date/Time: Sun Jul 29 21:47:30 EDT 2012 > Additional Info: > CRITICAL: Error doing kinit for nagios [kinit(v5): Cannot resolve network > address for KDC in realm EXAMPLE.COM while getting initial credentials] > ### > Subject: ** PROBLEM Service Alert: > domu-12-31-39-17-2e-a7.compute-1.internal/DATANODE::Process down is UNKNOWN ** > Body: > * Nagios * > Notification Type: PROBLEM > Service: DATANODE::Process down > Host: domu-12-31-39-17-2e-a7.compute-1.internal > Address: domu-12-31-39-17-2e-a7.compute-1.internal > State: UNKNOWN > Date/Time: Sun Jul 29 21:47:40 EDT 2012 > Additional Info: > check_tcp: Port must be a positive integer > ### > Subject: ** PROBLEM Service Alert: > ip-10-140-10-213.ec2.internal/DATANODE::Storage full is UNKNOWN ** > Body: > * Nagios * > Notification Type: PROBLEM > Service: DATANODE::Storage full > Host: ip-10-140-10-213.ec2.internal > Address: ip-10-140-10-213.ec2.internal > State: UNKNOWN > Date/Time: Sun Jul 29 21:47:50 EDT 2012 > Additional Info: > Usage: 0 -h host -p port -w warn% -c crit% > ### > Subject: ** PROBLEM Service Alert: > domu-12-31-39-17-2e-a7.compute-1.internal/HIVE-METASTORE::HIVE-METASTORE > status check is CRITICAL ** > Body: > * Nagios * > Notification Type: PROBLEM > Service: HIVE-METASTORE::HIVE-METASTORE status check > Host: domu-12-31-39-17-2e-a7.compute-1.internal > Address: domu-12-31-39-17-2e-a7.compute-1.internal > State: CRITICAL > Date/Time: Sun Jul 29 21:47:50 EDT 2012 > Additional Info: > CRITICAL: Error doing kinit for nagios [kinit(v5): Cannot resolve network > address for KDC in realm EXAMPLE.COM while getting initial credentials] > ### > Subject: ** PROBLEM Service Alert: > domu-12-31-39-17-2e-a7.compute-1.internal/OOZIE::Oozie status check is > CRITICAL ** > Body: > * Nagios * > Notification Type: PROBLEM > Service: OOZIE::Oozie status check > Host: domu-12-31-39-17-2e-a7.compute-1.internal > Address: domu-12-31-39-17-2e-a7.compute-1.internal > State: CRITICAL > Date/Time: Sun Jul 29 21:48:00 EDT 2012 > Additional Info: > CRITICAL: Error doing kinit for nagios [kinit(v5): Cannot resolve network > address for KDC in realm EXAMPLE.COM while getting initial credentials] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (AMBARI-662) Soon after a cluster was (seemingly) successfully deployed, a number of Nagios alerts were sent
[ https://issues.apache.org/jira/browse/AMBARI-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reopened AMBARI-662: > Soon after a cluster was (seemingly) successfully deployed, a number of > Nagios alerts were sent > --- > > Key: AMBARI-662 > URL: https://issues.apache.org/jira/browse/AMBARI-662 > Project: Ambari > Issue Type: Bug >Reporter: Yusaku Sako >Priority: Critical > > Below are some of the Nagios alerts that I got soon after I successfully > deployed a cluster. > During the cluster install, I did not choose to enable Kerberos Security. > Yet it seems that a check is being performed for "kinit". Also, the realm > EXAMPLE.COM is bogus. > ### > Subject: ** PROBLEM Service Alert: > domu-12-31-39-17-2e-a7.compute-1.internal/TEMPLETON::Templeton status check > is CRITICAL ** > Body: > * Nagios * > Notification Type: PROBLEM > Service: TEMPLETON::Templeton status check > Host: domu-12-31-39-17-2e-a7.compute-1.internal > Address: domu-12-31-39-17-2e-a7.compute-1.internal > State: CRITICAL > Date/Time: Sun Jul 29 21:47:30 EDT 2012 > Additional Info: > CRITICAL: Error doing kinit for nagios [kinit(v5): Cannot resolve network > address for KDC in realm EXAMPLE.COM while getting initial credentials] > ### > Subject: ** PROBLEM Service Alert: > domu-12-31-39-17-2e-a7.compute-1.internal/DATANODE::Process down is UNKNOWN ** > Body: > * Nagios * > Notification Type: PROBLEM > Service: DATANODE::Process down > Host: domu-12-31-39-17-2e-a7.compute-1.internal > Address: domu-12-31-39-17-2e-a7.compute-1.internal > State: UNKNOWN > Date/Time: Sun Jul 29 21:47:40 EDT 2012 > Additional Info: > check_tcp: Port must be a positive integer > ### > Subject: ** PROBLEM Service Alert: > ip-10-140-10-213.ec2.internal/DATANODE::Storage full is UNKNOWN ** > Body: > * Nagios * > Notification Type: PROBLEM > Service: DATANODE::Storage full > Host: ip-10-140-10-213.ec2.internal > Address: ip-10-140-10-213.ec2.internal > State: UNKNOWN > Date/Time: Sun Jul 29 21:47:50 EDT 2012 > Additional Info: > Usage: 0 -h host -p port -w warn% -c crit% > ### > Subject: ** PROBLEM Service Alert: > domu-12-31-39-17-2e-a7.compute-1.internal/HIVE-METASTORE::HIVE-METASTORE > status check is CRITICAL ** > Body: > * Nagios * > Notification Type: PROBLEM > Service: HIVE-METASTORE::HIVE-METASTORE status check > Host: domu-12-31-39-17-2e-a7.compute-1.internal > Address: domu-12-31-39-17-2e-a7.compute-1.internal > State: CRITICAL > Date/Time: Sun Jul 29 21:47:50 EDT 2012 > Additional Info: > CRITICAL: Error doing kinit for nagios [kinit(v5): Cannot resolve network > address for KDC in realm EXAMPLE.COM while getting initial credentials] > ### > Subject: ** PROBLEM Service Alert: > domu-12-31-39-17-2e-a7.compute-1.internal/OOZIE::Oozie status check is > CRITICAL ** > Body: > * Nagios * > Notification Type: PROBLEM > Service: OOZIE::Oozie status check > Host: domu-12-31-39-17-2e-a7.compute-1.internal > Address: domu-12-31-39-17-2e-a7.compute-1.internal > State: CRITICAL > Date/Time: Sun Jul 29 21:48:00 EDT 2012 > Additional Info: > CRITICAL: Error doing kinit for nagios [kinit(v5): Cannot resolve network > address for KDC in realm EXAMPLE.COM while getting initial credentials] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-7624) Create UI unit test skeleton for File browser view
[ https://issues.apache.org/jira/browse/AMBARI-7624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-7624: --- Assignee: Jaimin Jetly > Create UI unit test skeleton for File browser view > -- > > Key: AMBARI-7624 > URL: https://issues.apache.org/jira/browse/AMBARI-7624 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 1.7.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 2.1.0 > > > We are committing to a new frontend dev process where every UI patch needs to > go with unit or/and functional test. > This requires creating skeleton for unit test for Files view contrib project. > As a resolution to this ticket, please create a UI unit test skeleton for > Files view and add a sample unit test to it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-14652) Express upgrade to HDP 2.4 has failed on Calculating Yarn Properties for Spark
[ https://issues.apache.org/jira/browse/AMBARI-14652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-14652: Assignee: Dmytro Grinenko > Express upgrade to HDP 2.4 has failed on Calculating Yarn Properties for Spark > -- > > Key: AMBARI-14652 > URL: https://issues.apache.org/jira/browse/AMBARI-14652 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.2.1 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Blocker > Fix For: 2.2.1 > > Attachments: AMBARI-14652.patch > > > Error text > > Server action failed > Calculations on new yarn properties have failed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-14669) Add yarn-site properties for Spark Shuffle Aux services (2.2->2.4 upgrade path)
[ https://issues.apache.org/jira/browse/AMBARI-14669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-14669: Assignee: Dmytro Grinenko > Add yarn-site properties for Spark Shuffle Aux services (2.2->2.4 upgrade > path) > --- > > Key: AMBARI-14669 > URL: https://issues.apache.org/jira/browse/AMBARI-14669 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.2.1 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: 2.2.1 > > Attachments: AMBARI-14669.patch > > > Since upgrade packs for 2.2->2.4 were added almost at the same time, > properties for spark need to be added to this path too > Additionally add unit-test for SparkShufflePropertyConfig -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-14428) Spark client and History Server failed to deploy from first try on HDP-2.3.0.0
[
https://issues.apache.org/jira/browse/AMBARI-14428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako reassigned AMBARI-14428:
Assignee: Dmytro Grinenko
> Spark client and History Server failed to deploy from first try on HDP-2.3.0.0
> --
>
> Key: AMBARI-14428
> URL: https://issues.apache.org/jira/browse/AMBARI-14428
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.1
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Blocker
> Fix For: 2.2.1
>
> Attachments: AMBARI-14428.patch
>
>
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK/1.2.0.2.2/package/scripts/spark_client.py",
> line 59, in
> SparkClient().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 219, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK/1.2.0.2.2/package/scripts/spark_client.py",
> line 35, in install
> self.configure(env)
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK/1.2.0.2.2/package/scripts/spark_client.py",
> line 38, in configure
> import params
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK/1.2.0.2.2/package/scripts/params.py",
> line 152, in
> version = get_hdp_version('spark-thriftserver')
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_hdp_version.py",
> line 79, in get_hdp_version
> 'Unable to determine the current version because of a non-zero return
> code of {0}'.format(str(return_code)))
> resource_management.core.exceptions.Fail: Unable to determine the current
> version because of a non-zero return code of 1
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-13886) Stop-and-Start Upgrade: Fix unit tests that were ignored/missing on server
[ https://issues.apache.org/jira/browse/AMBARI-13886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-13886: Assignee: Dmytro Grinenko > Stop-and-Start Upgrade: Fix unit tests that were ignored/missing on server > -- > > Key: AMBARI-13886 > URL: https://issues.apache.org/jira/browse/AMBARI-13886 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.2.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: 2.2.0 > > > Enable and fix server side unit-tests, previously disabled during feature > merge. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-14238) EU: Downgrade goes through all steps even if initiated at first prompt, should exit since hasn't changed stack/configs
[ https://issues.apache.org/jira/browse/AMBARI-14238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-14238: Assignee: Dmytro Grinenko > EU: Downgrade goes through all steps even if initiated at first prompt, > should exit since hasn't changed stack/configs > -- > > Key: AMBARI-14238 > URL: https://issues.apache.org/jira/browse/AMBARI-14238 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: 2.2.0 > > > Steps: > 1. Setup HDP 2.3.2 cluster with Ambari 2.1.3 > 2. Initiate Express Upgrade > 3. Wait for the first message titled "stop all YARN queues" to appear > 4. Hit Downgrade > Result: > Downgrade starts all the way from top as if it was triggered at Finalize HDFS > phase and takes a while to complete > Expected Result: > It would be good to have downgrade attempt the actions only for which > downgrade is really required -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-14286) Express Upgrade: Failure while trying to restart Namenode with socket timeout error
[
https://issues.apache.org/jira/browse/AMBARI-14286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako reassigned AMBARI-14286:
Assignee: Dmytro Grinenko
> Express Upgrade: Failure while trying to restart Namenode with socket timeout
> error
> ---
>
> Key: AMBARI-14286
> URL: https://issues.apache.org/jira/browse/AMBARI-14286
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk, 2.2.0
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.2.0
>
>
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
> line 432, in
> NameNode().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 217, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 513, in restart
> self.start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
> line 102, in start
> namenode(action="start", hdfs_binary=hdfs_binary,
> upgrade_type=upgrade_type, env=env)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py",
> line 59, in namenode
> setup_ranger_hdfs(upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/setup_ranger_hdfs.py",
> line 56, in setup_ranger_hdfs
> hdp_version_override = hdp_version, skip_if_rangeradmin_down= not
> params.retryAble)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/setup_ranger_plugin_xml.py",
> line 78, in setup_ranger_plugin
> policy_user)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/ranger_functions.py",
> line 100, in create_ranger_repository
> response_code = self.check_ranger_login_urllib2(self.baseUrl)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/ranger_functions.py",
> line 200, in check_ranger_login_urllib2
> response = urllib2.urlopen(url, timeout=20)
> File "/usr/lib/python2.7/urllib2.py", line 127, in urlopen
> return _opener.open(url, data, timeout)
> File "/usr/lib/python2.7/urllib2.py", line 410, in open
> response = meth(req, response)
> File "/usr/lib/python2.7/urllib2.py", line 523, in http_response
> 'http', request, response, code, msg, hdrs)
> File "/usr/lib/python2.7/urllib2.py", line 442, in error
> result = self._call_chain(*args)
> File "/usr/lib/python2.7/urllib2.py", line 382, in _call_chain
> result = func(*args)
> File "/usr/lib/python2.7/urllib2.py", line 629, in http_error_302
> return self.parent.open(new, timeout=req.timeout)
> File "/usr/lib/python2.7/urllib2.py", line 404, in open
> response = self._open(req, data)
> File "/usr/lib/python2.7/urllib2.py", line 422, in _open
> '_open', req)
> File "/usr/lib/python2.7/urllib2.py", line 382, in _call_chain
> result = func(*args)
> File "/usr/lib/python2.7/urllib2.py", line 1214, in http_open
> return self.do_open(httplib.HTTPConnection, req)
> File "/usr/lib/python2.7/urllib2.py", line 1187, in do_open
> r = h.getresponse(buffering=True)
> File "/usr/lib/python2.7/httplib.py", line 1051, in getresponse
> response.begin()
> File "/usr/lib/python2.7/httplib.py", line 415, in begin
> version, status, reason = self._read_status()
> File "/usr/lib/python2.7/httplib.py", line 371, in _read_status
> line = self.fp.readline(_MAXLINE + 1)
> File "/usr/lib/python2.7/socket.py", line 476, in readline
> data = self._sock.recv(self._rbufsize)
> socket.timeout: timed out
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-15627) Ambari is expecting hadoop client package and configuration, even if no HDFS components are installed on this host
[
https://issues.apache.org/jira/browse/AMBARI-15627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako reassigned AMBARI-15627:
Assignee: Dmytro Grinenko
> Ambari is expecting hadoop client package and configuration, even if no HDFS
> components are installed on this host
> --
>
> Key: AMBARI-15627
> URL: https://issues.apache.org/jira/browse/AMBARI-15627
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15627-branch-2.2.patch, AMBARI-15627.patch,
> AMBARI-15627.patch.1
>
>
> This happens during an ugprade from HDP 2.3.0 to 2.3.4.7. Couple nodes have
> Kafka broker/Zookeeper installed with no clients or any other components.
> Hence, during the installation, there is no HDFS package installed on this
> node. However, during the start up Ambari expects this node to have
> /usr/hdp/current/hadoop-client/conf' during the start up:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
> line 39, in
> BeforeStartHook().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 219, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
> line 36, in hook
> create_topology_script_and_mapping()
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py",
> line 69, in create_topology_script_and_mapping
> create_topology_mapping()
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py",
> line 36, in create_topology_mapping
> group=params.user_group)
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 154, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 158, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 121, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 152, in action_create
> sudo.makedirs(path, self.resource.mode or 0755)
> File "/usr/lib/python2.6/site-packages/resource_management/core/sudo.py",
> line 55, in makedirs
> os.makedirs(path, mode)
> File "/usr/lib64/python2.6/os.py", line 157, in makedirs
> mkdir(name, mode)
> OSError: [Errno 2] No such file or directory:
> '/usr/hdp/current/hadoop-client/conf'
> Error: Error: Unable to run the custom hook script ['/usr/bin/python2',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py',
> 'START', '/var/lib/ambari-agent/data/command-3343.json',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START',
> '/var/lib/ambari-agent/data/structured-out-3343.json', 'INFO',
> '/var/lib/ambari-agent/tmp']
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-15550) PXF should use hostname instead of localhost in pxf urls
[ https://issues.apache.org/jira/browse/AMBARI-15550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-15550: Assignee: bhuvnesh chaudhary > PXF should use hostname instead of localhost in pxf urls > > > Key: AMBARI-15550 > URL: https://issues.apache.org/jira/browse/AMBARI-15550 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: trunk, 2.2.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary >Priority: Minor > Fix For: 2.3.0, 2.2.0 > > Attachments: AMBARI-15550.patch, AMBARI-15550-test-case-fixed.patch > > > PXF should use actual hostname instead of localhost in pxf urls. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-15521) Change Spark Thrift Server default configuration for spark.hadoop.cacheConf
[ https://issues.apache.org/jira/browse/AMBARI-15521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-15521: Assignee: Bikas Saha > Change Spark Thrift Server default configuration for spark.hadoop.cacheConf > --- > > Key: AMBARI-15521 > URL: https://issues.apache.org/jira/browse/AMBARI-15521 > Project: Ambari > Issue Type: Bug >Reporter: Bikas Saha >Assignee: Bikas Saha > Fix For: 2.2.2 > > Attachments: AMBARI-15521.1.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-15265) Install & Manage Zeppelin with Ambari
[ https://issues.apache.org/jira/browse/AMBARI-15265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-15265: Assignee: Renjith Kamath > Install & Manage Zeppelin with Ambari > - > > Key: AMBARI-15265 > URL: https://issues.apache.org/jira/browse/AMBARI-15265 > Project: Ambari > Issue Type: New Feature >Reporter: Renjith Kamath >Assignee: Renjith Kamath > Fix For: 2.4.0 > > Attachments: AMBARI-15265_branch-2.2-2.patch, > AMBARI-15265_branch-2.2-3.patch, AMBARI-15265_branch-2.2-4.patch, > AMBARI-15265_branch-2.2-5.patch, AMBARI-15265_branch-2.2-6.patch, > AMBARI-15265_branch-2.2.patch > > > Ambari to support the following scenario for Zeppelin Service > * Install of Zeppelin > * Provide start/stop of Zeppelin component > * Configure Zeppelin with Ambari including Zeppelin LDAP Authentication > * Ambari to provide Quicklink from Ambari to Zeppelin > * Ambari to Kerberize a cluster with Zeppelin in it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-15485) Update Spark to 1.6.1 for HDP stack
[ https://issues.apache.org/jira/browse/AMBARI-15485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-15485: Assignee: Bikas Saha > Update Spark to 1.6.1 for HDP stack > --- > > Key: AMBARI-15485 > URL: https://issues.apache.org/jira/browse/AMBARI-15485 > Project: Ambari > Issue Type: Bug >Reporter: Bikas Saha >Assignee: Bikas Saha > Fix For: 2.2.2 > > Attachments: AMBARI-15485.1.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-15502) Add description for LLAP configs
[ https://issues.apache.org/jira/browse/AMBARI-15502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-15502: Assignee: Sumit Mohanty > Add description for LLAP configs > > > Key: AMBARI-15502 > URL: https://issues.apache.org/jira/browse/AMBARI-15502 > Project: Ambari > Issue Type: Bug > Components: ambari-server, stacks >Affects Versions: 2.4.0 >Reporter: Jaimin Jetly >Assignee: Sumit Mohanty > Fix For: 2.4.0 > > Attachments: AMBARI-15502.1.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-16081) Fix specific unit tests to use a single db
[ https://issues.apache.org/jira/browse/AMBARI-16081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-16081: Assignee: Nate Cole > Fix specific unit tests to use a single db > -- > > Key: AMBARI-16081 > URL: https://issues.apache.org/jira/browse/AMBARI-16081 > Project: Ambari > Issue Type: Epic > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Attachments: test_times - 2016-04-22.xlsx > > > Many test classes instantiate a new DB for each test. This makes those > classes take a very long time. This effort will be done over time, using the > attached spreadsheet to determine which classes should be done first. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-15689) Unable to edit log dir for ZK
[ https://issues.apache.org/jira/browse/AMBARI-15689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-15689: Assignee: Antonenko Alexander > Unable to edit log dir for ZK > - > > Key: AMBARI-15689 > URL: https://issues.apache.org/jira/browse/AMBARI-15689 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15689.patch > > > Unable to edit log dir for ZK. > I only checked HDFS and ZK. HDFS I was able to modify, ZK i was not. > Please check ALL services. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-15933) Views work for Hue to Views Migration Tool
[ https://issues.apache.org/jira/browse/AMBARI-15933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-15933: Assignee: Pradarttana > Views work for Hue to Views Migration Tool > -- > > Key: AMBARI-15933 > URL: https://issues.apache.org/jira/browse/AMBARI-15933 > Project: Ambari > Issue Type: New Feature > Components: ambari-views >Affects Versions: 2.4.0 > Environment: Hue is only supported on Linux (non HDInsight), hence > whever Hue was previously supported on we must be able to migrate. >Reporter: Pradarttana >Assignee: Pradarttana >Priority: Critical > Labels: ambari-views, dev-test, scoping > Fix For: 2.4.0 > > Attachments: AMBARI-15933.1_trunk.patch, AMBARI-15933.2_trunk.patch, > AMBARI-15933.3_trunk.patch, AMBARI-15933.4_trunk.patch, > AMBARI-15933.5_trunk.patch, AMBARI-15933_trunk.patch > > Original Estimate: 840h > Remaining Estimate: 840h > > Problem: Hue is planned to be deprecated, hence need a way for customers to > migrate over artifacts from Hue to the equivalent Views. > Link to the PRD Doc > https://docs.google.com/a/hortonworks.com/document/d/13m-Ioxamq4oF3yYHASkVjJ3mhpRlKuM12BCgCAJaap4/edit?usp=sharing > This RMP is a clone specifically to cover the work on the Views Framework > side. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-15608) hive-interactive-env: avoiding including copies of Hive-1.x classes
[ https://issues.apache.org/jira/browse/AMBARI-15608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-15608: Assignee: Gopal V > hive-interactive-env: avoiding including copies of Hive-1.x classes > --- > > Key: AMBARI-15608 > URL: https://issues.apache.org/jira/browse/AMBARI-15608 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Gopal V >Assignee: Gopal V > Labels: Hive > Attachments: AMBARI-15608.1.patch > > > Spark-assembly jars contain Hive-1.x classes which break both rolling > upgrades and hive-2.0 installations. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-16772) Zeppelin restart with Ambari fails - according to Ambari
[
https://issues.apache.org/jira/browse/AMBARI-16772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako reassigned AMBARI-16772:
Assignee: Renjith Kamath
> Zeppelin restart with Ambari fails - according to Ambari
>
>
> Key: AMBARI-16772
> URL: https://issues.apache.org/jira/browse/AMBARI-16772
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
> Environment: centos
>Reporter: Renjith Kamath
>Assignee: Renjith Kamath
> Fix For: 2.4.0
>
> Attachments: AMBARI-16772-trunk-v1.patch
>
>
> Configure Zeppelin to authenticate users.
> Log in to Zeppelin as a user (let's say user1)
> Re-start Zeppelin with Ambai, note Ambari reports Zeppelin fails to restart.
> However Zeppelin is restarted fine.
> Note 401 in the log of the error below. I suspect it is because with
> authentication enabled Ambari isn't able to contact zeppelin.
> {code: title=stderr: /var/lib/ambari-agent/data/errors-249.txt}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.4/services/ZEPPELIN/package/scripts/master.py",
> line 235, in
> Master().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 219, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 535, in restart
> self.start(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.4/services/ZEPPELIN/package/scripts/master.py",
> line 179, in start
> self.update_zeppelin_interpreter()
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.4/services/ZEPPELIN/package/scripts/master.py",
> line 196, in update_zeppelin_interpreter
> data = json.load(urllib2.urlopen(zeppelin_int_url))
> File "/usr/lib64/python2.6/urllib2.py", line 126, in urlopen
> return _opener.open(url, data, timeout)
> File "/usr/lib64/python2.6/urllib2.py", line 397, in open
> response = meth(req, response)
> File "/usr/lib64/python2.6/urllib2.py", line 510, in http_response
> 'http', request, response, code, msg, hdrs)
> File "/usr/lib64/python2.6/urllib2.py", line 435, in error
> return self._call_chain(*args)
> File "/usr/lib64/python2.6/urllib2.py", line 369, in _call_chain
> result = func(*args)
> File "/usr/lib64/python2.6/urllib2.py", line 518, in http_error_default
> raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
> urllib2.HTTPError: HTTP Error 401: Unauthorized
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-16133) Zeppelin to select only tested Interpreter
[ https://issues.apache.org/jira/browse/AMBARI-16133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-16133: Assignee: Prabhjyot Singh > Zeppelin to select only tested Interpreter > -- > > Key: AMBARI-16133 > URL: https://issues.apache.org/jira/browse/AMBARI-16133 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Fix For: 2.4.0 > > Attachments: AMBARI-16133.trunk.patch > > > Allowing only those interpreters that are tested with ambari. i.e.; > Spark > Hive > Shell > MarkDown > R > Livy > Phoenix -- This message was sent by Atlassian JIRA (v6.4.14#64029)
