[jira] [Updated] (AMBARI-18622) Integrate PredictionIO (Machine Learning Engine) With Ambari

[Ananda Verma (JIRA)]

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

Ananda Verma updated AMBARI-18622:
--
Description: 
It makes sense to integrate PredictionIO with Ambari since it is now part of 
apache group and also heavily depends on current amabri/hdp stack.  

Feature includes adding support for apache predictionIO cluster provisioning 
via Ambari.

In general, pio can be defined as a service in HDP which has following 
components - 
1) Event Server  - stores events (data)
2) Engine - Engine is responsible for making prediction. It contains one or 
more machine learning algorithms. An engine reads training data and build 
predictive model(s). It is then deployed as a web service. A deployed engine 
responds to prediction queries from your application through REST API in 
real-time.

PredictionIO also has external dependencies on following  - 

1. HBase: Event Server uses Apache HBase as the data store. It stores imported 
events. If you are not using the PredictionIO Event Server, you do not need to 
install HBase.

2. Apache Spark: Spark is a large-scale data processing engine that powers the 
algorithm, training, and serving processing.

3. HDFS: The output of training has two parts: a model and its meta-data. The 
model is then stored in HDFS or a local file system.

4. Elasticsearch: It stores metadata such as model versions, engine versions, 
access key and app id mappings, evaluation results, etc.


  was:
Feature includes adding support for apache predictionIO cluster provisioning 
via Ambari.
In general, pio can be defined as a service in HDP which has following 
components - 
1) Event Server  - stores events (data)
2) Engine - Engine is responsible for making prediction. It contains one or 
more machine learning algorithms. An engine reads training data and build 
predictive model(s). It is then deployed as a web service. A deployed engine 
responds to prediction queries from your application through REST API in 
real-time.

PredictionIO also has external dependencies on following  - 

1. HBase: Event Server uses Apache HBase as the data store. It stores imported 
events. If you are not using the PredictionIO Event Server, you do not need to 
install HBase.

2. Apache Spark: Spark is a large-scale data processing engine that powers the 
algorithm, training, and serving processing.

3. HDFS: The output of training has two parts: a model and its meta-data. The 
model is then stored in HDFS or a local file system.

4. Elasticsearch: It stores metadata such as model versions, engine versions, 
access key and app id mappings, evaluation results, etc.



> Integrate PredictionIO (Machine Learning Engine) With Ambari
> 
>
> Key: AMBARI-18622
> URL: https://issues.apache.org/jira/browse/AMBARI-18622
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Affects Versions: 2.1.0
>Reporter: Ananda Verma
>
> It makes sense to integrate PredictionIO with Ambari since it is now part of 
> apache group and also heavily depends on current amabri/hdp stack.  
> Feature includes adding support for apache predictionIO cluster provisioning 
> via Ambari.
> In general, pio can be defined as a service in HDP which has following 
> components - 
> 1) Event Server  - stores events (data)
> 2) Engine - Engine is responsible for making prediction. It contains one or 
> more machine learning algorithms. An engine reads training data and build 
> predictive model(s). It is then deployed as a web service. A deployed engine 
> responds to prediction queries from your application through REST API in 
> real-time.
> PredictionIO also has external dependencies on following  - 
> 1. HBase: Event Server uses Apache HBase as the data store. It stores 
> imported events. If you are not using the PredictionIO Event Server, you do 
> not need to install HBase.
> 2. Apache Spark: Spark is a large-scale data processing engine that powers 
> the algorithm, training, and serving processing.
> 3. HDFS: The output of training has two parts: a model and its meta-data. The 
> model is then stored in HDFS or a local file system.
> 4. Elasticsearch: It stores metadata such as model versions, engine versions, 
> access key and app id mappings, evaluation results, etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-18622) Integrate PredictionIO (Machine Learning Engine) With Ambari

[Ananda Verma (JIRA)]

Ananda Verma created AMBARI-18622:
-

 Summary: Integrate PredictionIO (Machine Learning Engine) With 
Ambari
 Key: AMBARI-18622
 URL: https://issues.apache.org/jira/browse/AMBARI-18622
 Project: Ambari
  Issue Type: New Feature
  Components: ambari-server
Affects Versions: 2.1.0
Reporter: Ananda Verma


Feature includes adding support for apache predictionIO cluster provisioning 
via Ambari.
In general, pio can be defined as a service in HDP which has following 
components - 
1) Event Server  - stores events (data)
2) Engine - Engine is responsible for making prediction. It contains one or 
more machine learning algorithms. An engine reads training data and build 
predictive model(s). It is then deployed as a web service. A deployed engine 
responds to prediction queries from your application through REST API in 
real-time.

PredictionIO also has external dependencies on following  - 

1. HBase: Event Server uses Apache HBase as the data store. It stores imported 
events. If you are not using the PredictionIO Event Server, you do not need to 
install HBase.

2. Apache Spark: Spark is a large-scale data processing engine that powers the 
algorithm, training, and serving processing.

3. HDFS: The output of training has two parts: a model and its meta-data. The 
model is then stored in HDFS or a local file system.

4. Elasticsearch: It stores metadata such as model versions, engine versions, 
access key and app id mappings, evaluation results, etc.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (AMBARI-7811) Integrate ElasticSearch, LogStash and Kibana with Ambari

[Ananda Verma (JIRA)]

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

Ananda Verma edited comment on AMBARI-7811 at 10/18/16 5:36 AM:


All 3 integration as independent services would be better idea I guess. With 
HDP 2.4 log search preview is already made with ambari infra and it uses solr 
so definitely ELK is not coming for default log analysis server.

But elastic search integration definitely make sense. My team is already 
working on it since we are integrating predictionio which needs elastic search 
for meta store so it make sense for us to integrate. 


was (Author: rahul.vi...@gmail.com):
All 3 integration as independent services would be better idea I guess. With 
HDP 2.4 log search preview is already made with ambari infra and it uses solr 
so definitely ELK is not coming for default log analysis server.

But ElasticSearch integration definitely make sense. 

> Integrate ElasticSearch, LogStash and Kibana with Ambari
> 
>
> Key: AMBARI-7811
> URL: https://issues.apache.org/jira/browse/AMBARI-7811
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Reporter: Mingjiang Shi
>
> A hadoop cluster has many nodes, many services and many components, which 
> generates many logs on different machines.  It would be a good idea to search 
> and view those logs at a central place.  
> The ELK stack (elastic search, logstash and kibana) is the one of the best 
> open source log collection, storage and search solution.  By integrating ELK 
> with Ambari, user could optionally install ELK when deploying a cluster.  
> This will enable user to search and view all the logs at free.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-7811) Integrate ElasticSearch, LogStash and Kibana with Ambari

[Ananda Verma (JIRA)]

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

Ananda Verma commented on AMBARI-7811:
--

All 3 integration as independent services would be better idea I guess. With 
HDP 2.4 log search preview is already made with ambari infra and it uses solr 
so definitely ELK is not coming for default log analysis server.

But ElasticSearch integration definitely make sense. 

> Integrate ElasticSearch, LogStash and Kibana with Ambari
> 
>
> Key: AMBARI-7811
> URL: https://issues.apache.org/jira/browse/AMBARI-7811
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Reporter: Mingjiang Shi
>
> A hadoop cluster has many nodes, many services and many components, which 
> generates many logs on different machines.  It would be a good idea to search 
> and view those logs at a central place.  
> The ELK stack (elastic search, logstash and kibana) is the one of the best 
> open source log collection, storage and search solution.  By integrating ELK 
> with Ambari, user could optionally install ELK when deploying a cluster.  
> This will enable user to search and view all the logs at free.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18615) Fix JSHint errors in Workflow Manager view

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18615:


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

{color:red}-1 patch{color}.  The patch command could not apply the patch.

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

This message is automatically generated.

> Fix JSHint errors in Workflow Manager view
> --
>
> Key: AMBARI-18615
> URL: https://issues.apache.org/jira/browse/AMBARI-18615
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Fix For: 2.5.0
>
> Attachments: AMBARI-18615.patch
>
>
> When you compile the Workflow Manager view, you see 94 JSHint errors.
> app.js: line 18, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 19, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 20, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 21, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 23, col 1, 'let' is available in ES6 (use 'esversion: 6') or 
> Mozilla JS extensions (use moz).
> app.js: line 30, col 3, 'object short notation' is available in ES6 (use 
> 'esversion: 6') or Mozilla JS extensions (use moz).
> app.js: line 39, col 1, 'export' is only available in ES6 (use 'esversion: 
> 6').
> 7 errors
> components/action-credential-config.js: line 18, col 1, 'import' is only 
> available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 20, col 1, 'export' is only 
> available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 24, col 38, 'arrow function 
> syntax (=>)' is only available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 30, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/action-credential-config.js: line 33, col 36, 'arrow function 
> syntax (=>)' is only available in ES6 (use 'esversion: 6').
> 5 errors
> components/action-version-select.js: line 18, col 1, 'import' is only 
> available in ES6 (use 'esversion: 6').
> components/action-version-select.js: line 20, col 1, 'export' is only 
> available in ES6 (use 'esversion: 6').
> components/action-version-select.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 3 errors
> components/archive-config.js: line 18, col 1, 'import' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 19, col 1, 'import' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 21, col 1, 'export' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 29, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/archive-config.js: line 33, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/archive-config.js: line 36, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 6 errors
> components/arg-config.js: line 18, col 1, 'import' is only available in ES6 
> (use 'esversion: 6').
> components/arg-config.js: line 20, col 1, 'export' is only available in ES6 
> (use 'esversion: 6').
> components/arg-config.js: line 33, col 3, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/arg-config.js: line 38, col 5, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/arg-config.js: line 41, col 5, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 5 errors
> components/bundle-job-details.js: line 18, col 1, 'import' is only available 
> in ES6 (use 'esversion: 6').
> components/bundle-job-details.js: line 20, col 1, 'export' is only available 
> in ES6 (use 'esversion: 6').
> components/bundle-job-details.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/bundle-job-details.js: line 25, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/bundle-job-details.js: line 28, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla 

[jira] [Commented] (AMBARI-18616) Fix Log Search User Config bug

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18616:


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

{color:red}-1 patch{color}.  The patch command could not apply the patch.

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

This message is automatically generated.

> Fix Log Search User Config bug
> --
>
> Key: AMBARI-18616
> URL: https://issues.apache.org/jira/browse/AMBARI-18616
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-18616.patch
>
>
> Log Search User Config UI screen does not offer the chance to modify the 
> filter settings for those logs which don't have any log entries loaded so 
> far. For these logs the initial settings will be in effect until the first 
> modification of the filters when all of these settings will be erased, and 
> thus every log will be loaded for them without filtering.
> The User Config UI should always show all the logs, first those which already 
> have some log entries in the solr, then the rest.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18619) Optimize Service Checks to it picks a random host and prefers hosts with 0 active commands

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18619:


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

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

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

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

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

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
ambari-server:

  
org.apache.ambari.server.controller.internal.ActiveWidgetLayoutResourceProviderTest
  
org.apache.ambari.server.controller.internal.UserAuthorizationResourceProviderTest
  
org.apache.ambari.server.controller.AmbariManagementControllerTest
  
org.apache.ambari.server.controller.internal.UserResourceProviderTest

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8895//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8895//console

This message is automatically generated.

> Optimize Service Checks to it picks a random host and prefers hosts with 0 
> active commands
> --
>
> Key: AMBARI-18619
> URL: https://issues.apache.org/jira/browse/AMBARI-18619
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18619.branch-2.5.patch, AMBARI-18619.trunk.patch
>
>
> STR:
> * Deploy a 3-node cluster with Ambari 2.4 and HDP 2.5 with clients on every 
> host.
> * Run multiple service checks in parallel, but notice that they typically run 
> on the same 1 or 2 hosts.
> Currently, Ambari relies on getting the list of candidate hosts from the DB 
> and excludes all hosts that are in maintenance mode. From that list, it picks 
> the first host that is healthy (i.e., heartbeating). This means that the 
> logic does not pick a random host.
> Instead, Ambari should always pick a random host and prefer to schedule on 
> hosts that have 0 in-progress commands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18621) Service Summary screen does not show hostname in tooltip pop-up for all services

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18621:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5817 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5817/])
AMBARI-18621. Service Summary screen does not show hostname in tooltip (jaimin: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a93c0f4004a02b02c95e2057115c961c192662b8])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostComponentResourceProvider.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClientConfigResourceProviderTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/HostResourceProviderTest.java
* (edit) 
ambari-web/app/templates/main/service/info/summary/master_components.hbs
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/ServiceComponentHostRequest.java
* (edit) ambari-web/app/mappers/hosts_mapper.js
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/svccomphost/ServiceComponentHostImpl.java
* (edit) ambari-web/app/controllers/global/update_controller.js
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/HostComponentResourceProviderTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/ServiceComponentHostResponse.java
* (edit) ambari-web/app/models/host_component.js
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/ServiceComponentHost.java
* (edit) ambari-server/src/main/resources/properties.json
* (edit) ambari-web/app/mappers/service_metrics_mapper.js
* (edit) ambari-web/app/mappers/component_config_mapper.js


> Service Summary screen does not show hostname in tooltip pop-up for all 
> services
> 
>
> Key: AMBARI-18621
> URL: https://issues.apache.org/jira/browse/AMBARI-18621
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, ambari-web
>Affects Versions: 2.0.0, 2.1.2
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18621.patch
>
>
> *STR:*
> # Install a cluster with more than 25 nodes
> # Add "Hive Metastore" hosts on nodes that are above first 25 nodes 
> lexicographically
> *Expected Result:* On Service summary page while hovering on "Hive Metastore" 
> label links, all such links should display public host name in the tooltip
> *Actual Result:* "Hive Metastore" hosts that are running on hosts above first 
> 25 lexicographically does not display public host names on being hovered. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18595) Icons don't display in Windows 10 Microsoft Edge or Internet Explorer 11

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18595:
-

ABORTED: Integrated in Jenkins build Ambari-trunk-Commit #5816 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5816/])
AMBARI-18595 Icons don't display in Windows 10 Microsoft Edge or (zhewang: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=fdda172fed36ae3e156dc2757a09f85d0a379175])
* (edit) ambari-web/pom.xml


> Icons don't display in Windows 10 Microsoft Edge or Internet Explorer 11
> 
>
> Key: AMBARI-18595
> URL: https://issues.apache.org/jira/browse/AMBARI-18595
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
> Environment: Microsoft Windows 10
>  - Microsoft Edge
>  - Microsoft Internet Explorer 11
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-18595.v0.patch, Capture.PNG
>
>
> Icons do not display in any page as shown in the screen-shot attached.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (AMBARI-18575) Fix for improving time taken by 'ExecutionScheduleManagerTest' and 'UpgradeCatalog221Test' java tests.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar edited comment on AMBARI-18575 at 10/18/16 2:28 AM:



*commits:*


*trunk:*

{code}
commit 911deb744485aa0366aad168c98566cf6381d4cc
Author: Swapan Shridhar 
Date:   Tue Oct 11 16:09:00 2016 -0700

AMBARI-18575. Fix for improving time taken by 
'ExecutionScheduleManagerTest' and 'UpgradeCatalog221Test' java tests.
{code}

*branch-2.5:*

{code}
commit 4512f5525d129bdd4f73b68dfa139631d0368c35
Author: Swapan Shridhar 
Date:   Tue Oct 11 16:09:00 2016 -0700

AMBARI-18575. Fix for improving time taken by 
'ExecutionScheduleManagerTest' and 'UpgradeCatalog221Test' java tests.
{code}


was (Author: swapanshridhar):

*commits:*


*trunk:*

{code}
commit 911deb744485aa0366aad168c98566cf6381d4cc
Author: Swapan Shridhar 
Date:   Tue Oct 11 16:09:00 2016 -0700

AMBARI-18575. Fix for improving time taken by 
'ExecutionScheduleManagerTest' and 'UpgradeCatalog221Test' java tests.
{code}

*branch-2.4:*

{code}
commit fdc5bd3fdf23b2035a27648d2db20e22c2159a0b
Author: Swapan Shridhar 
Date:   Wed Oct 12 15:51:26 2016 -0700

AMBARI-18575. Fix for improving time taken by 
'ExecutionScheduleManagerTest' and 'UpgradeCatalog221Test' java tests.
{code}


*branch-2.5:*

{code}
commit 4512f5525d129bdd4f73b68dfa139631d0368c35
Author: Swapan Shridhar 
Date:   Tue Oct 11 16:09:00 2016 -0700

AMBARI-18575. Fix for improving time taken by 
'ExecutionScheduleManagerTest' and 'UpgradeCatalog221Test' java tests.
{code}

> Fix for improving time taken by 'ExecutionScheduleManagerTest' and 
> 'UpgradeCatalog221Test' java tests.
> --
>
> Key: AMBARI-18575
> URL: https://issues.apache.org/jira/browse/AMBARI-18575
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-18575.patch
>
>
> Current time taken:
> ||Test||Count||Time (s)||
> |org.apache.ambari.server.upgrade.UpgradeCatalog221Test   |13|36.586|
> |org.apache.ambari.server.scheduler.ExecutionScheduleManagerTest|9|30.685|
> Initially reported as part of test improvements (along with other tests) in 
> BUG : BUG-65777



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18595) Icons don't display in Windows 10 Microsoft Edge or Internet Explorer 11

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18595:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #161 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/161/])
AMBARI-18595 Icons don't display in Windows 10 Microsoft Edge or (zhewang: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d6cebbd2a960156c450066fb96f394810e00aae4])
* (edit) ambari-web/pom.xml


> Icons don't display in Windows 10 Microsoft Edge or Internet Explorer 11
> 
>
> Key: AMBARI-18595
> URL: https://issues.apache.org/jira/browse/AMBARI-18595
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
> Environment: Microsoft Windows 10
>  - Microsoft Edge
>  - Microsoft Internet Explorer 11
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-18595.v0.patch, Capture.PNG
>
>
> Icons do not display in any page as shown in the screen-shot attached.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18621) Service Summary screen does not show hostname in tooltip pop-up for all services

[Jaimin D Jetly (JIRA)]

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

Jaimin D Jetly updated AMBARI-18621:

Resolution: Fixed
Status: Resolved  (was: Patch Available)

Received +1 on review board.
Patch committed to trunk, branch-2.5 and branch-2.4

> Service Summary screen does not show hostname in tooltip pop-up for all 
> services
> 
>
> Key: AMBARI-18621
> URL: https://issues.apache.org/jira/browse/AMBARI-18621
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, ambari-web
>Affects Versions: 2.0.0, 2.1.2
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18621.patch
>
>
> *STR:*
> # Install a cluster with more than 25 nodes
> # Add "Hive Metastore" hosts on nodes that are above first 25 nodes 
> lexicographically
> *Expected Result:* On Service summary page while hovering on "Hive Metastore" 
> label links, all such links should display public host name in the tooltip
> *Actual Result:* "Hive Metastore" hosts that are running on hosts above first 
> 25 lexicographically does not display public host names on being hovered. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17636) Service Configs page: can't see all config versions in dropdown

[Hudson (JIRA)]

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

Hudson commented on AMBARI-17636:
-

ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #160 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/160/])
AMBARI-17636 Service Configs page: can't see all config versions in (zhewang: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e41a036c5ee8891fd19f027c825e067914ab65fc])
* (edit) ambari-web/app/templates/common/configs/config_history_flow.hbs
* (edit) ambari-web/app/views/common/configs/config_history_flow.js
* (edit) ambari-web/app/styles/config_history_flow.less


> Service Configs page: can't see all config versions in dropdown
> ---
>
> Key: AMBARI-17636
> URL: https://issues.apache.org/jira/browse/AMBARI-17636
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-17636.v0.patch, AMBARI-17636.v3.patch, 
> AMBARI-17636.v4.patch, AMBARI-17636.v5.patch, AMBARI-17636.v6.patch, 
> AMBARI-17636.v7.patch, bugfix.gif
>
>
> * Go to Service->Configs page (that have more than ~ 30 versions)
> * Open versions dropdown
> *Result:*
> Number of visible versions limited by window height.
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18621) Service Summary screen does not show hostname in tooltip pop-up for all services

[Jaimin D Jetly (JIRA)]

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

Jaimin D Jetly updated AMBARI-18621:

Status: Patch Available  (was: Open)

*Testing Done:*
* Verified on a cluster (> 25 nodes) that the patch resolves the issue
* Verified that all unit tests for ambari-web passes with the patch
{code}
  29243 tests complete (31 seconds)
  154 tests pending
{code}

* Modified and Verified ambari-server unit tests are not affected with the patch
{code}
Results :

Failed tests: 
  UpgradeCatalog222Test.testInitializeStromAndKafkaWidgets:1107 
  Unexpected method call 
AmbariManagementController.initializeWidgetsAndLayouts(EasyMock for interface 
org.apache.ambari.server.state.Cluster, EasyMock for interface 
org.apache.ambari.server.state.Service):
AmbariManagementController.getClusters(): expected: at least 0, actual: 1
AmbariManagementController.initializeWidgetsAndLayouts(EasyMock for 
interface org.apache.ambari.server.state.Cluster, EasyMock for interface 
org.apache.ambari.server.state.Service): expected: 1, actual: 0
  DataStoreImplTest.testFind:526 expected: but was:
  DataStoreImplTest.testRemove:475 expected: but was:
  DataStoreImplTest.testStore_update:357 expected: but was:
  DataStoreImplTest.testStore_update_longStringValue:426 
  Expectation failure on verify:
DynamicEntity.set("DS_id", 99): expected: 1, actual: 0
Tests in error: 
  KerberosCheckerTest.testCheckFailed »  Unexpected exception, 
expected Service Summary screen does not show hostname in tooltip pop-up for all 
> services
> 
>
> Key: AMBARI-18621
> URL: https://issues.apache.org/jira/browse/AMBARI-18621
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, ambari-web
>Affects Versions: 2.0.0, 2.1.2
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18621.patch
>
>
> *STR:*
> # Install a cluster with more than 25 nodes
> # Add "Hive Metastore" hosts on nodes that are above first 25 nodes 
> lexicographically
> *Expected Result:* On Service summary page while hovering on "Hive Metastore" 
> label links, all such links should display public host name in the tooltip
> *Actual Result:* "Hive Metastore" hosts that are running on hosts above first 
> 25 lexicographically does not display public host names on being hovered. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18621) Service Summary screen does not show hostname in tooltip pop-up for all services

[Jaimin D Jetly (JIRA)]

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

Jaimin D Jetly updated AMBARI-18621:

Description: 
*STR:*
# Install a cluster with more than 25 nodes
# Add "Hive Metastore" hosts on nodes that are above first 25 nodes 
lexicographically

*Expected Result:* On Service summary page while hovering on "Hive Metastore" 
label links, all such links should display public host name in the tooltip
*Actual Result:* "Hive Metastore" hosts that are running on hosts above first 
25 lexicographically does not display public host names on being hovered. 

> Service Summary screen does not show hostname in tooltip pop-up for all 
> services
> 
>
> Key: AMBARI-18621
> URL: https://issues.apache.org/jira/browse/AMBARI-18621
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, ambari-web
>Affects Versions: 2.0.0, 2.1.2
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18621.patch
>
>
> *STR:*
> # Install a cluster with more than 25 nodes
> # Add "Hive Metastore" hosts on nodes that are above first 25 nodes 
> lexicographically
> *Expected Result:* On Service summary page while hovering on "Hive Metastore" 
> label links, all such links should display public host name in the tooltip
> *Actual Result:* "Hive Metastore" hosts that are running on hosts above first 
> 25 lexicographically does not display public host names on being hovered. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18621) Service Summary screen does not show hostname in tooltip pop-up for all services

[Jaimin D Jetly (JIRA)]

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

Jaimin D Jetly updated AMBARI-18621:

Attachment: AMBARI-18621.patch

> Service Summary screen does not show hostname in tooltip pop-up for all 
> services
> 
>
> Key: AMBARI-18621
> URL: https://issues.apache.org/jira/browse/AMBARI-18621
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, ambari-web
>Affects Versions: 2.0.0, 2.1.2
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18621.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-18621) Service Summary screen does not show hostname in tooltip pop-up for all services

[Jaimin D Jetly (JIRA)]

Jaimin D Jetly created AMBARI-18621:
---

 Summary: Service Summary screen does not show hostname in tooltip 
pop-up for all services
 Key: AMBARI-18621
 URL: https://issues.apache.org/jira/browse/AMBARI-18621
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server, ambari-web
Affects Versions: 2.0.0, 2.1.2
Reporter: Jaimin D Jetly
Assignee: Jaimin D Jetly
Priority: Critical
 Fix For: 2.4.2






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (AMBARI-18620) Support migration from LDAP to PAM in Ambari

[Vishal Ghugare (JIRA)]

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

Vishal Ghugare reassigned AMBARI-18620:
---

Assignee: Vishal Ghugare

> Support migration from LDAP to PAM in Ambari
> 
>
> Key: AMBARI-18620
> URL: https://issues.apache.org/jira/browse/AMBARI-18620
> Project: Ambari
>  Issue Type: Story
>Affects Versions: trunk
>Reporter: Vishal Ghugare
>Assignee: Vishal Ghugare
>  Labels: security
> Fix For: trunk
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-18620) Support migration from LDAP to PAM in Ambari

[Vishal Ghugare (JIRA)]

Vishal Ghugare created AMBARI-18620:
---

 Summary: Support migration from LDAP to PAM in Ambari
 Key: AMBARI-18620
 URL: https://issues.apache.org/jira/browse/AMBARI-18620
 Project: Ambari
  Issue Type: Story
Affects Versions: trunk
Reporter: Vishal Ghugare
 Fix For: trunk






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (AMBARI-18612) Backport AMBARI-18551 to 2.4 branch

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez resolved AMBARI-18612.
--
Resolution: Fixed

> Backport AMBARI-18551 to 2.4 branch
> ---
>
> Key: AMBARI-18612
> URL: https://issues.apache.org/jira/browse/AMBARI-18612
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.4.0, 2.4.1, 2.4.2
>Reporter: Venkat Ranganathan
>Assignee: Venkat Ranganathan
> Fix For: 2.4.2
>
> Attachments: AMBARI-18612.diff
>
>
> AMBARI-18551 was applied to trunk and 2.5.   we need to apply it to 2.4 also



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18612) Backport AMBARI-18551 to 2.4 branch

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez commented on AMBARI-18612:
--

Pushed to branch-2.4, commit 3b2ce6c3bbd5b12480f5b592b216cb15fa9860e7

> Backport AMBARI-18551 to 2.4 branch
> ---
>
> Key: AMBARI-18612
> URL: https://issues.apache.org/jira/browse/AMBARI-18612
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.4.0, 2.4.1, 2.4.2
>Reporter: Venkat Ranganathan
>Assignee: Venkat Ranganathan
> Fix For: 2.4.2
>
> Attachments: AMBARI-18612.diff
>
>
> AMBARI-18551 was applied to trunk and 2.5.   we need to apply it to 2.4 also



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18612) Backport AMBARI-18551 to 2.4 branch

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez commented on AMBARI-18612:
--

+1 python unit tests passed

> Backport AMBARI-18551 to 2.4 branch
> ---
>
> Key: AMBARI-18612
> URL: https://issues.apache.org/jira/browse/AMBARI-18612
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.4.0, 2.4.1, 2.4.2
>Reporter: Venkat Ranganathan
>Assignee: Venkat Ranganathan
> Fix For: 2.4.2
>
> Attachments: AMBARI-18612.diff
>
>
> AMBARI-18551 was applied to trunk and 2.5.   we need to apply it to 2.4 also



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18612) Backport AMBARI-18551 to 2.4 branch

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-18612:
-
Fix Version/s: 2.4.2

> Backport AMBARI-18551 to 2.4 branch
> ---
>
> Key: AMBARI-18612
> URL: https://issues.apache.org/jira/browse/AMBARI-18612
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.4.0, 2.4.1, 2.4.2
>Reporter: Venkat Ranganathan
>Assignee: Venkat Ranganathan
> Fix For: 2.4.2
>
> Attachments: AMBARI-18612.diff
>
>
> AMBARI-18551 was applied to trunk and 2.5.   we need to apply it to 2.4 also



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18619) Optimize Service Checks to it picks a random host and prefers hosts with 0 active commands

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-18619:
-
Attachment: AMBARI-18619.trunk.patch
AMBARI-18619.branch-2.5.patch

> Optimize Service Checks to it picks a random host and prefers hosts with 0 
> active commands
> --
>
> Key: AMBARI-18619
> URL: https://issues.apache.org/jira/browse/AMBARI-18619
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18619.branch-2.5.patch, AMBARI-18619.trunk.patch
>
>
> STR:
> * Deploy a 3-node cluster with Ambari 2.4 and HDP 2.5 with clients on every 
> host.
> * Run multiple service checks in parallel, but notice that they typically run 
> on the same 1 or 2 hosts.
> Currently, Ambari relies on getting the list of candidate hosts from the DB 
> and excludes all hosts that are in maintenance mode. From that list, it picks 
> the first host that is healthy (i.e., heartbeating). This means that the 
> logic does not pick a random host.
> Instead, Ambari should always pick a random host and prefer to schedule on 
> hosts that have 0 in-progress commands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18619) Optimize Service Checks to it picks a random host and prefers hosts with 0 active commands

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-18619:
-
Attachment: (was: AMBARI-18169.trunk.patch)

> Optimize Service Checks to it picks a random host and prefers hosts with 0 
> active commands
> --
>
> Key: AMBARI-18619
> URL: https://issues.apache.org/jira/browse/AMBARI-18619
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18619.branch-2.5.patch, AMBARI-18619.trunk.patch
>
>
> STR:
> * Deploy a 3-node cluster with Ambari 2.4 and HDP 2.5 with clients on every 
> host.
> * Run multiple service checks in parallel, but notice that they typically run 
> on the same 1 or 2 hosts.
> Currently, Ambari relies on getting the list of candidate hosts from the DB 
> and excludes all hosts that are in maintenance mode. From that list, it picks 
> the first host that is healthy (i.e., heartbeating). This means that the 
> logic does not pick a random host.
> Instead, Ambari should always pick a random host and prefer to schedule on 
> hosts that have 0 in-progress commands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18619) Optimize Service Checks to it picks a random host and prefers hosts with 0 active commands

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-18619:
-
Attachment: (was: AMBARI-18169.branch-2.5.patch)

> Optimize Service Checks to it picks a random host and prefers hosts with 0 
> active commands
> --
>
> Key: AMBARI-18619
> URL: https://issues.apache.org/jira/browse/AMBARI-18619
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18169.trunk.patch
>
>
> STR:
> * Deploy a 3-node cluster with Ambari 2.4 and HDP 2.5 with clients on every 
> host.
> * Run multiple service checks in parallel, but notice that they typically run 
> on the same 1 or 2 hosts.
> Currently, Ambari relies on getting the list of candidate hosts from the DB 
> and excludes all hosts that are in maintenance mode. From that list, it picks 
> the first host that is healthy (i.e., heartbeating). This means that the 
> logic does not pick a random host.
> Instead, Ambari should always pick a random host and prefer to schedule on 
> hosts that have 0 in-progress commands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18619) Optimize Service Checks to it picks a random host and prefers hosts with 0 active commands

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-18619:
-
Status: Patch Available  (was: Open)

> Optimize Service Checks to it picks a random host and prefers hosts with 0 
> active commands
> --
>
> Key: AMBARI-18619
> URL: https://issues.apache.org/jira/browse/AMBARI-18619
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18169.branch-2.5.patch, AMBARI-18169.trunk.patch
>
>
> STR:
> * Deploy a 3-node cluster with Ambari 2.4 and HDP 2.5 with clients on every 
> host.
> * Run multiple service checks in parallel, but notice that they typically run 
> on the same 1 or 2 hosts.
> Currently, Ambari relies on getting the list of candidate hosts from the DB 
> and excludes all hosts that are in maintenance mode. From that list, it picks 
> the first host that is healthy (i.e., heartbeating). This means that the 
> logic does not pick a random host.
> Instead, Ambari should always pick a random host and prefer to schedule on 
> hosts that have 0 in-progress commands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18619) Optimize Service Checks to it picks a random host and prefers hosts with 0 active commands

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-18619:
-
Attachment: AMBARI-18169.trunk.patch
AMBARI-18169.branch-2.5.patch

> Optimize Service Checks to it picks a random host and prefers hosts with 0 
> active commands
> --
>
> Key: AMBARI-18619
> URL: https://issues.apache.org/jira/browse/AMBARI-18619
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18169.branch-2.5.patch, AMBARI-18169.trunk.patch
>
>
> STR:
> * Deploy a 3-node cluster with Ambari 2.4 and HDP 2.5 with clients on every 
> host.
> * Run multiple service checks in parallel, but notice that they typically run 
> on the same 1 or 2 hosts.
> Currently, Ambari relies on getting the list of candidate hosts from the DB 
> and excludes all hosts that are in maintenance mode. From that list, it picks 
> the first host that is healthy (i.e., heartbeating). This means that the 
> logic does not pick a random host.
> Instead, Ambari should always pick a random host and prefer to schedule on 
> hosts that have 0 in-progress commands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-18619) Optimize Service Checks to it picks a random host and prefers hosts with 0 active commands

[Alejandro Fernandez (JIRA)]

Alejandro Fernandez created AMBARI-18619:


 Summary: Optimize Service Checks to it picks a random host and 
prefers hosts with 0 active commands
 Key: AMBARI-18619
 URL: https://issues.apache.org/jira/browse/AMBARI-18619
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.0
Reporter: Alejandro Fernandez
Assignee: Alejandro Fernandez
Priority: Critical
 Fix For: 2.5.0


STR:
* Deploy a 3-node cluster with Ambari 2.4 and HDP 2.5 with clients on every 
host.
* Run multiple service checks in parallel, but notice that they typically run 
on the same 1 or 2 hosts.

Currently, Ambari relies on getting the list of candidate hosts from the DB and 
excludes all hosts that are in maintenance mode. From that list, it picks the 
first host that is healthy (i.e., heartbeating). This means that the logic does 
not pick a random host.

Instead, Ambari should always pick a random host and prefer to schedule on 
hosts that have 0 in-progress commands.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18575) Fix for improving time taken by 'ExecutionScheduleManagerTest' and 'UpgradeCatalog221Test' java tests.

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-18575:
---
Fix Version/s: (was: 2.4.2)

> Fix for improving time taken by 'ExecutionScheduleManagerTest' and 
> 'UpgradeCatalog221Test' java tests.
> --
>
> Key: AMBARI-18575
> URL: https://issues.apache.org/jira/browse/AMBARI-18575
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-18575.patch
>
>
> Current time taken:
> ||Test||Count||Time (s)||
> |org.apache.ambari.server.upgrade.UpgradeCatalog221Test   |13|36.586|
> |org.apache.ambari.server.scheduler.ExecutionScheduleManagerTest|9|30.685|
> Initially reported as part of test improvements (along with other tests) in 
> BUG : BUG-65777



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18615) Fix JSHint errors in Workflow Manager view

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-18615:

Status: Patch Available  (was: In Progress)

> Fix JSHint errors in Workflow Manager view
> --
>
> Key: AMBARI-18615
> URL: https://issues.apache.org/jira/browse/AMBARI-18615
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Fix For: 2.5.0
>
> Attachments: AMBARI-18615.patch
>
>
> When you compile the Workflow Manager view, you see 94 JSHint errors.
> app.js: line 18, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 19, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 20, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 21, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 23, col 1, 'let' is available in ES6 (use 'esversion: 6') or 
> Mozilla JS extensions (use moz).
> app.js: line 30, col 3, 'object short notation' is available in ES6 (use 
> 'esversion: 6') or Mozilla JS extensions (use moz).
> app.js: line 39, col 1, 'export' is only available in ES6 (use 'esversion: 
> 6').
> 7 errors
> components/action-credential-config.js: line 18, col 1, 'import' is only 
> available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 20, col 1, 'export' is only 
> available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 24, col 38, 'arrow function 
> syntax (=>)' is only available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 30, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/action-credential-config.js: line 33, col 36, 'arrow function 
> syntax (=>)' is only available in ES6 (use 'esversion: 6').
> 5 errors
> components/action-version-select.js: line 18, col 1, 'import' is only 
> available in ES6 (use 'esversion: 6').
> components/action-version-select.js: line 20, col 1, 'export' is only 
> available in ES6 (use 'esversion: 6').
> components/action-version-select.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 3 errors
> components/archive-config.js: line 18, col 1, 'import' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 19, col 1, 'import' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 21, col 1, 'export' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 29, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/archive-config.js: line 33, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/archive-config.js: line 36, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 6 errors
> components/arg-config.js: line 18, col 1, 'import' is only available in ES6 
> (use 'esversion: 6').
> components/arg-config.js: line 20, col 1, 'export' is only available in ES6 
> (use 'esversion: 6').
> components/arg-config.js: line 33, col 3, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/arg-config.js: line 38, col 5, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/arg-config.js: line 41, col 5, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 5 errors
> components/bundle-job-details.js: line 18, col 1, 'import' is only available 
> in ES6 (use 'esversion: 6').
> components/bundle-job-details.js: line 20, col 1, 'export' is only available 
> in ES6 (use 'esversion: 6').
> components/bundle-job-details.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/bundle-job-details.js: line 25, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/bundle-job-details.js: line 28, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 5 errors
> components/coord-job-details.js: line 18, col 1, 'import' is only available 
> in ES6 (use 'esversion: 6').
> components/coord-job-details.js: line 20, col 1, 'export' is only available 
> in ES6 (use 'esversion: 6').
> components/coord-job-details.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or 

[jira] [Updated] (AMBARI-18615) Fix JSHint errors in Workflow Manager view

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-18615:

Attachment: AMBARI-18615.patch

> Fix JSHint errors in Workflow Manager view
> --
>
> Key: AMBARI-18615
> URL: https://issues.apache.org/jira/browse/AMBARI-18615
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Fix For: 2.5.0
>
> Attachments: AMBARI-18615.patch
>
>
> When you compile the Workflow Manager view, you see 94 JSHint errors.
> app.js: line 18, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 19, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 20, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 21, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 23, col 1, 'let' is available in ES6 (use 'esversion: 6') or 
> Mozilla JS extensions (use moz).
> app.js: line 30, col 3, 'object short notation' is available in ES6 (use 
> 'esversion: 6') or Mozilla JS extensions (use moz).
> app.js: line 39, col 1, 'export' is only available in ES6 (use 'esversion: 
> 6').
> 7 errors
> components/action-credential-config.js: line 18, col 1, 'import' is only 
> available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 20, col 1, 'export' is only 
> available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 24, col 38, 'arrow function 
> syntax (=>)' is only available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 30, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/action-credential-config.js: line 33, col 36, 'arrow function 
> syntax (=>)' is only available in ES6 (use 'esversion: 6').
> 5 errors
> components/action-version-select.js: line 18, col 1, 'import' is only 
> available in ES6 (use 'esversion: 6').
> components/action-version-select.js: line 20, col 1, 'export' is only 
> available in ES6 (use 'esversion: 6').
> components/action-version-select.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 3 errors
> components/archive-config.js: line 18, col 1, 'import' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 19, col 1, 'import' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 21, col 1, 'export' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 29, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/archive-config.js: line 33, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/archive-config.js: line 36, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 6 errors
> components/arg-config.js: line 18, col 1, 'import' is only available in ES6 
> (use 'esversion: 6').
> components/arg-config.js: line 20, col 1, 'export' is only available in ES6 
> (use 'esversion: 6').
> components/arg-config.js: line 33, col 3, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/arg-config.js: line 38, col 5, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/arg-config.js: line 41, col 5, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 5 errors
> components/bundle-job-details.js: line 18, col 1, 'import' is only available 
> in ES6 (use 'esversion: 6').
> components/bundle-job-details.js: line 20, col 1, 'export' is only available 
> in ES6 (use 'esversion: 6').
> components/bundle-job-details.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/bundle-job-details.js: line 25, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/bundle-job-details.js: line 28, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 5 errors
> components/coord-job-details.js: line 18, col 1, 'import' is only available 
> in ES6 (use 'esversion: 6').
> components/coord-job-details.js: line 20, col 1, 'export' is only available 
> in ES6 (use 'esversion: 6').
> components/coord-job-details.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS 

[jira] [Updated] (AMBARI-18615) Fix JSHint errors in Workflow Manager view

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-18615:

Status: Open  (was: Patch Available)

> Fix JSHint errors in Workflow Manager view
> --
>
> Key: AMBARI-18615
> URL: https://issues.apache.org/jira/browse/AMBARI-18615
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Fix For: 2.5.0
>
>
> When you compile the Workflow Manager view, you see 94 JSHint errors.
> app.js: line 18, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 19, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 20, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 21, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 23, col 1, 'let' is available in ES6 (use 'esversion: 6') or 
> Mozilla JS extensions (use moz).
> app.js: line 30, col 3, 'object short notation' is available in ES6 (use 
> 'esversion: 6') or Mozilla JS extensions (use moz).
> app.js: line 39, col 1, 'export' is only available in ES6 (use 'esversion: 
> 6').
> 7 errors
> components/action-credential-config.js: line 18, col 1, 'import' is only 
> available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 20, col 1, 'export' is only 
> available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 24, col 38, 'arrow function 
> syntax (=>)' is only available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 30, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/action-credential-config.js: line 33, col 36, 'arrow function 
> syntax (=>)' is only available in ES6 (use 'esversion: 6').
> 5 errors
> components/action-version-select.js: line 18, col 1, 'import' is only 
> available in ES6 (use 'esversion: 6').
> components/action-version-select.js: line 20, col 1, 'export' is only 
> available in ES6 (use 'esversion: 6').
> components/action-version-select.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 3 errors
> components/archive-config.js: line 18, col 1, 'import' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 19, col 1, 'import' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 21, col 1, 'export' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 29, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/archive-config.js: line 33, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/archive-config.js: line 36, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 6 errors
> components/arg-config.js: line 18, col 1, 'import' is only available in ES6 
> (use 'esversion: 6').
> components/arg-config.js: line 20, col 1, 'export' is only available in ES6 
> (use 'esversion: 6').
> components/arg-config.js: line 33, col 3, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/arg-config.js: line 38, col 5, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/arg-config.js: line 41, col 5, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 5 errors
> components/bundle-job-details.js: line 18, col 1, 'import' is only available 
> in ES6 (use 'esversion: 6').
> components/bundle-job-details.js: line 20, col 1, 'export' is only available 
> in ES6 (use 'esversion: 6').
> components/bundle-job-details.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/bundle-job-details.js: line 25, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/bundle-job-details.js: line 28, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 5 errors
> components/coord-job-details.js: line 18, col 1, 'import' is only available 
> in ES6 (use 'esversion: 6').
> components/coord-job-details.js: line 20, col 1, 'export' is only available 
> in ES6 (use 'esversion: 6').
> components/coord-job-details.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 

[jira] [Updated] (AMBARI-18615) Fix JSHint errors in Workflow Manager view

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-18615:

Attachment: (was: AMBARI-18615.patch)

> Fix JSHint errors in Workflow Manager view
> --
>
> Key: AMBARI-18615
> URL: https://issues.apache.org/jira/browse/AMBARI-18615
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Fix For: 2.5.0
>
>
> When you compile the Workflow Manager view, you see 94 JSHint errors.
> app.js: line 18, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 19, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 20, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 21, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 23, col 1, 'let' is available in ES6 (use 'esversion: 6') or 
> Mozilla JS extensions (use moz).
> app.js: line 30, col 3, 'object short notation' is available in ES6 (use 
> 'esversion: 6') or Mozilla JS extensions (use moz).
> app.js: line 39, col 1, 'export' is only available in ES6 (use 'esversion: 
> 6').
> 7 errors
> components/action-credential-config.js: line 18, col 1, 'import' is only 
> available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 20, col 1, 'export' is only 
> available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 24, col 38, 'arrow function 
> syntax (=>)' is only available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 30, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/action-credential-config.js: line 33, col 36, 'arrow function 
> syntax (=>)' is only available in ES6 (use 'esversion: 6').
> 5 errors
> components/action-version-select.js: line 18, col 1, 'import' is only 
> available in ES6 (use 'esversion: 6').
> components/action-version-select.js: line 20, col 1, 'export' is only 
> available in ES6 (use 'esversion: 6').
> components/action-version-select.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 3 errors
> components/archive-config.js: line 18, col 1, 'import' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 19, col 1, 'import' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 21, col 1, 'export' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 29, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/archive-config.js: line 33, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/archive-config.js: line 36, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 6 errors
> components/arg-config.js: line 18, col 1, 'import' is only available in ES6 
> (use 'esversion: 6').
> components/arg-config.js: line 20, col 1, 'export' is only available in ES6 
> (use 'esversion: 6').
> components/arg-config.js: line 33, col 3, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/arg-config.js: line 38, col 5, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/arg-config.js: line 41, col 5, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 5 errors
> components/bundle-job-details.js: line 18, col 1, 'import' is only available 
> in ES6 (use 'esversion: 6').
> components/bundle-job-details.js: line 20, col 1, 'export' is only available 
> in ES6 (use 'esversion: 6').
> components/bundle-job-details.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/bundle-job-details.js: line 25, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/bundle-job-details.js: line 28, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 5 errors
> components/coord-job-details.js: line 18, col 1, 'import' is only available 
> in ES6 (use 'esversion: 6').
> components/coord-job-details.js: line 20, col 1, 'export' is only available 
> in ES6 (use 'esversion: 6').
> components/coord-job-details.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 

[jira] [Updated] (AMBARI-18615) Fix JSHint errors in Workflow Manager view

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-18615:

Fix Version/s: 2.5.0
Affects Version/s: 2.5.0
   Status: Patch Available  (was: In Progress)

> Fix JSHint errors in Workflow Manager view
> --
>
> Key: AMBARI-18615
> URL: https://issues.apache.org/jira/browse/AMBARI-18615
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Fix For: 2.5.0
>
> Attachments: AMBARI-18615.patch
>
>
> When you compile the Workflow Manager view, you see 94 JSHint errors.
> app.js: line 18, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 19, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 20, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 21, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 23, col 1, 'let' is available in ES6 (use 'esversion: 6') or 
> Mozilla JS extensions (use moz).
> app.js: line 30, col 3, 'object short notation' is available in ES6 (use 
> 'esversion: 6') or Mozilla JS extensions (use moz).
> app.js: line 39, col 1, 'export' is only available in ES6 (use 'esversion: 
> 6').
> 7 errors
> components/action-credential-config.js: line 18, col 1, 'import' is only 
> available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 20, col 1, 'export' is only 
> available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 24, col 38, 'arrow function 
> syntax (=>)' is only available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 30, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/action-credential-config.js: line 33, col 36, 'arrow function 
> syntax (=>)' is only available in ES6 (use 'esversion: 6').
> 5 errors
> components/action-version-select.js: line 18, col 1, 'import' is only 
> available in ES6 (use 'esversion: 6').
> components/action-version-select.js: line 20, col 1, 'export' is only 
> available in ES6 (use 'esversion: 6').
> components/action-version-select.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 3 errors
> components/archive-config.js: line 18, col 1, 'import' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 19, col 1, 'import' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 21, col 1, 'export' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 29, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/archive-config.js: line 33, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/archive-config.js: line 36, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 6 errors
> components/arg-config.js: line 18, col 1, 'import' is only available in ES6 
> (use 'esversion: 6').
> components/arg-config.js: line 20, col 1, 'export' is only available in ES6 
> (use 'esversion: 6').
> components/arg-config.js: line 33, col 3, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/arg-config.js: line 38, col 5, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/arg-config.js: line 41, col 5, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 5 errors
> components/bundle-job-details.js: line 18, col 1, 'import' is only available 
> in ES6 (use 'esversion: 6').
> components/bundle-job-details.js: line 20, col 1, 'export' is only available 
> in ES6 (use 'esversion: 6').
> components/bundle-job-details.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/bundle-job-details.js: line 25, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/bundle-job-details.js: line 28, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 5 errors
> components/coord-job-details.js: line 18, col 1, 'import' is only available 
> in ES6 (use 'esversion: 6').
> components/coord-job-details.js: line 20, col 1, 'export' is only available 
> in ES6 (use 'esversion: 6').
> components/coord-job-details.js: line 22, col 

[jira] [Updated] (AMBARI-18615) Fix JSHint errors in Workflow Manager view

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-18615:

Status: Patch Available  (was: In Progress)

> Fix JSHint errors in Workflow Manager view
> --
>
> Key: AMBARI-18615
> URL: https://issues.apache.org/jira/browse/AMBARI-18615
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Attachments: AMBARI-18615.patch
>
>
> When you compile the Workflow Manager view, you see 94 JSHint errors.
> app.js: line 18, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 19, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 20, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 21, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 23, col 1, 'let' is available in ES6 (use 'esversion: 6') or 
> Mozilla JS extensions (use moz).
> app.js: line 30, col 3, 'object short notation' is available in ES6 (use 
> 'esversion: 6') or Mozilla JS extensions (use moz).
> app.js: line 39, col 1, 'export' is only available in ES6 (use 'esversion: 
> 6').
> 7 errors
> components/action-credential-config.js: line 18, col 1, 'import' is only 
> available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 20, col 1, 'export' is only 
> available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 24, col 38, 'arrow function 
> syntax (=>)' is only available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 30, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/action-credential-config.js: line 33, col 36, 'arrow function 
> syntax (=>)' is only available in ES6 (use 'esversion: 6').
> 5 errors
> components/action-version-select.js: line 18, col 1, 'import' is only 
> available in ES6 (use 'esversion: 6').
> components/action-version-select.js: line 20, col 1, 'export' is only 
> available in ES6 (use 'esversion: 6').
> components/action-version-select.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 3 errors
> components/archive-config.js: line 18, col 1, 'import' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 19, col 1, 'import' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 21, col 1, 'export' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 29, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/archive-config.js: line 33, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/archive-config.js: line 36, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 6 errors
> components/arg-config.js: line 18, col 1, 'import' is only available in ES6 
> (use 'esversion: 6').
> components/arg-config.js: line 20, col 1, 'export' is only available in ES6 
> (use 'esversion: 6').
> components/arg-config.js: line 33, col 3, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/arg-config.js: line 38, col 5, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/arg-config.js: line 41, col 5, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 5 errors
> components/bundle-job-details.js: line 18, col 1, 'import' is only available 
> in ES6 (use 'esversion: 6').
> components/bundle-job-details.js: line 20, col 1, 'export' is only available 
> in ES6 (use 'esversion: 6').
> components/bundle-job-details.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/bundle-job-details.js: line 25, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/bundle-job-details.js: line 28, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 5 errors
> components/coord-job-details.js: line 18, col 1, 'import' is only available 
> in ES6 (use 'esversion: 6').
> components/coord-job-details.js: line 20, col 1, 'export' is only available 
> in ES6 (use 'esversion: 6').
> components/coord-job-details.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 

[jira] [Created] (AMBARI-18618) Expose App.StackServiceComponent.coHost to individual Service

[David M. Lyle (JIRA)]

David M. Lyle created AMBARI-18618:
--

 Summary: Expose App.StackServiceComponent.coHost to individual 
Service
 Key: AMBARI-18618
 URL: https://issues.apache.org/jira/browse/AMBARI-18618
 Project: Ambari
  Issue Type: Improvement
Affects Versions: 2.4.2
Reporter: David M. Lyle


Currently the HIVE/WebHCat cohost behavior is controlled in 
stack_service_component.js. I'd like to use the same behavior in a custom 
service. Please expose this capability to the individual service definition. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18615) Fix JSHint errors in Workflow Manager view

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-18615:

Status: Open  (was: Patch Available)

> Fix JSHint errors in Workflow Manager view
> --
>
> Key: AMBARI-18615
> URL: https://issues.apache.org/jira/browse/AMBARI-18615
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Attachments: AMBARI-18615.patch
>
>
> When you compile the Workflow Manager view, you see 94 JSHint errors.
> app.js: line 18, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 19, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 20, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 21, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 23, col 1, 'let' is available in ES6 (use 'esversion: 6') or 
> Mozilla JS extensions (use moz).
> app.js: line 30, col 3, 'object short notation' is available in ES6 (use 
> 'esversion: 6') or Mozilla JS extensions (use moz).
> app.js: line 39, col 1, 'export' is only available in ES6 (use 'esversion: 
> 6').
> 7 errors
> components/action-credential-config.js: line 18, col 1, 'import' is only 
> available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 20, col 1, 'export' is only 
> available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 24, col 38, 'arrow function 
> syntax (=>)' is only available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 30, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/action-credential-config.js: line 33, col 36, 'arrow function 
> syntax (=>)' is only available in ES6 (use 'esversion: 6').
> 5 errors
> components/action-version-select.js: line 18, col 1, 'import' is only 
> available in ES6 (use 'esversion: 6').
> components/action-version-select.js: line 20, col 1, 'export' is only 
> available in ES6 (use 'esversion: 6').
> components/action-version-select.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 3 errors
> components/archive-config.js: line 18, col 1, 'import' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 19, col 1, 'import' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 21, col 1, 'export' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 29, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/archive-config.js: line 33, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/archive-config.js: line 36, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 6 errors
> components/arg-config.js: line 18, col 1, 'import' is only available in ES6 
> (use 'esversion: 6').
> components/arg-config.js: line 20, col 1, 'export' is only available in ES6 
> (use 'esversion: 6').
> components/arg-config.js: line 33, col 3, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/arg-config.js: line 38, col 5, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/arg-config.js: line 41, col 5, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 5 errors
> components/bundle-job-details.js: line 18, col 1, 'import' is only available 
> in ES6 (use 'esversion: 6').
> components/bundle-job-details.js: line 20, col 1, 'export' is only available 
> in ES6 (use 'esversion: 6').
> components/bundle-job-details.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/bundle-job-details.js: line 25, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/bundle-job-details.js: line 28, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 5 errors
> components/coord-job-details.js: line 18, col 1, 'import' is only available 
> in ES6 (use 'esversion: 6').
> components/coord-job-details.js: line 20, col 1, 'export' is only available 
> in ES6 (use 'esversion: 6').
> components/coord-job-details.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/coord-job-details.js: 

[jira] [Created] (AMBARI-18617) Adding custom property to hive-site adds it to other 'Custom' panels on hive

[Dhanya Balasundaran (JIRA)]

Dhanya Balasundaran created AMBARI-18617:


 Summary: Adding custom property to hive-site adds it to other 
'Custom' panels on hive
 Key: AMBARI-18617
 URL: https://issues.apache.org/jira/browse/AMBARI-18617
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.2
Reporter: Dhanya Balasundaran
 Fix For: 2.4.2



- Navigate through Ambari Install Wizard to reach Customize Services page
- Choose Hive
- Add a custom property to Custom-hive-site
- Noticed that its getting added to Custom hivemetastore-site,
Custom hiveserver2-interactive-site, Custom hiveserver2-site, 
Custom hivemetastore-site, Custom tez-interactive-site. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18615) Fix JSHint errors in Workflow Manager view

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-18615:

Attachment: AMBARI-18615.patch

> Fix JSHint errors in Workflow Manager view
> --
>
> Key: AMBARI-18615
> URL: https://issues.apache.org/jira/browse/AMBARI-18615
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Attachments: AMBARI-18615.patch
>
>
> When you compile the Workflow Manager view, you see 94 JSHint errors.
> app.js: line 18, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 19, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 20, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 21, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 23, col 1, 'let' is available in ES6 (use 'esversion: 6') or 
> Mozilla JS extensions (use moz).
> app.js: line 30, col 3, 'object short notation' is available in ES6 (use 
> 'esversion: 6') or Mozilla JS extensions (use moz).
> app.js: line 39, col 1, 'export' is only available in ES6 (use 'esversion: 
> 6').
> 7 errors
> components/action-credential-config.js: line 18, col 1, 'import' is only 
> available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 20, col 1, 'export' is only 
> available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 24, col 38, 'arrow function 
> syntax (=>)' is only available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 30, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/action-credential-config.js: line 33, col 36, 'arrow function 
> syntax (=>)' is only available in ES6 (use 'esversion: 6').
> 5 errors
> components/action-version-select.js: line 18, col 1, 'import' is only 
> available in ES6 (use 'esversion: 6').
> components/action-version-select.js: line 20, col 1, 'export' is only 
> available in ES6 (use 'esversion: 6').
> components/action-version-select.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 3 errors
> components/archive-config.js: line 18, col 1, 'import' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 19, col 1, 'import' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 21, col 1, 'export' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 29, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/archive-config.js: line 33, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/archive-config.js: line 36, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 6 errors
> components/arg-config.js: line 18, col 1, 'import' is only available in ES6 
> (use 'esversion: 6').
> components/arg-config.js: line 20, col 1, 'export' is only available in ES6 
> (use 'esversion: 6').
> components/arg-config.js: line 33, col 3, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/arg-config.js: line 38, col 5, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/arg-config.js: line 41, col 5, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 5 errors
> components/bundle-job-details.js: line 18, col 1, 'import' is only available 
> in ES6 (use 'esversion: 6').
> components/bundle-job-details.js: line 20, col 1, 'export' is only available 
> in ES6 (use 'esversion: 6').
> components/bundle-job-details.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/bundle-job-details.js: line 25, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/bundle-job-details.js: line 28, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 5 errors
> components/coord-job-details.js: line 18, col 1, 'import' is only available 
> in ES6 (use 'esversion: 6').
> components/coord-job-details.js: line 20, col 1, 'export' is only available 
> in ES6 (use 'esversion: 6').
> components/coord-job-details.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/coord-job-details.js: line 

[jira] [Commented] (AMBARI-18601) Analyze and Optimize Ambari Server Unit Tests - - Group 4

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-18601:


LGTM, +1

> Analyze and Optimize Ambari Server Unit Tests - - Group 4
> -
>
> Key: AMBARI-18601
> URL: https://issues.apache.org/jira/browse/AMBARI-18601
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-18601-1.patch, AMBARI-18601-2.patch
>
>
> ||Test||Count||Time (s)||
> |org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.availability.MetricCollectorHAControllerTest
> | |197.933|
> |org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.discovery.TestMetadataManager|
>  |143.545|
> |org.apache.ambari.server.upgrade.UpgradeCatalog220Test   |27|60.285|
> |org.apache.ambari.server.state.ConfigHelperTest|18|45.862|
> |org.apache.ambari.server.orm.dao.ServiceConfigDAOTest|15|40.703|
> |org.apache.ambari.server.state.ServiceComponentTest|9|31.207|
> |org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest|5|38.724|



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18616) Fix Log Search User Config bug

[Miklos Gergely (JIRA)]

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

Miklos Gergely updated AMBARI-18616:

Status: Patch Available  (was: In Progress)

> Fix Log Search User Config bug
> --
>
> Key: AMBARI-18616
> URL: https://issues.apache.org/jira/browse/AMBARI-18616
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-18616.patch
>
>
> Log Search User Config UI screen does not offer the chance to modify the 
> filter settings for those logs which don't have any log entries loaded so 
> far. For these logs the initial settings will be in effect until the first 
> modification of the filters when all of these settings will be erased, and 
> thus every log will be loaded for them without filtering.
> The User Config UI should always show all the logs, first those which already 
> have some log entries in the solr, then the rest.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18616) Fix Log Search User Config bug

[Miklos Gergely (JIRA)]

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

Miklos Gergely updated AMBARI-18616:

Attachment: AMBARI-18616.patch

> Fix Log Search User Config bug
> --
>
> Key: AMBARI-18616
> URL: https://issues.apache.org/jira/browse/AMBARI-18616
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-18616.patch
>
>
> Log Search User Config UI screen does not offer the chance to modify the 
> filter settings for those logs which don't have any log entries loaded so 
> far. For these logs the initial settings will be in effect until the first 
> modification of the filters when all of these settings will be erased, and 
> thus every log will be loaded for them without filtering.
> The User Config UI should always show all the logs, first those which already 
> have some log entries in the solr, then the rest.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18600) Workflow Designer View: When logs are empty, you see the spinner, instead of a message

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18600:


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

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

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

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

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

{color:red}-1 core tests{color}.  The test build failed in 
contrib/views/wfmanager/src/main/resources/ui 

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8894//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8894//console

This message is automatically generated.

> Workflow Designer View: When logs are empty, you see the spinner, instead of 
> a message
> --
>
> Key: AMBARI-18600
> URL: https://issues.apache.org/jira/browse/AMBARI-18600
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: 2.5.0
>
> Attachments: AMBARI-18600.patch
>
>
> In the workflow designer view instance, if there is no log available for the 
> workflow, then the spinner is seen giving the impression that logs are still 
> being retrieved. This happens for all the logs, viz. the job log, error log 
> and audit log.
> A message sould be displayed when there are no messages in the log.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-18616) Fix Log Search User Config bug

[Miklos Gergely (JIRA)]

Miklos Gergely created AMBARI-18616:
---

 Summary: Fix Log Search User Config bug
 Key: AMBARI-18616
 URL: https://issues.apache.org/jira/browse/AMBARI-18616
 Project: Ambari
  Issue Type: Bug
  Components: ambari-logsearch
Affects Versions: 2.4.0
Reporter: Miklos Gergely
Assignee: Miklos Gergely
 Fix For: 2.5.0


Log Search User Config UI screen does not offer the chance to modify the filter 
settings for those logs which don't have any log entries loaded so far. For 
these logs the initial settings will be in effect until the first modification 
of the filters when all of these settings will be erased, and thus every log 
will be loaded for them without filtering.
The User Config UI should always show all the logs, first those which already 
have some log entries in the solr, then the rest.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17636) Service Configs page: can't see all config versions in dropdown

[Hudson (JIRA)]

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

Hudson commented on AMBARI-17636:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5815 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5815/])
AMBARI-17636 Service Configs page: can't see all config versions in (zhewang: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=89d964e0e0e5b6285d8207420720cd54888c])
* (edit) ambari-web/app/templates/common/configs/config_history_flow.hbs
* (edit) ambari-web/app/views/common/configs/config_history_flow.js
* (edit) ambari-web/app/styles/config_history_flow.less


> Service Configs page: can't see all config versions in dropdown
> ---
>
> Key: AMBARI-17636
> URL: https://issues.apache.org/jira/browse/AMBARI-17636
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-17636.v0.patch, AMBARI-17636.v3.patch, 
> AMBARI-17636.v4.patch, AMBARI-17636.v5.patch, AMBARI-17636.v6.patch, 
> AMBARI-17636.v7.patch, bugfix.gif
>
>
> * Go to Service->Configs page (that have more than ~ 30 versions)
> * Open versions dropdown
> *Result:*
> Number of visible versions limited by window height.
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18611) Ambari MIB Should Be Included with Installation Bits

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18611:


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

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

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

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

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

{color:red}-1 core tests{color}.  The test build failed in ambari-server 

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8893//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8893//console

This message is automatically generated.

> Ambari MIB Should Be Included with Installation Bits
> 
>
> Key: AMBARI-18611
> URL: https://issues.apache.org/jira/browse/AMBARI-18611
> Project: Ambari
>  Issue Type: Bug
>  Components: alerts
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18611.patch
>
>
> The Ambari MIB located at 
> https://github.com/apache/ambari/blob/trunk/contrib/alert-snmp-mib/APACHE-AMBARI-MIB.txt
>  should be included on the file system when Ambari is installed.
> It's location should be alongside other resources at:
> /var/lib/ambari-server/resources



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18615) Fix JSHint errors in Workflow Manager view

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-18615:

Summary: Fix JSHint errors in Workflow Manager view  (was: Fix JSHint 
errors in Workflow manage view)

> Fix JSHint errors in Workflow Manager view
> --
>
> Key: AMBARI-18615
> URL: https://issues.apache.org/jira/browse/AMBARI-18615
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>
> When you compile the Workflow Manager view, you see 94 JSHint errors.
> app.js: line 18, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 19, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 20, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 21, col 1, 'import' is only available in ES6 (use 'esversion: 
> 6').
> app.js: line 23, col 1, 'let' is available in ES6 (use 'esversion: 6') or 
> Mozilla JS extensions (use moz).
> app.js: line 30, col 3, 'object short notation' is available in ES6 (use 
> 'esversion: 6') or Mozilla JS extensions (use moz).
> app.js: line 39, col 1, 'export' is only available in ES6 (use 'esversion: 
> 6').
> 7 errors
> components/action-credential-config.js: line 18, col 1, 'import' is only 
> available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 20, col 1, 'export' is only 
> available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 24, col 38, 'arrow function 
> syntax (=>)' is only available in ES6 (use 'esversion: 6').
> components/action-credential-config.js: line 30, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/action-credential-config.js: line 33, col 36, 'arrow function 
> syntax (=>)' is only available in ES6 (use 'esversion: 6').
> 5 errors
> components/action-version-select.js: line 18, col 1, 'import' is only 
> available in ES6 (use 'esversion: 6').
> components/action-version-select.js: line 20, col 1, 'export' is only 
> available in ES6 (use 'esversion: 6').
> components/action-version-select.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 3 errors
> components/archive-config.js: line 18, col 1, 'import' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 19, col 1, 'import' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 21, col 1, 'export' is only available in 
> ES6 (use 'esversion: 6').
> components/archive-config.js: line 29, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/archive-config.js: line 33, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/archive-config.js: line 36, col 5, 'concise methods' is available 
> in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 6 errors
> components/arg-config.js: line 18, col 1, 'import' is only available in ES6 
> (use 'esversion: 6').
> components/arg-config.js: line 20, col 1, 'export' is only available in ES6 
> (use 'esversion: 6').
> components/arg-config.js: line 33, col 3, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/arg-config.js: line 38, col 5, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/arg-config.js: line 41, col 5, 'concise methods' is available in 
> ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 5 errors
> components/bundle-job-details.js: line 18, col 1, 'import' is only available 
> in ES6 (use 'esversion: 6').
> components/bundle-job-details.js: line 20, col 1, 'export' is only available 
> in ES6 (use 'esversion: 6').
> components/bundle-job-details.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/bundle-job-details.js: line 25, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> components/bundle-job-details.js: line 28, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 5 errors
> components/coord-job-details.js: line 18, col 1, 'import' is only available 
> in ES6 (use 'esversion: 6').
> components/coord-job-details.js: line 20, col 1, 'export' is only available 
> in ES6 (use 'esversion: 6').
> components/coord-job-details.js: line 22, col 5, 'concise methods' is 
> available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
> 

[jira] [Created] (AMBARI-18615) Fix JSHint errors in Workflow manage view

[Sangeeta Ravindran (JIRA)]

Sangeeta Ravindran created AMBARI-18615:
---

 Summary: Fix JSHint errors in Workflow manage view
 Key: AMBARI-18615
 URL: https://issues.apache.org/jira/browse/AMBARI-18615
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Reporter: Sangeeta Ravindran
Assignee: Sangeeta Ravindran


When you compile the Workflow Manager view, you see 94 JSHint errors.

app.js: line 18, col 1, 'import' is only available in ES6 (use 'esversion: 6').
app.js: line 19, col 1, 'import' is only available in ES6 (use 'esversion: 6').
app.js: line 20, col 1, 'import' is only available in ES6 (use 'esversion: 6').
app.js: line 21, col 1, 'import' is only available in ES6 (use 'esversion: 6').
app.js: line 23, col 1, 'let' is available in ES6 (use 'esversion: 6') or 
Mozilla JS extensions (use moz).
app.js: line 30, col 3, 'object short notation' is available in ES6 (use 
'esversion: 6') or Mozilla JS extensions (use moz).
app.js: line 39, col 1, 'export' is only available in ES6 (use 'esversion: 6').

7 errors

components/action-credential-config.js: line 18, col 1, 'import' is only 
available in ES6 (use 'esversion: 6').
components/action-credential-config.js: line 20, col 1, 'export' is only 
available in ES6 (use 'esversion: 6').
components/action-credential-config.js: line 24, col 38, 'arrow function syntax 
(=>)' is only available in ES6 (use 'esversion: 6').
components/action-credential-config.js: line 30, col 5, 'concise methods' is 
available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
components/action-credential-config.js: line 33, col 36, 'arrow function syntax 
(=>)' is only available in ES6 (use 'esversion: 6').

5 errors

components/action-version-select.js: line 18, col 1, 'import' is only available 
in ES6 (use 'esversion: 6').
components/action-version-select.js: line 20, col 1, 'export' is only available 
in ES6 (use 'esversion: 6').
components/action-version-select.js: line 22, col 5, 'concise methods' is 
available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).

3 errors

components/archive-config.js: line 18, col 1, 'import' is only available in ES6 
(use 'esversion: 6').
components/archive-config.js: line 19, col 1, 'import' is only available in ES6 
(use 'esversion: 6').
components/archive-config.js: line 21, col 1, 'export' is only available in ES6 
(use 'esversion: 6').
components/archive-config.js: line 29, col 5, 'concise methods' is available in 
ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
components/archive-config.js: line 33, col 5, 'concise methods' is available in 
ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
components/archive-config.js: line 36, col 5, 'concise methods' is available in 
ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).

6 errors

components/arg-config.js: line 18, col 1, 'import' is only available in ES6 
(use 'esversion: 6').
components/arg-config.js: line 20, col 1, 'export' is only available in ES6 
(use 'esversion: 6').
components/arg-config.js: line 33, col 3, 'concise methods' is available in ES6 
(use 'esversion: 6') or Mozilla JS extensions (use moz).
components/arg-config.js: line 38, col 5, 'concise methods' is available in ES6 
(use 'esversion: 6') or Mozilla JS extensions (use moz).
components/arg-config.js: line 41, col 5, 'concise methods' is available in ES6 
(use 'esversion: 6') or Mozilla JS extensions (use moz).

5 errors

components/bundle-job-details.js: line 18, col 1, 'import' is only available in 
ES6 (use 'esversion: 6').
components/bundle-job-details.js: line 20, col 1, 'export' is only available in 
ES6 (use 'esversion: 6').
components/bundle-job-details.js: line 22, col 5, 'concise methods' is 
available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
components/bundle-job-details.js: line 25, col 5, 'concise methods' is 
available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
components/bundle-job-details.js: line 28, col 5, 'concise methods' is 
available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).

5 errors

components/coord-job-details.js: line 18, col 1, 'import' is only available in 
ES6 (use 'esversion: 6').
components/coord-job-details.js: line 20, col 1, 'export' is only available in 
ES6 (use 'esversion: 6').
components/coord-job-details.js: line 22, col 5, 'concise methods' is available 
in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
components/coord-job-details.js: line 25, col 5, 'concise methods' is available 
in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
components/coord-job-details.js: line 28, col 5, 'concise methods' is available 
in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).

5 errors

components/credentials-config.js: line 17, col 1, 'import' is only available in 
ES6 (use 'esversion: 6').

[jira] [Commented] (AMBARI-18601) Analyze and Optimize Ambari Server Unit Tests - - Group 4

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18601:


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

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

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

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

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

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

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8892//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8892//console

This message is automatically generated.

> Analyze and Optimize Ambari Server Unit Tests - - Group 4
> -
>
> Key: AMBARI-18601
> URL: https://issues.apache.org/jira/browse/AMBARI-18601
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-18601-1.patch, AMBARI-18601-2.patch
>
>
> ||Test||Count||Time (s)||
> |org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.availability.MetricCollectorHAControllerTest
> | |197.933|
> |org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.discovery.TestMetadataManager|
>  |143.545|
> |org.apache.ambari.server.upgrade.UpgradeCatalog220Test   |27|60.285|
> |org.apache.ambari.server.state.ConfigHelperTest|18|45.862|
> |org.apache.ambari.server.orm.dao.ServiceConfigDAOTest|15|40.703|
> |org.apache.ambari.server.state.ServiceComponentTest|9|31.207|
> |org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest|5|38.724|



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18595) Icons don't display in Windows 10 Microsoft Edge or Internet Explorer 11

[Zhe (Joe) Wang (JIRA)]

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

Zhe (Joe) Wang updated AMBARI-18595:

Resolution: Fixed
Status: Resolved  (was: Patch Available)

Patch committed to trunk and branch-2.5 fdda172fed36ae3e156dc2757a09f85d0a379175

> Icons don't display in Windows 10 Microsoft Edge or Internet Explorer 11
> 
>
> Key: AMBARI-18595
> URL: https://issues.apache.org/jira/browse/AMBARI-18595
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
> Environment: Microsoft Windows 10
>  - Microsoft Edge
>  - Microsoft Internet Explorer 11
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-18595.v0.patch, Capture.PNG
>
>
> Icons do not display in any page as shown in the screen-shot attached.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17636) Service Configs page: can't see all config versions in dropdown

[Zhe (Joe) Wang (JIRA)]

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

Zhe (Joe) Wang updated AMBARI-17636:

Resolution: Fixed
Status: Resolved  (was: Patch Available)

Patch committed to branch-2.5 e41a036c5ee8891fd19f027c825e067914ab65fc and 
trunk 89d964e0e0e5b6285d8207420720cd54888c

> Service Configs page: can't see all config versions in dropdown
> ---
>
> Key: AMBARI-17636
> URL: https://issues.apache.org/jira/browse/AMBARI-17636
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-17636.v0.patch, AMBARI-17636.v3.patch, 
> AMBARI-17636.v4.patch, AMBARI-17636.v5.patch, AMBARI-17636.v6.patch, 
> AMBARI-17636.v7.patch, bugfix.gif
>
>
> * Go to Service->Configs page (that have more than ~ 30 versions)
> * Open versions dropdown
> *Result:*
> Number of visible versions limited by window height.
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17636) Service Configs page: can't see all config versions in dropdown

[Vivek Ratnavel Subramanian (JIRA)]

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

Vivek Ratnavel Subramanian updated AMBARI-17636:

Attachment: AMBARI-17636.v7.patch

> Service Configs page: can't see all config versions in dropdown
> ---
>
> Key: AMBARI-17636
> URL: https://issues.apache.org/jira/browse/AMBARI-17636
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-17636.v0.patch, AMBARI-17636.v3.patch, 
> AMBARI-17636.v4.patch, AMBARI-17636.v5.patch, AMBARI-17636.v6.patch, 
> AMBARI-17636.v7.patch, bugfix.gif
>
>
> * Go to Service->Configs page (that have more than ~ 30 versions)
> * Open versions dropdown
> *Result:*
> Number of visible versions limited by window height.
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17636) Service Configs page: can't see all config versions in dropdown

[Vivek Ratnavel Subramanian (JIRA)]

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

Vivek Ratnavel Subramanian updated AMBARI-17636:

Status: Patch Available  (was: Open)

> Service Configs page: can't see all config versions in dropdown
> ---
>
> Key: AMBARI-17636
> URL: https://issues.apache.org/jira/browse/AMBARI-17636
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-17636.v0.patch, AMBARI-17636.v3.patch, 
> AMBARI-17636.v4.patch, AMBARI-17636.v5.patch, AMBARI-17636.v6.patch, 
> AMBARI-17636.v7.patch, bugfix.gif
>
>
> * Go to Service->Configs page (that have more than ~ 30 versions)
> * Open versions dropdown
> *Result:*
> Number of visible versions limited by window height.
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17636) Service Configs page: can't see all config versions in dropdown

[Vivek Ratnavel Subramanian (JIRA)]

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

Vivek Ratnavel Subramanian updated AMBARI-17636:

Attachment: AMBARI-17636.v7.patch

> Service Configs page: can't see all config versions in dropdown
> ---
>
> Key: AMBARI-17636
> URL: https://issues.apache.org/jira/browse/AMBARI-17636
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-17636.v0.patch, AMBARI-17636.v3.patch, 
> AMBARI-17636.v4.patch, AMBARI-17636.v5.patch, AMBARI-17636.v6.patch, 
> bugfix.gif
>
>
> * Go to Service->Configs page (that have more than ~ 30 versions)
> * Open versions dropdown
> *Result:*
> Number of visible versions limited by window height.
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17636) Service Configs page: can't see all config versions in dropdown

[Vivek Ratnavel Subramanian (JIRA)]

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

Vivek Ratnavel Subramanian updated AMBARI-17636:

Attachment: (was: AMBARI-17636.v7.patch)

> Service Configs page: can't see all config versions in dropdown
> ---
>
> Key: AMBARI-17636
> URL: https://issues.apache.org/jira/browse/AMBARI-17636
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-17636.v0.patch, AMBARI-17636.v3.patch, 
> AMBARI-17636.v4.patch, AMBARI-17636.v5.patch, AMBARI-17636.v6.patch, 
> bugfix.gif
>
>
> * Go to Service->Configs page (that have more than ~ 30 versions)
> * Open versions dropdown
> *Result:*
> Number of visible versions limited by window height.
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17636) Service Configs page: can't see all config versions in dropdown

[Vivek Ratnavel Subramanian (JIRA)]

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

Vivek Ratnavel Subramanian updated AMBARI-17636:

Attachment: (was: AMBARI-17636.v7.patch)

> Service Configs page: can't see all config versions in dropdown
> ---
>
> Key: AMBARI-17636
> URL: https://issues.apache.org/jira/browse/AMBARI-17636
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-17636.v0.patch, AMBARI-17636.v3.patch, 
> AMBARI-17636.v4.patch, AMBARI-17636.v5.patch, AMBARI-17636.v6.patch, 
> bugfix.gif
>
>
> * Go to Service->Configs page (that have more than ~ 30 versions)
> * Open versions dropdown
> *Result:*
> Number of visible versions limited by window height.
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17636) Service Configs page: can't see all config versions in dropdown

[Vivek Ratnavel Subramanian (JIRA)]

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

Vivek Ratnavel Subramanian updated AMBARI-17636:

Status: Open  (was: Patch Available)

> Service Configs page: can't see all config versions in dropdown
> ---
>
> Key: AMBARI-17636
> URL: https://issues.apache.org/jira/browse/AMBARI-17636
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-17636.v0.patch, AMBARI-17636.v3.patch, 
> AMBARI-17636.v4.patch, AMBARI-17636.v5.patch, AMBARI-17636.v6.patch, 
> bugfix.gif
>
>
> * Go to Service->Configs page (that have more than ~ 30 versions)
> * Open versions dropdown
> *Result:*
> Number of visible versions limited by window height.
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17636) Service Configs page: can't see all config versions in dropdown

[Vivek Ratnavel Subramanian (JIRA)]

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

Vivek Ratnavel Subramanian updated AMBARI-17636:

Status: Patch Available  (was: Open)

> Service Configs page: can't see all config versions in dropdown
> ---
>
> Key: AMBARI-17636
> URL: https://issues.apache.org/jira/browse/AMBARI-17636
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-17636.v0.patch, AMBARI-17636.v3.patch, 
> AMBARI-17636.v4.patch, AMBARI-17636.v5.patch, AMBARI-17636.v6.patch, 
> AMBARI-17636.v7.patch, bugfix.gif
>
>
> * Go to Service->Configs page (that have more than ~ 30 versions)
> * Open versions dropdown
> *Result:*
> Number of visible versions limited by window height.
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17636) Service Configs page: can't see all config versions in dropdown

[Vivek Ratnavel Subramanian (JIRA)]

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

Vivek Ratnavel Subramanian updated AMBARI-17636:

Status: Open  (was: Patch Available)

> Service Configs page: can't see all config versions in dropdown
> ---
>
> Key: AMBARI-17636
> URL: https://issues.apache.org/jira/browse/AMBARI-17636
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-17636.v0.patch, AMBARI-17636.v3.patch, 
> AMBARI-17636.v4.patch, AMBARI-17636.v5.patch, AMBARI-17636.v6.patch, 
> AMBARI-17636.v7.patch, bugfix.gif
>
>
> * Go to Service->Configs page (that have more than ~ 30 versions)
> * Open versions dropdown
> *Result:*
> Number of visible versions limited by window height.
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17636) Service Configs page: can't see all config versions in dropdown

[Vivek Ratnavel Subramanian (JIRA)]

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

Vivek Ratnavel Subramanian updated AMBARI-17636:

Attachment: AMBARI-17636.v7.patch

> Service Configs page: can't see all config versions in dropdown
> ---
>
> Key: AMBARI-17636
> URL: https://issues.apache.org/jira/browse/AMBARI-17636
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-17636.v0.patch, AMBARI-17636.v3.patch, 
> AMBARI-17636.v4.patch, AMBARI-17636.v5.patch, AMBARI-17636.v6.patch, 
> AMBARI-17636.v7.patch, bugfix.gif
>
>
> * Go to Service->Configs page (that have more than ~ 30 versions)
> * Open versions dropdown
> *Result:*
> Number of visible versions limited by window height.
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-18614) Remove Unnecessary Locks Inside Of SCH Business Object Implementations

[Jonathan Hurley (JIRA)]

Jonathan Hurley created AMBARI-18614:


 Summary: Remove Unnecessary Locks Inside Of SCH Business Object 
Implementations
 Key: AMBARI-18614
 URL: https://issues.apache.org/jira/browse/AMBARI-18614
 Project: Ambari
  Issue Type: Task
  Components: ambari-server
Affects Versions: 2.5.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Critical
 Fix For: 2.5.0


Many of the business object implementations include needless locks which simply 
add the overhead and contention in larger clusters. Some examples of these are :

- HostImpl
-- get/set DisksInfo()
-- get/set TotalMemBytes()

- ServiceComponentHostImpl
-- get/set MaintenanceState()
-- get/set LastOpLastUpdateTime()

These types of methods are found on other business classes as well, like 
{{ClusterImpl}} and {{ServiceImpl}}. Additionally, methods like 
{{convertToResponse()}} and {{debugDump()}} need not acquire locks since they 
are used mostly for serialization of data to the web client where the data will 
then immediately become stale anyway.

The {{ServiceComponentHost}} business object should have the following work 
performed:
- Remove locking around areas where its no longer required
- Replace collections with thread-safe concurrent versions
- Remove some reliance on state-full business objects (caches)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (AMBARI-18556) Remove Unnecessary Locks Inside Of Service Business Object Implementations

[Jonathan Hurley (JIRA)]

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

Jonathan Hurley resolved AMBARI-18556.
--
Resolution: Fixed

> Remove Unnecessary Locks Inside Of Service Business Object Implementations
> --
>
> Key: AMBARI-18556
> URL: https://issues.apache.org/jira/browse/AMBARI-18556
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
>
> Many of the business object implementations include needless locks which 
> simply add the overhead and contention in larger clusters. Some examples of 
> these are :
> - HostImpl
> -- get/set DisksInfo()
> -- get/set TotalMemBytes()
> - ServiceComponentHostImpl
> -- get/set MaintenanceState()
> -- get/set LastOpLastUpdateTime()
> These types of methods are found on other business classes as well, like 
> {{ClusterImpl}} and {{ServiceImpl}}. Additionally, methods like 
> {{convertToResponse()}} and {{debugDump()}} need not acquire locks since they 
> are used mostly for serialization of data to the web client where the data 
> will then immediately become stale anyway.
> The {{Service}} business object should have the following work performed:
> - Remove locking around areas where its no longer required
> - Replace collections with thread-safe concurrent versions
> - Remove some reliance on state-full business objects (caches)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18613) Minor fixes for HDF mpack

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18613:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5814 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5814/])
AMBARI-18613: Minor fixes for HDF mpack (jluniya) (jluniya: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d132ca17354b867cb167f8800e868a27f0b6252d])
* (edit) 
contrib/management-packs/hdf-ambari-mpack/src/main/resources/common-services/NIFI/1.0.0/package/scripts/params.py
* (edit) 
contrib/management-packs/hdf-ambari-mpack/src/main/resources/stacks/HDF/2.0/repos/repoinfo.xml


> Minor fixes for HDF mpack
> -
>
> Key: AMBARI-18613
> URL: https://issues.apache.org/jira/browse/AMBARI-18613
> Project: Ambari
>  Issue Type: Bug
>  Components: contrib
>Affects Versions: trunk
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: trunk
>
> Attachments: AMBARI-18613.patch
>
>
> # Change to regex to obtain common_name_for_certificate
> # Update repoinfo.xml



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18601) Analyze and Optimize Ambari Server Unit Tests - - Group 4

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-18601:
---
Attachment: AMBARI-18601-2.patch

> Analyze and Optimize Ambari Server Unit Tests - - Group 4
> -
>
> Key: AMBARI-18601
> URL: https://issues.apache.org/jira/browse/AMBARI-18601
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-18601-1.patch, AMBARI-18601-2.patch
>
>
> ||Test||Count||Time (s)||
> |org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.availability.MetricCollectorHAControllerTest
> | |197.933|
> |org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.discovery.TestMetadataManager|
>  |143.545|
> |org.apache.ambari.server.upgrade.UpgradeCatalog220Test   |27|60.285|
> |org.apache.ambari.server.state.ConfigHelperTest|18|45.862|
> |org.apache.ambari.server.orm.dao.ServiceConfigDAOTest|15|40.703|
> |org.apache.ambari.server.state.ServiceComponentTest|9|31.207|
> |org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest|5|38.724|



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18601) Analyze and Optimize Ambari Server Unit Tests - - Group 4

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-18601:
---
Status: Patch Available  (was: Open)

> Analyze and Optimize Ambari Server Unit Tests - - Group 4
> -
>
> Key: AMBARI-18601
> URL: https://issues.apache.org/jira/browse/AMBARI-18601
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-18601-1.patch, AMBARI-18601-2.patch
>
>
> ||Test||Count||Time (s)||
> |org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.availability.MetricCollectorHAControllerTest
> | |197.933|
> |org.apache.hadoop.yarn.server.applicationhistoryservice.metrics.timeline.discovery.TestMetadataManager|
>  |143.545|
> |org.apache.ambari.server.upgrade.UpgradeCatalog220Test   |27|60.285|
> |org.apache.ambari.server.state.ConfigHelperTest|18|45.862|
> |org.apache.ambari.server.orm.dao.ServiceConfigDAOTest|15|40.703|
> |org.apache.ambari.server.state.ServiceComponentTest|9|31.207|
> |org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProviderTest|5|38.724|



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18588) Ambari server should not crash with NPE when parsing HTTP response for YARN RM properties

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18588:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #159 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/159/])
AMBARI-18588 Ambari server should not crash with NPE when parsing HTTP (dili: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=fb6a71318efd1fbeb936f02c42462e9bce9bf716])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/JsonHttpPropertyRequest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/URLStreamProvider.java


> Ambari server should not crash with NPE when parsing HTTP response for YARN 
> RM properties
> -
>
> Key: AMBARI-18588
> URL: https://issues.apache.org/jira/browse/AMBARI-18588
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-18588.patch, AMBARI-18588_v2.patch
>
>
> When YARN RM HTTP response is a 404, the response body is empty and this 
> results in an empty responseMap, that later caused Ambari server to crash 
> with NPE when it tries to read properties from the responseMap.
> This JIRA proposes to set property values as null when the responseMap is 
> null (due to empty body passed back from the YARN web server side).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18376) Deploying 2 Clusters simultaneously results in one cluster failing.

[Raymond (JIRA)]

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

Raymond updated AMBARI-18376:
-
Remaining Estimate: (was: 4h)
 Original Estimate: (was: 4h)

> Deploying 2 Clusters simultaneously results in one cluster failing.
> ---
>
> Key: AMBARI-18376
> URL: https://issues.apache.org/jira/browse/AMBARI-18376
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.2.2
>Reporter: Raymond
>Priority: Minor
>
> Steps to Reproduce:
> 1) Spin up an Ambari server node
> 2) Setup 10 ambari agent nodes
> 3) create 2 blueprints and 2 cluster templates with 5 nodes for each cluster 
> (hdfs, zookeeper, yarn)
> 4) Upload both blueprints using the ambari api
> 5) Upload both cluster templates using the ambari api
> One cluster will fail, ssh into one of the nodes (with a zookeeper server) on 
> the failed cluster.
> Find the zoo.cfg file in /etc/zookeeper (find /etc/zookeeper -name zoo.cfg)
> Actual: cat the zoo.cfg, notice all hostnames of both clusters are in this 
> file
> Expected: zoo.cfg should contain only the hostnames defined for this cluster.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18613) Minor fixes for HDF mpack

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-18613:


commit d132ca17354b867cb167f8800e868a27f0b6252d
Author: Jayush Luniya 
Date:   Mon Oct 17 13:06:51 2016 -0700

AMBARI-18613: Minor fixes for HDF mpack (jluniya)

> Minor fixes for HDF mpack
> -
>
> Key: AMBARI-18613
> URL: https://issues.apache.org/jira/browse/AMBARI-18613
> Project: Ambari
>  Issue Type: Bug
>  Components: contrib
>Affects Versions: trunk
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: trunk
>
> Attachments: AMBARI-18613.patch
>
>
> # Change to regex to obtain common_name_for_certificate
> # Update repoinfo.xml



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18588) Ambari server should not crash with NPE when parsing HTTP response for YARN RM properties

[Di Li (JIRA)]

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

Di Li commented on AMBARI-18588:


pushed to branch-2.5 as 
https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=fb6a71318efd1fbeb936f02c42462e9bce9bf716

> Ambari server should not crash with NPE when parsing HTTP response for YARN 
> RM properties
> -
>
> Key: AMBARI-18588
> URL: https://issues.apache.org/jira/browse/AMBARI-18588
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-18588.patch, AMBARI-18588_v2.patch
>
>
> When YARN RM HTTP response is a 404, the response body is empty and this 
> results in an empty responseMap, that later caused Ambari server to crash 
> with NPE when it tries to read properties from the responseMap.
> This JIRA proposes to set property values as null when the responseMap is 
> null (due to empty body passed back from the YARN web server side).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-15537) Service Level Extensions for Add-On Services

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-15537:
---
Fix Version/s: 2.4.2

> Service Level Extensions for Add-On Services
> 
>
> Key: AMBARI-15537
> URL: https://issues.apache.org/jira/browse/AMBARI-15537
> Project: Ambari
>  Issue Type: Epic
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.4.2
>
>
> In order to make add-on services self contained we need to support following 
> extension points
> - Upgrade Pack Extensions
> - Stack Advisor Extensions
> - Role Command Order Extensions. This is covered in AMBARI-9363 (service 
> level RCO extension)
> - Repo Extensions



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18613) Minor fixes for HDF mpack

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-18613:


LGTM, +1

> Minor fixes for HDF mpack
> -
>
> Key: AMBARI-18613
> URL: https://issues.apache.org/jira/browse/AMBARI-18613
> Project: Ambari
>  Issue Type: Bug
>  Components: contrib
>Affects Versions: trunk
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: trunk
>
> Attachments: AMBARI-18613.patch
>
>
> # Change to regex to obtain common_name_for_certificate
> # Update repoinfo.xml



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (AMBARI-18385) Add HDF management pack

[Jayush Luniya (JIRA)]

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

Jayush Luniya resolved AMBARI-18385.

Resolution: Fixed

> Add HDF management pack
> ---
>
> Key: AMBARI-18385
> URL: https://issues.apache.org/jira/browse/AMBARI-18385
> Project: Ambari
>  Issue Type: Bug
>  Components: contrib
>Affects Versions: trunk
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: trunk
>
> Attachments: AMBARI-18385.patch
>
>
> Add HDF management pack to Ambari



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18613) Minor fixes for HDF mpack

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-18613:


[~sumitmohanty] can you review the patch?

> Minor fixes for HDF mpack
> -
>
> Key: AMBARI-18613
> URL: https://issues.apache.org/jira/browse/AMBARI-18613
> Project: Ambari
>  Issue Type: Bug
>  Components: contrib
>Affects Versions: trunk
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: trunk
>
> Attachments: AMBARI-18613.patch
>
>
> # Change to regex to obtain common_name_for_certificate
> # Update repoinfo.xml



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18613) Minor fixes for HDF mpack

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-18613:
---
Attachment: AMBARI-18613.patch

> Minor fixes for HDF mpack
> -
>
> Key: AMBARI-18613
> URL: https://issues.apache.org/jira/browse/AMBARI-18613
> Project: Ambari
>  Issue Type: Bug
>  Components: contrib
>Affects Versions: trunk
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: trunk
>
> Attachments: AMBARI-18613.patch
>
>
> # Change to regex to obtain common_name_for_certificate
> # Update repoinfo.xml



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-18613) Minor fixes for HDF mpack

[Jayush Luniya (JIRA)]

Jayush Luniya created AMBARI-18613:
--

 Summary: Minor fixes for HDF mpack
 Key: AMBARI-18613
 URL: https://issues.apache.org/jira/browse/AMBARI-18613
 Project: Ambari
  Issue Type: Bug
  Components: contrib
Affects Versions: trunk
Reporter: Jayush Luniya
Assignee: Jayush Luniya
 Fix For: trunk


# Change to regex to obtain common_name_for_certificate
# Update repoinfo.xml



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18612) Backport AMBARI-18551 to 2.4 branch

[Venkat Ranganathan (JIRA)]

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

Venkat Ranganathan commented on AMBARI-18612:
-

bypassing rb as this is a simple fix

> Backport AMBARI-18551 to 2.4 branch
> ---
>
> Key: AMBARI-18612
> URL: https://issues.apache.org/jira/browse/AMBARI-18612
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.4.0, 2.4.1, 2.4.2
>Reporter: Venkat Ranganathan
>Assignee: Venkat Ranganathan
> Attachments: AMBARI-18612.diff
>
>
> AMBARI-18551 was applied to trunk and 2.5.   we need to apply it to 2.4 also



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18612) Backport AMBARI-18551 to 2.4 branch

[Venkat Ranganathan (JIRA)]

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

Venkat Ranganathan updated AMBARI-18612:

Attachment: AMBARI-18612.diff

> Backport AMBARI-18551 to 2.4 branch
> ---
>
> Key: AMBARI-18612
> URL: https://issues.apache.org/jira/browse/AMBARI-18612
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.4.0, 2.4.1, 2.4.2
>Reporter: Venkat Ranganathan
>Assignee: Venkat Ranganathan
> Attachments: AMBARI-18612.diff
>
>
> AMBARI-18551 was applied to trunk and 2.5.   we need to apply it to 2.4 also



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-18612) Backport AMBARI-18551 to 2.4 branch

[Venkat Ranganathan (JIRA)]

Venkat Ranganathan created AMBARI-18612:
---

 Summary: Backport AMBARI-18551 to 2.4 branch
 Key: AMBARI-18612
 URL: https://issues.apache.org/jira/browse/AMBARI-18612
 Project: Ambari
  Issue Type: Bug
  Components: ambari-agent
Affects Versions: 2.4.0, 2.4.1, 2.4.2
Reporter: Venkat Ranganathan
Assignee: Venkat Ranganathan


AMBARI-18551 was applied to trunk and 2.5.   we need to apply it to 2.4 also



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18611) Ambari MIB Should Be Included with Installation Bits

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18611:


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

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

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

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

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

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

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8891//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8891//console

This message is automatically generated.

> Ambari MIB Should Be Included with Installation Bits
> 
>
> Key: AMBARI-18611
> URL: https://issues.apache.org/jira/browse/AMBARI-18611
> Project: Ambari
>  Issue Type: Bug
>  Components: alerts
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18611.patch
>
>
> The Ambari MIB located at 
> https://github.com/apache/ambari/blob/trunk/contrib/alert-snmp-mib/APACHE-AMBARI-MIB.txt
>  should be included on the file system when Ambari is installed.
> It's location should be alongside other resources at:
> /var/lib/ambari-server/resources



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18611) Ambari MIB Should Be Included with Installation Bits

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18611:


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

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

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

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

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

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

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8890//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8890//console

This message is automatically generated.

> Ambari MIB Should Be Included with Installation Bits
> 
>
> Key: AMBARI-18611
> URL: https://issues.apache.org/jira/browse/AMBARI-18611
> Project: Ambari
>  Issue Type: Bug
>  Components: alerts
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18611.patch
>
>
> The Ambari MIB located at 
> https://github.com/apache/ambari/blob/trunk/contrib/alert-snmp-mib/APACHE-AMBARI-MIB.txt
>  should be included on the file system when Ambari is installed.
> It's location should be alongside other resources at:
> /var/lib/ambari-server/resources



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18600) Workflow Designer View: When logs are empty, you see the spinner, instead of a message

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-18600:

Attachment: AMBARI-18600.patch

> Workflow Designer View: When logs are empty, you see the spinner, instead of 
> a message
> --
>
> Key: AMBARI-18600
> URL: https://issues.apache.org/jira/browse/AMBARI-18600
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: 2.5.0
>
> Attachments: AMBARI-18600.patch
>
>
> In the workflow designer view instance, if there is no log available for the 
> workflow, then the spinner is seen giving the impression that logs are still 
> being retrieved. This happens for all the logs, viz. the job log, error log 
> and audit log.
> A message sould be displayed when there are no messages in the log.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18600) Workflow Designer View: When logs are empty, you see the spinner, instead of a message

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-18600:

Status: Patch Available  (was: Open)

> Workflow Designer View: When logs are empty, you see the spinner, instead of 
> a message
> --
>
> Key: AMBARI-18600
> URL: https://issues.apache.org/jira/browse/AMBARI-18600
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: 2.5.0
>
> Attachments: AMBARI-18600.patch
>
>
> In the workflow designer view instance, if there is no log available for the 
> workflow, then the spinner is seen giving the impression that logs are still 
> being retrieved. This happens for all the logs, viz. the job log, error log 
> and audit log.
> A message sould be displayed when there are no messages in the log.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18600) Workflow Designer View: When logs are empty, you see the spinner, instead of a message

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-18600:

Attachment: (was: AMBARI-18600.patch)

> Workflow Designer View: When logs are empty, you see the spinner, instead of 
> a message
> --
>
> Key: AMBARI-18600
> URL: https://issues.apache.org/jira/browse/AMBARI-18600
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: 2.5.0
>
>
> In the workflow designer view instance, if there is no log available for the 
> workflow, then the spinner is seen giving the impression that logs are still 
> being retrieved. This happens for all the logs, viz. the job log, error log 
> and audit log.
> A message sould be displayed when there are no messages in the log.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18600) Workflow Designer View: When logs are empty, you see the spinner, instead of a message

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-18600:

Status: Open  (was: Patch Available)

> Workflow Designer View: When logs are empty, you see the spinner, instead of 
> a message
> --
>
> Key: AMBARI-18600
> URL: https://issues.apache.org/jira/browse/AMBARI-18600
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: 2.5.0
>
>
> In the workflow designer view instance, if there is no log available for the 
> workflow, then the spinner is seen giving the impression that logs are still 
> being retrieved. This happens for all the logs, viz. the job log, error log 
> and audit log.
> A message sould be displayed when there are no messages in the log.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18611) Ambari MIB Should Be Included with Installation Bits

[Dmytro Sen (JIRA)]

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

Dmytro Sen updated AMBARI-18611:

Status: Patch Available  (was: Open)

> Ambari MIB Should Be Included with Installation Bits
> 
>
> Key: AMBARI-18611
> URL: https://issues.apache.org/jira/browse/AMBARI-18611
> Project: Ambari
>  Issue Type: Bug
>  Components: alerts
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18611.patch
>
>
> The Ambari MIB located at 
> https://github.com/apache/ambari/blob/trunk/contrib/alert-snmp-mib/APACHE-AMBARI-MIB.txt
>  should be included on the file system when Ambari is installed.
> It's location should be alongside other resources at:
> /var/lib/ambari-server/resources



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18611) Ambari MIB Should Be Included with Installation Bits

[Dmytro Sen (JIRA)]

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

Dmytro Sen updated AMBARI-18611:

Attachment: AMBARI-18611.patch

> Ambari MIB Should Be Included with Installation Bits
> 
>
> Key: AMBARI-18611
> URL: https://issues.apache.org/jira/browse/AMBARI-18611
> Project: Ambari
>  Issue Type: Bug
>  Components: alerts
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18611.patch
>
>
> The Ambari MIB located at 
> https://github.com/apache/ambari/blob/trunk/contrib/alert-snmp-mib/APACHE-AMBARI-MIB.txt
>  should be included on the file system when Ambari is installed.
> It's location should be alongside other resources at:
> /var/lib/ambari-server/resources



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-18611) Ambari MIB Should Be Included with Installation Bits

[Dmytro Sen (JIRA)]

Dmytro Sen created AMBARI-18611:
---

 Summary: Ambari MIB Should Be Included with Installation Bits
 Key: AMBARI-18611
 URL: https://issues.apache.org/jira/browse/AMBARI-18611
 Project: Ambari
  Issue Type: Bug
  Components: alerts
Affects Versions: 2.5.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Priority: Critical
 Fix For: 2.5.0


The Ambari MIB located at 
https://github.com/apache/ambari/blob/trunk/contrib/alert-snmp-mib/APACHE-AMBARI-MIB.txt
 should be included on the file system when Ambari is installed.
It's location should be alongside other resources at:
/var/lib/ambari-server/resources



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-18610) Use knox to connect to Spark-thrift server

[Davide Isoardi (JIRA)]

Davide Isoardi created AMBARI-18610:
---

 Summary: Use knox to connect to Spark-thrift server
 Key: AMBARI-18610
 URL: https://issues.apache.org/jira/browse/AMBARI-18610
 Project: Ambari
  Issue Type: Improvement
  Components: ambari-server
Affects Versions: 2.2.2
Reporter: Davide Isoardi
Priority: Minor


Add the features for connecting to Spark-thrift server via Knox with JDBC 
connection in a kerberized environment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18600) Workflow Designer View: When logs are empty, you see the spinner, instead of a message

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-18600:

Attachment: AMBARI-18600.patch

> Workflow Designer View: When logs are empty, you see the spinner, instead of 
> a message
> --
>
> Key: AMBARI-18600
> URL: https://issues.apache.org/jira/browse/AMBARI-18600
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: 2.5.0
>
> Attachments: AMBARI-18600.patch
>
>
> In the workflow designer view instance, if there is no log available for the 
> workflow, then the spinner is seen giving the impression that logs are still 
> being retrieved. This happens for all the logs, viz. the job log, error log 
> and audit log.
> A message sould be displayed when there are no messages in the log.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18600) Workflow Designer View: When logs are empty, you see the spinner, instead of a message

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-18600:

Attachment: (was: AMBARI-18600.patch)

> Workflow Designer View: When logs are empty, you see the spinner, instead of 
> a message
> --
>
> Key: AMBARI-18600
> URL: https://issues.apache.org/jira/browse/AMBARI-18600
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: 2.5.0
>
>
> In the workflow designer view instance, if there is no log available for the 
> workflow, then the spinner is seen giving the impression that logs are still 
> being retrieved. This happens for all the logs, viz. the job log, error log 
> and audit log.
> A message sould be displayed when there are no messages in the log.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14384) Ambari Metrics doesn't use SPNEGO to authenticate

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-14384:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12833744/AMBARI-14384.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:red}-1 javac{color:red}.  The patch appears to cause the build to 
fail.

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

This message is automatically generated.

> Ambari Metrics doesn't use SPNEGO to authenticate
> -
>
> Key: AMBARI-14384
> URL: https://issues.apache.org/jira/browse/AMBARI-14384
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-metrics
>Affects Versions: 2.1.2
>Reporter: Ward Viaene
>Assignee: Dmytro Sen
> Fix For: 2.5.0
>
> Attachments: AMBARI-14384.patch
>
>
> * Kerberos enabled cluster
> * SPNEGO enabled on hadoop APIs
> /var/log/ambari-metrics-monitor/ambari-metrics-monitor.out:
> 2015-12-15 13:26:30,663 [INFO] emitter.py:101 - server: 
> http://metrics-collector:6188/ws/v1/timeline/metrics
> 2015-12-15 13:26:30,671 [WARNING] emitter.py:84 - Error sending metrics to 
> server. HTTP Error 401: Authentication required
> 2015-12-15 13:26:30,671 [WARNING] emitter.py:90 - Retrying after 5 ...
> The same problem appears to be happening on the sinks:
> * 
> ambari/ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/AbstractTimelineMetricsSink.java
> ** No SPNEGO support



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18588) Ambari server should not crash with NPE when parsing HTTP response for YARN RM properties

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18588:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5812 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5812/])
AMBARI-18588 Ambari server should not crash with NPE when parsing HTTP (dili: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=73f1dea9674359ecbfd723917c83913b20986906])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/JsonHttpPropertyRequest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/URLStreamProvider.java


> Ambari server should not crash with NPE when parsing HTTP response for YARN 
> RM properties
> -
>
> Key: AMBARI-18588
> URL: https://issues.apache.org/jira/browse/AMBARI-18588
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-18588.patch, AMBARI-18588_v2.patch
>
>
> When YARN RM HTTP response is a 404, the response body is empty and this 
> results in an empty responseMap, that later caused Ambari server to crash 
> with NPE when it tries to read properties from the responseMap.
> This JIRA proposes to set property values as null when the responseMap is 
> null (due to empty body passed back from the YARN web server side).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14384) Ambari Metrics doesn't use SPNEGO to authenticate

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-14384:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12833744/AMBARI-14384.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:red}-1 javac{color:red}.  The patch appears to cause the build to 
fail.

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

This message is automatically generated.

> Ambari Metrics doesn't use SPNEGO to authenticate
> -
>
> Key: AMBARI-14384
> URL: https://issues.apache.org/jira/browse/AMBARI-14384
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-metrics
>Affects Versions: 2.1.2
>Reporter: Ward Viaene
>Assignee: Dmytro Sen
> Fix For: 2.5.0
>
> Attachments: AMBARI-14384.patch
>
>
> * Kerberos enabled cluster
> * SPNEGO enabled on hadoop APIs
> /var/log/ambari-metrics-monitor/ambari-metrics-monitor.out:
> 2015-12-15 13:26:30,663 [INFO] emitter.py:101 - server: 
> http://metrics-collector:6188/ws/v1/timeline/metrics
> 2015-12-15 13:26:30,671 [WARNING] emitter.py:84 - Error sending metrics to 
> server. HTTP Error 401: Authentication required
> 2015-12-15 13:26:30,671 [WARNING] emitter.py:90 - Retrying after 5 ...
> The same problem appears to be happening on the sinks:
> * 
> ambari/ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/AbstractTimelineMetricsSink.java
> ** No SPNEGO support



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18588) Ambari server should not crash with NPE when parsing HTTP response for YARN RM properties

[Di Li (JIRA)]

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

Di Li commented on AMBARI-18588:


pushed to trunk as 
https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=73f1dea9674359ecbfd723917c83913b20986906

> Ambari server should not crash with NPE when parsing HTTP response for YARN 
> RM properties
> -
>
> Key: AMBARI-18588
> URL: https://issues.apache.org/jira/browse/AMBARI-18588
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-18588.patch, AMBARI-18588_v2.patch
>
>
> When YARN RM HTTP response is a 404, the response body is empty and this 
> results in an empty responseMap, that later caused Ambari server to crash 
> with NPE when it tries to read properties from the responseMap.
> This JIRA proposes to set property values as null when the responseMap is 
> null (due to empty body passed back from the YARN web server side).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18588) Ambari server should not crash with NPE when parsing HTTP response for YARN RM properties

[Di Li (JIRA)]

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

Di Li updated AMBARI-18588:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Ambari server should not crash with NPE when parsing HTTP response for YARN 
> RM properties
> -
>
> Key: AMBARI-18588
> URL: https://issues.apache.org/jira/browse/AMBARI-18588
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-18588.patch, AMBARI-18588_v2.patch
>
>
> When YARN RM HTTP response is a 404, the response body is empty and this 
> results in an empty responseMap, that later caused Ambari server to crash 
> with NPE when it tries to read properties from the responseMap.
> This JIRA proposes to set property values as null when the responseMap is 
> null (due to empty body passed back from the YARN web server side).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-14384) Ambari Metrics doesn't use SPNEGO to authenticate

[Dmytro Sen (JIRA)]

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

Dmytro Sen updated AMBARI-14384:

Status: Patch Available  (was: Open)

> Ambari Metrics doesn't use SPNEGO to authenticate
> -
>
> Key: AMBARI-14384
> URL: https://issues.apache.org/jira/browse/AMBARI-14384
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-metrics
>Affects Versions: 2.1.2
>Reporter: Ward Viaene
>Assignee: Dmytro Sen
> Fix For: 2.5.0
>
> Attachments: AMBARI-14384.patch
>
>
> * Kerberos enabled cluster
> * SPNEGO enabled on hadoop APIs
> /var/log/ambari-metrics-monitor/ambari-metrics-monitor.out:
> 2015-12-15 13:26:30,663 [INFO] emitter.py:101 - server: 
> http://metrics-collector:6188/ws/v1/timeline/metrics
> 2015-12-15 13:26:30,671 [WARNING] emitter.py:84 - Error sending metrics to 
> server. HTTP Error 401: Authentication required
> 2015-12-15 13:26:30,671 [WARNING] emitter.py:90 - Retrying after 5 ...
> The same problem appears to be happening on the sinks:
> * 
> ambari/ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/AbstractTimelineMetricsSink.java
> ** No SPNEGO support



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-14384) Ambari Metrics doesn't use SPNEGO to authenticate

[Dmytro Sen (JIRA)]

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

Dmytro Sen updated AMBARI-14384:

Attachment: AMBARI-14384.patch

> Ambari Metrics doesn't use SPNEGO to authenticate
> -
>
> Key: AMBARI-14384
> URL: https://issues.apache.org/jira/browse/AMBARI-14384
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-metrics
>Affects Versions: 2.1.2
>Reporter: Ward Viaene
>Assignee: Dmytro Sen
> Fix For: 2.5.0
>
> Attachments: AMBARI-14384.patch
>
>
> * Kerberos enabled cluster
> * SPNEGO enabled on hadoop APIs
> /var/log/ambari-metrics-monitor/ambari-metrics-monitor.out:
> 2015-12-15 13:26:30,663 [INFO] emitter.py:101 - server: 
> http://metrics-collector:6188/ws/v1/timeline/metrics
> 2015-12-15 13:26:30,671 [WARNING] emitter.py:84 - Error sending metrics to 
> server. HTTP Error 401: Authentication required
> 2015-12-15 13:26:30,671 [WARNING] emitter.py:90 - Retrying after 5 ...
> The same problem appears to be happening on the sinks:
> * 
> ambari/ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/AbstractTimelineMetricsSink.java
> ** No SPNEGO support



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18609) Implement a way to configure Stack Upgrade Merger to skip particular properties to be merged from stack defaults

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18609:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12833726/AMBARI-18609.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 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

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

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

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8887//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8887//console

This message is automatically generated.

> Implement a way to configure Stack Upgrade Merger to skip particular 
> properties to be merged from stack defaults
> 
>
> Key: AMBARI-18609
> URL: https://issues.apache.org/jira/browse/AMBARI-18609
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18609.patch
>
>
> We need to reincarnate on-stack-upgrade feature in less functionality way. 
> It's true, that we don't need an analog to Stack Advisor or Upgrade Packs, 
> however we need a way to exclude some property from being merged with stack 
> defaults during Upgrade.
> Why we need this: there could be a lot of situations, when we need some 
> properties only in some 
> picante moments, and these properties regulated according to Stack 
> Advisor/Wizards or another internal state. In this case, these properties 
> shipped with dummy stack default values, which are incorrect.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18607) Test and fix new tables styles on Ambari

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18607:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5811 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5811/])
AMBARI-18607. Test and fix new tables styles on Ambari (alexantonenko) (hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5c32fed74cce667bacffbe7f0d549ceed709e3fc])
* (edit) ambari-web/app/templates/main/host/host_alerts.hbs
* (edit) ambari-web/app/templates/main/alerts/add_definition_to_group_popup.hbs
* (edit) ambari-web/app/templates/wizard/step6.hbs
* (edit) 
ambari-web/app/templates/common/modal_popups/config_recommendation_popup.hbs
* (edit) ambari-web/app/templates/main/admin/stack_upgrade/services.hbs
* (edit) ambari-web/app/templates/main/dashboard/config_history.hbs
* (edit) ambari-web/app/templates/wizard/step3.hbs
* (edit) ambari-web/app/styles/config_history_flow.less
* (edit) ambari-web/app/templates/main/admin/serviceAccounts.hbs
* (edit) ambari-web/app/templates/main/admin/stack_upgrade/upgrade_history.hbs
* (edit) ambari-web/app/templates/main/views.hbs
* (edit) ambari-web/app/templates/main/alerts/definition_details.hbs
* (edit) ambari-web/app/templates/common/modal_popups/hosts_table_list_popup.hbs
* (edit) ambari-web/app/templates/main/alerts.hbs
* (edit) ambari-web/app/templates/wizard/step9/step9_install_host_popup.hbs
* (edit) ambari-web/app/styles/theme/bootstrap-ambari.css
* (edit) ambari-web/app/views/main/alert_definitions_view.js
* (edit) ambari-web/app/templates/wizard/step4.hbs
* (edit) ambari-web/app/templates/common/configs/propertyDependence.hbs
* (edit) ambari-web/app/styles/alerts.less
* (edit) ambari-web/app/templates/main/host.hbs
* (edit) ambari-web/app/templates/common/modal_popups/dependent_configs_list.hbs
* (edit) ambari-web/app/templates/experimental.hbs
* (edit) ambari-web/app/templates/main/host/logs.hbs
* (edit) ambari-web/app/templates/wizard/step1.hbs
* (edit) ambari-web/app/templates/main/service/info/configs_save_popup.hbs
* (edit) ambari-web/app/templates/main/host/addHost/step4.hbs
* (edit) ambari-web/app/styles/modal_popups.less
* (edit) ambari-web/app/templates/common/configs/overrideWindow.hbs
* (edit) ambari-web/app/templates/main/host/stack_versions.hbs
* (edit) ambari-web/app/templates/common/settings.hbs
* (edit) ambari-web/app/styles/application.less
* (edit) 
ambari-web/app/templates/main/admin/stack_upgrade/upgrade_configs_merge_table.hbs


> Test and fix new tables styles on Ambari
> 
>
> Key: AMBARI-18607
> URL: https://issues.apache.org/jira/browse/AMBARI-18607
> 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-18607.patch
>
>
> Implement basic tables styling.
> Add missing classnames and HTML tags for tables where needed.
> Remove redundant styles.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)