[jira] [Updated] (AMBARI-19570) Hive View 2.0.0: Enable view of ranger authorization for a table

[DIPAYAN BHOWMICK (JIRA)]

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

DIPAYAN BHOWMICK updated AMBARI-19570:
--
Status: Patch Available  (was: Open)

> Hive View 2.0.0: Enable view of ranger authorization for a table
> 
>
> Key: AMBARI-19570
> URL: https://issues.apache.org/jira/browse/AMBARI-19570
> Project: Ambari
>  Issue Type: Bug
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.5.0
>
> Attachments: AMBARI-19570.branch-2.5.patch
>
>
> User should be able to see the users and groups authorized to access the 
> table(through ranger) in table manager.



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

[jira] [Resolved] (AMBARI-19570) Hive View 2.0.0: Enable view of ranger authorization for a table

[DIPAYAN BHOWMICK (JIRA)]

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

DIPAYAN BHOWMICK resolved AMBARI-19570.
---
Resolution: Fixed

> Hive View 2.0.0: Enable view of ranger authorization for a table
> 
>
> Key: AMBARI-19570
> URL: https://issues.apache.org/jira/browse/AMBARI-19570
> Project: Ambari
>  Issue Type: Bug
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.5.0
>
> Attachments: AMBARI-19570.branch-2.5.patch
>
>
> User should be able to see the users and groups authorized to access the 
> table(through ranger) in table manager.



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

[jira] [Updated] (AMBARI-19570) Hive View 2.0.0: Enable view of ranger authorization for a table

[DIPAYAN BHOWMICK (JIRA)]

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

DIPAYAN BHOWMICK updated AMBARI-19570:
--
Status: In Progress  (was: Patch Available)

Checked in to branch-2.5, trunk

> Hive View 2.0.0: Enable view of ranger authorization for a table
> 
>
> Key: AMBARI-19570
> URL: https://issues.apache.org/jira/browse/AMBARI-19570
> Project: Ambari
>  Issue Type: Bug
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.5.0
>
> Attachments: AMBARI-19570.branch-2.5.patch
>
>
> User should be able to see the users and groups authorized to access the 
> table(through ranger) in table manager.



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

[jira] [Updated] (AMBARI-19578) Fix issues around modifying yarn min container size

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-19578:
---
Summary: Fix issues around modifying yarn min container size  (was: Fix 
minor issues around modifying yarn min container size)

> Fix issues around modifying yarn min container size
> ---
>
> Key: AMBARI-19578
> URL: https://issues.apache.org/jira/browse/AMBARI-19578
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19578.patch
>
>
> * rename variables
> * do not over write yarn.nodemanager.resource.memory-mb when its not a fresh 
> install
> * re-valuate how "ramPerContainer" is evaluated wrt 
> yarn.scheduler.minimum-allocation-mb



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

[jira] [Updated] (AMBARI-19578) Fix minor issues around modifying yarn min container size

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-19578:
---
Status: Patch Available  (was: Open)

> Fix minor issues around modifying yarn min container size
> -
>
> Key: AMBARI-19578
> URL: https://issues.apache.org/jira/browse/AMBARI-19578
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19578.patch
>
>
> * rename variables
> * do not over write yarn.nodemanager.resource.memory-mb when its not a fresh 
> install
> * re-valuate how "ramPerContainer" is evaluated wrt 
> yarn.scheduler.minimum-allocation-mb



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

[jira] [Commented] (AMBARI-19529) Atlas service check should fail only if all metadata servers are down.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19529:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6459 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6459/])
AMBARI-19529 : Atlas service check should fail only if all metadata (mugdha: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=badf9f7bb7037597e0887614ce68bfb800f7b705])
* (edit) 
ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/service_check.py


> Atlas service check should fail only if all metadata servers are down.
> --
>
> Key: AMBARI-19529
> URL: https://issues.apache.org/jira/browse/AMBARI-19529
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-19529_branch-2.5 .patch, AMBARI-19529_trunk.patch
>
>
> On Atlas-HA environments, Atlas service check fails even if one of the hosts 
> is down, the service check should only fail when All the Atlas metadata 
> servers are down.



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

[jira] [Updated] (AMBARI-19578) Fix minor issues around modifying yarn min container size

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-19578:
---
Attachment: AMBARI-19578.patch

> Fix minor issues around modifying yarn min container size
> -
>
> Key: AMBARI-19578
> URL: https://issues.apache.org/jira/browse/AMBARI-19578
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19578.patch
>
>
> * rename variables
> * do not over write yarn.nodemanager.resource.memory-mb when its not a fresh 
> install
> * re-valuate how "ramPerContainer" is evaluated wrt 
> yarn.scheduler.minimum-allocation-mb



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

[jira] [Created] (AMBARI-19578) Fix minor issues around modifying yarn min container size

[Sumit Mohanty (JIRA)]

Sumit Mohanty created AMBARI-19578:
--

 Summary: Fix minor issues around modifying yarn min container size
 Key: AMBARI-19578
 URL: https://issues.apache.org/jira/browse/AMBARI-19578
 Project: Ambari
  Issue Type: Bug
  Components: stacks
Affects Versions: 2.5.0
Reporter: Sumit Mohanty
Assignee: Sumit Mohanty
Priority: Critical
 Fix For: 2.5.0


* rename variables
* do not over write yarn.nodemanager.resource.memory-mb when its not a fresh 
install
* re-valuate how "ramPerContainer" is evaluated wrt 
yarn.scheduler.minimum-allocation-mb



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

[jira] [Updated] (AMBARI-18829) Allow Ambari to manage Kafka's Custom JAAS Config

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-18829:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Allow Ambari to manage Kafka's Custom JAAS Config
> -
>
> Key: AMBARI-18829
> URL: https://issues.apache.org/jira/browse/AMBARI-18829
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18829.patch
>
>
> Move kafka_jaas_conf.j2 and kafka_client_jaas_conf.j2 as configurations that 
> can be edited using Ambari.



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

[jira] [Updated] (AMBARI-18969) Add support to provide additional slider specific parameters to llap

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-18969:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Add support to provide additional slider specific parameters to llap
> 
>
> Key: AMBARI-18969
> URL: https://issues.apache.org/jira/browse/AMBARI-18969
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18969.patch
>
>
> Parameters need to be provided to the 
> slider --service llap script, to restrict the range of ports.
> The range of ports needs to be taken as input from the user.
> Ambari could either add this as a port list field, or a more generic 
> slider.global-conf entry list.



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

[jira] [Commented] (AMBARI-19576) Downgrade request fails as existing Upgrade request is considered 'in progress'

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19576:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12847719/AMBARI-19576.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 test build failed in ambari-web 

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

This message is automatically generated.

> Downgrade request fails as existing Upgrade request is considered 'in 
> progress'
> ---
>
> Key: AMBARI-19576
> URL: https://issues.apache.org/jira/browse/AMBARI-19576
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19576.patch
>
>
> ambari-server --hash
> c1748443f8585c9457691c2a39e35da1d3e66c52
> Build #2.5.0.0-633
> *STR*
> # Started Express Upgrade to HDP-2.6.0.0 (via UI)
> # Hit downgrade at first manual prompt
> *Result*
> Downgrade failed with below error:
> {code}
> 14 Jan 2017 16:53:46,013 ERROR [ambari-client-thread-35] 
> AbstractResourceProvider:285 - Caught AmbariException when creating a resource
> org.apache.ambari.server.AmbariException: Unable to perform downgrade as 
> another downgrade (request ID 293) is in progress.
> at 
> org.apache.ambari.server.controller.internal.UpgradeResourceProvider$PreReqCheckValidator.check(UpgradeResourceProvider.java:2028)
> at 
> org.apache.ambari.server.controller.internal.UpgradeResourceProvider$UpgradeRequestValidator.validate(UpgradeResourceProvider.java:1952)
> at 
> org.apache.ambari.server.controller.internal.UpgradeResourceProvider$UpgradeRequestValidator.validate(UpgradeResourceProvider.java:1956)
> at 
> org.apache.ambari.server.controller.internal.UpgradeResourceProvider.validateRequest(UpgradeResourceProvider.java:660)
> at 
> org.apache.ambari.server.controller.internal.UpgradeResourceProvider.access$100(UpgradeResourceProvider.java:140)
> at 
> org.apache.ambari.server.controller.internal.UpgradeResourceProvider$1.invoke(UpgradeResourceProvider.java:399)
> at 
> org.apache.ambari.server.controller.internal.UpgradeResourceProvider$1.invoke(UpgradeResourceProvider.java:374)
> at 
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.invokeWithRetry(AbstractResourceProvider.java:455)
> at 
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.createResources(AbstractResourceProvider.java:278)
> at 
> org.apache.ambari.server.controller.internal.UpgradeResourceProvider.createResources(UpgradeResourceProvider.java:374)
> at 
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
> at 
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
> at 
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37)
> at 
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73)
> at 
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
> at 
> org.apache.ambari.server.api.services.UpgradeService.createUpgrade(UpgradeService.java:58)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> {code}



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

[jira] [Updated] (AMBARI-19230) Ambari does not select correct heap size for HSIHS2

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-19230:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Ambari does not select correct heap size for HSIHS2
> ---
>
> Key: AMBARI-19230
> URL: https://issues.apache.org/jira/browse/AMBARI-19230
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19230.patch
>
>
> Ensure that by default heap size for HS2 is picked up for HSI HS2.
> In addition there is a UT failure that needed fixing.



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

[jira] [Updated] (AMBARI-19338) AM sizing for LLAP - min container size changes

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-19338:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> AM sizing for LLAP - min container size changes
> ---
>
> Key: AMBARI-19338
> URL: https://issues.apache.org/jira/browse/AMBARI-19338
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Reporter: Dmytro Sen
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19338_2.patch, AMBARI-19338_3.patch
>
>
> Currently, AMs are sized too big for LLAP (especially with small setups). 
> Better defaults are needed, but min container size has to change for that. 



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

[jira] [Updated] (AMBARI-18986) Deployment failure when command does not have role

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-18986:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Deployment failure when command does not have role
> --
>
> Key: AMBARI-18986
> URL: https://issues.apache.org/jira/browse/AMBARI-18986
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent, stacks
>Affects Versions: 2.5.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18986.patch
>
>
> Deployment failures as some custom commands for security (kerberization) do 
> not populate "role".
> {code}
> ERROR 2016-11-24 17:03:40,971 CustomServiceOrchestrator.py:235 - Caught an 
> exception while executing custom service command:  'exceptions.KeyError'>: 'role'; 'role'
> Traceback (most recent call last):
>   File 
> "/usr/lib/python2.6/site-packages/ambari_agent/CustomServiceOrchestrator.py", 
> line 157, in runCommand
> if command['role'] == self.METRICS_GRAFANA:
> KeyError: 'role'
> {code}



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

[jira] [Updated] (AMBARI-19157) hive_heapsize property should not auto add m

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-19157:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> hive_heapsize property should not auto add m
> 
>
> Key: AMBARI-19157
> URL: https://issues.apache.org/jira/browse/AMBARI-19157
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web, stacks
>Affects Versions: 2.5.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.5.0
>
> Attachments: AMBARI-19157.patch
>
>
> ambari web auto adds 'm' to hive_heapsize property and that leads to an extra 
> m in the hive-env.sh file.



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

[jira] [Commented] (AMBARI-19545) Ambari-agent: In HIVE and OOZIE stack scripts, copy JCEKS file to desired location

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19545:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6458 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6458/])
AMBARI-19545: Ambari-agent - In HIVE and OOZIE stack scripts, copy JCEKS 
(nsomasundaram: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ded8ee71c1c50ac76bc70ad8df8c39c7654d3fe9])
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py
* (edit) 
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie.py


> Ambari-agent: In HIVE and OOZIE stack scripts, copy JCEKS file to desired 
> location
> --
>
> Key: AMBARI-19545
> URL: https://issues.apache.org/jira/browse/AMBARI-19545
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: rb55538.patch
>
>
> Ambari agent generates the JCEKS provider files as 
> /var/lib/ambari-agent/cred/conf//.jceks. 
> OOZIE and HIVE scripts should specify a location of their choice and set the 
> desired ACLs, instead of using the default location.



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

[jira] [Updated] (AMBARI-19529) Atlas service check should fail only if all metadata servers are down.

[Mugdha Varadkar (JIRA)]

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

Mugdha Varadkar updated AMBARI-19529:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to branch-2.5: 
[d54fab9aee119428427bad38f5f5df011f0c3b48|https://github.com/apache/ambari/commit/d54fab9aee119428427bad38f5f5df011f0c3b48]
and trunk: 
[badf9f7bb7037597e0887614ce68bfb800f7b705|https://github.com/apache/ambari/commit/badf9f7bb7037597e0887614ce68bfb800f7b705]

> Atlas service check should fail only if all metadata servers are down.
> --
>
> Key: AMBARI-19529
> URL: https://issues.apache.org/jira/browse/AMBARI-19529
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-19529_branch-2.5 .patch, AMBARI-19529_trunk.patch
>
>
> On Atlas-HA environments, Atlas service check fails even if one of the hosts 
> is down, the service check should only fail when All the Atlas metadata 
> servers are down.



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

[jira] [Updated] (AMBARI-19545) Ambari-agent: In HIVE and OOZIE stack scripts, copy JCEKS file to desired location

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-19545:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Ambari-agent: In HIVE and OOZIE stack scripts, copy JCEKS file to desired 
> location
> --
>
> Key: AMBARI-19545
> URL: https://issues.apache.org/jira/browse/AMBARI-19545
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: rb55538.patch
>
>
> Ambari agent generates the JCEKS provider files as 
> /var/lib/ambari-agent/cred/conf//.jceks. 
> OOZIE and HIVE scripts should specify a location of their choice and set the 
> desired ACLs, instead of using the default location.



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

[jira] [Created] (AMBARI-19577) Add Livy session recovery configurations in Ambari

[Saisai Shao (JIRA)]

Saisai Shao created AMBARI-19577:


 Summary: Add Livy session recovery configurations in Ambari
 Key: AMBARI-19577
 URL: https://issues.apache.org/jira/browse/AMBARI-19577
 Project: Ambari
  Issue Type: Bug
  Components: stacks
Affects Versions: 2.5.0
Reporter: Saisai Shao
Assignee: Saisai Shao


Update the Ambari Livy configurations to support session recovery.



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

[jira] [Commented] (AMBARI-19097) HDP 3.0 TP - create Service Advisor for HDFS

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19097:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6457 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6457/])
AMBARI-19097. HDP 3.0 TP - create Service Advisor for HDFS (alejandro) 
(afernandez: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=326cc1b2a1e05073050a38ea104d6d63ed76f373])
* (edit) 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/stack_advisor.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py
* (edit) 
ambari-server/src/main/resources/stacks/HDPWIN/2.1/services/stack_advisor.py
* (edit) ambari-server/src/main/resources/stacks/stack_advisor.py
* (edit) ambari-server/src/test/python/TestStackAdvisor.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/common/test_stack_advisor.py
* (edit) 
ambari-server/src/main/resources/stacks/HDPWIN/2.2/services/stack_advisor.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.1/services/stack_advisor.py
* (edit) ambari-server/src/test/python/stacks/2.1/common/test_stack_advisor.py
* (add) 
ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/service_advisor.py
* (edit) 
ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.9/service_advisor.py


> HDP 3.0 TP - create Service Advisor for HDFS
> 
>
> Key: AMBARI-19097
> URL: https://issues.apache.org/jira/browse/AMBARI-19097
> Project: Ambari
>  Issue Type: Story
>  Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19097.patch
>
>
> Create a Service Advisor script for HDFS in HDP 3.0 Tech Preview.
> The Service Advisor must encapsulate all of the logic inherited/overwritten 
> from HDP 2.0.6 through HDP 2.6



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

[jira] [Commented] (AMBARI-19559) Log Namenode formatting output into ambari-agent command logs

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19559:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6457 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6457/])
Revert "Revert "AMBARI-19559. Log Namenode formatting output into (smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=733f2478ac964f9af33a6b82490062295c4a42b7])
* (edit) 
ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/hdfs_namenode.py
* (edit) 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/hdfs_namenode.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py
* (edit) 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py


> Log Namenode formatting output into ambari-agent command logs
> -
>
> Key: AMBARI-19559
> URL: https://issues.apache.org/jira/browse/AMBARI-19559
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
> Fix For: 2.5.0
>
> Attachments: AMBARI-19559.branch-2.5.v1.patch, AMBARI-19559.v1.patch
>
>
> NN is being formatted during it's first startup. The script used for 
> formatting NN logs to standard output which currently is being collected only 
> in DEBUG mode by ambari agent thus is lost in production environments where 
> the agent usually runs in non-DEBUG mode. The NN formatting log is useful for 
> trouble shooting thus these should be collected and written out into the NN 
> start command output log.
> This can be done by adding logoutput=True option to the NN format script 
> invocation within NN start script.



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

[jira] [Commented] (AMBARI-19390) AMS Collector works in HTTP mode after setting ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19390:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6457 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6457/])
AMBARI-19390. AMS Collector works in HTTP mode after setting (swagle: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5bdd6cf7e24469da3d5bec987939b35fff263983])
* (edit) 
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py


> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY
> -
>
> Key: AMBARI-19390
> URL: https://issues.apache.org/jira/browse/AMBARI-19390
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-19390-1.patch, AMBARI-19390-2.patch, 
> AMBARI-19390.patch
>
>
> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY



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

[jira] [Commented] (AMBARI-19390) AMS Collector works in HTTP mode after setting ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19390:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #729 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/729/])
AMBARI-19390. AMS Collector works in HTTP mode after setting (swagle: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=08d011191d654ca43b4987f52476535af921398d])
* (edit) 
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py


> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY
> -
>
> Key: AMBARI-19390
> URL: https://issues.apache.org/jira/browse/AMBARI-19390
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-19390-1.patch, AMBARI-19390-2.patch, 
> AMBARI-19390.patch
>
>
> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY



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

[jira] [Commented] (AMBARI-19559) Log Namenode formatting output into ambari-agent command logs

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19559:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #729 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/729/])
Revert "Revert "AMBARI-19559. Log Namenode formatting output into (smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ef869d324e6fa6bfb7b87c671929bceee5e2d627])
* (edit) 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py
* (edit) 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/hdfs_namenode.py


> Log Namenode formatting output into ambari-agent command logs
> -
>
> Key: AMBARI-19559
> URL: https://issues.apache.org/jira/browse/AMBARI-19559
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
> Fix For: 2.5.0
>
> Attachments: AMBARI-19559.branch-2.5.v1.patch, AMBARI-19559.v1.patch
>
>
> NN is being formatted during it's first startup. The script used for 
> formatting NN logs to standard output which currently is being collected only 
> in DEBUG mode by ambari agent thus is lost in production environments where 
> the agent usually runs in non-DEBUG mode. The NN formatting log is useful for 
> trouble shooting thus these should be collected and written out into the NN 
> start command output log.
> This can be done by adding logoutput=True option to the NN format script 
> invocation within NN start script.



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

[jira] [Updated] (AMBARI-19576) Downgrade request fails as existing Upgrade request is considered 'in progress'

[Richard Zang (JIRA)]

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

Richard Zang updated AMBARI-19576:
--
Status: Patch Available  (was: Open)

> Downgrade request fails as existing Upgrade request is considered 'in 
> progress'
> ---
>
> Key: AMBARI-19576
> URL: https://issues.apache.org/jira/browse/AMBARI-19576
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19576.patch
>
>
> ambari-server --hash
> c1748443f8585c9457691c2a39e35da1d3e66c52
> Build #2.5.0.0-633
> *STR*
> # Started Express Upgrade to HDP-2.6.0.0 (via UI)
> # Hit downgrade at first manual prompt
> *Result*
> Downgrade failed with below error:
> {code}
> 14 Jan 2017 16:53:46,013 ERROR [ambari-client-thread-35] 
> AbstractResourceProvider:285 - Caught AmbariException when creating a resource
> org.apache.ambari.server.AmbariException: Unable to perform downgrade as 
> another downgrade (request ID 293) is in progress.
> at 
> org.apache.ambari.server.controller.internal.UpgradeResourceProvider$PreReqCheckValidator.check(UpgradeResourceProvider.java:2028)
> at 
> org.apache.ambari.server.controller.internal.UpgradeResourceProvider$UpgradeRequestValidator.validate(UpgradeResourceProvider.java:1952)
> at 
> org.apache.ambari.server.controller.internal.UpgradeResourceProvider$UpgradeRequestValidator.validate(UpgradeResourceProvider.java:1956)
> at 
> org.apache.ambari.server.controller.internal.UpgradeResourceProvider.validateRequest(UpgradeResourceProvider.java:660)
> at 
> org.apache.ambari.server.controller.internal.UpgradeResourceProvider.access$100(UpgradeResourceProvider.java:140)
> at 
> org.apache.ambari.server.controller.internal.UpgradeResourceProvider$1.invoke(UpgradeResourceProvider.java:399)
> at 
> org.apache.ambari.server.controller.internal.UpgradeResourceProvider$1.invoke(UpgradeResourceProvider.java:374)
> at 
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.invokeWithRetry(AbstractResourceProvider.java:455)
> at 
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.createResources(AbstractResourceProvider.java:278)
> at 
> org.apache.ambari.server.controller.internal.UpgradeResourceProvider.createResources(UpgradeResourceProvider.java:374)
> at 
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
> at 
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
> at 
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37)
> at 
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73)
> at 
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
> at 
> org.apache.ambari.server.api.services.UpgradeService.createUpgrade(UpgradeService.java:58)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> {code}



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

[jira] [Updated] (AMBARI-19576) Downgrade request fails as existing Upgrade request is considered 'in progress'

[Richard Zang (JIRA)]

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

Richard Zang updated AMBARI-19576:
--
Attachment: AMBARI-19576.patch

> Downgrade request fails as existing Upgrade request is considered 'in 
> progress'
> ---
>
> Key: AMBARI-19576
> URL: https://issues.apache.org/jira/browse/AMBARI-19576
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19576.patch
>
>
> ambari-server --hash
> c1748443f8585c9457691c2a39e35da1d3e66c52
> Build #2.5.0.0-633
> *STR*
> # Started Express Upgrade to HDP-2.6.0.0 (via UI)
> # Hit downgrade at first manual prompt
> *Result*
> Downgrade failed with below error:
> {code}
> 14 Jan 2017 16:53:46,013 ERROR [ambari-client-thread-35] 
> AbstractResourceProvider:285 - Caught AmbariException when creating a resource
> org.apache.ambari.server.AmbariException: Unable to perform downgrade as 
> another downgrade (request ID 293) is in progress.
> at 
> org.apache.ambari.server.controller.internal.UpgradeResourceProvider$PreReqCheckValidator.check(UpgradeResourceProvider.java:2028)
> at 
> org.apache.ambari.server.controller.internal.UpgradeResourceProvider$UpgradeRequestValidator.validate(UpgradeResourceProvider.java:1952)
> at 
> org.apache.ambari.server.controller.internal.UpgradeResourceProvider$UpgradeRequestValidator.validate(UpgradeResourceProvider.java:1956)
> at 
> org.apache.ambari.server.controller.internal.UpgradeResourceProvider.validateRequest(UpgradeResourceProvider.java:660)
> at 
> org.apache.ambari.server.controller.internal.UpgradeResourceProvider.access$100(UpgradeResourceProvider.java:140)
> at 
> org.apache.ambari.server.controller.internal.UpgradeResourceProvider$1.invoke(UpgradeResourceProvider.java:399)
> at 
> org.apache.ambari.server.controller.internal.UpgradeResourceProvider$1.invoke(UpgradeResourceProvider.java:374)
> at 
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.invokeWithRetry(AbstractResourceProvider.java:455)
> at 
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.createResources(AbstractResourceProvider.java:278)
> at 
> org.apache.ambari.server.controller.internal.UpgradeResourceProvider.createResources(UpgradeResourceProvider.java:374)
> at 
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
> at 
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
> at 
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37)
> at 
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73)
> at 
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
> at 
> org.apache.ambari.server.api.services.UpgradeService.createUpgrade(UpgradeService.java:58)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> {code}



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

[jira] [Created] (AMBARI-19576) Downgrade request fails as existing Upgrade request is considered 'in progress'

[Richard Zang (JIRA)]

Richard Zang created AMBARI-19576:
-

 Summary: Downgrade request fails as existing Upgrade request is 
considered 'in progress'
 Key: AMBARI-19576
 URL: https://issues.apache.org/jira/browse/AMBARI-19576
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.5.0
Reporter: Richard Zang
Assignee: Richard Zang
Priority: Blocker
 Fix For: 2.5.0


ambari-server --hash
c1748443f8585c9457691c2a39e35da1d3e66c52

Build #2.5.0.0-633

*STR*
# Started Express Upgrade to HDP-2.6.0.0 (via UI)
# Hit downgrade at first manual prompt

*Result*
Downgrade failed with below error:
{code}
14 Jan 2017 16:53:46,013 ERROR [ambari-client-thread-35] 
AbstractResourceProvider:285 - Caught AmbariException when creating a resource
org.apache.ambari.server.AmbariException: Unable to perform downgrade as 
another downgrade (request ID 293) is in progress.
at 
org.apache.ambari.server.controller.internal.UpgradeResourceProvider$PreReqCheckValidator.check(UpgradeResourceProvider.java:2028)
at 
org.apache.ambari.server.controller.internal.UpgradeResourceProvider$UpgradeRequestValidator.validate(UpgradeResourceProvider.java:1952)
at 
org.apache.ambari.server.controller.internal.UpgradeResourceProvider$UpgradeRequestValidator.validate(UpgradeResourceProvider.java:1956)
at 
org.apache.ambari.server.controller.internal.UpgradeResourceProvider.validateRequest(UpgradeResourceProvider.java:660)
at 
org.apache.ambari.server.controller.internal.UpgradeResourceProvider.access$100(UpgradeResourceProvider.java:140)
at 
org.apache.ambari.server.controller.internal.UpgradeResourceProvider$1.invoke(UpgradeResourceProvider.java:399)
at 
org.apache.ambari.server.controller.internal.UpgradeResourceProvider$1.invoke(UpgradeResourceProvider.java:374)
at 
org.apache.ambari.server.controller.internal.AbstractResourceProvider.invokeWithRetry(AbstractResourceProvider.java:455)
at 
org.apache.ambari.server.controller.internal.AbstractResourceProvider.createResources(AbstractResourceProvider.java:278)
at 
org.apache.ambari.server.controller.internal.UpgradeResourceProvider.createResources(UpgradeResourceProvider.java:374)
at 
org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
at 
org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
at 
org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37)
at 
org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73)
at 
org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
at 
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
at 
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
at 
org.apache.ambari.server.api.services.UpgradeService.createUpgrade(UpgradeService.java:58)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
{code}



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

[jira] [Created] (AMBARI-19575) AppTimeline server start failed after wirencryption

[Kishor Ramakrishnan (JIRA)]

Kishor Ramakrishnan created AMBARI-19575:


 Summary: AppTimeline server start failed after wirencryption
 Key: AMBARI-19575
 URL: https://issues.apache.org/jira/browse/AMBARI-19575
 Project: Ambari
  Issue Type: Bug
  Components: ambari-admin
Affects Versions: 2.5.0
Reporter: Kishor Ramakrishnan
Priority: Critical
 Fix For: 2.5.0


AppTimeline server start failed after wirencryption

Traceback (most recent call last):
  File 
"/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/application_timeline_server.py",
 line 155, in 
ApplicationTimelineServer().execute()
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 313, in execute
method(env)
  File 
"/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/application_timeline_server.py",
 line 44, in start
self.configure(env) # FOR SECURITY
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 116, in locking_configure
original_configure(obj, *args, **kw)
  File 
"/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/application_timeline_server.py",
 line 55, in configure
yarn(name='apptimelineserver')
  File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", 
line 89, in thunk
return fn(*args, **kwargs)
  File 
"/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/yarn.py",
 line 337, in yarn
mode=0755
  File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
line 155, in __init__
self.env.run()
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
line 160, in run
self.run_action(resource, action)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
line 124, in run_action
provider_action()
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
 line 555, in action_create_on_execute
self.action_delayed("create")
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
 line 552, in action_delayed
self.get_hdfs_resource_executor().action_delayed(action_name, self)
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
 line 288, in action_delayed
self._set_mode(self.target_status)
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
 line 459, in _set_mode
self.util.run_command(self.main_resource.resource.target, 'SETPERMISSION', 
method='PUT', permission=self.mode, assertable_result=False)
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
 line 199, in run_command
raise Fail(err_msg)
resource_management.core.exceptions.Fail: Execution of 'curl -sS -L -w 
'%{http_code}' -X PUT --negotiate -u : -k 
'https://{HOST}:50470/webhdfs/v1/ats/done?op=SETPERMISSION=cstm-hdfs=755''
 returned status_code=403. 
{
  "RemoteException": {
"exception": "SafeModeException", 
"javaClassName": 
"org.apache.hadoop.hdfs.server.namenode.SafeModeException", 
"message": "Cannot set permission for /ats/done. Name node is in safe 
mode.\nThe reported blocks 725 needs additional 2 blocks to reach the threshold 
1. of total blocks 726.\nThe number of live datanodes 2 has reached the 
minimum number 0. Safe mode will be turned off automatically once the 
thresholds have been reached."
  }
}



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

[jira] [Commented] (AMBARI-19547) HSI tez am memory set to 0, incorrect calculations for non llap queues

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19547:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6456 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6456/])
AMBARI-19547. HSI tez am memory set to 0, incorrect calculations for non 
(sshridhar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=07430c4c41f53bfa95806e662efd64a61f66ed62])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hive-interactive-env.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/tez-interactive-site.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/hive-interactive-site.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hive-interactive-site.xml


> HSI tez am memory set to 0, incorrect calculations for non llap queues
> --
>
> Key: AMBARI-19547
> URL: https://issues.apache.org/jira/browse/AMBARI-19547
> Project: Ambari
>  Issue Type: Bug
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: 2.5.0
>
> Attachments: AMBARI-19547.01.patch
>
>




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

[jira] [Commented] (AMBARI-19390) AMS Collector works in HTTP mode after setting ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19390:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6456 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6456/])
AMBARI-19390. AMS Collector works in HTTP mode after setting (swagle: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=61aa4c52ddf45e5c0a3f731d3676e462260ffc7a])
* (edit) 
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py


> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY
> -
>
> Key: AMBARI-19390
> URL: https://issues.apache.org/jira/browse/AMBARI-19390
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-19390-1.patch, AMBARI-19390-2.patch, 
> AMBARI-19390.patch
>
>
> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY



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

[jira] [Updated] (AMBARI-19097) HDP 3.0 TP - create Service Advisor for HDFS

[Alejandro Fernandez (JIRA)]

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

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

> HDP 3.0 TP - create Service Advisor for HDFS
> 
>
> Key: AMBARI-19097
> URL: https://issues.apache.org/jira/browse/AMBARI-19097
> Project: Ambari
>  Issue Type: Story
>  Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19097.patch
>
>
> Create a Service Advisor script for HDFS in HDP 3.0 Tech Preview.
> The Service Advisor must encapsulate all of the logic inherited/overwritten 
> from HDP 2.0.6 through HDP 2.6



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

[jira] [Updated] (AMBARI-19097) HDP 3.0 TP - create Service Advisor for HDFS

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-19097:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Pushed to trunk, commit 326cc1b2a1e05073050a38ea104d6d63ed76f373

> HDP 3.0 TP - create Service Advisor for HDFS
> 
>
> Key: AMBARI-19097
> URL: https://issues.apache.org/jira/browse/AMBARI-19097
> Project: Ambari
>  Issue Type: Story
>  Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19097.patch
>
>
> Create a Service Advisor script for HDFS in HDP 3.0 Tech Preview.
> The Service Advisor must encapsulate all of the logic inherited/overwritten 
> from HDP 2.0.6 through HDP 2.6



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

[jira] [Commented] (AMBARI-19390) AMS Collector works in HTTP mode after setting ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19390:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #728 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/728/])
AMBARI-19390. AMS Collector works in HTTP mode after setting (swagle: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0d5576f2d2f52be1b502b3c356849437eff4a121])
* (edit) 
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py


> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY
> -
>
> Key: AMBARI-19390
> URL: https://issues.apache.org/jira/browse/AMBARI-19390
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-19390-1.patch, AMBARI-19390-2.patch, 
> AMBARI-19390.patch
>
>
> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY



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

[jira] [Commented] (AMBARI-19547) HSI tez am memory set to 0, incorrect calculations for non llap queues

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19547:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #728 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/728/])
AMBARI-19547. HSI tez am memory set to 0, incorrect calculations for non 
(sshridhar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=31a1460779c8afb6c63db0e62c87f045b399c7f9])
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hive-interactive-env.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/hive-interactive-site.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/tez-interactive-site.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hive-interactive-site.xml


> HSI tez am memory set to 0, incorrect calculations for non llap queues
> --
>
> Key: AMBARI-19547
> URL: https://issues.apache.org/jira/browse/AMBARI-19547
> Project: Ambari
>  Issue Type: Bug
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: 2.5.0
>
> Attachments: AMBARI-19547.01.patch
>
>




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

[jira] [Updated] (AMBARI-19473) Add Downgrade request validation to avoid accidental double-upgrades

[Jonathan Hurley (JIRA)]

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

Jonathan Hurley updated AMBARI-19473:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Add Downgrade request validation to avoid accidental double-upgrades
> 
>
> Key: AMBARI-19473
> URL: https://issues.apache.org/jira/browse/AMBARI-19473
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19473.patch
>
>
> There are currently several ways of starting upgrades / downgrades:
> - The use of a directive on the request
> {noformat}
> http://localhost:8080/api/v1/clusters/c1/upgrades?downgrade=true
> {noformat}
> - The POST body JSON
> {noformat}
> {
> "RequestInfo": {
>   "downgrade": "true"
>   },
> "Upgrade":{
>   "from_version": ...
>  }
> }
> {noformat}
> The directive is confusing and can allow multiple downgrades or upgrades to 
> be scheduled concurrently. It should be removed for consistency and the 
> {{Upgrade/direction}} property should replace it.



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

[jira] [Updated] (AMBARI-19390) AMS Collector works in HTTP mode after setting ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY

[Siddharth Wagle (JIRA)]

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

Siddharth Wagle updated AMBARI-19390:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY
> -
>
> Key: AMBARI-19390
> URL: https://issues.apache.org/jira/browse/AMBARI-19390
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-19390-1.patch, AMBARI-19390-2.patch, 
> AMBARI-19390.patch
>
>
> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY



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

[jira] [Commented] (AMBARI-19390) AMS Collector works in HTTP mode after setting ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-19390:


Thanks [~swagle]. +1

> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY
> -
>
> Key: AMBARI-19390
> URL: https://issues.apache.org/jira/browse/AMBARI-19390
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-19390-1.patch, AMBARI-19390-2.patch, 
> AMBARI-19390.patch
>
>
> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY



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

[jira] [Resolved] (AMBARI-19559) Log Namenode formatting output into ambari-agent command logs

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty resolved AMBARI-19559.

Resolution: Fixed

Local environment issue. Sorry about that.

> Log Namenode formatting output into ambari-agent command logs
> -
>
> Key: AMBARI-19559
> URL: https://issues.apache.org/jira/browse/AMBARI-19559
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
> Fix For: 2.5.0
>
> Attachments: AMBARI-19559.branch-2.5.v1.patch, AMBARI-19559.v1.patch
>
>
> NN is being formatted during it's first startup. The script used for 
> formatting NN logs to standard output which currently is being collected only 
> in DEBUG mode by ambari agent thus is lost in production environments where 
> the agent usually runs in non-DEBUG mode. The NN formatting log is useful for 
> trouble shooting thus these should be collected and written out into the NN 
> start command output log.
> This can be done by adding logoutput=True option to the NN format script 
> invocation within NN start script.



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

[jira] [Commented] (AMBARI-19390) AMS Collector works in HTTP mode after setting ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY

[Siddharth Wagle (JIRA)]

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

Siddharth Wagle commented on AMBARI-19390:
--

Fixed:

--
Ran 269 tests in 6.655s

OK
--
Total run:1159
Total errors:0
Total failures:0
OK

> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY
> -
>
> Key: AMBARI-19390
> URL: https://issues.apache.org/jira/browse/AMBARI-19390
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-19390-1.patch, AMBARI-19390-2.patch, 
> AMBARI-19390.patch
>
>
> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY



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

[jira] [Updated] (AMBARI-19390) AMS Collector works in HTTP mode after setting ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY

[Siddharth Wagle (JIRA)]

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

Siddharth Wagle updated AMBARI-19390:
-
Attachment: AMBARI-19390-2.patch

> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY
> -
>
> Key: AMBARI-19390
> URL: https://issues.apache.org/jira/browse/AMBARI-19390
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-19390-1.patch, AMBARI-19390-2.patch, 
> AMBARI-19390.patch
>
>
> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY



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

[jira] [Updated] (AMBARI-19390) AMS Collector works in HTTP mode after setting ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY

[Siddharth Wagle (JIRA)]

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

Siddharth Wagle updated AMBARI-19390:
-
Status: Patch Available  (was: Reopened)

> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY
> -
>
> Key: AMBARI-19390
> URL: https://issues.apache.org/jira/browse/AMBARI-19390
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-19390-1.patch, AMBARI-19390-2.patch, 
> AMBARI-19390.patch
>
>
> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY



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

[jira] [Reopened] (AMBARI-19390) AMS Collector works in HTTP mode after setting ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY

[Siddharth Wagle (JIRA)]

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

Siddharth Wagle reopened AMBARI-19390:
--

Unit test failing.

> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY
> -
>
> Key: AMBARI-19390
> URL: https://issues.apache.org/jira/browse/AMBARI-19390
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-19390-1.patch, AMBARI-19390.patch
>
>
> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY



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

[jira] [Commented] (AMBARI-19573) Increase max limit for -Xmn parameter

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19573:


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

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

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

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

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

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

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

This message is automatically generated.

> Increase max limit for -Xmn parameter
> -
>
> Key: AMBARI-19573
> URL: https://issues.apache.org/jira/browse/AMBARI-19573
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Ted Yu
> Attachments: AMBARI-19573.v2.patch
>
>
> Currently, max value for -Xmn parameter is bounded by (hbase-rs-2.2.json):
> {code}
> "hbase_regionserver_xmn_max": "512",
> {code}
> During multiple troubleshooting sessions with customers, we (thanks to 
> [~vrodionov]) found that this limit is too low for large heap size.
> This JIRA is to increase the limit to 4000 MB.



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

[jira] [Updated] (AMBARI-19390) AMS Collector works in HTTP mode after setting ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY

[Siddharth Wagle (JIRA)]

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

Siddharth Wagle updated AMBARI-19390:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Manually verified and pushed to trunk and 2.5

> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY
> -
>
> Key: AMBARI-19390
> URL: https://issues.apache.org/jira/browse/AMBARI-19390
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-19390-1.patch, AMBARI-19390.patch
>
>
> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY



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

[jira] [Updated] (AMBARI-19519) Log Feeder should store keystore / truststore passwords in files

[Miklos Gergely (JIRA)]

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

Miklos Gergely updated AMBARI-19519:

Attachment: AMBARI-19519.patch

> Log Feeder should store keystore / truststore passwords in files
> 
>
> Key: AMBARI-19519
> URL: https://issues.apache.org/jira/browse/AMBARI-19519
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-19519.patch
>
>
> Log Feeder should not put the passwords of the keystore/truststore in the 
> command line, as it may be visible to others. Instead it should be in a file, 
> just like for Log Search Portal.



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

[jira] [Commented] (AMBARI-19390) AMS Collector works in HTTP mode after setting ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-19390:


LGTM, +1

> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY
> -
>
> Key: AMBARI-19390
> URL: https://issues.apache.org/jira/browse/AMBARI-19390
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-19390-1.patch, AMBARI-19390.patch
>
>
> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY



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

[jira] [Updated] (AMBARI-19390) AMS Collector works in HTTP mode after setting ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY

[Siddharth Wagle (JIRA)]

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

Siddharth Wagle updated AMBARI-19390:
-
Attachment: AMBARI-19390-1.patch

> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY
> -
>
> Key: AMBARI-19390
> URL: https://issues.apache.org/jira/browse/AMBARI-19390
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-19390-1.patch, AMBARI-19390.patch
>
>
> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY



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

[jira] [Updated] (AMBARI-19390) AMS Collector works in HTTP mode after setting ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY

[Siddharth Wagle (JIRA)]

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

Siddharth Wagle updated AMBARI-19390:
-
Status: Patch Available  (was: Reopened)

Addendum patch.

> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY
> -
>
> Key: AMBARI-19390
> URL: https://issues.apache.org/jira/browse/AMBARI-19390
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-19390-1.patch, AMBARI-19390.patch
>
>
> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY



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

[jira] [Reopened] (AMBARI-19390) AMS Collector works in HTTP mode after setting ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY

[Siddharth Wagle (JIRA)]

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

Siddharth Wagle reopened AMBARI-19390:
--

Collector start failed.
{code}
ambari-sudo.sh /usr/lib/jvm/java-openjdk/bin/keytool -importkeystore 
-srckeystore /etc/security/clientKeys/truststore.jks -destkeystore 
/tmp/tmpCVYxb0/truststore.p12 -srcalias  -deststoretype PKCS12 -srcstorepass 
clientTrustStorePassword -deststorepass clientTrustStorePassword' returned 1. 
Illegal option:  PKCS12
{code}

> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY
> -
>
> Key: AMBARI-19390
> URL: https://issues.apache.org/jira/browse/AMBARI-19390
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
>Assignee: Aravindan Vijayan
> Fix For: 2.5.0
>
> Attachments: AMBARI-19390.patch
>
>
> AMS Collector works in HTTP mode after setting 
> ams-site/timeline.metrics.service.http.policy=HTTPS_ONLY to HTTPS_ONLY



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

[jira] [Commented] (AMBARI-19559) Log Namenode formatting output into ambari-agent command logs

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19559:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6455 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6455/])
Revert "AMBARI-19559. Log Namenode formatting output into ambari-agent 
(smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=abeb45e5648b29714182c80c9f8b98bf38120e34])
* (edit) ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py
* (edit) 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py
* (edit) 
ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/hdfs_namenode.py
* (edit) 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/hdfs_namenode.py


> Log Namenode formatting output into ambari-agent command logs
> -
>
> Key: AMBARI-19559
> URL: https://issues.apache.org/jira/browse/AMBARI-19559
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
> Fix For: 2.5.0
>
> Attachments: AMBARI-19559.branch-2.5.v1.patch, AMBARI-19559.v1.patch
>
>
> NN is being formatted during it's first startup. The script used for 
> formatting NN logs to standard output which currently is being collected only 
> in DEBUG mode by ambari agent thus is lost in production environments where 
> the agent usually runs in non-DEBUG mode. The NN formatting log is useful for 
> trouble shooting thus these should be collected and written out into the NN 
> start command output log.
> This can be done by adding logoutput=True option to the NN format script 
> invocation within NN start script.



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

[jira] [Updated] (AMBARI-19547) HSI tez am memory set to 0, incorrect calculations for non llap queues

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-19547:
-
Summary: HSI tez am memory set to 0, incorrect calculations for non llap 
queues  (was: HSI tez am memory set to 0, incorrect calcaultions for non llap 
queues)

> HSI tez am memory set to 0, incorrect calculations for non llap queues
> --
>
> Key: AMBARI-19547
> URL: https://issues.apache.org/jira/browse/AMBARI-19547
> Project: Ambari
>  Issue Type: Bug
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: 2.5.0
>
> Attachments: AMBARI-19547.01.patch
>
>




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

[jira] [Commented] (AMBARI-19559) Log Namenode formatting output into ambari-agent command logs

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19559:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #727 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/727/])
Revert "AMBARI-19559. Log Namenode formatting output into ambari-agent 
(smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ea4051ab4205e0d68c45ffcbc0651fff7faa0d6c])
* (edit) 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py
* (edit) 
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/hdfs_namenode.py


> Log Namenode formatting output into ambari-agent command logs
> -
>
> Key: AMBARI-19559
> URL: https://issues.apache.org/jira/browse/AMBARI-19559
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
> Fix For: 2.5.0
>
> Attachments: AMBARI-19559.branch-2.5.v1.patch, AMBARI-19559.v1.patch
>
>
> NN is being formatted during it's first startup. The script used for 
> formatting NN logs to standard output which currently is being collected only 
> in DEBUG mode by ambari agent thus is lost in production environments where 
> the agent usually runs in non-DEBUG mode. The NN formatting log is useful for 
> trouble shooting thus these should be collected and written out into the NN 
> start command output log.
> This can be done by adding logoutput=True option to the NN format script 
> invocation within NN start script.



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

[jira] [Commented] (AMBARI-19547) HSI tez am memory set to 0, incorrect calcaultions for non llap queues

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar commented on AMBARI-19547:
--

Review comments updated in Reviewboard.

> HSI tez am memory set to 0, incorrect calcaultions for non llap queues
> --
>
> Key: AMBARI-19547
> URL: https://issues.apache.org/jira/browse/AMBARI-19547
> Project: Ambari
>  Issue Type: Bug
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: 2.5.0
>
> Attachments: AMBARI-19547.01.patch
>
>




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

[jira] [Commented] (AMBARI-19547) HSI tez am memory set to 0, incorrect calcaultions for non llap queues

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar commented on AMBARI-19547:
--

Added reviewboard link.

> HSI tez am memory set to 0, incorrect calcaultions for non llap queues
> --
>
> Key: AMBARI-19547
> URL: https://issues.apache.org/jira/browse/AMBARI-19547
> Project: Ambari
>  Issue Type: Bug
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: 2.5.0
>
> Attachments: AMBARI-19547.01.patch
>
>




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

[jira] [Commented] (AMBARI-19519) Log Feeder should store keystore / truststore passwords in files

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19519:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6454 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6454/])
AMBARI-19519 Log Feeder should store keystore / truststore passwords in 
(mgergely: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=17db42826eb7f4c03f554fc7b2f5633d0a480934])
* (edit) 
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/LogFeeder.java
* (edit) ambari-server/src/test/python/stacks/2.4/LOGSEARCH/test_logfeeder.py
* (add) 
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/util/SSLUtil.java
* (edit) 
ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/scripts/params.py
* (edit) ambari-server/src/test/python/stacks/2.4/configs/default.json
* (edit) 
ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/scripts/setup_logfeeder.py
* (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/scripts/run.sh
* (edit) 
ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/properties/logfeeder-env.sh.j2
* (edit) 
ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/scripts/setup_logsearch.py


> Log Feeder should store keystore / truststore passwords in files
> 
>
> Key: AMBARI-19519
> URL: https://issues.apache.org/jira/browse/AMBARI-19519
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
>
> Log Feeder should not put the passwords of the keystore/truststore in the 
> command line, as it may be visible to others. Instead it should be in a file, 
> just like for Log Search Portal.



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

[jira] [Updated] (AMBARI-19451) When defining yarn.scheduler.capacity..accessible-node-labels with space, Yarn Queue Manager shows error for the queue

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-19451:

   Resolution: Fixed
Fix Version/s: trunk
   Status: Resolved  (was: Patch Available)

Commited to branch 2.5 as

commit f90599ad3f43a835bbb8114d339ab8a6af4a7f1f
Author: Sangeeta Ravindran 
Date:   Mon Jan 16 13:10:41 2017 -0800

AMBARI-19451: When defining 
yarn.scheduler.capacity..accessible-node-labels with space, Yarn 
Queue Manager shows error for the queue (sangeetar)

Commited to trunk as

commit e0552d62e8229ee2cbbca216c491e3234b624d4d
Author: Sangeeta Ravindran 
Date:   Mon Jan 16 14:12:06 2017 -0800

AMBARI-19451: When defining 
yarn.scheduler.capacity..accessible-node-labels with space, Yarn 
Queue Manager shows error for the queue (sangeetar)


> When defining yarn.scheduler.capacity..accessible-node-labels 
> with space, Yarn Queue Manager shows error for the queue
> --
>
> Key: AMBARI-19451
> URL: https://issues.apache.org/jira/browse/AMBARI-19451
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19451.patch, Error.jpg, YarnConfig.jpg
>
>
> Per the Apache documentation for Yarn Node Labels 
> (http://hadoop.apache.org/docs/r2.7.3/hadoop-yarn/hadoop-yarn-site/NodeLabel.html),
>  queues that can only access nodes without labels are defined by setting the 
> property "yarn.scheduler.capacity..accessible-node-labels" with 
> space as the value.
> Reproduction Steps:
> 1. In the Capacity Scheduler view (Yarn Queue Manager), create queues q1,q2, 
> and set accessible node labels for root,q1,q2 but not for default queue
> 2. Since there is no way to specify a "space" as the value for accessible 
> node labels via Yarn Queue Manager, add this property manually via yarn 
> configs. i.e. In Yarn -> Configs -> Scheduler, manually add 
> yarn.scheduler.capacity.root.default.accessible-node-labels= (space after the 
> =)
> 3. Save the configuration and restart Resource Manager as required
> 4. Return to Yarn Queue Manager, and click the default queue. It shows an 
> error - Label is not exist on cluster.



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

[jira] [Updated] (AMBARI-19573) Increase max limit for -Xmn parameter

[Ted Yu (JIRA)]

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

Ted Yu updated AMBARI-19573:

Attachment: (was: AMBARI-19573.v1.patch)

> Increase max limit for -Xmn parameter
> -
>
> Key: AMBARI-19573
> URL: https://issues.apache.org/jira/browse/AMBARI-19573
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Ted Yu
> Attachments: AMBARI-19573.v2.patch
>
>
> Currently, max value for -Xmn parameter is bounded by (hbase-rs-2.2.json):
> {code}
> "hbase_regionserver_xmn_max": "512",
> {code}
> During multiple troubleshooting sessions with customers, we (thanks to 
> [~vrodionov]) found that this limit is too low for large heap size.
> This JIRA is to increase the limit to 4000 MB.



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

[jira] [Updated] (AMBARI-19573) Increase max limit for -Xmn parameter

[Ted Yu (JIRA)]

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

Ted Yu updated AMBARI-19573:

Attachment: AMBARI-19573.v2.patch

> Increase max limit for -Xmn parameter
> -
>
> Key: AMBARI-19573
> URL: https://issues.apache.org/jira/browse/AMBARI-19573
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Ted Yu
> Attachments: AMBARI-19573.v2.patch
>
>
> Currently, max value for -Xmn parameter is bounded by (hbase-rs-2.2.json):
> {code}
> "hbase_regionserver_xmn_max": "512",
> {code}
> During multiple troubleshooting sessions with customers, we (thanks to 
> [~vrodionov]) found that this limit is too low for large heap size.
> This JIRA is to increase the limit to 4000 MB.



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

[jira] [Reopened] (AMBARI-19559) Log Namenode formatting output into ambari-agent command logs

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty reopened AMBARI-19559:


Unit tests failing - 

{code}
Failed tests:
FAIL: test_start_default (test_namenode.TestNamenode)
--
Traceback (most recent call last):
  File 
"/Users/smohanty/enlistments/asf-ambari/ambari-common/src/test/python/mock/mock.py",
 line 1199, in patched
return func(*args, **keywargs)
  File 
"/Users/smohanty/enlistments/asf-ambari/ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py",
 line 185, in test_start_default
logoutput = True,
  File 
"/Users/smohanty/enlistments/asf-ambari/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
 line 281, in assertResourceCalled
self.assertEquals(kwargs, resource.arguments)
AssertionError: {'logoutput': True, 'path': ['/usr/bin'], 'user': 'hdfs'} != 
{'path': ['/usr/bin'], 'user': u'hdfs'}
- {'logoutput': True, 'path': ['/usr/bin'], 'user': 'hdfs'}
?  ---

+ {'path': ['/usr/bin'], 'user': u'hdfs'}
?+


FAIL: test_start_default_alt_fs (test_namenode.TestNamenode)
--
Traceback (most recent call last):
  File 
"/Users/smohanty/enlistments/asf-ambari/ambari-common/src/test/python/mock/mock.py",
 line 1199, in patched
return func(*args, **keywargs)
  File 
"/Users/smohanty/enlistments/asf-ambari/ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py",
 line 68, in test_start_default_alt_fs
logoutput = True,
  File 
"/Users/smohanty/enlistments/asf-ambari/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
 line 281, in assertResourceCalled
self.assertEquals(kwargs, resource.arguments)
AssertionError: {'logoutput': True, 'path': ['/usr/bin'], 'user': 'hdfs'} != 
{'path': ['/usr/bin'], 'user': u'hdfs'}
- {'logoutput': True, 'path': ['/usr/bin'], 'user': 'hdfs'}
?  ---

+ {'path': ['/usr/bin'], 'user': u'hdfs'}
?+


FAIL: test_start_ha_bootstrap_active_from_blueprint (test_namenode.TestNamenode)
--
Traceback (most recent call last):
  File 
"/Users/smohanty/enlistments/asf-ambari/ambari-common/src/test/python/mock/mock.py",
 line 1199, in patched
return func(*args, **keywargs)
  File 
"/Users/smohanty/enlistments/asf-ambari/ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py",
 line 742, in test_start_ha_bootstrap_active_from_blueprint
logoutput = True,
  File 
"/Users/smohanty/enlistments/asf-ambari/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
 line 281, in assertResourceCalled
self.assertEquals(kwargs, resource.arguments)
AssertionError: {'logoutput': True, 'path': ['/usr/bin'], 'user': 'hdfs'} != 
{'path': ['/usr/bin'], 'user': u'hdfs'}
- {'logoutput': True, 'path': ['/usr/bin'], 'user': 'hdfs'}
?  ---

+ {'path': ['/usr/bin'], 'user': u'hdfs'}
?+


FAIL: test_start_secured (test_namenode.TestNamenode)
--
Traceback (most recent call last):
  File 
"/Users/smohanty/enlistments/asf-ambari/ambari-common/src/test/python/mock/mock.py",
 line 1199, in patched
return func(*args, **keywargs)
  File 
"/Users/smohanty/enlistments/asf-ambari/ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py",
 line 315, in test_start_secured
logoutput = True,
  File 
"/Users/smohanty/enlistments/asf-ambari/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
 line 281, in assertResourceCalled
self.assertEquals(kwargs, resource.arguments)
AssertionError: {'logoutput': True, 'path': ['/usr/bin'], 'user': 'hdfs'} != 
{'path': ['/usr/bin'], 'user': u'hdfs'}
- {'logoutput': True, 'path': ['/usr/bin'], 'user': 'hdfs'}
?  ---

+ {'path': ['/usr/bin'], 'user': u'hdfs'}
?+


--
Total run:1151
Total errors:0
Total failures:4
{code}

> Log Namenode formatting output into ambari-agent command logs
> -
>
> Key: AMBARI-19559
> URL: https://issues.apache.org/jira/browse/AMBARI-19559
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
> Fix For: 2.5.0
>
> Attachments: AMBARI-19559.branch-2.5.v1.patch, AMBARI-19559.v1.patch
>
>
> NN is being formatted during it's first startup. The script used for 
> formatting NN logs to standard output which currently is being collected only 
> in DEBUG mode by ambari agent thus is lost in 

[jira] [Commented] (AMBARI-19411) Metrics Sink for Atlas

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19411:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12847687/AMBARI-19411.v3.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: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/10087//console

This message is automatically generated.

> Metrics Sink for Atlas
> --
>
> Key: AMBARI-19411
> URL: https://issues.apache.org/jira/browse/AMBARI-19411
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: 2.5.0
>Reporter: Apoorv Naik
> Fix For: 2.5.0
>
> Attachments: AMBARI-19411.v1.patch, AMBARI-19411.v2.patch, 
> AMBARI-19411.v3.patch
>
>
> Currently atlas has no way of publishing metrics/insights to AMS. This change 
> adds a Atlas sink that will periodically collect and emit metrics.



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

[jira] [Commented] (AMBARI-19519) Log Feeder should store keystore / truststore passwords in files

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19519:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #726 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/726/])
AMBARI-19519 Log Feeder should store keystore / truststore passwords in 
(mgergely: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d2802272d22b79945ea0a1330a5108f9d39241d9])
* (edit) 
ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/properties/logfeeder-env.sh.j2
* (edit) ambari-server/src/test/python/stacks/2.4/LOGSEARCH/test_logfeeder.py
* (edit) ambari-server/src/test/python/stacks/2.4/configs/default.json
* (edit) 
ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/scripts/setup_logsearch.py
* (edit) 
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/LogFeeder.java
* (edit) 
ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/scripts/params.py
* (add) 
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/util/SSLUtil.java
* (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/scripts/run.sh
* (edit) 
ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/scripts/setup_logfeeder.py


> Log Feeder should store keystore / truststore passwords in files
> 
>
> Key: AMBARI-19519
> URL: https://issues.apache.org/jira/browse/AMBARI-19519
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
>
> Log Feeder should not put the passwords of the keystore/truststore in the 
> command line, as it may be visible to others. Instead it should be in a file, 
> just like for Log Search Portal.



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

[jira] [Commented] (AMBARI-19451) When defining yarn.scheduler.capacity..accessible-node-labels with space, Yarn Queue Manager shows error for the queue

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19451:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6453 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6453/])
AMBARI-19451: When defining (sangeetar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e0552d62e8229ee2cbbca216c491e3234b624d4d])
* (edit) 
contrib/views/capacity-scheduler/src/main/resources/ui/app/serializers.js
* (edit) 
contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/components/queueContainer.hbs


> When defining yarn.scheduler.capacity..accessible-node-labels 
> with space, Yarn Queue Manager shows error for the queue
> --
>
> Key: AMBARI-19451
> URL: https://issues.apache.org/jira/browse/AMBARI-19451
> 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-19451.patch, Error.jpg, YarnConfig.jpg
>
>
> Per the Apache documentation for Yarn Node Labels 
> (http://hadoop.apache.org/docs/r2.7.3/hadoop-yarn/hadoop-yarn-site/NodeLabel.html),
>  queues that can only access nodes without labels are defined by setting the 
> property "yarn.scheduler.capacity..accessible-node-labels" with 
> space as the value.
> Reproduction Steps:
> 1. In the Capacity Scheduler view (Yarn Queue Manager), create queues q1,q2, 
> and set accessible node labels for root,q1,q2 but not for default queue
> 2. Since there is no way to specify a "space" as the value for accessible 
> node labels via Yarn Queue Manager, add this property manually via yarn 
> configs. i.e. In Yarn -> Configs -> Scheduler, manually add 
> yarn.scheduler.capacity.root.default.accessible-node-labels= (space after the 
> =)
> 3. Save the configuration and restart Resource Manager as required
> 4. Return to Yarn Queue Manager, and click the default queue. It shows an 
> error - Label is not exist on cluster.



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

[jira] [Updated] (AMBARI-19097) HDP 3.0 TP - create Service Advisor for HDFS

[Alejandro Fernandez (JIRA)]

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

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

> HDP 3.0 TP - create Service Advisor for HDFS
> 
>
> Key: AMBARI-19097
> URL: https://issues.apache.org/jira/browse/AMBARI-19097
> Project: Ambari
>  Issue Type: Story
>  Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19097.patch
>
>
> Create a Service Advisor script for HDFS in HDP 3.0 Tech Preview.
> The Service Advisor must encapsulate all of the logic inherited/overwritten 
> from HDP 2.0.6 through HDP 2.6



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

[jira] [Updated] (AMBARI-19097) HDP 3.0 TP - create Service Advisor for HDFS

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-19097:
-
Attachment: AMBARI-19097.patch

> HDP 3.0 TP - create Service Advisor for HDFS
> 
>
> Key: AMBARI-19097
> URL: https://issues.apache.org/jira/browse/AMBARI-19097
> Project: Ambari
>  Issue Type: Story
>  Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19097.patch
>
>
> Create a Service Advisor script for HDFS in HDP 3.0 Tech Preview.
> The Service Advisor must encapsulate all of the logic inherited/overwritten 
> from HDP 2.0.6 through HDP 2.6



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

[jira] [Updated] (AMBARI-19097) HDP 3.0 TP - create Service Advisor for HDFS

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-19097:
-
Attachment: (was: AMBARI-19097.patch)

> HDP 3.0 TP - create Service Advisor for HDFS
> 
>
> Key: AMBARI-19097
> URL: https://issues.apache.org/jira/browse/AMBARI-19097
> Project: Ambari
>  Issue Type: Story
>  Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19097.patch
>
>
> Create a Service Advisor script for HDFS in HDP 3.0 Tech Preview.
> The Service Advisor must encapsulate all of the logic inherited/overwritten 
> from HDP 2.0.6 through HDP 2.6



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

[jira] [Commented] (AMBARI-19573) Increase max limit for -Xmn parameter

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19573:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12847689/AMBARI-19573.v1.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/10086//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/10086//console

This message is automatically generated.

> Increase max limit for -Xmn parameter
> -
>
> Key: AMBARI-19573
> URL: https://issues.apache.org/jira/browse/AMBARI-19573
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Ted Yu
> Attachments: AMBARI-19573.v1.patch
>
>
> Currently, max value for -Xmn parameter is bounded by (hbase-rs-2.2.json):
> {code}
> "hbase_regionserver_xmn_max": "512",
> {code}
> During multiple troubleshooting sessions with customers, we (thanks to 
> [~vrodionov]) found that this limit is too low for large heap size.
> This JIRA is to increase the limit to 4000 MB.



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

[jira] [Commented] (AMBARI-19519) Log Feeder should store keystore / truststore passwords in files

[Miklos Gergely (JIRA)]

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

Miklos Gergely commented on AMBARI-19519:
-

committed to trunk:
{code:java}
commit 17db42826eb7f4c03f554fc7b2f5633d0a480934
Author: Miklos Gergely 
Date:   Mon Jan 16 23:57:10 2017 +0100

AMBARI-19519 Log Feeder should store keystore / truststore passwords in 
files (mgergely)

Change-Id: I1d5b39b035391c01d1911715cffcd20b7561b65d
{code}

committed to branch-2.5:
{code:java}
commit d2802272d22b79945ea0a1330a5108f9d39241d9
Author: Miklos Gergely 
Date:   Mon Jan 16 23:58:25 2017 +0100

AMBARI-19519 Log Feeder should store keystore / truststore passwords in 
files (mgergely)

Change-Id: I51641dd39f833057e51dbd19ed0160b8bc9fb029
{code}

> Log Feeder should store keystore / truststore passwords in files
> 
>
> Key: AMBARI-19519
> URL: https://issues.apache.org/jira/browse/AMBARI-19519
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
>
> Log Feeder should not put the passwords of the keystore/truststore in the 
> command line, as it may be visible to others. Instead it should be in a file, 
> just like for Log Search Portal.



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

[jira] [Resolved] (AMBARI-19519) Log Feeder should store keystore / truststore passwords in files

[Miklos Gergely (JIRA)]

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

Miklos Gergely resolved AMBARI-19519.
-
Resolution: Fixed

> Log Feeder should store keystore / truststore passwords in files
> 
>
> Key: AMBARI-19519
> URL: https://issues.apache.org/jira/browse/AMBARI-19519
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
>
> Log Feeder should not put the passwords of the keystore/truststore in the 
> command line, as it may be visible to others. Instead it should be in a file, 
> just like for Log Search Portal.



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

[jira] [Assigned] (AMBARI-19573) Increase max limit for -Xmn parameter

[Ted Yu (JIRA)]

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

Ted Yu reassigned AMBARI-19573:
---

Assignee: Ted Yu

> Increase max limit for -Xmn parameter
> -
>
> Key: AMBARI-19573
> URL: https://issues.apache.org/jira/browse/AMBARI-19573
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Ted Yu
> Attachments: AMBARI-19573.v1.patch
>
>
> Currently, max value for -Xmn parameter is bounded by (hbase-rs-2.2.json):
> {code}
> "hbase_regionserver_xmn_max": "512",
> {code}
> During multiple troubleshooting sessions with customers, we (thanks to 
> [~vrodionov]) found that this limit is too low for large heap size.
> This JIRA is to increase the limit to 4000 MB.



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

[jira] [Updated] (AMBARI-19573) Increase max limit for -Xmn parameter

[Ted Yu (JIRA)]

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

Ted Yu updated AMBARI-19573:

Status: Patch Available  (was: Open)

> Increase max limit for -Xmn parameter
> -
>
> Key: AMBARI-19573
> URL: https://issues.apache.org/jira/browse/AMBARI-19573
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Ted Yu
> Attachments: AMBARI-19573.v1.patch
>
>
> Currently, max value for -Xmn parameter is bounded by (hbase-rs-2.2.json):
> {code}
> "hbase_regionserver_xmn_max": "512",
> {code}
> During multiple troubleshooting sessions with customers, we (thanks to 
> [~vrodionov]) found that this limit is too low for large heap size.
> This JIRA is to increase the limit to 4000 MB.



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

[jira] [Created] (AMBARI-19574) Add upgrade logic for the heap dump control option added in HDP 2.6 stack.

[Jonathan Hurley (JIRA)]

Jonathan Hurley created AMBARI-19574:


 Summary: Add upgrade logic for the heap dump control option added 
in HDP 2.6 stack.
 Key: AMBARI-19574
 URL: https://issues.apache.org/jira/browse/AMBARI-19574
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.5.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Critical
 Fix For: 2.5.0


Looking at https://reviews.apache.org/r/54527, some properties were added for 
Hive and Hive2 which need to be included in the upgrade from HDP 2.5 to HDP 2.6.

- It looks like the following properties were added to HDP 2.6 only. They will 
automatically be merged in on stack upgrades from HDP 2.5, so there's no work 
to be done there. The following will be automatically merged in since they are 
completely new:
-- {{hive-env/enable_heap_dump}}
-- {{hive-env/heap_dump_location}}
-- {{tez-env/enable_heap_dump}}
-- {{tez-env/heap_dump_location}}

- Since Ambari 2.4 doesn't support HDP 2.6, that means we don't need to worry 
about HDP 2.6 to HDP 2.6 at all (where we would need to add the above 
properties manually).

- Now the interesting part. The following properties are _NOT_ new. They 
existed in prior stacks, which means that they will be automatically merged 
only if they have not changed their default values on the prior stack:
-- {{tez-site/tez.task.launch.cmd-opts}}
-- {{hive-env/content}}
-- {{hive-interactive-env/llap_java_opts}}
-- {{hive-interactive-env/content}}

So, what do we do with them?

- {{tez-site/tez.task.launch.cmd-opts}} and 
{{hive-interactive-env/llap_java_opts}} don't seem too bad since it looks like 
the main difference is a token. We can do a find/replace for this:
-- {code:title=tez-site}
Replace: -XX:+UseParallelGC 
with
XX:+UseParallelGC{{heap_dump_opts}}
{code}
-- {code:title=hive-interactive-env/llap_java_opts}
Replace -XX:+UseParallelGC{% endif %}
with
XX:+UseParallelGC{% endif %}{{heap_dump_opts}}
{code}

However the {{content}} properties are much harder to work with, as customers 
change them all the time. This is where we need something more flexible than 
replace - something like an insert.



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

[jira] [Updated] (AMBARI-19535) When viewing details of a group, the group type is sometimes empty

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-19535:

   Resolution: Fixed
Fix Version/s: trunk
   Status: Resolved  (was: Patch Available)

Committed to trunk as 
commit 54db4072e87e4efc09d68d9b4c53b6f562983d9f
Author: Sangeeta Ravindran 
Date:   Mon Jan 16 12:58:14 2017 -0800

AMBARI-19535: When viewing details of a group, the group type is sometimes 
empty (sangeetar)

Committed to branch-2.5 as 
commit 38e0b578b59aa662c6a41f67948aa25bc9679934
Author: Sangeeta Ravindran 
Date:   Mon Jan 16 10:20:10 2017 -0800

AMBARI-19535: When viewing details of a group, the group type is sometimes 
empty (sangeetar)

> When viewing details of a group, the group type is sometimes empty
> --
>
> Key: AMBARI-19535
> URL: https://issues.apache.org/jira/browse/AMBARI-19535
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19535.patch, GrouptTypeEmpty.jpg
>
>
> When you click on a Group and view its details, sometimes the Type shows an 
> empty value. 
> The following error can be seen on the web console.
> vendor.js:22245 TypeError: Cannot read property 'LABEL_KEY' of undefined at 
> main.js:2278 at wrappedCallback (vendor.js:23746) at vendor.js:23832 at 
> Scope.$eval (vendor.js:24875) at Scope.$digest (vendor.js:24687) at 
> Scope.$apply (vendor.js:24979) at done (vendor.js:20552) at completeRequest 
> (vendor.js:20766) at XMLHttpRequest.xhr.onreadystatechange (vendor.js:20705)



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

[jira] [Updated] (AMBARI-19573) Increase max limit for -Xmn parameter

[Ted Yu (JIRA)]

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

Ted Yu updated AMBARI-19573:

Attachment: AMBARI-19573.v1.patch

> Increase max limit for -Xmn parameter
> -
>
> Key: AMBARI-19573
> URL: https://issues.apache.org/jira/browse/AMBARI-19573
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Ted Yu
> Attachments: AMBARI-19573.v1.patch
>
>
> Currently, max value for -Xmn parameter is bounded by (hbase-rs-2.2.json):
> {code}
> "hbase_regionserver_xmn_max": "512",
> {code}
> During multiple troubleshooting sessions with customers, we (thanks to 
> [~vrodionov]) found that this limit is too low for large heap size.
> This JIRA is to increase the limit to 4000 MB.



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

[jira] [Created] (AMBARI-19573) Increase max limit for -Xmn parameter

[Ted Yu (JIRA)]

Ted Yu created AMBARI-19573:
---

 Summary: Increase max limit for -Xmn parameter
 Key: AMBARI-19573
 URL: https://issues.apache.org/jira/browse/AMBARI-19573
 Project: Ambari
  Issue Type: Improvement
Reporter: Ted Yu


Currently, max value for -Xmn parameter is bounded by (hbase-rs-2.2.json):
{code}
"hbase_regionserver_xmn_max": "512",
{code}
During multiple troubleshooting sessions with customers, we (thanks to 
[~vrodionov]) found that this limit is too low for large heap size.

This JIRA is to increase the limit to 4000 MB.



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

[jira] [Updated] (AMBARI-19411) Metrics Sink for Atlas

[Apoorv Naik (JIRA)]

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

Apoorv Naik updated AMBARI-19411:
-
Attachment: (was: AMBARI-19411.v3.patch)

> Metrics Sink for Atlas
> --
>
> Key: AMBARI-19411
> URL: https://issues.apache.org/jira/browse/AMBARI-19411
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: 2.5.0
>Reporter: Apoorv Naik
> Fix For: 2.5.0
>
> Attachments: AMBARI-19411.v1.patch, AMBARI-19411.v2.patch, 
> AMBARI-19411.v3.patch
>
>
> Currently atlas has no way of publishing metrics/insights to AMS. This change 
> adds a Atlas sink that will periodically collect and emit metrics.



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

[jira] [Updated] (AMBARI-19411) Metrics Sink for Atlas

[Apoorv Naik (JIRA)]

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

Apoorv Naik updated AMBARI-19411:
-
Attachment: AMBARI-19411.v3.patch

> Metrics Sink for Atlas
> --
>
> Key: AMBARI-19411
> URL: https://issues.apache.org/jira/browse/AMBARI-19411
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: 2.5.0
>Reporter: Apoorv Naik
> Fix For: 2.5.0
>
> Attachments: AMBARI-19411.v1.patch, AMBARI-19411.v2.patch, 
> AMBARI-19411.v3.patch
>
>
> Currently atlas has no way of publishing metrics/insights to AMS. This change 
> adds a Atlas sink that will periodically collect and emit metrics.



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

[jira] [Updated] (AMBARI-19411) Metrics Sink for Atlas

[Apoorv Naik (JIRA)]

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

Apoorv Naik updated AMBARI-19411:
-
Attachment: AMBARI-19411.v3.patch

> Metrics Sink for Atlas
> --
>
> Key: AMBARI-19411
> URL: https://issues.apache.org/jira/browse/AMBARI-19411
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: 2.5.0
>Reporter: Apoorv Naik
> Fix For: 2.5.0
>
> Attachments: AMBARI-19411.v1.patch, AMBARI-19411.v2.patch, 
> AMBARI-19411.v3.patch
>
>
> Currently atlas has no way of publishing metrics/insights to AMS. This change 
> adds a Atlas sink that will periodically collect and emit metrics.



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

[jira] [Updated] (AMBARI-19411) Metrics Sink for Atlas

[Apoorv Naik (JIRA)]

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

Apoorv Naik updated AMBARI-19411:
-
Attachment: (was: AMBARI-19411.v3.patch)

> Metrics Sink for Atlas
> --
>
> Key: AMBARI-19411
> URL: https://issues.apache.org/jira/browse/AMBARI-19411
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: 2.5.0
>Reporter: Apoorv Naik
> Fix For: 2.5.0
>
> Attachments: AMBARI-19411.v1.patch, AMBARI-19411.v2.patch, 
> AMBARI-19411.v3.patch
>
>
> Currently atlas has no way of publishing metrics/insights to AMS. This change 
> adds a Atlas sink that will periodically collect and emit metrics.



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

[jira] [Commented] (AMBARI-19451) When defining yarn.scheduler.capacity..accessible-node-labels with space, Yarn Queue Manager shows error for the queue

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19451:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #725 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/725/])
AMBARI-19451: When defining (sangeetar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f90599ad3f43a835bbb8114d339ab8a6af4a7f1f])
* (edit) 
contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/components/queueContainer.hbs
* (edit) 
contrib/views/capacity-scheduler/src/main/resources/ui/app/serializers.js


> When defining yarn.scheduler.capacity..accessible-node-labels 
> with space, Yarn Queue Manager shows error for the queue
> --
>
> Key: AMBARI-19451
> URL: https://issues.apache.org/jira/browse/AMBARI-19451
> 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-19451.patch, Error.jpg, YarnConfig.jpg
>
>
> Per the Apache documentation for Yarn Node Labels 
> (http://hadoop.apache.org/docs/r2.7.3/hadoop-yarn/hadoop-yarn-site/NodeLabel.html),
>  queues that can only access nodes without labels are defined by setting the 
> property "yarn.scheduler.capacity..accessible-node-labels" with 
> space as the value.
> Reproduction Steps:
> 1. In the Capacity Scheduler view (Yarn Queue Manager), create queues q1,q2, 
> and set accessible node labels for root,q1,q2 but not for default queue
> 2. Since there is no way to specify a "space" as the value for accessible 
> node labels via Yarn Queue Manager, add this property manually via yarn 
> configs. i.e. In Yarn -> Configs -> Scheduler, manually add 
> yarn.scheduler.capacity.root.default.accessible-node-labels= (space after the 
> =)
> 3. Save the configuration and restart Resource Manager as required
> 4. Return to Yarn Queue Manager, and click the default queue. It shows an 
> error - Label is not exist on cluster.



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

[jira] [Updated] (AMBARI-19411) Metrics Sink for Atlas

[Apoorv Naik (JIRA)]

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

Apoorv Naik updated AMBARI-19411:
-
Attachment: (was: AMBARI-19411.v3.patch)

> Metrics Sink for Atlas
> --
>
> Key: AMBARI-19411
> URL: https://issues.apache.org/jira/browse/AMBARI-19411
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: 2.5.0
>Reporter: Apoorv Naik
> Fix For: 2.5.0
>
> Attachments: AMBARI-19411.v1.patch, AMBARI-19411.v2.patch, 
> AMBARI-19411.v3.patch
>
>
> Currently atlas has no way of publishing metrics/insights to AMS. This change 
> adds a Atlas sink that will periodically collect and emit metrics.



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

[jira] [Updated] (AMBARI-19411) Metrics Sink for Atlas

[Apoorv Naik (JIRA)]

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

Apoorv Naik updated AMBARI-19411:
-
Attachment: AMBARI-19411.v3.patch

> Metrics Sink for Atlas
> --
>
> Key: AMBARI-19411
> URL: https://issues.apache.org/jira/browse/AMBARI-19411
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: 2.5.0
>Reporter: Apoorv Naik
> Fix For: 2.5.0
>
> Attachments: AMBARI-19411.v1.patch, AMBARI-19411.v2.patch, 
> AMBARI-19411.v3.patch
>
>
> Currently atlas has no way of publishing metrics/insights to AMS. This change 
> adds a Atlas sink that will periodically collect and emit metrics.



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

[jira] [Updated] (AMBARI-19411) Metrics Sink for Atlas

[Apoorv Naik (JIRA)]

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

Apoorv Naik updated AMBARI-19411:
-
Attachment: (was: 0001-AMBARI-19411-Atlas-AMS-support.patch)

> Metrics Sink for Atlas
> --
>
> Key: AMBARI-19411
> URL: https://issues.apache.org/jira/browse/AMBARI-19411
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: 2.5.0
>Reporter: Apoorv Naik
> Fix For: 2.5.0
>
> Attachments: AMBARI-19411.v1.patch, AMBARI-19411.v2.patch, 
> AMBARI-19411.v3.patch
>
>
> Currently atlas has no way of publishing metrics/insights to AMS. This change 
> adds a Atlas sink that will periodically collect and emit metrics.



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

[jira] [Updated] (AMBARI-19411) Metrics Sink for Atlas

[Apoorv Naik (JIRA)]

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

Apoorv Naik updated AMBARI-19411:
-
Attachment: AMBARI-19411.v3.patch

> Metrics Sink for Atlas
> --
>
> Key: AMBARI-19411
> URL: https://issues.apache.org/jira/browse/AMBARI-19411
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: 2.5.0
>Reporter: Apoorv Naik
> Fix For: 2.5.0
>
> Attachments: AMBARI-19411.v1.patch, AMBARI-19411.v2.patch, 
> AMBARI-19411.v3.patch
>
>
> Currently atlas has no way of publishing metrics/insights to AMS. This change 
> adds a Atlas sink that will periodically collect and emit metrics.



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

[jira] [Commented] (AMBARI-19535) When viewing details of a group, the group type is sometimes empty

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19535:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6452 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6452/])
AMBARI-19535: When viewing details of a group, the group type is (sangeetar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=54db4072e87e4efc09d68d9b4c53b6f562983d9f])
* (edit) 
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/groups/GroupsEditCtrl.js


> When viewing details of a group, the group type is sometimes empty
> --
>
> Key: AMBARI-19535
> URL: https://issues.apache.org/jira/browse/AMBARI-19535
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Fix For: 2.5.0
>
> Attachments: AMBARI-19535.patch, GrouptTypeEmpty.jpg
>
>
> When you click on a Group and view its details, sometimes the Type shows an 
> empty value. 
> The following error can be seen on the web console.
> vendor.js:22245 TypeError: Cannot read property 'LABEL_KEY' of undefined at 
> main.js:2278 at wrappedCallback (vendor.js:23746) at vendor.js:23832 at 
> Scope.$eval (vendor.js:24875) at Scope.$digest (vendor.js:24687) at 
> Scope.$apply (vendor.js:24979) at done (vendor.js:20552) at completeRequest 
> (vendor.js:20766) at XMLHttpRequest.xhr.onreadystatechange (vendor.js:20705)



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

[jira] [Commented] (AMBARI-19537) Provide default value for yarn leveldb state store path

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19537:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6451 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6451/])
AMBARI-19537: Provide default value for yarn leveldb state store path (dili: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7301a803190261608769e232d2da7505f20aa9ae])
* (edit) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/scripts/params_linux.py
* (edit) 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py


> Provide default value for yarn leveldb state store path
> ---
>
> Key: AMBARI-19537
> URL: https://issues.apache.org/jira/browse/AMBARI-19537
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-19537.patch
>
>




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

[jira] [Commented] (AMBARI-19446) Able to skip writing configuration files when the config type doesn't exist in the command JSON file

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19446:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6451 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6451/])
AMBARI-19446: Able to skip writing configuration files when the config (dili: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e78b92b8da7e573848b26cae951195a46fed2cff])
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py
* (edit) 
ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/knox.py
* (edit) 
ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/params_linux.py
* (add) 
ambari-common/src/main/python/resource_management/libraries/functions/get_config.py
* (edit) 
ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/sqoop.py
* (edit) 
ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/params_windows.py


> Able to skip writing configuration files when the config type doesn't exist 
> in the command JSON file
> 
>
> Key: AMBARI-19446
> URL: https://issues.apache.org/jira/browse/AMBARI-19446
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-19446.patch
>
>
> Able to skip writing configuration files when the config type doesn't exist 
> in the command JSON file.



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

[jira] [Updated] (AMBARI-18814) Add common log rotation settings to HDFS configs

[Madhuvanthi Radhakrishnan (JIRA)]

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

Madhuvanthi Radhakrishnan updated AMBARI-18814:
---
Attachment: AMBARI-18814_addendum.patch

> Add common log rotation settings to HDFS configs
> 
>
> Key: AMBARI-18814
> URL: https://issues.apache.org/jira/browse/AMBARI-18814
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Attachments: AMBARI-18814_addendum.patch, AMBARI-18814.patch
>
>
> Add common log rotation settings to HDFS configs



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

[jira] [Updated] (AMBARI-19274) Add common log rotation settings to hbase, zookeeper, ams

[Madhuvanthi Radhakrishnan (JIRA)]

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

Madhuvanthi Radhakrishnan updated AMBARI-19274:
---
Attachment: AMBARI-18814_addendum.patch

> Add common log rotation settings to hbase, zookeeper, ams
> -
>
> Key: AMBARI-19274
> URL: https://issues.apache.org/jira/browse/AMBARI-19274
> Project: Ambari
>  Issue Type: Task
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Attachments: AMBARI-18814_addendum.patch, AMBARI-19274-2.patch, 
> AMBARI-19274.patch
>
>
> Add common log rotation settings to hbase, zookeeper, ams



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

[jira] [Commented] (AMBARI-19568) Setup the correct authentication and authorization between ZooKeeper and oozie

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19568:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12847634/AMBARI-19568_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:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

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

This message is automatically generated.

> Setup the correct authentication and authorization between ZooKeeper and oozie
> --
>
> Key: AMBARI-19568
> URL: https://issues.apache.org/jira/browse/AMBARI-19568
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-agent, ambari-server
>Affects Versions: 2.5.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19568_branch-2.5.patch, AMBARI-19568_trunk.patch
>
>
> The communication between ZooKeeper and Oozie must be secure when kerberos is 
> enabled. This can be achieved by setting oozie.zookeeper.secure property to 
> true in oozie-site.xml. This makes oozie to install secure permissions to its 
> znodes. These permissions should be removed when we disable kerberos.



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

[jira] [Commented] (AMBARI-19540) Possibly too frequent calls to stack advisor as user changes sliders

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19540:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6450 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6450/])
AMBARI-19540. Possibly too frequent calls to stack advisor as user (hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4393724735343f331c881dc5187ddb66d701b277])
* (edit) ambari-web/app/templates/common/configs/widgets/controls.hbs


> Possibly too frequent calls to stack advisor as user changes sliders
> 
>
> Key: AMBARI-19540
> URL: https://issues.apache.org/jira/browse/AMBARI-19540
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Antonenko Alexander
> Fix For: 2.5.0
>
> Attachments: AMBARI-19540.patch, AMBARI-19540.v0.patch, 
> AMBARI-19540.v1.branch-2.5.patch
>
>
> As you can see 3 calls are made while changing from 1024 to 2048 and 
> similarly 3 calls when coming back to 1024. 
> Beyond performance concern, multiple calls have a functional issue. The call 
> includes previous value of the changed property - see the values. I would 
> have expected the old value to be the value that was the original/saved 
> value. However, it is wherever UI makes the stack advisor calls.
> [root@smq1-1 stack-recommendations]# find . -name services.json | xargs grep 
> -A 3 changed
> ./55/services.json:  "changed-configurations" : [ {
> ./55/services.json-"type" : "yarn-site",
> ./55/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./55/services.json-"old_value" : "1024"
> ./56/services.json:  "changed-configurations" : [ {
> ./56/services.json-"type" : "yarn-site",
> ./56/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./56/services.json-"old_value" : "1280"
> ./57/services.json:  "changed-configurations" : [ {
> ./57/services.json-"type" : "yarn-site",
> ./57/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./57/services.json-"old_value" : "1792"
> ./58/services.json:  "changed-configurations" : [ {
> ./58/services.json-"type" : "yarn-site",
> ./58/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./58/services.json-"old_value" : "2048"
> ./59/services.json:  "changed-configurations" : [ {
> ./59/services.json-"type" : "yarn-site",
> ./59/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./59/services.json-"old_value" : "1792"
> ./60/services.json:  "changed-configurations" : [ {
> ./60/services.json-"type" : "yarn-site",
> ./60/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./60/services.json-"old_value" : "1280"



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

[jira] [Commented] (AMBARI-19476) Incorrect error message when trying to add a group to multiple roles

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran commented on AMBARI-19476:
-

Thanks Alexander.
Trunk test case failure is unrelated to patch.

Test Result (1 failure / +1)
org.apache.ambari.server.state.cluster.ClusterDeadlockTest.testDeadlockWhileRestartingComponents


> Incorrect error message when trying to add a group to multiple roles
> 
>
> Key: AMBARI-19476
> URL: https://issues.apache.org/jira/browse/AMBARI-19476
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: 2.5.0
>
> Attachments: AMBARI-19476.patch, 
> ErrorMessageAddingGroupToMultipleRoles.jpg
>
>
> 1. Create a group and assign roles to the group.
> 2. If you add the same group to multiple roles, the error message says "Only 
> 1 role allowed per user".



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

[jira] [Commented] (AMBARI-19540) Possibly too frequent calls to stack advisor as user changes sliders

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19540:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #724 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/724/])
AMBARI-19540. Possibly too frequent calls to stack advisor as user (hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e60ac672007d11daacfb02d119c5d35249b5bf5f])
* (edit) ambari-web/app/views/common/controls_view.js
* (edit) ambari-web/app/templates/common/configs/widgets/controls.hbs


> Possibly too frequent calls to stack advisor as user changes sliders
> 
>
> Key: AMBARI-19540
> URL: https://issues.apache.org/jira/browse/AMBARI-19540
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Antonenko Alexander
> Fix For: 2.5.0
>
> Attachments: AMBARI-19540.patch, AMBARI-19540.v0.patch, 
> AMBARI-19540.v1.branch-2.5.patch
>
>
> As you can see 3 calls are made while changing from 1024 to 2048 and 
> similarly 3 calls when coming back to 1024. 
> Beyond performance concern, multiple calls have a functional issue. The call 
> includes previous value of the changed property - see the values. I would 
> have expected the old value to be the value that was the original/saved 
> value. However, it is wherever UI makes the stack advisor calls.
> [root@smq1-1 stack-recommendations]# find . -name services.json | xargs grep 
> -A 3 changed
> ./55/services.json:  "changed-configurations" : [ {
> ./55/services.json-"type" : "yarn-site",
> ./55/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./55/services.json-"old_value" : "1024"
> ./56/services.json:  "changed-configurations" : [ {
> ./56/services.json-"type" : "yarn-site",
> ./56/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./56/services.json-"old_value" : "1280"
> ./57/services.json:  "changed-configurations" : [ {
> ./57/services.json-"type" : "yarn-site",
> ./57/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./57/services.json-"old_value" : "1792"
> ./58/services.json:  "changed-configurations" : [ {
> ./58/services.json-"type" : "yarn-site",
> ./58/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./58/services.json-"old_value" : "2048"
> ./59/services.json:  "changed-configurations" : [ {
> ./59/services.json-"type" : "yarn-site",
> ./59/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./59/services.json-"old_value" : "1792"
> ./60/services.json:  "changed-configurations" : [ {
> ./60/services.json-"type" : "yarn-site",
> ./60/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./60/services.json-"old_value" : "1280"



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

[jira] [Commented] (AMBARI-19476) Incorrect error message when trying to add a group to multiple roles

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19476:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #724 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/724/])
AMBARI-19476. Incorrect error message when trying to add a group to (hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f5845cc3ce16c3f3e61d9e17a6d86a4579f95684])
* (edit) 
ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/PermissionsSaver.js
* (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/i18n.config.js


> Incorrect error message when trying to add a group to multiple roles
> 
>
> Key: AMBARI-19476
> URL: https://issues.apache.org/jira/browse/AMBARI-19476
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: 2.5.0
>
> Attachments: AMBARI-19476.patch, 
> ErrorMessageAddingGroupToMultipleRoles.jpg
>
>
> 1. Create a group and assign roles to the group.
> 2. If you add the same group to multiple roles, the error message says "Only 
> 1 role allowed per user".



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

[jira] [Commented] (AMBARI-19430) Use common property for principal name prefix to help with customization of unique principal names

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19430:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #724 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/724/])
AMBARI-19430. Use common property for principal name prefix to help with 
(rlevas: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=43f8f73ee97c0cc369c1d6ec8e356c290a28c6c1])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK/kerberos.json
* (edit) ambari-server/src/main/resources/stacks/PERF/1.0/kerberos.json
* (edit) 
ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/kerberos.json
* (edit) 
ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/kerberos.json
* (edit) 
ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/kerberos.json
* (edit) 
ambari-server/src/main/resources/common-services/STORM/0.9.1/kerberos.json
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/HDFS/kerberos.json
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/SPARK/kerberos.json
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/HBASE/kerberos.json
* (edit) 
ambari-server/src/main/resources/common-services/SPARK/1.2.1/kerberos.json
* (edit) 
ambari-server/src/main/resources/common-services/SPARK2/2.0.0/kerberos.json
* (edit) 
ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/kerberos.json
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/services/ACCUMULO/kerberos.json
* (edit) 
ambari-server/src/main/resources/common-services/STORM/1.0.1/kerberos.json
* (edit) 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/kerberos.json
* (edit) 
ambari-server/src/test/resources/kerberos/test_kerberos_descriptor_simple.json
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3.ECS/services/ECS/kerberos.json
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosDescriptorUpdateHelperTest.java
* (edit) 
ambari-server/src/main/resources/common-services/SPARK/1.4.1/kerberos.json
* (edit) 
ambari-server/src/test/resources/kerberos/test_kerberos_descriptor_no_hdfs.json
* (edit) 
ambari-server/src/test/resources/kerberos/test_kerberos_descriptor_2_1_3.json
* (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/kerberos.json
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3.ECS/services/HBASE/kerberos.json
* (edit) 
ambari-server/src/main/resources/stacks/PERF/1.0/services/HBASE/kerberos.json
* (edit) 
ambari-server/src/main/resources/stacks/PERF/1.0/services/SLEEPY/kerberos.json
* (edit) 
ambari-server/src/main/resources/common-services/ACCUMULO/1.6.1.2.2.0/kerberos.json
* (edit) 
ambari-server/src/main/resources/stacks/PERF/1.0/services/HAPPY/kerberos.json
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/KerberosHelperTest.java
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/kerberos.json
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3.GlusterFS/services/ACCUMULO/kerberos.json
* (edit) 
ambari-server/src/main/resources/stacks/PERF/1.0/services/GRUMPY/kerberos.json
* (edit) 
ambari-server/src/test/resources/stacks/HDP/2.0.8/services/HDFS/kerberos.json


> Use common property for principal name prefix to help with customization of 
> unique principal names
> --
>
> Key: AMBARI-19430
> URL: https://issues.apache.org/jira/browse/AMBARI-19430
> Project: Ambari
>  Issue Type: Bug
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: kerberos, kerberos_descriptor
> Attachments: AMBARI-19430_branch-2.5_01.patch, 
> AMBARI-19430_trunk_01.patch
>
>
> Use common property for principal name prefix to help with customization of 
> unique principal names.  
> All _headless_ Kerberos identities have a non-unique principal name (across 
> clusters). To help this issue, the cluster name is appended to these 
> principal names by adding "-$\{cluster-name|toLower()\}" after the principal 
> name component. If the user wants to change this convention, they will need 
> to find all _headless_ principals and make the change. On top of that, when 
> adding new components, they will need to remember to make the change to new 
> _headless_ principal names. 
> A better solution is to provide a _global_ property named "principal_suffix" 
> and use that in each _headless_ principal name. By default the value for this 
> property will be
> {code}
> principal_suffix="-${cluster_name|toLower()}"
> {code}
> If the user would like not use a prefix (in the event there is only a single 
> cluster connecting to the KDC), the value can be changed to
> {code}
> principal_suffix=""
> 

[jira] [Commented] (AMBARI-19537) Provide default value for yarn leveldb state store path

[Di Li (JIRA)]

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

Di Li commented on AMBARI-19537:


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

> Provide default value for yarn leveldb state store path
> ---
>
> Key: AMBARI-19537
> URL: https://issues.apache.org/jira/browse/AMBARI-19537
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-19537.patch
>
>




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

[jira] [Updated] (AMBARI-19537) Provide default value for yarn leveldb state store path

[Di Li (JIRA)]

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

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

> Provide default value for yarn leveldb state store path
> ---
>
> Key: AMBARI-19537
> URL: https://issues.apache.org/jira/browse/AMBARI-19537
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-19537.patch
>
>




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

[jira] [Commented] (AMBARI-19540) Possibly too frequent calls to stack advisor as user changes sliders

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19540:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12847658/AMBARI-19540.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/10083//console

This message is automatically generated.

> Possibly too frequent calls to stack advisor as user changes sliders
> 
>
> Key: AMBARI-19540
> URL: https://issues.apache.org/jira/browse/AMBARI-19540
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Antonenko Alexander
> Fix For: 2.5.0
>
> Attachments: AMBARI-19540.patch, AMBARI-19540.v0.patch, 
> AMBARI-19540.v1.branch-2.5.patch
>
>
> As you can see 3 calls are made while changing from 1024 to 2048 and 
> similarly 3 calls when coming back to 1024. 
> Beyond performance concern, multiple calls have a functional issue. The call 
> includes previous value of the changed property - see the values. I would 
> have expected the old value to be the value that was the original/saved 
> value. However, it is wherever UI makes the stack advisor calls.
> [root@smq1-1 stack-recommendations]# find . -name services.json | xargs grep 
> -A 3 changed
> ./55/services.json:  "changed-configurations" : [ {
> ./55/services.json-"type" : "yarn-site",
> ./55/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./55/services.json-"old_value" : "1024"
> ./56/services.json:  "changed-configurations" : [ {
> ./56/services.json-"type" : "yarn-site",
> ./56/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./56/services.json-"old_value" : "1280"
> ./57/services.json:  "changed-configurations" : [ {
> ./57/services.json-"type" : "yarn-site",
> ./57/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./57/services.json-"old_value" : "1792"
> ./58/services.json:  "changed-configurations" : [ {
> ./58/services.json-"type" : "yarn-site",
> ./58/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./58/services.json-"old_value" : "2048"
> ./59/services.json:  "changed-configurations" : [ {
> ./59/services.json-"type" : "yarn-site",
> ./59/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./59/services.json-"old_value" : "1792"
> ./60/services.json:  "changed-configurations" : [ {
> ./60/services.json-"type" : "yarn-site",
> ./60/services.json-"name" : "yarn.scheduler.minimum-allocation-mb",
> ./60/services.json-"old_value" : "1280"



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

[jira] [Commented] (AMBARI-19545) Ambari-agent: In HIVE and OOZIE stack scripts, copy JCEKS file to desired location

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19545:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12847654/rb55538.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/10082//console

This message is automatically generated.

> Ambari-agent: In HIVE and OOZIE stack scripts, copy JCEKS file to desired 
> location
> --
>
> Key: AMBARI-19545
> URL: https://issues.apache.org/jira/browse/AMBARI-19545
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: rb55538.patch
>
>
> Ambari agent generates the JCEKS provider files as 
> /var/lib/ambari-agent/cred/conf//.jceks. 
> OOZIE and HIVE scripts should specify a location of their choice and set the 
> desired ACLs, instead of using the default location.



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

[jira] [Commented] (AMBARI-19542) Cannot change group/user privileges in list view if the user has VIEW.USER privilege

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19542:


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

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

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

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

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

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

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

This message is automatically generated.

> Cannot change group/user privileges in list view if the user has VIEW.USER 
> privilege
> 
>
> Key: AMBARI-19542
> URL: https://issues.apache.org/jira/browse/AMBARI-19542
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: 2.5.0
>
> Attachments: AMBARI-19542.patch
>
>
> 1. Create a view for e.g. Capacity Scheduler view and grant a group / user 
> permissions for the view.
> 2. Go to Roles list view. Try to assign the group / user a different role via 
> the List view.
> There is no response in the UI and the role is not updated. On the browser 
> console, the following erorr can be seen.
> DELETE 
> http://9.30.56.80:8081/api/v1/clusters/C1/privileges?PrivilegeInfo/privilege_id.in(416)
>  500 (Internal Server Error)
> In the ambari-server.log, the following exception is seen:
> Caused by: org.apache.ambari.server.AmbariException: Can't remove VIEW 
> permission from a CAPACITY-SCHEDULER{1.0.0} resource.
> at 
> org.apache.ambari.server.controller.internal.PrivilegeResourceProvider$2.invoke(PrivilegeResourceProvider.java:460)
> This does not happen when roles are assigned via the Block view.



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

[jira] [Commented] (AMBARI-19446) Able to skip writing configuration files when the config type doesn't exist in the command JSON file

[Di Li (JIRA)]

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

Di Li commented on AMBARI-19446:


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

> Able to skip writing configuration files when the config type doesn't exist 
> in the command JSON file
> 
>
> Key: AMBARI-19446
> URL: https://issues.apache.org/jira/browse/AMBARI-19446
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-19446.patch
>
>
> Able to skip writing configuration files when the config type doesn't exist 
> in the command JSON file.



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