[jira] [Commented] (AMBARI-21226) Improve Spark thriftserver default configuration

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048673#comment-16048673
 ] 

Hudson commented on AMBARI-21226:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7624 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7624/])
AMBARI-21226. Add two new Spark thrift server related configurations in 
(smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=24e2cacb8ede081824b9162ba124acdffa33e0ec])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/nonrolling-upgrade-2.6.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/config-upgrade.xml
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK/configuration/spark-thrift-sparkconf.xml
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/configuration/spark2-thrift-sparkconf.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/upgrade-2.6.xml


> Improve Spark thriftserver default configuration
> 
>
> Key: AMBARI-21226
> URL: https://issues.apache.org/jira/browse/AMBARI-21226
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Reporter: Saisai Shao
>Assignee: Saisai Shao
>
> Add two new default configurations to Ambari Spark stacks, this is mainly 
> used to improve the stability of long running of thriftserver.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21226) Improve Spark thriftserver default configuration

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048667#comment-16048667
 ] 

Hudson commented on AMBARI-21226:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1594 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1594/])
AMBARI-21226. Add two new Spark thrift server related configurations in 
(smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2461ddbcd1c4fa00b628395b60625648a9074cd9])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/config-upgrade.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/nonrolling-upgrade-2.6.xml
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/configuration/spark2-thrift-sparkconf.xml
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK/configuration/spark-thrift-sparkconf.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/upgrade-2.6.xml


> Improve Spark thriftserver default configuration
> 
>
> Key: AMBARI-21226
> URL: https://issues.apache.org/jira/browse/AMBARI-21226
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Reporter: Saisai Shao
>Assignee: Saisai Shao
>
> Add two new default configurations to Ambari Spark stacks, this is mainly 
> used to improve the stability of long running of thriftserver.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048655#comment-16048655
 ] 

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/12872919/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/11649//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] [Resolved] (AMBARI-21226) Improve Spark thriftserver default configuration

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty resolved AMBARI-21226.

Resolution: Fixed

> Improve Spark thriftserver default configuration
> 
>
> Key: AMBARI-21226
> URL: https://issues.apache.org/jira/browse/AMBARI-21226
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Reporter: Saisai Shao
>Assignee: Saisai Shao
>
> Add two new default configurations to Ambari Spark stacks, this is mainly 
> used to improve the stability of long running of thriftserver.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21226) Improve Spark thriftserver default configuration

[Sumit Mohanty (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048648#comment-16048648
 ] 

Sumit Mohanty commented on AMBARI-21226:


+1 for the patch  - committed to trunk and branch-2.5

> Improve Spark thriftserver default configuration
> 
>
> Key: AMBARI-21226
> URL: https://issues.apache.org/jira/browse/AMBARI-21226
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Reporter: Saisai Shao
>Assignee: Saisai Shao
>
> Add two new default configurations to Ambari Spark stacks, this is mainly 
> used to improve the stability of long running of thriftserver.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo

[Qin Liu (JIRA)]

 [ 
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

[Qin Liu (JIRA)]

 [ 
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
>
> 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

[Qin Liu (JIRA)]

 [ 
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

[Qin Liu (JIRA)]

 [ 
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
>
> 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

[Qin Liu (JIRA)]

 [ 
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
>
> 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

[Qin Liu (JIRA)]

 [ 
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

[Qin Liu (JIRA)]

 [ 
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
>
> 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

[Qin Liu (JIRA)]

 [ 
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-21207) Extend Swagger Maven pluging to handle nested API's

[JIRA]

 [ 
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_v3.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_v3.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

[JIRA]

 [ 
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_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_v3.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-21241) Support revert for patch upgrades

[Nate Cole (JIRA)]

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

Nate Cole updated AMBARI-21241:
---
Status: Patch Available  (was: Open)

> Support revert for patch upgrades
> -
>
> Key: AMBARI-21241
> URL: https://issues.apache.org/jira/browse/AMBARI-21241
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-21241.patch
>
>
> Add the ability to specify that a previous patch needs to be reverted to the 
> original repository.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21241) Support revert for patch upgrades

[Nate Cole (JIRA)]

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

Nate Cole updated AMBARI-21241:
---
Attachment: AMBARI-21241.patch

> Support revert for patch upgrades
> -
>
> Key: AMBARI-21241
> URL: https://issues.apache.org/jira/browse/AMBARI-21241
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-21241.patch
>
>
> Add the ability to specify that a previous patch needs to be reverted to the 
> original repository.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21241) Support revert for patch upgrades

[Nate Cole (JIRA)]

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

Nate Cole updated AMBARI-21241:
---
Summary: Support revert for patch upgrades  (was: Support revert for 
patches)

> Support revert for patch upgrades
> -
>
> Key: AMBARI-21241
> URL: https://issues.apache.org/jira/browse/AMBARI-21241
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 3.0.0
>
>
> Add the ability to specify that a previous patch needs to be reverted to the 
> original repository.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (AMBARI-21241) Support revert for patches

[Nate Cole (JIRA)]

Nate Cole created AMBARI-21241:
--

 Summary: Support revert for patches
 Key: AMBARI-21241
 URL: https://issues.apache.org/jira/browse/AMBARI-21241
 Project: Ambari
  Issue Type: Task
  Components: ambari-server
Reporter: Nate Cole
Assignee: Nate Cole
Priority: Critical
 Fix For: 3.0.0


Add the ability to specify that a previous patch needs to be reverted to the 
original repository.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21240) Some topology request data retained after host removed

[Doroszlai, Attila (JIRA)]

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

Doroszlai, Attila updated AMBARI-21240:
---
Status: Patch Available  (was: In Progress)

> Some topology request data retained after host removed
> --
>
> Key: AMBARI-21240
> URL: https://issues.apache.org/jira/browse/AMBARI-21240
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.1
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0, 2.5.2
>
> Attachments: AMBARI-21240.patch
>
>
> {{TopologyRequest}} and {{TopologyLogicalRequest}} records are retained even 
> if no child {{TopologyHostRequest}} records are present anymore.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21240) Some topology request data retained after host removed

[Doroszlai, Attila (JIRA)]

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

Doroszlai, Attila updated AMBARI-21240:
---
Attachment: AMBARI-21240.patch

> Some topology request data retained after host removed
> --
>
> Key: AMBARI-21240
> URL: https://issues.apache.org/jira/browse/AMBARI-21240
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.1
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0, 2.5.2
>
> Attachments: AMBARI-21240.patch
>
>
> {{TopologyRequest}} and {{TopologyLogicalRequest}} records are retained even 
> if no child {{TopologyHostRequest}} records are present anymore.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (AMBARI-21240) Some topology request data retained after host removed

[Doroszlai, Attila (JIRA)]

Doroszlai, Attila created AMBARI-21240:
--

 Summary: Some topology request data retained after host removed
 Key: AMBARI-21240
 URL: https://issues.apache.org/jira/browse/AMBARI-21240
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.5.1
Reporter: Doroszlai, Attila
Assignee: Doroszlai, Attila
 Fix For: 3.0.0, 2.5.2


{{TopologyRequest}} and {{TopologyLogicalRequest}} records are retained even if 
no child {{TopologyHostRequest}} records are present anymore.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21239) Ambari leaves a lot of processes from Hive alert on the machine

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047980#comment-16047980
 ] 

Hudson commented on AMBARI-21239:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7622 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7622/])
AMBARI-21239. Ambari leaves a lot of processes from Hive alert on the 
(aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=31ac3c21b71868df4f4e2ac82e72defa79767bd6])
* (edit) 
ambari-common/src/main/python/resource_management/libraries/functions/hive_check.py
* (edit) 
ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_service_check.py


> Ambari leaves a lot of processes from Hive alert on the machine
> ---
>
> Key: AMBARI-21239
> URL: https://issues.apache.org/jira/browse/AMBARI-21239
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.2
>
> Attachments: AMBARI-21239.patch
>
>
> I had a running Ambari instance on version 2.5.1.0-105. Unfortunately i lost
> the database VM storing the metadata after the cluster had been runing for
> almost 2 weeks without issues. What I observed is that the instance in a few
> hours got really slow. Upon investigation found hundreds of Beeline processes
> like this:
> 
> 
> ambari-+ 3439770 3439769  0 06:19 ?00:00:00 -bash -c export  
> PATH='/usr/sbin:/sbin:/usr/lib/ambari-server/*:/sbin:/usr/sbin:/bin:/usr/bin:/var/lib/ambari-agent:/bin/:/usr/bin/:/usr/lib/hive/bin/:/usr/sbin/'
>  ; ! beeline -u 
> 'jdbc:hive2://ctr-e133-1493418528701-31316-01-08.hwx.site:10500/;transportMode=binary'
>   -e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL'
> ambari-+ 3439814 3439770  0 06:19 ?00:00:42 
> /usr/lib/jvm/java-openjdk/bin/java -Xmx1024m -Dhdp.version=2.6.1.0-64 
> -Djava.net.preferIPv4Stack=true -Dhdp.version=2.6.1.0-64 
> -Dhadoop.log.dir=/grid/0/log/hdfs/ambari-qa -Dhadoop.log.file=hadoop.log 
> -Dhadoop.home.dir=/usr/hdp/2.6.1.0-64/hadoop -Dhadoop.id.str=ambari-qa 
> -Dhadoop.root.logger=INFO,console 
> -Djava.library.path=:/usr/hdp/2.6.1.0-64/hadoop/lib/native/Linux-amd64-64:/usr/hdp/current/hadoop-client/lib/native/Linux-amd64-64:/usr/hdp/2.6.1.0-64/hadoop/lib/native
>  -Dhadoop.policy.file=hadoop-policy.xml -Djava.net.preferIPv4Stack=true 
> -Xmx1024m -Xmx1024m 
> -Djava.util.logging.config.file=/usr/hdp/2.6.1.0-64/hive/conf/parquet-logging.properties
>  -Dlog4j.configuration=beeline-log4j.properties 
> -Dhadoop.security.logger=INFO,NullAppender org.apache.hadoop.util.RunJar 
> /usr/hdp/2.6.1.0-64/hive/lib/hive-beeline-1.2.1000.2.6.1.0-64.jar 
> org.apache.hive.beeline.BeeLine -u 
> jdbc:hive2://ctr-e133-1493418528701-31316-01-08.hwx.site:10500/;transportMode=binary
>  -e
> ambari-+ 3439816 3439770  0 06:19 ?00:00:00 awk {print}
> ambari-+ 3439817 3439770  0 06:19 ?00:00:00 grep -i -e Connection 
> refused -e Invalid URL
> ambari-+ 3440645 3440644  0 06:22 ?00:00:00 -bash -c export  
> PATH='/usr/sbin:/sbin:/usr/lib/ambari-server/*:/sbin:/usr/sbin:/bin:/usr/bin:/var/lib/ambari-agent:/bin/:/usr/bin/:/usr/lib/hive/bin/:/usr/sbin/'
>  ; ! beeline -u 
> 'jdbc:hive2://ctr-e133-1493418528701-31316-01-08.hwx.site:10500/;transportMode=binary'
>   -e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL'
> ambari-+ 3440685 3440645  0 06:22 ?00:00:42 
> /usr/lib/jvm/java-openjdk/bin/java -Xmx1024m -Dhdp.version=2.6.1.0-64 
> -Djava.net.preferIPv4Stack=true -Dhdp.version=2.6.1.0-64 
> -Dhadoop.log.dir=/grid/0/log/hdfs/ambari-qa -Dhadoop.log.file=hadoop.log 
> -Dhadoop.home.dir=/usr/hdp/2.6.1.0-64/hadoop -Dhadoop.id.str=ambari-qa 
> -Dhadoop.root.logger=INFO,console 
> -Djava.library.path=:/usr/hdp/2.6.1.0-64/hadoop/lib/native/Linux-amd64-64:/usr/hdp/current/hadoop-client/lib/native/Linux-amd64-64:/usr/hdp/2.6.1.0-64/hadoop/lib/native
>  -Dhadoop.policy.file=hadoop-policy.xml -Djava.net.preferIPv4Stack=true 
> -Xmx1024m -Xmx1024m 
> -Djava.util.logging.config.file=/usr/hdp/2.6.1.0-64/hive/conf/parquet-logging.properties
>  -Dlog4j.configuration=beeline-log4j.properties 
> -Dhadoop.security.logger=INFO,NullAppender org.apache.hadoop.util.RunJar 
> /usr/hdp/2.6.1.0-64/hive/lib/hive-beeline-1.2.1000.2.6.1.0-64.jar 
> org.apache.hive.beeline.BeeLine -u 
> jdbc:hive2://ctr-e133-1493418528701-31316-01-08.hwx.site:10500/;transportMode=binary
>  -e
> ambari-+ 3440686 3440645  0 06:22 ?00:00:00 awk {print}
> ambari-+ 3440687 3440645  0 06:22 ?00:00:00 grep -i -e Connection 
> refused -e Invalid URL
> ambari-+ 3441185 3441184  0 06:25 ?00:00:00 -bash -c export  
> 

[jira] [Commented] (AMBARI-21239) Ambari leaves a lot of processes from Hive alert on the machine

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047960#comment-16047960
 ] 

Hadoop QA commented on AMBARI-21239:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12872871/AMBARI-21239.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/11647//console

This message is automatically generated.

> Ambari leaves a lot of processes from Hive alert on the machine
> ---
>
> Key: AMBARI-21239
> URL: https://issues.apache.org/jira/browse/AMBARI-21239
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.2
>
> Attachments: AMBARI-21239.patch
>
>
> I had a running Ambari instance on version 2.5.1.0-105. Unfortunately i lost
> the database VM storing the metadata after the cluster had been runing for
> almost 2 weeks without issues. What I observed is that the instance in a few
> hours got really slow. Upon investigation found hundreds of Beeline processes
> like this:
> 
> 
> ambari-+ 3439770 3439769  0 06:19 ?00:00:00 -bash -c export  
> PATH='/usr/sbin:/sbin:/usr/lib/ambari-server/*:/sbin:/usr/sbin:/bin:/usr/bin:/var/lib/ambari-agent:/bin/:/usr/bin/:/usr/lib/hive/bin/:/usr/sbin/'
>  ; ! beeline -u 
> 'jdbc:hive2://ctr-e133-1493418528701-31316-01-08.hwx.site:10500/;transportMode=binary'
>   -e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL'
> ambari-+ 3439814 3439770  0 06:19 ?00:00:42 
> /usr/lib/jvm/java-openjdk/bin/java -Xmx1024m -Dhdp.version=2.6.1.0-64 
> -Djava.net.preferIPv4Stack=true -Dhdp.version=2.6.1.0-64 
> -Dhadoop.log.dir=/grid/0/log/hdfs/ambari-qa -Dhadoop.log.file=hadoop.log 
> -Dhadoop.home.dir=/usr/hdp/2.6.1.0-64/hadoop -Dhadoop.id.str=ambari-qa 
> -Dhadoop.root.logger=INFO,console 
> -Djava.library.path=:/usr/hdp/2.6.1.0-64/hadoop/lib/native/Linux-amd64-64:/usr/hdp/current/hadoop-client/lib/native/Linux-amd64-64:/usr/hdp/2.6.1.0-64/hadoop/lib/native
>  -Dhadoop.policy.file=hadoop-policy.xml -Djava.net.preferIPv4Stack=true 
> -Xmx1024m -Xmx1024m 
> -Djava.util.logging.config.file=/usr/hdp/2.6.1.0-64/hive/conf/parquet-logging.properties
>  -Dlog4j.configuration=beeline-log4j.properties 
> -Dhadoop.security.logger=INFO,NullAppender org.apache.hadoop.util.RunJar 
> /usr/hdp/2.6.1.0-64/hive/lib/hive-beeline-1.2.1000.2.6.1.0-64.jar 
> org.apache.hive.beeline.BeeLine -u 
> jdbc:hive2://ctr-e133-1493418528701-31316-01-08.hwx.site:10500/;transportMode=binary
>  -e
> ambari-+ 3439816 3439770  0 06:19 ?00:00:00 awk {print}
> ambari-+ 3439817 3439770  0 06:19 ?00:00:00 grep -i -e Connection 
> refused -e Invalid URL
> ambari-+ 3440645 3440644  0 06:22 ?00:00:00 -bash -c export  
> PATH='/usr/sbin:/sbin:/usr/lib/ambari-server/*:/sbin:/usr/sbin:/bin:/usr/bin:/var/lib/ambari-agent:/bin/:/usr/bin/:/usr/lib/hive/bin/:/usr/sbin/'
>  ; ! beeline -u 
> 'jdbc:hive2://ctr-e133-1493418528701-31316-01-08.hwx.site:10500/;transportMode=binary'
>   -e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL'
> ambari-+ 3440685 3440645  0 06:22 ?00:00:42 
> /usr/lib/jvm/java-openjdk/bin/java -Xmx1024m -Dhdp.version=2.6.1.0-64 
> -Djava.net.preferIPv4Stack=true -Dhdp.version=2.6.1.0-64 
> -Dhadoop.log.dir=/grid/0/log/hdfs/ambari-qa -Dhadoop.log.file=hadoop.log 
> -Dhadoop.home.dir=/usr/hdp/2.6.1.0-64/hadoop -Dhadoop.id.str=ambari-qa 
> -Dhadoop.root.logger=INFO,console 
> -Djava.library.path=:/usr/hdp/2.6.1.0-64/hadoop/lib/native/Linux-amd64-64:/usr/hdp/current/hadoop-client/lib/native/Linux-amd64-64:/usr/hdp/2.6.1.0-64/hadoop/lib/native
>  -Dhadoop.policy.file=hadoop-policy.xml -Djava.net.preferIPv4Stack=true 
> -Xmx1024m -Xmx1024m 
> -Djava.util.logging.config.file=/usr/hdp/2.6.1.0-64/hive/conf/parquet-logging.properties
>  -Dlog4j.configuration=beeline-log4j.properties 
> -Dhadoop.security.logger=INFO,NullAppender org.apache.hadoop.util.RunJar 
> /usr/hdp/2.6.1.0-64/hive/lib/hive-beeline-1.2.1000.2.6.1.0-64.jar 
> org.apache.hive.beeline.BeeLine -u 
> 

[jira] [Commented] (AMBARI-21233) ambari-web hits JS error in dev mode

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047949#comment-16047949
 ] 

Hudson commented on AMBARI-21233:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7621 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7621/])
AMBARI-21233. ambari-web hits JS error in dev mode (alexantonenko) (hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f80c6ee45b5c6708aa9db98b9afe7ebbeba2afe7])
* (edit) ambari-web/app/controllers/global/cluster_controller.js
* (edit) ambari-web/app/mappers/repository_version_mapper.js
* (edit) ambari-web/test/controllers/wizard/step8_test.js
* (edit) ambari-web/app/controllers/global/user_settings_controller.js
* (edit) ambari-web/test/views/main/dashboard/widgets_test.js
* (edit) ambari-web/app/views/main/dashboard/widgets.js
* (edit) ambari-web/app/utils/ajax/ajax.js


> 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
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-21233.patch
>
>
> http://localhost: hits JS several error and dashboard does not show up



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21229) Logical Request: Provision Cluster API request status updated as COMPLETED as soon as BP deploy starts

[Sandor Magyari (JIRA)]

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

Sandor Magyari updated AMBARI-21229:

Attachment: AMBARI-21229.patch

> Logical Request: Provision Cluster API request status updated as COMPLETED as 
> soon as BP deploy starts
> --
>
> Key: AMBARI-21229
> URL: https://issues.apache.org/jira/browse/AMBARI-21229
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21229.patch
>
>
> Logical Request: Provision Cluster API request status updates as COMPLETED as 
> soon as BP deploy starts instead of IN_PROGRESS.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21239) Ambari leaves a lot of processes from Hive alert on the machine

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-21239:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk and branch-2.5

> Ambari leaves a lot of processes from Hive alert on the machine
> ---
>
> Key: AMBARI-21239
> URL: https://issues.apache.org/jira/browse/AMBARI-21239
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.2
>
> Attachments: AMBARI-21239.patch
>
>
> I had a running Ambari instance on version 2.5.1.0-105. Unfortunately i lost
> the database VM storing the metadata after the cluster had been runing for
> almost 2 weeks without issues. What I observed is that the instance in a few
> hours got really slow. Upon investigation found hundreds of Beeline processes
> like this:
> 
> 
> ambari-+ 3439770 3439769  0 06:19 ?00:00:00 -bash -c export  
> PATH='/usr/sbin:/sbin:/usr/lib/ambari-server/*:/sbin:/usr/sbin:/bin:/usr/bin:/var/lib/ambari-agent:/bin/:/usr/bin/:/usr/lib/hive/bin/:/usr/sbin/'
>  ; ! beeline -u 
> 'jdbc:hive2://ctr-e133-1493418528701-31316-01-08.hwx.site:10500/;transportMode=binary'
>   -e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL'
> ambari-+ 3439814 3439770  0 06:19 ?00:00:42 
> /usr/lib/jvm/java-openjdk/bin/java -Xmx1024m -Dhdp.version=2.6.1.0-64 
> -Djava.net.preferIPv4Stack=true -Dhdp.version=2.6.1.0-64 
> -Dhadoop.log.dir=/grid/0/log/hdfs/ambari-qa -Dhadoop.log.file=hadoop.log 
> -Dhadoop.home.dir=/usr/hdp/2.6.1.0-64/hadoop -Dhadoop.id.str=ambari-qa 
> -Dhadoop.root.logger=INFO,console 
> -Djava.library.path=:/usr/hdp/2.6.1.0-64/hadoop/lib/native/Linux-amd64-64:/usr/hdp/current/hadoop-client/lib/native/Linux-amd64-64:/usr/hdp/2.6.1.0-64/hadoop/lib/native
>  -Dhadoop.policy.file=hadoop-policy.xml -Djava.net.preferIPv4Stack=true 
> -Xmx1024m -Xmx1024m 
> -Djava.util.logging.config.file=/usr/hdp/2.6.1.0-64/hive/conf/parquet-logging.properties
>  -Dlog4j.configuration=beeline-log4j.properties 
> -Dhadoop.security.logger=INFO,NullAppender org.apache.hadoop.util.RunJar 
> /usr/hdp/2.6.1.0-64/hive/lib/hive-beeline-1.2.1000.2.6.1.0-64.jar 
> org.apache.hive.beeline.BeeLine -u 
> jdbc:hive2://ctr-e133-1493418528701-31316-01-08.hwx.site:10500/;transportMode=binary
>  -e
> ambari-+ 3439816 3439770  0 06:19 ?00:00:00 awk {print}
> ambari-+ 3439817 3439770  0 06:19 ?00:00:00 grep -i -e Connection 
> refused -e Invalid URL
> ambari-+ 3440645 3440644  0 06:22 ?00:00:00 -bash -c export  
> PATH='/usr/sbin:/sbin:/usr/lib/ambari-server/*:/sbin:/usr/sbin:/bin:/usr/bin:/var/lib/ambari-agent:/bin/:/usr/bin/:/usr/lib/hive/bin/:/usr/sbin/'
>  ; ! beeline -u 
> 'jdbc:hive2://ctr-e133-1493418528701-31316-01-08.hwx.site:10500/;transportMode=binary'
>   -e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL'
> ambari-+ 3440685 3440645  0 06:22 ?00:00:42 
> /usr/lib/jvm/java-openjdk/bin/java -Xmx1024m -Dhdp.version=2.6.1.0-64 
> -Djava.net.preferIPv4Stack=true -Dhdp.version=2.6.1.0-64 
> -Dhadoop.log.dir=/grid/0/log/hdfs/ambari-qa -Dhadoop.log.file=hadoop.log 
> -Dhadoop.home.dir=/usr/hdp/2.6.1.0-64/hadoop -Dhadoop.id.str=ambari-qa 
> -Dhadoop.root.logger=INFO,console 
> -Djava.library.path=:/usr/hdp/2.6.1.0-64/hadoop/lib/native/Linux-amd64-64:/usr/hdp/current/hadoop-client/lib/native/Linux-amd64-64:/usr/hdp/2.6.1.0-64/hadoop/lib/native
>  -Dhadoop.policy.file=hadoop-policy.xml -Djava.net.preferIPv4Stack=true 
> -Xmx1024m -Xmx1024m 
> -Djava.util.logging.config.file=/usr/hdp/2.6.1.0-64/hive/conf/parquet-logging.properties
>  -Dlog4j.configuration=beeline-log4j.properties 
> -Dhadoop.security.logger=INFO,NullAppender org.apache.hadoop.util.RunJar 
> /usr/hdp/2.6.1.0-64/hive/lib/hive-beeline-1.2.1000.2.6.1.0-64.jar 
> org.apache.hive.beeline.BeeLine -u 
> jdbc:hive2://ctr-e133-1493418528701-31316-01-08.hwx.site:10500/;transportMode=binary
>  -e
> ambari-+ 3440686 3440645  0 06:22 ?00:00:00 awk {print}
> ambari-+ 3440687 3440645  0 06:22 ?00:00:00 grep -i -e Connection 
> refused -e Invalid URL
> ambari-+ 3441185 3441184  0 06:25 ?00:00:00 -bash -c export  
> PATH='/usr/sbin:/sbin:/usr/lib/ambari-server/*:/sbin:/usr/sbin:/bin:/usr/bin:/var/lib/ambari-agent:/bin/:/usr/bin/:/usr/lib/hive/bin/:/usr/sbin/'
>  ; ! beeline -u 
> 'jdbc:hive2://ctr-e133-1493418528701-31316-01-08.hwx.site:10500/;transportMode=binary'
>   -e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL'
> ambari-+ 3441224 3441185  0 06:25 ?00:00:46 
> /usr/lib/jvm/java-openjdk/bin/java -Xmx1024m -Dhdp.version=2.6.1.0-64 
> 

[jira] [Updated] (AMBARI-21229) Logical Request: Provision Cluster API request status updated as COMPLETED as soon as BP deploy starts

[Sandor Magyari (JIRA)]

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

Sandor Magyari updated AMBARI-21229:

Attachment: (was: AMBARI-21229.patch)

> Logical Request: Provision Cluster API request status updated as COMPLETED as 
> soon as BP deploy starts
> --
>
> Key: AMBARI-21229
> URL: https://issues.apache.org/jira/browse/AMBARI-21229
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
>Priority: Blocker
> Fix For: 2.5.2
>
>
> Logical Request: Provision Cluster API request status updates as COMPLETED as 
> soon as BP deploy starts instead of IN_PROGRESS.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (AMBARI-21239) Ambari leaves a lot of processes from Hive alert on the machine

[Andrew Onischuk (JIRA)]

Andrew Onischuk created AMBARI-21239:


 Summary: Ambari leaves a lot of processes from Hive alert on the 
machine
 Key: AMBARI-21239
 URL: https://issues.apache.org/jira/browse/AMBARI-21239
 Project: Ambari
  Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
 Fix For: 2.5.2


I had a running Ambari instance on version 2.5.1.0-105. Unfortunately i lost
the database VM storing the metadata after the cluster had been runing for
almost 2 weeks without issues. What I observed is that the instance in a few
hours got really slow. Upon investigation found hundreds of Beeline processes
like this:



ambari-+ 3439770 3439769  0 06:19 ?00:00:00 -bash -c export  
PATH='/usr/sbin:/sbin:/usr/lib/ambari-server/*:/sbin:/usr/sbin:/bin:/usr/bin:/var/lib/ambari-agent:/bin/:/usr/bin/:/usr/lib/hive/bin/:/usr/sbin/'
 ; ! beeline -u 
'jdbc:hive2://ctr-e133-1493418528701-31316-01-08.hwx.site:10500/;transportMode=binary'
  -e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL'
ambari-+ 3439814 3439770  0 06:19 ?00:00:42 
/usr/lib/jvm/java-openjdk/bin/java -Xmx1024m -Dhdp.version=2.6.1.0-64 
-Djava.net.preferIPv4Stack=true -Dhdp.version=2.6.1.0-64 
-Dhadoop.log.dir=/grid/0/log/hdfs/ambari-qa -Dhadoop.log.file=hadoop.log 
-Dhadoop.home.dir=/usr/hdp/2.6.1.0-64/hadoop -Dhadoop.id.str=ambari-qa 
-Dhadoop.root.logger=INFO,console 
-Djava.library.path=:/usr/hdp/2.6.1.0-64/hadoop/lib/native/Linux-amd64-64:/usr/hdp/current/hadoop-client/lib/native/Linux-amd64-64:/usr/hdp/2.6.1.0-64/hadoop/lib/native
 -Dhadoop.policy.file=hadoop-policy.xml -Djava.net.preferIPv4Stack=true 
-Xmx1024m -Xmx1024m 
-Djava.util.logging.config.file=/usr/hdp/2.6.1.0-64/hive/conf/parquet-logging.properties
 -Dlog4j.configuration=beeline-log4j.properties 
-Dhadoop.security.logger=INFO,NullAppender org.apache.hadoop.util.RunJar 
/usr/hdp/2.6.1.0-64/hive/lib/hive-beeline-1.2.1000.2.6.1.0-64.jar 
org.apache.hive.beeline.BeeLine -u 
jdbc:hive2://ctr-e133-1493418528701-31316-01-08.hwx.site:10500/;transportMode=binary
 -e
ambari-+ 3439816 3439770  0 06:19 ?00:00:00 awk {print}
ambari-+ 3439817 3439770  0 06:19 ?00:00:00 grep -i -e Connection 
refused -e Invalid URL
ambari-+ 3440645 3440644  0 06:22 ?00:00:00 -bash -c export  
PATH='/usr/sbin:/sbin:/usr/lib/ambari-server/*:/sbin:/usr/sbin:/bin:/usr/bin:/var/lib/ambari-agent:/bin/:/usr/bin/:/usr/lib/hive/bin/:/usr/sbin/'
 ; ! beeline -u 
'jdbc:hive2://ctr-e133-1493418528701-31316-01-08.hwx.site:10500/;transportMode=binary'
  -e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL'
ambari-+ 3440685 3440645  0 06:22 ?00:00:42 
/usr/lib/jvm/java-openjdk/bin/java -Xmx1024m -Dhdp.version=2.6.1.0-64 
-Djava.net.preferIPv4Stack=true -Dhdp.version=2.6.1.0-64 
-Dhadoop.log.dir=/grid/0/log/hdfs/ambari-qa -Dhadoop.log.file=hadoop.log 
-Dhadoop.home.dir=/usr/hdp/2.6.1.0-64/hadoop -Dhadoop.id.str=ambari-qa 
-Dhadoop.root.logger=INFO,console 
-Djava.library.path=:/usr/hdp/2.6.1.0-64/hadoop/lib/native/Linux-amd64-64:/usr/hdp/current/hadoop-client/lib/native/Linux-amd64-64:/usr/hdp/2.6.1.0-64/hadoop/lib/native
 -Dhadoop.policy.file=hadoop-policy.xml -Djava.net.preferIPv4Stack=true 
-Xmx1024m -Xmx1024m 
-Djava.util.logging.config.file=/usr/hdp/2.6.1.0-64/hive/conf/parquet-logging.properties
 -Dlog4j.configuration=beeline-log4j.properties 
-Dhadoop.security.logger=INFO,NullAppender org.apache.hadoop.util.RunJar 
/usr/hdp/2.6.1.0-64/hive/lib/hive-beeline-1.2.1000.2.6.1.0-64.jar 
org.apache.hive.beeline.BeeLine -u 
jdbc:hive2://ctr-e133-1493418528701-31316-01-08.hwx.site:10500/;transportMode=binary
 -e
ambari-+ 3440686 3440645  0 06:22 ?00:00:00 awk {print}
ambari-+ 3440687 3440645  0 06:22 ?00:00:00 grep -i -e Connection 
refused -e Invalid URL
ambari-+ 3441185 3441184  0 06:25 ?00:00:00 -bash -c export  
PATH='/usr/sbin:/sbin:/usr/lib/ambari-server/*:/sbin:/usr/sbin:/bin:/usr/bin:/var/lib/ambari-agent:/bin/:/usr/bin/:/usr/lib/hive/bin/:/usr/sbin/'
 ; ! beeline -u 
'jdbc:hive2://ctr-e133-1493418528701-31316-01-08.hwx.site:10500/;transportMode=binary'
  -e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL'
ambari-+ 3441224 3441185  0 06:25 ?00:00:46 
/usr/lib/jvm/java-openjdk/bin/java -Xmx1024m -Dhdp.version=2.6.1.0-64 
-Djava.net.preferIPv4Stack=true -Dhdp.version=2.6.1.0-64 
-Dhadoop.log.dir=/grid/0/log/hdfs/ambari-qa -Dhadoop.log.file=hadoop.log 
-Dhadoop.home.dir=/usr/hdp/2.6.1.0-64/hadoop -Dhadoop.id.str=ambari-qa 
-Dhadoop.root.logger=INFO,console 
-Djava.library.path=:/usr/hdp/2.6.1.0-64/hadoop/lib/native/Linux-amd64-64:/usr/hdp/current/hadoop-client/lib/native/Linux-amd64-64:/usr/hdp/2.6.1.0-64/hadoop/lib/native
 -Dhadoop.policy.file=hadoop-policy.xml 

[jira] [Updated] (AMBARI-21239) Ambari leaves a lot of processes from Hive alert on the machine

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-21239:
-
Attachment: AMBARI-21239.patch

> Ambari leaves a lot of processes from Hive alert on the machine
> ---
>
> Key: AMBARI-21239
> URL: https://issues.apache.org/jira/browse/AMBARI-21239
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.2
>
> Attachments: AMBARI-21239.patch
>
>
> I had a running Ambari instance on version 2.5.1.0-105. Unfortunately i lost
> the database VM storing the metadata after the cluster had been runing for
> almost 2 weeks without issues. What I observed is that the instance in a few
> hours got really slow. Upon investigation found hundreds of Beeline processes
> like this:
> 
> 
> ambari-+ 3439770 3439769  0 06:19 ?00:00:00 -bash -c export  
> PATH='/usr/sbin:/sbin:/usr/lib/ambari-server/*:/sbin:/usr/sbin:/bin:/usr/bin:/var/lib/ambari-agent:/bin/:/usr/bin/:/usr/lib/hive/bin/:/usr/sbin/'
>  ; ! beeline -u 
> 'jdbc:hive2://ctr-e133-1493418528701-31316-01-08.hwx.site:10500/;transportMode=binary'
>   -e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL'
> ambari-+ 3439814 3439770  0 06:19 ?00:00:42 
> /usr/lib/jvm/java-openjdk/bin/java -Xmx1024m -Dhdp.version=2.6.1.0-64 
> -Djava.net.preferIPv4Stack=true -Dhdp.version=2.6.1.0-64 
> -Dhadoop.log.dir=/grid/0/log/hdfs/ambari-qa -Dhadoop.log.file=hadoop.log 
> -Dhadoop.home.dir=/usr/hdp/2.6.1.0-64/hadoop -Dhadoop.id.str=ambari-qa 
> -Dhadoop.root.logger=INFO,console 
> -Djava.library.path=:/usr/hdp/2.6.1.0-64/hadoop/lib/native/Linux-amd64-64:/usr/hdp/current/hadoop-client/lib/native/Linux-amd64-64:/usr/hdp/2.6.1.0-64/hadoop/lib/native
>  -Dhadoop.policy.file=hadoop-policy.xml -Djava.net.preferIPv4Stack=true 
> -Xmx1024m -Xmx1024m 
> -Djava.util.logging.config.file=/usr/hdp/2.6.1.0-64/hive/conf/parquet-logging.properties
>  -Dlog4j.configuration=beeline-log4j.properties 
> -Dhadoop.security.logger=INFO,NullAppender org.apache.hadoop.util.RunJar 
> /usr/hdp/2.6.1.0-64/hive/lib/hive-beeline-1.2.1000.2.6.1.0-64.jar 
> org.apache.hive.beeline.BeeLine -u 
> jdbc:hive2://ctr-e133-1493418528701-31316-01-08.hwx.site:10500/;transportMode=binary
>  -e
> ambari-+ 3439816 3439770  0 06:19 ?00:00:00 awk {print}
> ambari-+ 3439817 3439770  0 06:19 ?00:00:00 grep -i -e Connection 
> refused -e Invalid URL
> ambari-+ 3440645 3440644  0 06:22 ?00:00:00 -bash -c export  
> PATH='/usr/sbin:/sbin:/usr/lib/ambari-server/*:/sbin:/usr/sbin:/bin:/usr/bin:/var/lib/ambari-agent:/bin/:/usr/bin/:/usr/lib/hive/bin/:/usr/sbin/'
>  ; ! beeline -u 
> 'jdbc:hive2://ctr-e133-1493418528701-31316-01-08.hwx.site:10500/;transportMode=binary'
>   -e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL'
> ambari-+ 3440685 3440645  0 06:22 ?00:00:42 
> /usr/lib/jvm/java-openjdk/bin/java -Xmx1024m -Dhdp.version=2.6.1.0-64 
> -Djava.net.preferIPv4Stack=true -Dhdp.version=2.6.1.0-64 
> -Dhadoop.log.dir=/grid/0/log/hdfs/ambari-qa -Dhadoop.log.file=hadoop.log 
> -Dhadoop.home.dir=/usr/hdp/2.6.1.0-64/hadoop -Dhadoop.id.str=ambari-qa 
> -Dhadoop.root.logger=INFO,console 
> -Djava.library.path=:/usr/hdp/2.6.1.0-64/hadoop/lib/native/Linux-amd64-64:/usr/hdp/current/hadoop-client/lib/native/Linux-amd64-64:/usr/hdp/2.6.1.0-64/hadoop/lib/native
>  -Dhadoop.policy.file=hadoop-policy.xml -Djava.net.preferIPv4Stack=true 
> -Xmx1024m -Xmx1024m 
> -Djava.util.logging.config.file=/usr/hdp/2.6.1.0-64/hive/conf/parquet-logging.properties
>  -Dlog4j.configuration=beeline-log4j.properties 
> -Dhadoop.security.logger=INFO,NullAppender org.apache.hadoop.util.RunJar 
> /usr/hdp/2.6.1.0-64/hive/lib/hive-beeline-1.2.1000.2.6.1.0-64.jar 
> org.apache.hive.beeline.BeeLine -u 
> jdbc:hive2://ctr-e133-1493418528701-31316-01-08.hwx.site:10500/;transportMode=binary
>  -e
> ambari-+ 3440686 3440645  0 06:22 ?00:00:00 awk {print}
> ambari-+ 3440687 3440645  0 06:22 ?00:00:00 grep -i -e Connection 
> refused -e Invalid URL
> ambari-+ 3441185 3441184  0 06:25 ?00:00:00 -bash -c export  
> PATH='/usr/sbin:/sbin:/usr/lib/ambari-server/*:/sbin:/usr/sbin:/bin:/usr/bin:/var/lib/ambari-agent:/bin/:/usr/bin/:/usr/lib/hive/bin/:/usr/sbin/'
>  ; ! beeline -u 
> 'jdbc:hive2://ctr-e133-1493418528701-31316-01-08.hwx.site:10500/;transportMode=binary'
>   -e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL'
> ambari-+ 3441224 3441185  0 06:25 ?00:00:46 
> /usr/lib/jvm/java-openjdk/bin/java -Xmx1024m -Dhdp.version=2.6.1.0-64 
> -Djava.net.preferIPv4Stack=true -Dhdp.version=2.6.1.0-64 
> 

[jira] [Updated] (AMBARI-21236) Principal placeholder replacement in kerberos.json doesn't work with blueprint installs

[Attila Magyar (JIRA)]

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

Attila Magyar updated AMBARI-21236:
---
Attachment: AMBARI-21236_branch-2.5.patch
AMBARI-21236_trunk.patch

> Principal placeholder replacement in kerberos.json doesn't work with 
> blueprint installs
> ---
>
> Key: AMBARI-21236
> URL: https://issues.apache.org/jira/browse/AMBARI-21236
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Attila Magyar
>Assignee: Attila Magyar
> Fix For: 2.5.2
>
> Attachments: AMBARI-21236_branch-2.5.patch, AMBARI-21236_trunk.patch
>
>
> Kerberos principal placeholders like
> {code}
> sasl:${principals/YARN/RESOURCEMANAGER/resource_manager_rm|principalPrimary()}:rwcda
> {code}
> are not getting replaced if the cluster is created with blueprints 
> (kerberos=enabled).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21236) Principal placeholder replacement in kerberos.json doesn't work with blueprint installs

[Attila Magyar (JIRA)]

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

Attila Magyar updated AMBARI-21236:
---
Attachment: (was: AMBARI-21236_branch-2.5.patch)

> Principal placeholder replacement in kerberos.json doesn't work with 
> blueprint installs
> ---
>
> Key: AMBARI-21236
> URL: https://issues.apache.org/jira/browse/AMBARI-21236
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Attila Magyar
>Assignee: Attila Magyar
> Fix For: 2.5.2
>
>
> Kerberos principal placeholders like
> {code}
> sasl:${principals/YARN/RESOURCEMANAGER/resource_manager_rm|principalPrimary()}:rwcda
> {code}
> are not getting replaced if the cluster is created with blueprints 
> (kerberos=enabled).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21236) Principal placeholder replacement in kerberos.json doesn't work with blueprint installs

[Attila Magyar (JIRA)]

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

Attila Magyar updated AMBARI-21236:
---
Attachment: (was: AMBARI-21236_trunk.patch)

> Principal placeholder replacement in kerberos.json doesn't work with 
> blueprint installs
> ---
>
> Key: AMBARI-21236
> URL: https://issues.apache.org/jira/browse/AMBARI-21236
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Attila Magyar
>Assignee: Attila Magyar
> Fix For: 2.5.2
>
>
> Kerberos principal placeholders like
> {code}
> sasl:${principals/YARN/RESOURCEMANAGER/resource_manager_rm|principalPrimary()}:rwcda
> {code}
> are not getting replaced if the cluster is created with blueprints 
> (kerberos=enabled).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21236) Principal placeholder replacement in kerberos.json doesn't work with blueprint installs

[Attila Magyar (JIRA)]

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

Attila Magyar updated AMBARI-21236:
---
Attachment: (was: AMBARI-21236_trunk.patch)

> Principal placeholder replacement in kerberos.json doesn't work with 
> blueprint installs
> ---
>
> Key: AMBARI-21236
> URL: https://issues.apache.org/jira/browse/AMBARI-21236
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Attila Magyar
>Assignee: Attila Magyar
> Fix For: 2.5.2
>
>
> Kerberos principal placeholders like
> {code}
> sasl:${principals/YARN/RESOURCEMANAGER/resource_manager_rm|principalPrimary()}:rwcda
> {code}
> are not getting replaced if the cluster is created with blueprints 
> (kerberos=enabled).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21236) Principal placeholder replacement in kerberos.json doesn't work with blueprint installs

[Attila Magyar (JIRA)]

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

Attila Magyar updated AMBARI-21236:
---
Attachment: AMBARI-21236_branch-2.5.patch
AMBARI-21236_trunk.patch

> Principal placeholder replacement in kerberos.json doesn't work with 
> blueprint installs
> ---
>
> Key: AMBARI-21236
> URL: https://issues.apache.org/jira/browse/AMBARI-21236
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Attila Magyar
>Assignee: Attila Magyar
> Fix For: 2.5.2
>
> Attachments: AMBARI-21236_branch-2.5.patch, AMBARI-21236_trunk.patch, 
> AMBARI-21236_trunk.patch
>
>
> Kerberos principal placeholders like
> {code}
> sasl:${principals/YARN/RESOURCEMANAGER/resource_manager_rm|principalPrimary()}:rwcda
> {code}
> are not getting replaced if the cluster is created with blueprints 
> (kerberos=enabled).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21236) Principal placeholder replacement in kerberos.json doesn't work with blueprint installs

[Attila Magyar (JIRA)]

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

Attila Magyar updated AMBARI-21236:
---
Attachment: AMBARI-21236_trunk.patch

> Principal placeholder replacement in kerberos.json doesn't work with 
> blueprint installs
> ---
>
> Key: AMBARI-21236
> URL: https://issues.apache.org/jira/browse/AMBARI-21236
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Attila Magyar
>Assignee: Attila Magyar
> Fix For: 2.5.2
>
> Attachments: AMBARI-21236_trunk.patch
>
>
> Kerberos principal placeholders like
> {code}
> sasl:${principals/YARN/RESOURCEMANAGER/resource_manager_rm|principalPrimary()}:rwcda
> {code}
> are not getting replaced if the cluster is created with blueprints 
> (kerberos=enabled).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21236) Principal placeholder replacement in kerberos.json doesn't work with blueprint installs

[Attila Magyar (JIRA)]

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

Attila Magyar updated AMBARI-21236:
---
Attachment: (was: AMBARI-21236.patch)

> Principal placeholder replacement in kerberos.json doesn't work with 
> blueprint installs
> ---
>
> Key: AMBARI-21236
> URL: https://issues.apache.org/jira/browse/AMBARI-21236
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Attila Magyar
>Assignee: Attila Magyar
> Fix For: 2.5.2
>
> Attachments: AMBARI-21236_trunk.patch
>
>
> Kerberos principal placeholders like
> {code}
> sasl:${principals/YARN/RESOURCEMANAGER/resource_manager_rm|principalPrimary()}:rwcda
> {code}
> are not getting replaced if the cluster is created with blueprints 
> (kerberos=enabled).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21233) ambari-web hits JS error in dev mode

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander updated AMBARI-21233:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

committed to trunk

> 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
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-21233.patch
>
>
> http://localhost: hits JS several error and dashboard does not show up



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21238) Kafka userprincipal to shortname is not using AUTH_TO_LOCAL rules for authorization

[Eugene Chekanskiy (JIRA)]

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

Eugene Chekanskiy updated AMBARI-21238:
---
Status: Patch Available  (was: Open)

> Kafka userprincipal to shortname is not using AUTH_TO_LOCAL rules for 
> authorization
> ---
>
> Key: AMBARI-21238
> URL: https://issues.apache.org/jira/browse/AMBARI-21238
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Eugene Chekanskiy
>Assignee: Eugene Chekanskiy
> Fix For: 2.5.2
>
> Attachments: AMBARI-21238.branch-2.5.patch, AMBARI-21238.trunk.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21238) Kafka userprincipal to shortname is not using AUTH_TO_LOCAL rules for authorization

[Eugene Chekanskiy (JIRA)]

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

Eugene Chekanskiy updated AMBARI-21238:
---
Attachment: AMBARI-21238.branch-2.5.patch

> Kafka userprincipal to shortname is not using AUTH_TO_LOCAL rules for 
> authorization
> ---
>
> Key: AMBARI-21238
> URL: https://issues.apache.org/jira/browse/AMBARI-21238
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Eugene Chekanskiy
>Assignee: Eugene Chekanskiy
> Fix For: 2.5.2
>
> Attachments: AMBARI-21238.branch-2.5.patch, AMBARI-21238.trunk.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21238) Kafka userprincipal to shortname is not using AUTH_TO_LOCAL rules for authorization

[Eugene Chekanskiy (JIRA)]

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

Eugene Chekanskiy updated AMBARI-21238:
---
Attachment: AMBARI-21238.trunk.patch

> Kafka userprincipal to shortname is not using AUTH_TO_LOCAL rules for 
> authorization
> ---
>
> Key: AMBARI-21238
> URL: https://issues.apache.org/jira/browse/AMBARI-21238
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Eugene Chekanskiy
>Assignee: Eugene Chekanskiy
> Fix For: 2.5.2
>
> Attachments: AMBARI-21238.branch-2.5.patch, AMBARI-21238.trunk.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (AMBARI-21238) Kafka userprincipal to shortname is not using AUTH_TO_LOCAL rules for authorization

[Eugene Chekanskiy (JIRA)]

Eugene Chekanskiy created AMBARI-21238:
--

 Summary: Kafka userprincipal to shortname is not using 
AUTH_TO_LOCAL rules for authorization
 Key: AMBARI-21238
 URL: https://issues.apache.org/jira/browse/AMBARI-21238
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Reporter: Eugene Chekanskiy
Assignee: Eugene Chekanskiy
 Fix For: 2.5.2






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21228) Rename userconfig resource to event history in Log Search Portal

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047855#comment-16047855
 ] 

Hudson commented on AMBARI-21228:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7620 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7620/])
AMBARI-21228. Rename userconfig resource to event history in Log Search 
(oleewere: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=fc00b2caf927d083c70812bf1552aafa68958d1f])
* (delete) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/dao/UserConfigSolrDao.java
* (add) 
ambari-logsearch/ambari-logsearch-server/src/test/java/org/apache/ambari/logsearch/converter/EventHistoryRequestQueryConverterTest.java
* (delete) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/conf/global/SolrUserConfigState.java
* (add) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/request/impl/EventHistoryRequest.java
* (add) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/response/EventHistoryDataListResponse.java
* (edit) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/solr/SolrConstants.java
* (add) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/conf/SolrEventHistoryPropsConfig.java
* (add) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/response/EventHistoryData.java
* (add) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/conf/global/SolrEventHistoryState.java
* (delete) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/response/UserConfigData.java
* (delete) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/request/impl/UserConfigRequest.java
* (delete) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/rest/UserConfigResource.java
* (delete) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/response/UserConfigDataListResponse.java
* (add) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/request/EventHistoryParamDefinition.java
* (delete) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/converter/UserConfigRequestQueryConverter.java
* (edit) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/conf/SolrConfig.java
* (delete) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/web/filters/LogsearchUserConfigStateFilter.java
* (add) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/dao/EventHistorySolrDao.java
* (edit) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/dao/SolrSchemaFieldDao.java
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/main/webapp/scripts/model_bases/VUserFilterBase.js
* (add) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/converter/EventHistoryRequestQueryConverter.java
* (edit) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/rest/StatusResource.java
* (edit) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/doc/DocConstants.java
* (edit) 
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/common/LogFeederConstants.java
* (delete) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/conf/SolrUserPropsConfig.java
* (add) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/rest/EventHistoryResource.java
* (delete) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/request/UserConfigParamDefinition.java
* (edit) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/conf/SecurityConfig.java
* (add) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/manager/EventHistoryManager.java
* (delete) 
ambari-logsearch/ambari-logsearch-server/src/test/java/org/apache/ambari/logsearch/converter/UserConfigRequestQueryConverterTest.java
* (delete) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/manager/UserConfigManager.java
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/main/webapp/scripts/views/common/Header.js
* (add) 
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/web/filters/LogsearchEventHistoryStateFilter.java
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/main/webapp/scripts/collection_bases/VEventHistoryListBase.js


> Rename userconfig resource to event history in Log Search Portal
> 

[jira] [Commented] (AMBARI-21233) ambari-web hits JS error in dev mode

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047848#comment-16047848
 ] 

Hadoop QA commented on AMBARI-21233:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12872850/AMBARI-21233.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 2 new 
or modified test files.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-web.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/11646//console

This message is automatically generated.

> 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
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-21233.patch
>
>
> http://localhost: hits JS several error and dashboard does not show up



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21236) Principal placeholder replacement in kerberos.json doesn't work with blueprint installs

[Attila Magyar (JIRA)]

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

Attila Magyar updated AMBARI-21236:
---
Status: Patch Available  (was: Open)

> Principal placeholder replacement in kerberos.json doesn't work with 
> blueprint installs
> ---
>
> Key: AMBARI-21236
> URL: https://issues.apache.org/jira/browse/AMBARI-21236
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Attila Magyar
>Assignee: Attila Magyar
> Fix For: 2.5.2
>
> Attachments: AMBARI-21236.patch
>
>
> Kerberos principal placeholders like
> {code}
> sasl:${principals/YARN/RESOURCEMANAGER/resource_manager_rm|principalPrimary()}:rwcda
> {code}
> are not getting replaced if the cluster is created with blueprints 
> (kerberos=enabled).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21236) Principal placeholder replacement in kerberos.json doesn't work with blueprint installs

[Attila Magyar (JIRA)]

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

Attila Magyar updated AMBARI-21236:
---
Attachment: AMBARI-21236.patch

> Principal placeholder replacement in kerberos.json doesn't work with 
> blueprint installs
> ---
>
> Key: AMBARI-21236
> URL: https://issues.apache.org/jira/browse/AMBARI-21236
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Attila Magyar
>Assignee: Attila Magyar
> Fix For: 2.5.2
>
> Attachments: AMBARI-21236.patch
>
>
> Kerberos principal placeholders like
> {code}
> sasl:${principals/YARN/RESOURCEMANAGER/resource_manager_rm|principalPrimary()}:rwcda
> {code}
> are not getting replaced if the cluster is created with blueprints 
> (kerberos=enabled).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21233) ambari-web hits JS error in dev mode

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047808#comment-16047808
 ] 

Aleksandr Kovalenko commented on AMBARI-21233:
--

+1 for the patch

> 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
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-21233.patch
>
>
> http://localhost: hits JS several error and dashboard does not show up



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21233) ambari-web hits JS error in dev mode

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander updated AMBARI-21233:
-
Assignee: Antonenko Alexander
  Status: Patch Available  (was: Open)

> 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
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-21233.patch
>
>
> http://localhost: hits JS several error and dashboard does not show up



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21233) ambari-web hits JS error in dev mode

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander updated AMBARI-21233:
-
Attachment: AMBARI-21233.patch

> 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
>
> Attachments: AMBARI-21233.patch
>
>
> 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-21224) RU: Oozie LR job failed

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047792#comment-16047792
 ] 

Hudson commented on AMBARI-21224:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7619 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7619/])
AMBARI-21224. RU: Oozie LR job failed (aonishuk) (aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=27a99389e3c3566b6fc58b17cb06510ab9bffa13])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/YARN/configuration-mapred/mapred-site.xml


> RU: Oozie LR job failed
> ---
>
> Key: AMBARI-21224
> URL: https://issues.apache.org/jira/browse/AMBARI-21224
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.2
>
> Attachments: AMBARI-21224.patch
>
>
> Artifacts:  /test-logs/ambariru-e2e-fntofn-s12-sec/>
> From output.log:
> 
> 
> 
> 2017-05-28 19:42:27,765|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|001-170528103319986-oozie-oozi-C@257
>FAILED157-170528155827930-oozie-oozi-W - 2017-05-28 14:13 
> GMT 2009-01-01 22:20 GMT
> 2017-05-28 19:42:27,766|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|
> 2017-05-28 19:42:27,766|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|001-170528103319986-oozie-oozi-C@258
>SUCCEEDED 001-170528183839277-oozie-oozi-W - 2017-05-28 14:13 
> GMT 2009-01-01 22:25 GMT
> 2017-05-28 19:42:27,766|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|
> 2017-05-28 19:42:27,766|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|001-170528103319986-oozie-oozi-C@259
>SUCCEEDED 003-170528183839277-oozie-oozi-W - 2017-05-28 14:13 
> GMT 2009-01-01 22:30 GMT
> 2017-05-28 19:42:27,766|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|
> 2017-05-28 19:42:27,766|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|001-170528103319986-oozie-oozi-C@260
>SUCCEEDED 004-170528183839277-oozie-oozi-W - 2017-05-28 14:13 
> GMT 2009-01-01 22:35 GMT
> 2017-05-28 19:42:27,766|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|
> 2017-05-28 19:42:27,767|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|001-170528103319986-oozie-oozi-C@261
>SUCCEEDED 006-170528183839277-oozie-oozi-W - 2017-05-28 14:13 
> GMT 2009-01-01 22:40 GMT
> 2017-05-28 19:42:27,767|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|
> 2017-05-28 19:42:27,768|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|001-170528103319986-oozie-oozi-C@262
>SUCCEEDED 008-170528183839277-oozie-oozi-W - 2017-05-28 14:13 
> GMT 2009-01-01 22:45 GMT
> 2017-05-28 19:42:27,768|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|
> 2017-05-28 19:42:27,769|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|001-170528103319986-oozie-oozi-C@263
>SUCCEEDED 009-170528183839277-oozie-oozi-W - 2017-05-28 14:13 
> GMT 2009-01-01 22:50 GMT
> 2017-05-28 19:42:27,769|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|
> 2017-05-28 19:42:27,769|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|001-170528103319986-oozie-oozi-C@264
>SUCCEEDED 011-170528183839277-oozie-oozi-W - 2017-05-28 14:13 
> GMT 

[jira] [Commented] (AMBARI-21224) RU: Oozie LR job failed

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047791#comment-16047791
 ] 

Hudson commented on AMBARI-21224:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1592 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1592/])
AMBARI-21224. RU: Oozie LR job failed (aonishuk) (aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f2c91c250b7a1bb27a49e440413bb6a2892696e6])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/YARN/configuration-mapred/mapred-site.xml


> RU: Oozie LR job failed
> ---
>
> Key: AMBARI-21224
> URL: https://issues.apache.org/jira/browse/AMBARI-21224
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.2
>
> Attachments: AMBARI-21224.patch
>
>
> Artifacts:  /test-logs/ambariru-e2e-fntofn-s12-sec/>
> From output.log:
> 
> 
> 
> 2017-05-28 19:42:27,765|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|001-170528103319986-oozie-oozi-C@257
>FAILED157-170528155827930-oozie-oozi-W - 2017-05-28 14:13 
> GMT 2009-01-01 22:20 GMT
> 2017-05-28 19:42:27,766|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|
> 2017-05-28 19:42:27,766|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|001-170528103319986-oozie-oozi-C@258
>SUCCEEDED 001-170528183839277-oozie-oozi-W - 2017-05-28 14:13 
> GMT 2009-01-01 22:25 GMT
> 2017-05-28 19:42:27,766|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|
> 2017-05-28 19:42:27,766|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|001-170528103319986-oozie-oozi-C@259
>SUCCEEDED 003-170528183839277-oozie-oozi-W - 2017-05-28 14:13 
> GMT 2009-01-01 22:30 GMT
> 2017-05-28 19:42:27,766|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|
> 2017-05-28 19:42:27,766|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|001-170528103319986-oozie-oozi-C@260
>SUCCEEDED 004-170528183839277-oozie-oozi-W - 2017-05-28 14:13 
> GMT 2009-01-01 22:35 GMT
> 2017-05-28 19:42:27,766|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|
> 2017-05-28 19:42:27,767|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|001-170528103319986-oozie-oozi-C@261
>SUCCEEDED 006-170528183839277-oozie-oozi-W - 2017-05-28 14:13 
> GMT 2009-01-01 22:40 GMT
> 2017-05-28 19:42:27,767|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|
> 2017-05-28 19:42:27,768|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|001-170528103319986-oozie-oozi-C@262
>SUCCEEDED 008-170528183839277-oozie-oozi-W - 2017-05-28 14:13 
> GMT 2009-01-01 22:45 GMT
> 2017-05-28 19:42:27,768|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|
> 2017-05-28 19:42:27,769|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|001-170528103319986-oozie-oozi-C@263
>SUCCEEDED 009-170528183839277-oozie-oozi-W - 2017-05-28 14:13 
> GMT 2009-01-01 22:50 GMT
> 2017-05-28 19:42:27,769|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|
> 2017-05-28 19:42:27,769|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|001-170528103319986-oozie-oozi-C@264
>SUCCEEDED 011-170528183839277-oozie-oozi-W - 2017-05-28 14:13 
> GMT 2009-01-01 

[jira] [Updated] (AMBARI-21237) Add validation and recommendation if hive user value is different than hive

[Vitaly Brodetskyi (JIRA)]

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

Vitaly Brodetskyi updated AMBARI-21237:
---
Status: Patch Available  (was: Open)

> Add validation and recommendation if hive user value is different than hive
> ---
>
> Key: AMBARI-21237
> URL: https://issues.apache.org/jira/browse/AMBARI-21237
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21237.patch
>
>
> By default yarn.nodemanager.kill-escape.user is set to hive the default 
> username for Hive. When custom hive user is used the above property should be 
> modified via stack advisor and also validation error must be reported if the 
> value is not correct.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21237) Add validation and recommendation if hive user value is different than hive

[Vitaly Brodetskyi (JIRA)]

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

Vitaly Brodetskyi updated AMBARI-21237:
---
Attachment: AMBARI-21237.patch

> Add validation and recommendation if hive user value is different than hive
> ---
>
> Key: AMBARI-21237
> URL: https://issues.apache.org/jira/browse/AMBARI-21237
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21237.patch
>
>
> By default yarn.nodemanager.kill-escape.user is set to hive the default 
> username for Hive. When custom hive user is used the above property should be 
> modified via stack advisor and also validation error must be reported if the 
> value is not correct.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (AMBARI-21237) Add validation and recommendation if hive user value is different than hive

[Vitaly Brodetskyi (JIRA)]

Vitaly Brodetskyi created AMBARI-21237:
--

 Summary: Add validation and recommendation if hive user value is 
different than hive
 Key: AMBARI-21237
 URL: https://issues.apache.org/jira/browse/AMBARI-21237
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.5.0
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Priority: Blocker
 Fix For: 2.5.2


By default yarn.nodemanager.kill-escape.user is set to hive the default 
username for Hive. When custom hive user is used the above property should be 
modified via stack advisor and also validation error must be reported if the 
value is not correct.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (AMBARI-21228) Rename userconfig resource to event history in Log Search Portal

[JIRA]

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

Olivér Szabó resolved AMBARI-21228.
---
Resolution: Fixed

> Rename userconfig resource to event history in Log Search Portal
> 
>
> Key: AMBARI-21228
> URL: https://issues.apache.org/jira/browse/AMBARI-21228
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 3.0.0
>
> Attachments: AMBARI-21228.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21228) Rename userconfig resource to event history in Log Search Portal

[JIRA]

[ 
https://issues.apache.org/jira/browse/AMBARI-21228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047770#comment-16047770
 ] 

Olivér Szabó commented on AMBARI-21228:
---

{code:java}
commit fc00b2caf927d083c70812bf1552aafa68958d1f
Author: oleewere 
Date:   Mon Jun 12 17:12:58 2017 +0200

AMBARI-21228. Rename userconfig resource to event history in Log Search 
Portal (oleewere)
{code}

> Rename userconfig resource to event history in Log Search Portal
> 
>
> Key: AMBARI-21228
> URL: https://issues.apache.org/jira/browse/AMBARI-21228
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 3.0.0
>
> Attachments: AMBARI-21228.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21224) RU: Oozie LR job failed

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-21224:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk and branch-2.5

> RU: Oozie LR job failed
> ---
>
> Key: AMBARI-21224
> URL: https://issues.apache.org/jira/browse/AMBARI-21224
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.2
>
> Attachments: AMBARI-21224.patch
>
>
> Artifacts:  /test-logs/ambariru-e2e-fntofn-s12-sec/>
> From output.log:
> 
> 
> 
> 2017-05-28 19:42:27,765|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|001-170528103319986-oozie-oozi-C@257
>FAILED157-170528155827930-oozie-oozi-W - 2017-05-28 14:13 
> GMT 2009-01-01 22:20 GMT
> 2017-05-28 19:42:27,766|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|
> 2017-05-28 19:42:27,766|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|001-170528103319986-oozie-oozi-C@258
>SUCCEEDED 001-170528183839277-oozie-oozi-W - 2017-05-28 14:13 
> GMT 2009-01-01 22:25 GMT
> 2017-05-28 19:42:27,766|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|
> 2017-05-28 19:42:27,766|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|001-170528103319986-oozie-oozi-C@259
>SUCCEEDED 003-170528183839277-oozie-oozi-W - 2017-05-28 14:13 
> GMT 2009-01-01 22:30 GMT
> 2017-05-28 19:42:27,766|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|
> 2017-05-28 19:42:27,766|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|001-170528103319986-oozie-oozi-C@260
>SUCCEEDED 004-170528183839277-oozie-oozi-W - 2017-05-28 14:13 
> GMT 2009-01-01 22:35 GMT
> 2017-05-28 19:42:27,766|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|
> 2017-05-28 19:42:27,767|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|001-170528103319986-oozie-oozi-C@261
>SUCCEEDED 006-170528183839277-oozie-oozi-W - 2017-05-28 14:13 
> GMT 2009-01-01 22:40 GMT
> 2017-05-28 19:42:27,767|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|
> 2017-05-28 19:42:27,768|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|001-170528103319986-oozie-oozi-C@262
>SUCCEEDED 008-170528183839277-oozie-oozi-W - 2017-05-28 14:13 
> GMT 2009-01-01 22:45 GMT
> 2017-05-28 19:42:27,768|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|
> 2017-05-28 19:42:27,769|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|001-170528103319986-oozie-oozi-C@263
>SUCCEEDED 009-170528183839277-oozie-oozi-W - 2017-05-28 14:13 
> GMT 2009-01-01 22:50 GMT
> 2017-05-28 19:42:27,769|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|
> 2017-05-28 19:42:27,769|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|001-170528103319986-oozie-oozi-C@264
>SUCCEEDED 011-170528183839277-oozie-oozi-W - 2017-05-28 14:13 
> GMT 2009-01-01 22:55 GMT
> 2017-05-28 19:42:27,769|INFO|MainThread|machine.py:159 - 
> run()||GUID=fafc452f-4fed-47ee-abf3-0e65964e0236|
> 2017-05-28 

[jira] [Created] (AMBARI-21236) Principal placeholder replacement in kerberos.json doesn't work with blueprint installs

[Attila Magyar (JIRA)]

Attila Magyar created AMBARI-21236:
--

 Summary: Principal placeholder replacement in kerberos.json 
doesn't work with blueprint installs
 Key: AMBARI-21236
 URL: https://issues.apache.org/jira/browse/AMBARI-21236
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.5.2
Reporter: Attila Magyar
Assignee: Attila Magyar
 Fix For: 2.5.2


Kerberos principal placeholders like

{code}
sasl:${principals/YARN/RESOURCEMANAGER/resource_manager_rm|principalPrimary()}:rwcda
{code}

are not getting replaced if the cluster is created with blueprints 
(kerberos=enabled).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-20476) Ambari View examples phone-list-upgrade-view/phone-list-view cannot display normally

[Yao Lei (JIRA)]

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

Yao Lei updated AMBARI-20476:
-
Resolution: Information Provided
Status: Resolved  (was: Patch Available)

> Ambari View examples phone-list-upgrade-view/phone-list-view cannot display 
> normally
> 
>
> Key: AMBARI-20476
> URL: https://issues.apache.org/jira/browse/AMBARI-20476
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: trunk
>Reporter: Yao Lei
>Priority: Trivial
> Fix For: trunk
>
> Attachments: 1.0.0-list1.png, 1.0.0-list2.png, 2.0.0-list1.png, 
> 2.0.0-list2.png, AMBARI-20476-1.patch
>
>
> Problem: 
> After adding/updating/deleting one record,the web page displays html code 
> directly as shown in attached pictures.
> Steps to reproduce:
> 1.cd ambari-views/examples
> 2.cd phone-list-upgrade-view & mvn clean package
> 3.cd phone-list-view & mvn clean package
> 4.copy phone-list-upgrade-view/target/phone-list-upgrade-view-*.jar,
>phone-list-view/target/phone-list-view-*.jar 
>to /var/lib/ambari-server/resources/views
> 5.ambari-server restart
> 6.open the view and add/update/delete record.
> Solution: add response header to method doPost() in PhoneListServlet.java



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-9151) Expose allowed.system.users and banned.users for container-executor.cfg in Ambari web UI

[Hari Sekhon (JIRA)]

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

Hari Sekhon updated AMBARI-9151:

Priority: Major  (was: Minor)

> Expose allowed.system.users and banned.users for container-executor.cfg in 
> Ambari web UI
> 
>
> Key: AMBARI-9151
> URL: https://issues.apache.org/jira/browse/AMBARI-9151
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: 1.7.0
> Environment: HDP 2.2
>Reporter: Hari Sekhon
>
> Please expose all configuration options for container-executor.cfg including 
> allowed.system.users and banned.users in Ambari web UI.
> I've edited the underlying jinja2 templates under the hood but this could be 
> supported properly.
> Best Regards,
> Hari Sekhon
> http://www.linkedin.com/in/harisekhon



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-20767) Add the Chinese translation files

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-20767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047519#comment-16047519
 ] 

ASF GitHub Bot commented on AMBARI-20767:
-

Github user wangrenlei closed the pull request at:

https://github.com/apache/ambari/pull/54


> Add the Chinese translation files
> -
>
> Key: AMBARI-20767
> URL: https://issues.apache.org/jira/browse/AMBARI-20767
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-admin, ambari-web
>Affects Versions: 2.4.0
>Reporter: PetterWang
>  Labels: features
> Fix For: 2.4.0
>
> Attachments: AMBARI-20767_branch-2.4.0.patch, AMBARI-20767.patch
>
>
> Need chinese translation files , include 
> ambari-admin\src\main\resources\ui\admin-web\app\scripts\i18n.config.js and 
> ambari-web\app\locales\zh\messages.js



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)