[jira] [Updated] (AMBARI-18774) Install Package for non-HDP stack fails with non-VDF repo version

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-18774:
---
Attachment: AMBARI-18774.2.patch

> Install Package for non-HDP stack fails with non-VDF repo version
> -
>
> Key: AMBARI-18774
> URL: https://issues.apache.org/jira/browse/AMBARI-18774
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18774.2.patch, AMBARI-18774.patch
>
>
> Install Package fails when registering a new non-HDP version without using a 
> VDF. This is because the repo version is saved as display name (i.e. 
> "HDF-2.1.0.0-30" instead of "2.1.0.0-30"). If a new version is registered 
> using VDF, we dont run into this issue as the version is set correctly.
> {code}
> Ambari cannot install version HDF-2.1.0.0.  Version 2.0.1.0-12 is already 
> installed.
> {code}
> Fix:
> Remove HDP specific hardcodings from RepositoryVersionEntity.java



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

[jira] [Commented] (AMBARI-18774) Install Package for non-HDP stack fails with non-VDF repo version

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-18774:


mvn clean test
INFO 
INFO BUILD SUCCESS
INFO 
INFO Total time: 1:05:11.694s
INFO Finished at: Tue Nov 01 20:55:29 PDT 2016
INFO Final Memory: 56M/1012M
INFO 

> Install Package for non-HDP stack fails with non-VDF repo version
> -
>
> Key: AMBARI-18774
> URL: https://issues.apache.org/jira/browse/AMBARI-18774
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18774.patch
>
>
> Install Package fails when registering a new non-HDP version without using a 
> VDF. This is because the repo version is saved as display name (i.e. 
> "HDF-2.1.0.0-30" instead of "2.1.0.0-30"). If a new version is registered 
> using VDF, we dont run into this issue as the version is set correctly.
> {code}
> Ambari cannot install version HDF-2.1.0.0.  Version 2.0.1.0-12 is already 
> installed.
> {code}
> Fix:
> Remove HDP specific hardcodings from RepositoryVersionEntity.java



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

[jira] [Created] (AMBARI-18774) Install Package for non-HDP stack fails with non-VDF repo version

[Jayush Luniya (JIRA)]

Jayush Luniya created AMBARI-18774:
--

 Summary: Install Package for non-HDP stack fails with non-VDF repo 
version
 Key: AMBARI-18774
 URL: https://issues.apache.org/jira/browse/AMBARI-18774
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.0
Reporter: Jayush Luniya
Assignee: Jayush Luniya
Priority: Critical
 Fix For: 2.4.2


Install Package fails when registering a new non-HDP version without using a 
VDF. This is because the repo version is saved as display name (i.e. 
"HDF-2.1.0.0-30" instead of "2.1.0.0-30"). If a new version is registered using 
VDF, we dont run into this issue as the version is set correctly.

{code}
Ambari cannot install version HDF-2.1.0.0.  Version 2.0.1.0-12 is already 
installed.
{code}

Fix:
Remove HDP specific hardcodings from RepositoryVersionEntity.java



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

[jira] [Commented] (AMBARI-18763) Ambari upgrade fails when add-on mpack is installed

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-18763:


[~sumitmohanty]
Can you review the attached patch? Its a one-line change.

> Ambari upgrade fails when add-on mpack is installed
> ---
>
> Key: AMBARI-18763
> URL: https://issues.apache.org/jira/browse/AMBARI-18763
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18763.patch
>
>
> Install Ambari 2.4.0
> Install an add-on mpack
> Upgrade Ambari from 2.4.0 to 2.4.1 
> Ambari upgrade fails 
> ambari-server upgrade
> Using python /usr/bin/python
> Upgrading ambari-server
> Updating properties in ambari.properties ...
> WARNING: Original file ambari-env.sh kept
> ERROR: Unexpected OSError: Errno 17 File exists
> For more info run ambari-server with -v or --verbose option
> Note; Attached the ambari server upgrade in verbose output



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

[jira] [Updated] (AMBARI-18763) Ambari upgrade fails when add-on mpack is installed

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-18763:
---
Status: Patch Available  (was: In Progress)

> Ambari upgrade fails when add-on mpack is installed
> ---
>
> Key: AMBARI-18763
> URL: https://issues.apache.org/jira/browse/AMBARI-18763
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18763.patch
>
>
> Install Ambari 2.4.0
> Install an add-on mpack
> Upgrade Ambari from 2.4.0 to 2.4.1 
> Ambari upgrade fails 
> ambari-server upgrade
> Using python /usr/bin/python
> Upgrading ambari-server
> Updating properties in ambari.properties ...
> WARNING: Original file ambari-env.sh kept
> ERROR: Unexpected OSError: Errno 17 File exists
> For more info run ambari-server with -v or --verbose option
> Note; Attached the ambari server upgrade in verbose output



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

[jira] [Updated] (AMBARI-18763) Ambari upgrade fails when add-on mpack is installed

[Jayush Luniya (JIRA)]

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

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

> Ambari upgrade fails when add-on mpack is installed
> ---
>
> Key: AMBARI-18763
> URL: https://issues.apache.org/jira/browse/AMBARI-18763
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18763.patch
>
>
> Install Ambari 2.4.0
> Install an add-on mpack
> Upgrade Ambari from 2.4.0 to 2.4.1 
> Ambari upgrade fails 
> ambari-server upgrade
> Using python /usr/bin/python
> Upgrading ambari-server
> Updating properties in ambari.properties ...
> WARNING: Original file ambari-env.sh kept
> ERROR: Unexpected OSError: Errno 17 File exists
> For more info run ambari-server with -v or --verbose option
> Note; Attached the ambari server upgrade in verbose output



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

[jira] [Updated] (AMBARI-18375) Ranger Plugin configs are not generated for Hive interactive

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-18375:
---
Fix Version/s: (was: 2.4.2)
   (was: 2.4.1)
   2.5.0

> Ranger Plugin configs are not generated for Hive interactive
> 
>
> Key: AMBARI-18375
> URL: https://issues.apache.org/jira/browse/AMBARI-18375
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18375.patch
>
>
> If audit to hdfs is OFF for ranger hive plugin, configs related to plugins 
> are not generated for Hive interactive



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

[jira] [Updated] (AMBARI-18637) Management pack purge option should warn user and ask for confirmation before purging

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-18637:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Management pack purge option should warn user and ask for confirmation before 
> purging
> -
>
> Key: AMBARI-18637
> URL: https://issues.apache.org/jira/browse/AMBARI-18637
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.4.2
>
> Attachments: AMBARI-18637.patch
>
>




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

[jira] [Updated] (AMBARI-18637) Management pack purge option should warn user and ask for confirmation before purging

[Jayush Luniya (JIRA)]

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

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

> Management pack purge option should warn user and ask for confirmation before 
> purging
> -
>
> Key: AMBARI-18637
> URL: https://issues.apache.org/jira/browse/AMBARI-18637
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.4.2
>
> Attachments: AMBARI-18637.patch
>
>




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

[jira] [Commented] (AMBARI-18637) Management pack purge option should warn user and ask for confirmation before purging

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-18637:


Above test failures are not related to this patch.

> Management pack purge option should warn user and ask for confirmation before 
> purging
> -
>
> Key: AMBARI-18637
> URL: https://issues.apache.org/jira/browse/AMBARI-18637
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.4.2
>
> Attachments: AMBARI-18637.patch
>
>




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

[jira] [Resolved] (AMBARI-17107) Ambari Alert for NameNode Last Checkpoint in NameNode HA

[Jayush Luniya (JIRA)]

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

Jayush Luniya resolved AMBARI-17107.

Resolution: Duplicate

> Ambari Alert for NameNode Last Checkpoint in NameNode HA
> 
>
> Key: AMBARI-17107
> URL: https://issues.apache.org/jira/browse/AMBARI-17107
> Project: Ambari
>  Issue Type: Bug
>  Components: alerts
>Affects Versions: 2.2.2
> Environment: Hortonworks HDP 2.4.2 with HDFS HA enabled.
>Reporter: Rahul Pathak
>  Labels: easyfix
> Fix For: 2.4.0
>
>
> As can be seen in 
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_checkpoint_time.py
> At line 
> {code}NN_HTTP_ADDRESS_KEY = '{{hdfs-site/dfs.namenode.http-address}}'{code}
> It will not work in case of HA enabled cluster. 
> In case of HA this property will not exist and alert will fail.



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

[jira] [Updated] (AMBARI-15873) Ambari-Server Unit Test failures in trunk

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-15873:
---
Labels: revert  (was: reverted)

> Ambari-Server Unit Test failures in trunk
> -
>
> Key: AMBARI-15873
> URL: https://issues.apache.org/jira/browse/AMBARI-15873
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Blocker
>  Labels: revert
> Fix For: 2.4.0
>
>
> Unit test failure in ambari-server in trunk
> https://builds.apache.org/job/Ambari-trunk-Commit/4650/console
> Results :
> Failed tests: 
>   UpgradeCatalog240Test.testExecuteDDLUpdates:227 
>   Unexpected method call DBAccessor.addColumn("viewinstanceentity", 
> org.apache.ambari.server.orm.DBAccessor$DBColumnInfo@1a3492):
> DBAccessor.addColumn("host_role_command", 
> capture(org.apache.ambari.server.orm.DBAccessor$DBColumnInfo@1fbce70)): 
> expected: 1, actual: 1
> Tests run: 4225, Failures: 1, Errors: 0, Skipped: 32



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

[jira] [Reopened] (AMBARI-17133) Replace underscore character from Storm metrics sink

[Jayush Luniya (JIRA)]

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

Jayush Luniya reopened AMBARI-17133:


> Replace underscore character from Storm metrics sink
> 
>
> Key: AMBARI-17133
> URL: https://issues.apache.org/jira/browse/AMBARI-17133
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Jungtaek Lim
> Fix For: 2.4.0
>
>
> Since Ambari Metric Service uses "._" as separator for splitting metric and 
> functions, metric name shouldn't contain "._".
> Storm built-in metrics have metric names starting on '__' and with 
> AMBARI-16946 metric name is placed after '.' which finally makes '._' which 
> makes parsing messed up.
> We should remove '_' characters from metric name or replace them with '-' or 
> alike.
> (Replacing is more safer way if we replace them with special character.)



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

[jira] [Updated] (AMBARI-14883) Express Upgrade - All Service Checks Failure - Queue State

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-14883:
---
Assignee: Andrew Onischuk

> Express Upgrade - All Service Checks Failure - Queue State
> --
>
> Key: AMBARI-14883
> URL: https://issues.apache.org/jira/browse/AMBARI-14883
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-upgrade
>Affects Versions: 2.2.0
>Reporter: Matt Sharp
>Assignee: Andrew Onischuk
>Priority: Minor
> Attachments: AMBARI-14883.patch
>
>
> At the beginning of an Ambari 2.2.0 express upgrade, Ambari prompts you to 
> manually stop all Yarn queues.  At the end of the upgrade it does not prompt 
> you to manually start all Yarn queues again.  This results in the following 
> error during the All Service Checks phase:
> org.apache.hadoop.security.AccessControlException: Queue default is STOPPED.  
> Cannot accept submission of application: application_1454357083355_0002
> A prompt either needs to be added to update the queue state, or ideally 
> handled by Ambari entirely (especially since the cluster is stopped with 
> express upgrade path).



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

[jira] [Resolved] (AMBARI-14590) Error getting timeline metrics

[Jayush Luniya (JIRA)]

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

Jayush Luniya resolved AMBARI-14590.

Resolution: Invalid

> Error getting timeline metrics
> --
>
> Key: AMBARI-14590
> URL: https://issues.apache.org/jira/browse/AMBARI-14590
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.1.0
> Environment: openjdk version "1.8.0_45"
> Red Hat Enterprise Linux Server release 6.5
>Reporter: Sadek
>
> Hi,
> Both the Metrics Collector and Monitors are up and running but none of the 
> graphs are showing and ambari-server.log is filled with these errors:
> ERROR [qtp-client-18] MetricsPropertyProvider:185 - Error getting timeline 
> metrics.
> I do see these errors (for several metrcis) in console:
> Metrics with name "mem_cached" not found to compute expression
> I have connected to the local HBase instance on the collector node and I see 
> all tables there:
> hbase(main):011:0> list
> TABLE 
>   
>
> METRIC_AGGREGATE  
>   
>
> METRIC_AGGREGATE_DAILY
>   
>
> METRIC_AGGREGATE_HOURLY   
>   
>
> METRIC_RECORD 
>   
>
> METRIC_RECORD_DAILY   
>   
>
> METRIC_RECORD_HOURLY  
>   
>
> METRIC_RECORD_MINUTE  
>   
>
> SYSTEM.CATALOG
>   
>
> SYSTEM.SEQUENCE   
>   
>
> SYSTEM.STATS  
>   
>
> 10 row(s) in 0.0090 seconds
> Thanks!



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

[jira] [Updated] (AMBARI-14721) yarn-site properties for Spark Shuffle Aux should be added unconditionally

[Jayush Luniya (JIRA)]

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

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

> yarn-site properties for Spark Shuffle Aux should be added unconditionally
> --
>
> Key: AMBARI-14721
> URL: https://issues.apache.org/jira/browse/AMBARI-14721
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.2.1
>Reporter: Dmytro Grinenko
>Assignee: Andrew Onischuk
>Priority: Blocker
> Fix For: 2.2.1
>
> Attachments: AMBARI-14721.patch
>
>
> The spark shuffle related configs should be added unconditionally in HDP-2.4



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

[jira] [Reopened] (AMBARI-14590) Error getting timeline metrics

[Jayush Luniya (JIRA)]

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

Jayush Luniya reopened AMBARI-14590:


> Error getting timeline metrics
> --
>
> Key: AMBARI-14590
> URL: https://issues.apache.org/jira/browse/AMBARI-14590
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.1.0
> Environment: openjdk version "1.8.0_45"
> Red Hat Enterprise Linux Server release 6.5
>Reporter: Sadek
>
> Hi,
> Both the Metrics Collector and Monitors are up and running but none of the 
> graphs are showing and ambari-server.log is filled with these errors:
> ERROR [qtp-client-18] MetricsPropertyProvider:185 - Error getting timeline 
> metrics.
> I do see these errors (for several metrcis) in console:
> Metrics with name "mem_cached" not found to compute expression
> I have connected to the local HBase instance on the collector node and I see 
> all tables there:
> hbase(main):011:0> list
> TABLE 
>   
>
> METRIC_AGGREGATE  
>   
>
> METRIC_AGGREGATE_DAILY
>   
>
> METRIC_AGGREGATE_HOURLY   
>   
>
> METRIC_RECORD 
>   
>
> METRIC_RECORD_DAILY   
>   
>
> METRIC_RECORD_HOURLY  
>   
>
> METRIC_RECORD_MINUTE  
>   
>
> SYSTEM.CATALOG
>   
>
> SYSTEM.SEQUENCE   
>   
>
> SYSTEM.STATS  
>   
>
> 10 row(s) in 0.0090 seconds
> Thanks!



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

[jira] [Updated] (AMBARI-14721) yarn-site properties for Spark Shuffle Aux should be added unconditionally

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-14721:
---
Assignee: Andrew Onischuk

> yarn-site properties for Spark Shuffle Aux should be added unconditionally
> --
>
> Key: AMBARI-14721
> URL: https://issues.apache.org/jira/browse/AMBARI-14721
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.2.1
>Reporter: Dmytro Grinenko
>Assignee: Andrew Onischuk
>Priority: Blocker
> Fix For: 2.2.1
>
> Attachments: AMBARI-14721.patch
>
>
> The spark shuffle related configs should be added unconditionally in HDP-2.4



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

[jira] [Resolved] (AMBARI-17998) When I enable Kerberos,the Hive shell faild to access.

[Jayush Luniya (JIRA)]

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

Jayush Luniya resolved AMBARI-17998.

Resolution: Invalid

> When I enable Kerberos,the Hive shell faild to access.
> --
>
> Key: AMBARI-17998
> URL: https://issues.apache.org/jira/browse/AMBARI-17998
> Project: Ambari
>  Issue Type: Bug
>  Components: security
>Affects Versions: 2.2.2
> Environment: Centos6.7
>Reporter: niushuo
> Fix For: 2.2.2
>
>
> When I enable Kerberos,the serverice of Hive  was succeed to start.Bui when I 
> use the command "hive" to go in the Hive shell,it's show some error,show in 
> below,
> 2016-08-02 21:39:26,620 ERROR [pool-5-thread-183]: server.TThreadPoolServer 
> (TThreadPoolServer.java:run(296)) - Error occurred during processing of 
> message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Peer indicated failure: GSS initiate failed
>   at 
> org.apache.thrift.transport.TSaslServerTransport$Factory.getTransport(TSaslServerTransport.java:219)
>   at 
> org.apache.hadoop.hive.thrift.HadoopThriftAuthBridge$Server$TUGIAssumingTransportFactory$1.run(HadoopThriftAuthBridge.java:739)
>   at 
> org.apache.hadoop.hive.thrift.HadoopThriftAuthBridge$Server$TUGIAssumingTransportFactory$1.run(HadoopThriftAuthBridge.java:736)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:356)
>   at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1637)
>   at 
> org.apache.hadoop.hive.thrift.HadoopThriftAuthBridge$Server$TUGIAssumingTransportFactory.getTransport(HadoopThriftAuthBridge.java:736)
>   at 
> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:268)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.thrift.transport.TTransportException: Peer indicated 
> failure: GSS initiate failed
>   at 
> org.apache.thrift.transport.TSaslTransport.receiveSaslMessage(TSaslTransport.java:199)
>   at 
> org.apache.thrift.transport.TSaslServerTransport.handleSaslStartMessage(TSaslServerTransport.java:125)
>   at 
> org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:271)
>   at 
> org.apache.thrift.transport.TSaslServerTransport.open(TSaslServerTransport.java:41)
>   at 
> org.apache.thrift.transport.TSaslServerTransport$Factory.getTransport(TSaslServerTransport.java:216)
>   ... 10 more



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

[jira] [Resolved] (AMBARI-17997) When i enable kerberos,MapReduce2 and Yarn both faied to start.

[Jayush Luniya (JIRA)]

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

Jayush Luniya resolved AMBARI-17997.

Resolution: Invalid

> When i enable kerberos,MapReduce2 and Yarn both faied to start.
> ---
>
> Key: AMBARI-17997
> URL: https://issues.apache.org/jira/browse/AMBARI-17997
> Project: Ambari
>  Issue Type: Bug
>  Components: security
>Affects Versions: 2.2.2
> Environment: Centos6.7
>Reporter: niushuo
>
> No kerberos,the cluster was OK!But,When I enable kerberos,MapReduce2 and Yarn 
> both faied to start.The log like this,how can I do to fix the problem?
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py",
>  line 182, in 
> HistoryServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 219, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py",
>  line 92, in start
> self.configure(env) # FOR SECURITY
>   File 
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py",
>  line 55, in configure
> yarn(name="historyserver")
>   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 71, in yarn
> recursive_chmod=True
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 154, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 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 463, in action_create_on_execute
> self.action_delayed("create")
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
>  line 460, 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 250, in action_delayed
> self._assert_valid()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
>  line 234, in _assert_valid
> self.target_status = self._get_file_status(target)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
>  line 295, in _get_file_status
> list_status = self.util.run_command(target, 'GETFILESTATUS', 
> method='GET', ignore_status_codes=['404'], assertable_result=False)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
>  line 195, in run_command
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'curl -sS -L -w 
> '%{http_code}' -X GET --negotiate -u : 
> 'http://bigdata-32.bigdata:50070/webhdfs/v1/app-logs?op=GETFILESTATUS=hdfs''
>  returned status_code=401. 
> 
> 
> 
> Error 401 Authentication required
> 
> HTTP ERROR 401
> Problem accessing /webhdfs/v1/app-logs. Reason:
> Authentication requiredPowered by 
> Jetty://
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 



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

[jira] [Reopened] (AMBARI-17997) When i enable kerberos,MapReduce2 and Yarn both faied to start.

[Jayush Luniya (JIRA)]

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

Jayush Luniya reopened AMBARI-17997:


> When i enable kerberos,MapReduce2 and Yarn both faied to start.
> ---
>
> Key: AMBARI-17997
> URL: https://issues.apache.org/jira/browse/AMBARI-17997
> Project: Ambari
>  Issue Type: Bug
>  Components: security
>Affects Versions: 2.2.2
> Environment: Centos6.7
>Reporter: niushuo
>
> No kerberos,the cluster was OK!But,When I enable kerberos,MapReduce2 and Yarn 
> both faied to start.The log like this,how can I do to fix the problem?
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py",
>  line 182, in 
> HistoryServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 219, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py",
>  line 92, in start
> self.configure(env) # FOR SECURITY
>   File 
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py",
>  line 55, in configure
> yarn(name="historyserver")
>   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 71, in yarn
> recursive_chmod=True
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 154, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 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 463, in action_create_on_execute
> self.action_delayed("create")
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
>  line 460, 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 250, in action_delayed
> self._assert_valid()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
>  line 234, in _assert_valid
> self.target_status = self._get_file_status(target)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
>  line 295, in _get_file_status
> list_status = self.util.run_command(target, 'GETFILESTATUS', 
> method='GET', ignore_status_codes=['404'], assertable_result=False)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
>  line 195, in run_command
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'curl -sS -L -w 
> '%{http_code}' -X GET --negotiate -u : 
> 'http://bigdata-32.bigdata:50070/webhdfs/v1/app-logs?op=GETFILESTATUS=hdfs''
>  returned status_code=401. 
> 
> 
> 
> Error 401 Authentication required
> 
> HTTP ERROR 401
> Problem accessing /webhdfs/v1/app-logs. Reason:
> Authentication requiredPowered by 
> Jetty://
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 



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

[jira] [Resolved] (AMBARI-15746) ambari-agent start failed

[Jayush Luniya (JIRA)]

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

Jayush Luniya resolved AMBARI-15746.

Resolution: Invalid

> ambari-agent start failed 
> --
>
> Key: AMBARI-15746
> URL: https://issues.apache.org/jira/browse/AMBARI-15746
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.2.1
> Environment: RedHat Enterprise Linux 6.7
>Reporter: Adrian Blakey
>Priority: Blocker
>
> The agent does not start. Looks like OpenSSL is missing - it isn't.
> ambari-agent start
> Verifying Python version compatibility...
> Using python  /usr/bin/python
> Checking for previously running Ambari Agent...
> /var/run/ambari-agent/ambari-agent.pid found with no process. Removing 7128...
> Starting ambari-agent
> Verifying ambari-agent process status...
> ERROR: ambari-agent start failed. For more details, see 
> /var/log/ambari-agent/ambari-agent.out:
> 
> Can't open library libX11.so.6: libssl.so: cannot open shared object file: No 
> such file or directory
> 
> Agent out at: /var/log/ambari-agent/ambari-agent.out
> Agent log at: /var/log/ambari-agent/ambari-agent.log
> Red Hat Enterprise Linux Server release 6.7 (Santiago)
> java version "1.8.0_77"
> Java(TM) SE Runtime Environment (build 1.8.0_77-b03)
> Java HotSpot(TM) 64-Bit Server VM (build 25.77-b03, mixed mode)
> Package openssl-1.0.1e-42.el6_7.2.x86_64 already installed and latest version
> Package libXt-1.1.4-6.1.el6.x86_64 already installed and latest version
> Package libX11-1.6.0-6.el6.x86_64 already installed and latest version



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

[jira] [Reopened] (AMBARI-15746) ambari-agent start failed

[Jayush Luniya (JIRA)]

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

Jayush Luniya reopened AMBARI-15746:


> ambari-agent start failed 
> --
>
> Key: AMBARI-15746
> URL: https://issues.apache.org/jira/browse/AMBARI-15746
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.2.1
> Environment: RedHat Enterprise Linux 6.7
>Reporter: Adrian Blakey
>Priority: Blocker
>
> The agent does not start. Looks like OpenSSL is missing - it isn't.
> ambari-agent start
> Verifying Python version compatibility...
> Using python  /usr/bin/python
> Checking for previously running Ambari Agent...
> /var/run/ambari-agent/ambari-agent.pid found with no process. Removing 7128...
> Starting ambari-agent
> Verifying ambari-agent process status...
> ERROR: ambari-agent start failed. For more details, see 
> /var/log/ambari-agent/ambari-agent.out:
> 
> Can't open library libX11.so.6: libssl.so: cannot open shared object file: No 
> such file or directory
> 
> Agent out at: /var/log/ambari-agent/ambari-agent.out
> Agent log at: /var/log/ambari-agent/ambari-agent.log
> Red Hat Enterprise Linux Server release 6.7 (Santiago)
> java version "1.8.0_77"
> Java(TM) SE Runtime Environment (build 1.8.0_77-b03)
> Java HotSpot(TM) 64-Bit Server VM (build 25.77-b03, mixed mode)
> Package openssl-1.0.1e-42.el6_7.2.x86_64 already installed and latest version
> Package libXt-1.1.4-6.1.el6.x86_64 already installed and latest version
> Package libX11-1.6.0-6.el6.x86_64 already installed and latest version



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

[jira] [Reopened] (AMBARI-17107) Ambari Alert for NameNode Last Checkpoint in NameNode HA

[Jayush Luniya (JIRA)]

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

Jayush Luniya reopened AMBARI-17107:


> Ambari Alert for NameNode Last Checkpoint in NameNode HA
> 
>
> Key: AMBARI-17107
> URL: https://issues.apache.org/jira/browse/AMBARI-17107
> Project: Ambari
>  Issue Type: Bug
>  Components: alerts
>Affects Versions: 2.2.2
> Environment: Hortonworks HDP 2.4.2 with HDFS HA enabled.
>Reporter: Rahul Pathak
>  Labels: easyfix
> Fix For: 2.4.0
>
>
> As can be seen in 
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_checkpoint_time.py
> At line 
> {code}NN_HTTP_ADDRESS_KEY = '{{hdfs-site/dfs.namenode.http-address}}'{code}
> It will not work in case of HA enabled cluster. 
> In case of HA this property will not exist and alert will fail.



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

[jira] [Resolved] (AMBARI-14887) Atlas Integration : Fix Atlas-Kafka properties for Blueprints

[Jayush Luniya (JIRA)]

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

Jayush Luniya resolved AMBARI-14887.

Resolution: Duplicate

> Atlas Integration : Fix Atlas-Kafka properties for Blueprints
> -
>
> Key: AMBARI-14887
> URL: https://issues.apache.org/jira/browse/AMBARI-14887
> Project: Ambari
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
>
> The mechanism of setting the topology related properties(kafka and zk) in the 
> agent will result in issues with blueprint installs.
> Because each node in a blueprint provisioned cluster is provisioned 
> independently of other nodes, the blueprint topology manager needs to block 
> provisioning of all nodes until all hosts required for configuration topology 
> resolution are known.  This is determined in BlueprintConfigurationProcessor. 
>  Because these configurations are not registered with the blueprint 
> configuration processor it is possible for the atlas host to be provisioned 
> prior to the Kafka hosts being known which result in the failure of the agent 
> to set these topology related properties.
> In BlueprintConfigurationProcessor you will need too register updaters for 
> all of the topology related properties, in this case 
> "atlas.kafka.bootstrap.servers" and "atlas.kafka.zookeeper.connect".
> For example:
> atlasPropsMap.put("atlas.kafka.bootstrap.servers", new 
> MultipleHostTopologyUpdater("KAFKA_BROKER"));



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

[jira] [Reopened] (AMBARI-14887) Atlas Integration : Fix Atlas-Kafka properties for Blueprints

[Jayush Luniya (JIRA)]

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

Jayush Luniya reopened AMBARI-14887:


> Atlas Integration : Fix Atlas-Kafka properties for Blueprints
> -
>
> Key: AMBARI-14887
> URL: https://issues.apache.org/jira/browse/AMBARI-14887
> Project: Ambari
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
>
> The mechanism of setting the topology related properties(kafka and zk) in the 
> agent will result in issues with blueprint installs.
> Because each node in a blueprint provisioned cluster is provisioned 
> independently of other nodes, the blueprint topology manager needs to block 
> provisioning of all nodes until all hosts required for configuration topology 
> resolution are known.  This is determined in BlueprintConfigurationProcessor. 
>  Because these configurations are not registered with the blueprint 
> configuration processor it is possible for the atlas host to be provisioned 
> prior to the Kafka hosts being known which result in the failure of the agent 
> to set these topology related properties.
> In BlueprintConfigurationProcessor you will need too register updaters for 
> all of the topology related properties, in this case 
> "atlas.kafka.bootstrap.servers" and "atlas.kafka.zookeeper.connect".
> For example:
> atlasPropsMap.put("atlas.kafka.bootstrap.servers", new 
> MultipleHostTopologyUpdater("KAFKA_BROKER"));



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

[jira] [Updated] (AMBARI-16089) Atlas Integration : set atlas.cluster.name in hive-site

[Jayush Luniya (JIRA)]

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

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

> Atlas Integration : set atlas.cluster.name in hive-site
> ---
>
> Key: AMBARI-16089
> URL: https://issues.apache.org/jira/browse/AMBARI-16089
> Project: Ambari
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Attachments: AMBARI-16089.patch
>
>
> After deploying Hive+Atlas via Ambari, the value of 'atlas.cluster.name‘ in 
> 'Advanced hive-site’ is ‘default’. This results in incorrect value in entity 
> notifications to Ranger.



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

[jira] [Reopened] (AMBARI-16090) Atlas Integration : add defult login method configuration

[Jayush Luniya (JIRA)]

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

Jayush Luniya reopened AMBARI-16090:


> Atlas Integration : add defult login method configuration
> -
>
> Key: AMBARI-16090
> URL: https://issues.apache.org/jira/browse/AMBARI-16090
> Project: Ambari
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
>
> To enable login to Atlas UI, following properties have to be manually added 
> to ‘Custom application-properties’ in Atlas. 
> {code}
> atlas.login.method=file
> atlas.login.credentials.file=/etc/atlas/conf/users-credentials.properties
> {code}



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

[jira] [Updated] (AMBARI-15733) Atlas Integration : Support Atlas HA

[Jayush Luniya (JIRA)]

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

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

> Atlas Integration : Support Atlas HA
> 
>
> Key: AMBARI-15733
> URL: https://issues.apache.org/jira/browse/AMBARI-15733
> Project: Ambari
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Attachments: AMBARI-15733.patch
>
>
> # set cardinality to 1+ in Atlas stack definition
> # expose Atlas configuration to enable HA (atlas.server.ha.enabled)
> # set Atlas configuration for server id list (atlas.server.ids)
> # set Atlas configuration properties for hosts (atlas.server.host.id1, ...)
> # expose Atlas host component ha_state property in Ambari REST API.
> # Update Ambari quick link definition in Atlas stack definition to show 
> ha_state.  (See Yarn RM quick links)



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

[jira] [Updated] (AMBARI-16263) Falcon server start fails

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-16263:
---
Attachment: AMBARI-16263-2.patch

> Falcon server start fails
> -
>
> Key: AMBARI-16263
> URL: https://issues.apache.org/jira/browse/AMBARI-16263
> Project: Ambari
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Attachments: AMBARI-16263-2.patch
>
>
> Deployed HDP-2.5 and Falcon server failed to start.
> {code}
> cat /var/log/falcon/falcon.out.20160504002*
> Error: Could not find or load main class org.apache.falcon.FalconServer
> Error: Could not find or load main class org.apache.falcon.FalconServer
> Error: Could not find or load main class org.apache.falcon.FalconServer
> {code}
> The command to start, in Ambari is:
> {code}
> Execute['/usr/hdp/current/falcon-server/bin/falcon-start -port 15000'] 
> {'environment': {'HADOOP_HOME': '/usr/hdp/current/hadoop-client'}, 'path': 
> ['/usr/hdp/current/hadoop-client/bin'], 'user': 'falcon'}
> {code}



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

[jira] [Resolved] (AMBARI-15984) Atlas Integration : Expose Atlas audit configuration

[Jayush Luniya (JIRA)]

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

Jayush Luniya resolved AMBARI-15984.

Resolution: Duplicate

> Atlas Integration : Expose Atlas audit configuration
> 
>
> Key: AMBARI-15984
> URL: https://issues.apache.org/jira/browse/AMBARI-15984
> Project: Ambari
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
>
> Need to expose the following configuration for Atlas in 
> atlas-application.properties ...
> {code}
> atlas.audit.hbase.tablename=ATLAS_ENTITY_AUDIT_EVENTS
> atlas.audit.zookeeper.session.timeout.ms=1000
> atlas.audit.hbase.zookeeper.quorum=localhost:2181
> {code}



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

[jira] [Updated] (AMBARI-15818) Ambari should manage Atlas log4j.xml

[Jayush Luniya (JIRA)]

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

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

> Ambari should manage Atlas log4j.xml
> 
>
> Key: AMBARI-15818
> URL: https://issues.apache.org/jira/browse/AMBARI-15818
> Project: Ambari
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Fix For: 2.4.0
>
> Attachments: AMBARI-15818.patch
>
>
> Currently, Ambari does not provide a means of editing the Atlas log4j.xml 
> file which is problematic for users that want to make changes to the log 
> levels. Ambari/Atlas integration should allow for this file to be managed.



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

[jira] [Updated] (AMBARI-16464) Atlas Integration : Atlas fails to come up with solr as indexing search when the zookeeper quorum has more than one host

[Jayush Luniya (JIRA)]

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

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

> Atlas Integration : Atlas fails to come up with solr as indexing search when 
> the zookeeper quorum has more than one host
> 
>
> Key: AMBARI-16464
> URL: https://issues.apache.org/jira/browse/AMBARI-16464
> Project: Ambari
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Attachments: AMBARI-16464.patch
>
>
> Atlas fails to communicate with solr when the zookeeper quorum has more than 
> one host, as a result of this atlas fails to comeup.
> Actually the config parameter "atlas.graph.index.search.solr.zookeeper-url"  
> value is set to "{{zookeeper_quorum}}/logsearch".  Since there are more than 
> one zookeeper servers deployed, this value evaluates to 
> "[os-r6-apathan-atlas-erie-nosec-3.openstacklocal:2181, 
> os-r6-apathan-atlas-erie-nosec-2.openstacklocal:2181/logsearch]" which seems 
> to wrong. 
> Below is the application log of atlas
> {noformat}
> 2016-05-05 18:32:42,394 DEBUG - [main:] ~ atlas.graph.index.search.directory 
> = /var/lib/atlas/data/es (ApplicationProperties:86)
> 2016-05-05 18:32:42,394 DEBUG - [main:] ~ 
> atlas.graph.index.search.elasticsearch.client-only = false 
> (ApplicationProperties:86)
> 2016-05-05 18:32:42,394 DEBUG - [main:] ~ 
> atlas.graph.index.search.elasticsearch.local-mode = true 
> (ApplicationProperties:86)
> 2016-05-05 18:32:42,394 DEBUG - [main:] ~ atlas.graph.index.search.solr.mode 
> = cloud (ApplicationProperties:86)
> 2016-05-05 18:32:42,395 DEBUG - [main:] ~ 
> atlas.graph.index.search.solr.zookeeper-url = 
> [os-r6-apathan-atlas-erie-nosec-3.openstacklocal:2181, 
> os-r6-apathan-atlas-erie-nosec-2.openstacklocal:2181/logsearch] 
> (ApplicationProperties:86)
> 2016-05-05 18:32:42,395 DEBUG - [main:] ~ atlas.graph.storage.backend = hbase 
> (ApplicationProperties:86)
> {noformat}
> The exception because of this
> {noformat}
> 2016-05-05 18:33:11,212 INFO  - [main:] ~ Session: 0x25480887e74006a closed 
> (ZooKeeper:684)
> 2016-05-05 18:33:11,215 WARN  - [main:] ~ FAILED 
> o.e.j.w.WebAppContext@65064ae0{/,file:/var/lib/atlas/server/webapp/atlas/,STARTING}{/var/lib/atlas/server/webapp/atlas}:
>  java.lang.ExceptionInInitializerError (AbstractLifeCycle:212)
> java.lang.ExceptionInInitializerError
>   at 
> org.apache.atlas.repository.graph.DeleteHandler.(DeleteHandler.java:48)
>   at java.lang.Class.forName0(Native Method)
>   at java.lang.Class.forName(Class.java:264)
>   at 
> org.apache.atlas.ApplicationProperties.getClass(ApplicationProperties.java:99)
>   at 
> org.apache.atlas.RepositoryMetadataModule.getDeleteHandler(RepositoryMetadataModule.java:114)
>   at 
> org.apache.atlas.RepositoryMetadataModule.configure(RepositoryMetadataModule.java:90)
>   at com.google.inject.AbstractModule.configure(AbstractModule.java:62)
>   at 
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340)
>   at com.google.inject.spi.Elements.getElements(Elements.java:110)
>   at 
> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:138)
>   at 
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104)
>   at com.google.inject.Guice.createInjector(Guice.java:96)
>   at com.google.inject.Guice.createInjector(Guice.java:73)
>   at com.google.inject.Guice.createInjector(Guice.java:62)
>   at 
> org.apache.atlas.web.listeners.GuiceServletConfig.getInjector(GuiceServletConfig.java:79)
>   at 
> com.google.inject.servlet.GuiceServletContextListener.contextInitialized(GuiceServletContextListener.java:47)
>   at 
> org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:148)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
>   at 
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
>   at 
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
>   at 
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
>   at 
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
>   at 
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
>   at 
> 

[jira] [Updated] (AMBARI-16693) Atlas Server script error during upgrade.

[Jayush Luniya (JIRA)]

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

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

> Atlas Server script error during upgrade.
> -
>
> Key: AMBARI-16693
> URL: https://issues.apache.org/jira/browse/AMBARI-16693
> Project: Ambari
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Attachments: AMBARI-16693.patch
>
>
> An error {{kafka_broker_hosts' was not found in configurations dictionary!}} 
> is seen during upgrade ...
> {code}
> {
>   "href" : 
> "http://172.22.64.238:8080/api/v1/clusters/cl1/requests/59/tasks/597;,
>   "Tasks" : {
> "attempt_cnt" : 1,
> "cluster_name" : "cl1",
> "command" : "STOP",
> "command_detail" : "ATLAS_SERVER STOP",
> "end_time" : 1463369271424,
> "error_log" : "/var/lib/ambari-agent/data/errors-597.txt",
> "exit_code" : 1,
> "host_name" : "os-r6-swuvps-upg-sanity-211-5.openstacklocal",
> "id" : 597,
> "output_log" : "/var/lib/ambari-agent/data/output-597.txt",
> "request_id" : 59,
> "role" : "ATLAS_SERVER",
> "stage_id" : 0,
> "start_time" : 1463369268252,
> "status" : "FAILED",
> "stderr" : "Traceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py\",
>  line 165, in \nMetadataServer().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 254, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py\",
>  line 82, in stop\nimport params\n  File 
> \"/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/params.py\",
>  line 139, in \nif not len(kafka_broker_hosts) == 0:\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py\",
>  line 73, in __getattr__\nraise Fail(\"Configuration parameter '\" + 
> self.name + \"' was not found in configurations 
> dictionary!\")\nresource_management.core.exceptions.Fail: Configuration 
> parameter 'kafka_broker_hosts' was not found in configurations dictionary!",
> "stdout" : "\n\nCommand failed after 1 tries\n",
> "structured_out" : { }
>   }
> }
> {code}



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

[jira] [Resolved] (AMBARI-16689) Atlas Integration : Set atlas.kafka.auto.commit.enable to false

[Jayush Luniya (JIRA)]

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

Jayush Luniya resolved AMBARI-16689.

Resolution: Duplicate

> Atlas Integration : Set atlas.kafka.auto.commit.enable to false
> ---
>
> Key: AMBARI-16689
> URL: https://issues.apache.org/jira/browse/AMBARI-16689
> Project: Ambari
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
>
> As part of ATLAS-629, atlas-application.properties includes the following 
> property atlas.kafka.auto.commit.enable=false. Needs to be set as part of 
> Ambari installation as well.



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

[jira] [Reopened] (AMBARI-16689) Atlas Integration : Set atlas.kafka.auto.commit.enable to false

[Jayush Luniya (JIRA)]

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

Jayush Luniya reopened AMBARI-16689:


> Atlas Integration : Set atlas.kafka.auto.commit.enable to false
> ---
>
> Key: AMBARI-16689
> URL: https://issues.apache.org/jira/browse/AMBARI-16689
> Project: Ambari
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
>
> As part of ATLAS-629, atlas-application.properties includes the following 
> property atlas.kafka.auto.commit.enable=false. Needs to be set as part of 
> Ambari installation as well.



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

[jira] [Updated] (AMBARI-16690) Atlas Integration : Change default expanded web app directory

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-16690:
---
Attachment: AMBARI-16689.patch

> Atlas Integration : Change default expanded web app directory
> -
>
> Key: AMBARI-16690
> URL: https://issues.apache.org/jira/browse/AMBARI-16690
> Project: Ambari
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Attachments: AMBARI-16689.patch
>
>
> The Atlas web app is currently expanded to /var/lib/atlas. It should be in 
> /usr/hdp/.../atlas-server.



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

[jira] [Updated] (AMBARI-16730) Atlas Integration : Rename atlas lineage configurations

[Jayush Luniya (JIRA)]

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

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

> Atlas Integration : Rename atlas lineage configurations
> ---
>
> Key: AMBARI-16730
> URL: https://issues.apache.org/jira/browse/AMBARI-16730
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Fix For: 2.4.0
>
> Attachments: AMBARI-16730.patch
>
>
> As part of ATLAS-713, the following changes are required in atlas 
> configuration that is set by Ambari:
> # atlas.lineage.hive.table.schema.query.Table renamed to 
> atlas.lineage.schema.query.Table
> # atlas.lineage.hive.table.schema.query.hive_table renamed to 
> atlas.lineage.schema.query.hive_table



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

[jira] [Updated] (AMBARI-16781) Atlas HA configuration Property Changed

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-16781:
---
Attachment: AMBARI-16781-2.patch

> Atlas HA configuration Property Changed
> ---
>
> Key: AMBARI-16781
> URL: https://issues.apache.org/jira/browse/AMBARI-16781
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Erik Bergenholtz
>Assignee: Tom Beerbower
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16781-2.patch
>
>
> The Atlas HA properties to designate ha hosts has changed from:
> atlas.server.host.id to atlas.server.address.id this causes Atlas to not be 
> able to start in HA mode. The following changes need to be made:
> - resources/common-services/ATLAS/0.1.0.2.3/package/scripts/params.py 
> - 
> resources/stacks/HDP/2.5/services/ATLAS/configuration/application-properties.xml



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

[jira] [Updated] (AMBARI-17262) Atlas Integration : Remove {{atlas_conf_dir}} from HADOOP_CLASSPATH in hive-env.

[Jayush Luniya (JIRA)]

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

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

> Atlas Integration : Remove {{atlas_conf_dir}} from HADOOP_CLASSPATH in 
> hive-env.
> 
>
> Key: AMBARI-17262
> URL: https://issues.apache.org/jira/browse/AMBARI-17262
> Project: Ambari
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Attachments: AMBARI-17262.patch
>
>
> In Hive configuration ‘Advanced hive-env’ :
> {code}
> export 
> HADOOP_CLASSPATH={{atlas_conf_dir}}:{{atlas_home_dir}}/hook/hive:${HADOOP_CLASSPATH}
> {code}
> remove 
> {code}
> {{atlas_conf_dir}}
> {code}



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

[jira] [Updated] (AMBARI-17273) With Atlas HA enabled, atlas instance fails to come up with "Unable to find IDs matching any local host and port binding among id1"

[Jayush Luniya (JIRA)]

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

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

> With Atlas HA enabled, atlas instance fails to come up with "Unable to find 
> IDs matching any local host and port binding among id1"
> ---
>
> Key: AMBARI-17273
> URL: https://issues.apache.org/jira/browse/AMBARI-17273
> Project: Ambari
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Attachments: AMBARI-17273.patch
>
>
> Atlas fails to come up with below error. This is because if ID information 
> for all atlas instances is not generated and updated in 
> atlas-application.properties.
> {noformat}
> 2016-06-14 10:48:23,249 WARN  - [main:] ~ Failed startup of context 
> o.e.j.w.WebAppContext@2ad31d76{/,file:/grid/0/hdp/2.5.0.0-723/atlas/server/webapp/atlas/,STARTING}{/usr/hdp/current/atlas-server/server/webapp/atlas}
>  (WebAppContext:514)
> java.lang.RuntimeException: org.apache.atlas.AtlasException: Could not find 
> server id for this instance. Unable to find IDs matching any local host and 
> port binding among id1
> at org.apache.atlas.service.Services.start(Services.java:48)
> at 
> org.apache.atlas.web.listeners.GuiceServletConfig.startServices(GuiceServletConfig.java:142)
> at 
> org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:136)
> at 
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
> at 
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
> at 
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
> at 
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
> at 
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
> at 
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
> at 
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
> at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
> at org.eclipse.jetty.server.Server.start(Server.java:387)
> at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
> at 
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
> at org.eclipse.jetty.server.Server.doStart(Server.java:354)
> at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at 
> org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:93)
> at org.apache.atlas.Atlas.main(Atlas.java:113)
> Caused by: org.apache.atlas.AtlasException: Could not find server id for this 
> instance. Unable to find IDs matching any local host and port binding among 
> id1
> at 
> org.apache.atlas.ha.AtlasServerIdSelector.selectServerId(AtlasServerIdSelector.java:77)
> at 
> org.apache.atlas.web.service.ActiveInstanceElectorService.start(ActiveInstanceElectorService.java:105)
> at org.apache.atlas.service.Services.start(Services.java:45)
> ... 19 more
> 2016-06-14 10:48:23,284 INFO  - [main:] ~ Started 
> ServerConnector@255af999{HTTP/1.1}{0.0.0.0:21000} (ServerConnector:266)
> {noformat}
> Atlas-application.properties not updated with all other instance information 
> leading to atlas startup failure
> {noformat}
> [root@ayubTesting-3 ~]# cat /etc/atlas/conf/atlas-application.properties
> # Generated by Apache Ambari. Tue Jun 14 10:47:47 2016
> atlas.audit.hbase.tablename=ATLAS_ENTITY_AUDIT_EVENTS
> atlas.audit.hbase.zookeeper.quorum=ayubtesting-2.openstacklocal,ayubtesting-3.openstacklocal
> atlas.audit.zookeeper.session.timeout.ms=1000
> atlas.auth.policy.file=/etc/atlas/conf/policy-store.txt
> atlas.authentication.keytab=/etc/security/keytabs/atlas.service.keytab
> atlas.authentication.method=simple
> atlas.authentication.method.file=true
> atlas.authentication.method.file.filename=/etc/atlas/conf/users-credentials.properties
> atlas.authentication.method.kerberos=false
> atlas.authentication.method.ldap=false
> atlas.authentication.method.ldap.type=ldap
> atlas.authentication.method.ldap.url=
> atlas.authentication.principal=atlas
> atlas.authorizer.impl=simple
> atlas.cluster.name=cl1
> atlas.enableTLS=false
> 

[jira] [Updated] (AMBARI-17144) Atlas Integration : Required changes for atlas-application.properties

[Jayush Luniya (JIRA)]

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

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

> Atlas Integration : Required changes for atlas-application.properties
> -
>
> Key: AMBARI-17144
> URL: https://issues.apache.org/jira/browse/AMBARI-17144
> Project: Ambari
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Fix For: 2.4.0
>
> Attachments: AMBARI-17144.patch
>
>
> Changes in ATLAS-820 require following configurations to be present in 
> atlas-application.properties:
> {code}
> atlas.authentication.method.kerberos=false
> atlas.authentication.method.file=true
> atlas.authentication.method.ldap=false
> atlas.authentication.method.file.filename={{atlas_login_credentials_file}}
> atlas.authentication.method.ldap.type=ldap|ad
> atlas.authentication.method.ldap.url=
> {code}
>  
> When Kerberos is enabled, following configurations need to be set/added:
> {code}
> atlas.authentication.method.kerberos=true
> atlas.authentication.method.kerberos.keytab=/etc/security/keytabs/spnego.service.keytab
> atlas.authentication.method.kerberos.principal=HTTP/_h...@example.com
> atlas.authentication.method.kerberos.name.rules=
> atlas.kafka.sasl.kerberos.service.name=kafka
> atlas.kafka.security.protocol=SASL_PLAINTEXT
> atlas.jaas.KafkaClient.loginModuleName=com.sun.security.auth.module.Krb5LoginModule
> atlas.jaas.KafkaClient.loginModuleControlFlag=required
> atlas.jaas.KafkaClient.option.useKeyTab=true
> atlas.jaas.KafkaClient.option.storeKey=true
> atlas.jaas.KafkaClient.option.serviceName=kafka
> atlas.jaas.KafkaClient.option.keyTab={{atlas_keytab_path}}
> atlas.jaas.KafkaClient.option.principal={{atlas_jaas_principal}}
> {code} 
> Following properties are no more used and need to be removed:
> {code}
> atlas.http.authentication.enabled
> atlas.http.authentication.kerberos.keytab
> atlas.http.authentication.type
> atlas.http.authentication.kerberos.principal
> atlas.http.authentication.kerberos.name.rules
> atlas.login.method=
> atlas.login.credentials.file=
> {code} 



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

[jira] [Updated] (AMBARI-17274) As part of atlas startup,"/usr/lib/ambari-logsearch-solr-client/solrCloudCli.sh" script is executed by ambari, which fails with "java.io.FileNotFoundException"

[Jayush Luniya (JIRA)]

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

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

> As part of atlas 
> startup,"/usr/lib/ambari-logsearch-solr-client/solrCloudCli.sh" script is 
> executed by ambari, which fails with "java.io.FileNotFoundException"
> ---
>
> Key: AMBARI-17274
> URL: https://issues.apache.org/jira/browse/AMBARI-17274
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Fix For: 2.4.0
>
> Attachments: AMBARI-17274.patch
>
>
> Below is the error log.
> {noformat}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py",
>  line 173, in 
> MetadataServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 257, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py",
>  line 69, in start
> self.configure(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py",
>  line 53, in configure
> metadata()
>   File 
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata.py",
>  line 101, in metadata
> upload_conf_set('basic_configs', random_num)
>   File 
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata.py",
>  line 122, in upload_conf_set
> user=params.metadata_user)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/solr_cloud_util.py",
>  line 49, in upload_configuration_to_zk
> user=user
>   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/core/providers/system.py",
>  line 273, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 70, in inner
> result = function(command, **kwargs)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 293, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'export 
> JAVA_HOME=/usr/jdk64/jdk1.8.0_77 ; 
> /usr/lib/ambari-logsearch-solr-client/solrCloudCli.sh -z 
> os-d7-unsecure-atlas-3.openstacklocal:2181,os-d7-unsecure-atlas-1.openstacklocal:2181/ambari-solr
>  --upload-config -d 
> /usr/lib/ambari-logsearch-solr/server/solr/configsets/basic_configs/conf -cs 
> basic_configs -rt 5 -i 10' returned 1. log4j:ERROR setFile(null,true) call 
> failed.
> java.io.FileNotFoundException:  (No such file or directory)
>   at java.io.FileOutputStream.open0(Native Method)
>   at java.io.FileOutputStream.open(FileOutputStream.java:270)
>   at java.io.FileOutputStream.(FileOutputStream.java:213)
>   at java.io.FileOutputStream.(FileOutputStream.java:133)
>   at org.apache.log4j.FileAppender.setFile(FileAppender.java:294)
>   at 
> org.apache.log4j.RollingFileAppender.setFile(RollingFileAppender.java:207)
>   at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165)
>   at 
> org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307)
>   at 
> org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:172)
>   at 
> org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:104)
>   at 
> org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:842)
>   at 
> org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:768)
>   at 
> org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:648)
>   at 
> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:514)
>   at 
> 

[jira] [Resolved] (AMBARI-17167) Atlas Integration : Excessive logs: default log level should be set to 'info'; currently it is 'debug'

[Jayush Luniya (JIRA)]

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

Jayush Luniya resolved AMBARI-17167.

Resolution: Duplicate

> Atlas Integration : Excessive logs: default log level should be set to 
> 'info'; currently it is 'debug'
> --
>
> Key: AMBARI-17167
> URL: https://issues.apache.org/jira/browse/AMBARI-17167
> Project: Ambari
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
>




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

[jira] [Updated] (AMBARI-17166) Atlas Integration : HBase table name 'titan' to be configurable via Atlas properties

[Jayush Luniya (JIRA)]

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

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

> Atlas Integration : HBase table name 'titan' to be configurable via Atlas 
> properties
> 
>
> Key: AMBARI-17166
> URL: https://issues.apache.org/jira/browse/AMBARI-17166
> Project: Ambari
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Attachments: AMBARI-17166.patch
>
>
> Currently Atlas Hbase table name is 'titan' and there is no option to 
> configure the table name.
> We can add a property in Atlas advanced configuration on Ambari UI to specify 
> the table name.
> The following property in atlas-application.properties allows us to configure 
> Hbase table name
> atlas.graph.storage.hbase.table : "atlas_titan"



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

[jira] [Reopened] (AMBARI-17167) Atlas Integration : Excessive logs: default log level should be set to 'info'; currently it is 'debug'

[Jayush Luniya (JIRA)]

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

Jayush Luniya reopened AMBARI-17167:


> Atlas Integration : Excessive logs: default log level should be set to 
> 'info'; currently it is 'debug'
> --
>
> Key: AMBARI-17167
> URL: https://issues.apache.org/jira/browse/AMBARI-17167
> Project: Ambari
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
>




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

[jira] [Updated] (AMBARI-17203) Atlas Integration : ATLAS conf dir needs to be present in all ATLAS hook deployed hosts

[Jayush Luniya (JIRA)]

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

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

> Atlas Integration : ATLAS conf dir needs to be present in all ATLAS hook 
> deployed hosts
> ---
>
> Key: AMBARI-17203
> URL: https://issues.apache.org/jira/browse/AMBARI-17203
> Project: Ambari
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Attachments: AMBARI-17203.patch
>
>
> Atlas atlas-application.properties configuration is required by the Atlas 
> hooks (Falcon, Storm, Sqoop and Hive).
> Currently the atlas configuration is not being pushed to all the hook hosts 
> which could lead to issues if any config is changed. The Atlas configuration 
> changes needs to be pushed to all dependent hosts.



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

[jira] [Updated] (AMBARI-17031) Atlas Integration : Deploying HA Blueprint with Atlas does not work

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-17031:
---
Attachment: AMBARI-17031-2.patch

> Atlas Integration : Deploying HA Blueprint with Atlas does not work
> ---
>
> Key: AMBARI-17031
> URL: https://issues.apache.org/jira/browse/AMBARI-17031
> Project: Ambari
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Attachments: AMBARI-17031-2.patch
>
>
> When deploying a blueprint that specified ha enabled 
> (atlas.server.ha.enabled=true), the atlas.server.address.id1, 
> atlas.server.address.id2 (etc) needs to be replaced with the hostnames for 
> the host group. This does not occur today, instead the 
> atlas.server.address.id1 is tokenized with (for example): 
> atlas.server.host.id1: "server_hosts", which is not quite correct. I believe 
> the blueprint runtime generator needs to create the proper entries with a 
> different token that is replaced with each host where Atlas server is 
> deployed.



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

[jira] [Updated] (AMBARI-17098) Atlas Integration : Ambari overwrites users-credentials.properties and policy-store.txt

[Jayush Luniya (JIRA)]

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

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

> Atlas Integration : Ambari overwrites users-credentials.properties and 
> policy-store.txt
> ---
>
> Key: AMBARI-17098
> URL: https://issues.apache.org/jira/browse/AMBARI-17098
> Project: Ambari
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Attachments: AMBARI-17098.patch
>
>
> The Atlas users-credentials.properties and policy-store.txt are managed by 
> Ambari but can not be changed.  Ambari overwrites any changes when the Atlas 
> server is restarted.
> Make the files un-managed by Ambari so that they can be edited and will pick 
> up the latest changes from the Atlas distro on installation.



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

[jira] [Updated] (AMBARI-16932) Atlas server start failed after Ambari upgrade due to missing solrCloudCli.sh script

[Jayush Luniya (JIRA)]

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

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

> Atlas server start failed after Ambari upgrade due to missing solrCloudCli.sh 
> script
> 
>
> Key: AMBARI-16932
> URL: https://issues.apache.org/jira/browse/AMBARI-16932
> Project: Ambari
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Attachments: AMBARI-16932.patch
>
>
> *Steps*
> # Deploy HDP-2.4.2.0 cluster with Ambari 2.2.2.0 (including Atlas)
> # Upgrade Ambari to 2.4.0.0
> # Stop and start all services
> *Result*
> Atlas Metadata server start fails with below error:
> {code}
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py",
>  line 165, in 
> MetadataServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 257, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py",
>  line 67, in start
> self.configure(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py",
>  line 51, in configure
> metadata()
>   File 
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata.py",
>  line 113, in metadata
> upload_conf_set('basic_configs', random_num)
>   File 
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata.py",
>  line 135, in upload_conf_set
> group=params.user_group)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/solr_cloud_util.py",
>  line 48, in upload_configuration_to_zk
> group=group
>   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/core/providers/system.py",
>  line 273, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 70, in inner
> result = function(command, **kwargs)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
> line 293, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'export 
> JAVA_HOME=/usr/jdk64/jdk1.7.0_67 ; 
> /usr/lib/ambari-logsearch-solr-client/solrCloudCli.sh -z 
> os-r6-tgvuks-dgm10toeriedwngdha-r6-4.openstacklocal:2181,os-r6-tgvuks-dgm10toeriedwngdha-r6-3.openstacklocal:2181,os-r6-tgvuks-dgm10toeriedwngdha-r6-2.openstacklocal:2181None
>  --upload-config -d 
> /usr/lib/ambari-logsearch-solr/server/solr/configsets/basic_configs/conf -cs 
> basic_configs -rt 5 -i 10' returned 127. -bash: 
> /usr/lib/ambari-logsearch-solr-client/solrCloudCli.sh: No such file or 
> directory
> {code}



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

[jira] [Updated] (AMBARI-18653) Allow MASTER service install to be optional

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-18653:
---
Fix Version/s: 2.5.0

> Allow MASTER service install to be optional 
> 
>
> Key: AMBARI-18653
> URL: https://issues.apache.org/jira/browse/AMBARI-18653
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: 2.4.0
>Reporter: David M. Lyle
>Assignee: Jaimin D Jetly
> Fix For: 2.5.0
>
>
> Hive has logic that allows the MySQL to be installed optionally. Please 
> relocate that logic so other Master services can be optional as well.



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

[jira] [Updated] (AMBARI-18653) Allow MASTER service install to be optional

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-18653:
---
Assignee: Jaimin D Jetly

> Allow MASTER service install to be optional 
> 
>
> Key: AMBARI-18653
> URL: https://issues.apache.org/jira/browse/AMBARI-18653
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: 2.4.0
>Reporter: David M. Lyle
>Assignee: Jaimin D Jetly
>
> Hive has logic that allows the MySQL to be installed optionally. Please 
> relocate that logic so other Master services can be optional as well.



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

[jira] [Updated] (AMBARI-17867) Fix xml KERBEROS/1.10.3-10/configuration/kerberos-env.xml

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-17867:
---
Attachment: rb50373.patch

> Fix xml KERBEROS/1.10.3-10/configuration/kerberos-env.xml
> -
>
> Key: AMBARI-17867
> URL: https://issues.apache.org/jira/browse/AMBARI-17867
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Ajit Kumar
>Assignee: Ajit Kumar
> Fix For: 2.4.0
>
> Attachments: rb50373.patch
>
>
> Fix KERBEROS/1.10.3-10/configuration/kerberos-env.xml which has bad xml 
> element "host" at line number 89. This is breaking build 
> https://builds.apache.org/job/Ambari-trunk-Commit/5372
> Unit test failing:
> org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs



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

[jira] [Updated] (AMBARI-16145) Add dryrun API for host delete

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-16145:
---
Attachment: rb46750.patch

> Add dryrun API for host delete 
> ---
>
> Key: AMBARI-16145
> URL: https://issues.apache.org/jira/browse/AMBARI-16145
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Ajit Kumar
>Assignee: Ajit Kumar
> Fix For: 2.4.0
>
> Attachments: rb46750.patch
>
>
> Add dryrun API for host delete 
> API should be take dry_run directive and check if requested host can be 
> deleted w/o deleting the host and should return error if any, like host is 
> not in delete friendly state.
> {code}
> curl -i -X DELETE -u admin:admin -H 'X-Requested-By:ambari' 
> 'http://localhost:8080/api/v1/clusters/c1/hosts?dry_run=true/host_name=c6401.ambari.apache.org'
> {code}
> It should also support bulk delete format



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

[jira] [Updated] (AMBARI-15847) Add api for bulk delete host

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-15847:
---
Attachment: rb43927.patch

> Add api for bulk delete host
> 
>
> Key: AMBARI-15847
> URL: https://issues.apache.org/jira/browse/AMBARI-15847
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Ajit Kumar
>Assignee: Ajit Kumar
> Fix For: 2.4.0
>
> Attachments: rb43927.patch
>
>
> Currently if anyone has to delete more than 1 host, a script is required to 
> call delete host api in a loop for each host. This api takes in query and 
> instead of failing fast on the first error, puts the best effort to delete 
> all requested hosts. Response should be json object which has deleted keys 
> and keys which failed to delete with exception. 



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

[jira] [Resolved] (AMBARI-17020) Use 'llapstatus' comand after starting llap to check its status before starting HiveServer2

[Jayush Luniya (JIRA)]

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

Jayush Luniya resolved AMBARI-17020.

Resolution: Duplicate

> Use 'llapstatus' comand after starting llap to check its status before 
> starting HiveServer2
> ---
>
> Key: AMBARI-17020
> URL: https://issues.apache.org/jira/browse/AMBARI-17020
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
>
> - Right now, after starting llap app, we wait for 30 secs before starting 
> hive2/HiveServer2.
> - Need to have status check via 'llapstatus' command and start 
> hive2/HiveServer2 only if llap app deployment was a success.
> eg: llapstatus command:
> {code}
> hive2/bin/hive --service llapstatus --name 
> {code}



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

[jira] [Resolved] (AMBARI-16087) LLAP queue is not selected when enabling Hive Interactive Query during Install Wizard

[Jayush Luniya (JIRA)]

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

Jayush Luniya resolved AMBARI-16087.

Resolution: Duplicate

> LLAP queue is not selected when enabling Hive Interactive Query during 
> Install Wizard
> -
>
> Key: AMBARI-16087
> URL: https://issues.apache.org/jira/browse/AMBARI-16087
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
>




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

[jira] [Reopened] (AMBARI-16079) Wait for fixed number of times if the launched LLAP app is in "LAUNCHING" state to go to "RUNNING_ALL" or "RUNNING_PARTIAL"

[Jayush Luniya (JIRA)]

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

Jayush Luniya reopened AMBARI-16079:


> Wait for fixed number of times if the launched LLAP app is in "LAUNCHING" 
> state to go to "RUNNING_ALL" or "RUNNING_PARTIAL"
> ---
>
> Key: AMBARI-16079
> URL: https://issues.apache.org/jira/browse/AMBARI-16079
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
>
> - Wait for fixed number of times if the launched LLAP app is in "LAUNCHING" 
> state to go to "RUNNING_ALL" or "RUNNING_PARTIAL"



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

[jira] [Reopened] (AMBARI-16087) LLAP queue is not selected when enabling Hive Interactive Query during Install Wizard

[Jayush Luniya (JIRA)]

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

Jayush Luniya reopened AMBARI-16087:


> LLAP queue is not selected when enabling Hive Interactive Query during 
> Install Wizard
> -
>
> Key: AMBARI-16087
> URL: https://issues.apache.org/jira/browse/AMBARI-16087
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
>




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

[jira] [Resolved] (AMBARI-16079) Wait for fixed number of times if the launched LLAP app is in "LAUNCHING" state to go to "RUNNING_ALL" or "RUNNING_PARTIAL"

[Jayush Luniya (JIRA)]

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

Jayush Luniya resolved AMBARI-16079.

Resolution: Duplicate

> Wait for fixed number of times if the launched LLAP app is in "LAUNCHING" 
> state to go to "RUNNING_ALL" or "RUNNING_PARTIAL"
> ---
>
> Key: AMBARI-16079
> URL: https://issues.apache.org/jira/browse/AMBARI-16079
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
>
> - Wait for fixed number of times if the launched LLAP app is in "LAUNCHING" 
> state to go to "RUNNING_ALL" or "RUNNING_PARTIAL"



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

[jira] [Resolved] (AMBARI-16086) Hide 'llap' queue capacity slider when 'llap' queue is not being used for LLAP app

[Jayush Luniya (JIRA)]

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

Jayush Luniya resolved AMBARI-16086.

Resolution: Duplicate

> Hide 'llap' queue capacity slider when 'llap' queue is not being used for 
> LLAP app
> --
>
> Key: AMBARI-16086
> URL: https://issues.apache.org/jira/browse/AMBARI-16086
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
>




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

[jira] [Reopened] (AMBARI-16086) Hide 'llap' queue capacity slider when 'llap' queue is not being used for LLAP app

[Jayush Luniya (JIRA)]

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

Jayush Luniya reopened AMBARI-16086:


> Hide 'llap' queue capacity slider when 'llap' queue is not being used for 
> LLAP app
> --
>
> Key: AMBARI-16086
> URL: https://issues.apache.org/jira/browse/AMBARI-16086
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
>




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

[jira] [Reopened] (AMBARI-17327) Default value missing for "Memory Per Daemon" config parameter in install wizard[Hive>Advanced-hive-interactive-site group]

[Jayush Luniya (JIRA)]

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

Jayush Luniya reopened AMBARI-17327:


> Default value missing for "Memory Per Daemon" config parameter in install 
> wizard[Hive>Advanced-hive-interactive-site group] 
> 
>
> Key: AMBARI-17327
> URL: https://issues.apache.org/jira/browse/AMBARI-17327
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
> Environment: OS: CentOS6
>Reporter: Kishor Ramakrishnan
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
>
> Default value missing for "Memory Per Daemon" config parameter in install 
> wizard[Hive>Advanced-hive-interactive-site group] 
> Config-name : Memory Per Daemon
> Config group : Advanced-hive-interactive-site



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

[jira] [Resolved] (AMBARI-17327) Default value missing for "Memory Per Daemon" config parameter in install wizard[Hive>Advanced-hive-interactive-site group]

[Jayush Luniya (JIRA)]

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

Jayush Luniya resolved AMBARI-17327.

Resolution: Duplicate

> Default value missing for "Memory Per Daemon" config parameter in install 
> wizard[Hive>Advanced-hive-interactive-site group] 
> 
>
> Key: AMBARI-17327
> URL: https://issues.apache.org/jira/browse/AMBARI-17327
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
> Environment: OS: CentOS6
>Reporter: Kishor Ramakrishnan
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
>
> Default value missing for "Memory Per Daemon" config parameter in install 
> wizard[Hive>Advanced-hive-interactive-site group] 
> Config-name : Memory Per Daemon
> Config group : Advanced-hive-interactive-site



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

[jira] [Updated] (AMBARI-17242) Atlas Integration : atlas.authentication.principal should be set to atlas/_h...@example.com

[Jayush Luniya (JIRA)]

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

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

> Atlas Integration : atlas.authentication.principal should be set to 
> atlas/_h...@example.com
> ---
>
> Key: AMBARI-17242
> URL: https://issues.apache.org/jira/browse/AMBARI-17242
> Project: Ambari
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Attachments: AMBARI-17242.patch
>
>
> In a kerberized env, the value of atlas.authentication.principal should be 
> set to atlas/_h...@example.com. Currently the value is set to atlas which 
> causes Atlas server startup to fail.
> {code}
> 
>  (Atlas:194)
> 2016-06-11 01:51:27,820 INFO  - [main:] ~ > 
> (Atlas:195)
> 2016-06-11 01:51:27,820 INFO  - [main:] ~ Server starting with TLS ? false on 
> port 21000 (Atlas:196)
> 2016-06-11 01:51:27,820 INFO  - [main:] ~ < 
> (Atlas:197)
> 2016-06-11 01:51:27,885 INFO  - [main:] ~ Logging initialized @1201ms 
> (log:186)
> 2016-06-11 01:51:28,005 INFO  - [main:] ~ jetty-9.2.12.v20150709 (Server:327)
> 2016-06-11 01:51:29,022 INFO  - [main:] ~ Loading Guice modules 
> (GuiceServletConfig:65)
> 2016-06-11 01:51:29,199 WARN  - [main:] ~ Failed startup of context 
> o.e.j.w.WebAppContext@14cd1699{/,file:/usr/hdp/2.5.0.0-717/atlas/server/webapp/atlas/,STARTING}{/usr/hdp/current/atlas-server/server/webapp/atlas}
>  (WebAppContext:514)
> java.lang.IllegalStateException: Unable to perform KERBEROS login.
> at 
> org.apache.atlas.web.listeners.LoginProcessor.doServiceLogin(LoginProcessor.java:79)
> at 
> org.apache.atlas.web.listeners.LoginProcessor.login(LoginProcessor.java:58)
> at 
> org.apache.atlas.web.listeners.GuiceServletConfig.getInjector(GuiceServletConfig.java:76)
> at 
> com.google.inject.servlet.GuiceServletContextListener.contextInitialized(GuiceServletContextListener.java:47)
> at 
> org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:132)
> at 
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
> at 
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
> at 
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
> at 
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
> at 
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
> at 
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
> at 
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
> at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
> at org.eclipse.jetty.server.Server.start(Server.java:387)
> at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
> at 
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
> at org.eclipse.jetty.server.Server.doStart(Server.java:354)
> at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at 
> org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:93)
> at org.apache.atlas.Atlas.main(Atlas.java:113)
> Caused by: java.io.IOException: Login failure for atlas from keytab 
> /etc/security/keytabs/atlas.service.keytab: 
> javax.security.auth.login.LoginException: Unable to obtain password from user
>  
> at 
> org.apache.hadoop.security.UserGroupInformation.loginUserFromKeytab(UserGroupInformation.java:987)
> at 
> org.apache.atlas.web.listeners.LoginProcessor.doServiceLogin(LoginProcessor.java:73)
> ... 21 more
> Caused by: javax.security.auth.login.LoginException: Unable to obtain 
> password from user
>  
> at 
> com.sun.security.auth.module.Krb5LoginModule.promptForPass(Krb5LoginModule.java:897)
> at 
> com.sun.security.auth.module.Krb5LoginModule.attemptAuthentication(Krb5LoginModule.java:760)
>

[jira] [Updated] (AMBARI-16722) Change 'Number of LLAP Daemons', 'In-Memory Cache per Daemon', 'Maximum CPUs per Daemon' to be a 'Text Box' and 'YARN Memory per Daemon' to be a 'Label' instead of 'Sli

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-16722:
---
Attachment: AMBARI-16720.patch

> Change 'Number of LLAP Daemons', 'In-Memory Cache per Daemon', 'Maximum CPUs 
> per Daemon' to be a 'Text Box' and 'YARN Memory per Daemon' to be a 'Label' 
> instead of 'Slider'.
> -
>
> Key: AMBARI-16722
> URL: https://issues.apache.org/jira/browse/AMBARI-16722
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16720.patch
>
>




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

[jira] [Updated] (AMBARI-15873) Ambari-Server Unit Test failures in trunk

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-15873:
---
Labels: reverted  (was: )

> Ambari-Server Unit Test failures in trunk
> -
>
> Key: AMBARI-15873
> URL: https://issues.apache.org/jira/browse/AMBARI-15873
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Blocker
>  Labels: reverted
> Fix For: 2.4.0
>
>
> Unit test failure in ambari-server in trunk
> https://builds.apache.org/job/Ambari-trunk-Commit/4650/console
> Results :
> Failed tests: 
>   UpgradeCatalog240Test.testExecuteDDLUpdates:227 
>   Unexpected method call DBAccessor.addColumn("viewinstanceentity", 
> org.apache.ambari.server.orm.DBAccessor$DBColumnInfo@1a3492):
> DBAccessor.addColumn("host_role_command", 
> capture(org.apache.ambari.server.orm.DBAccessor$DBColumnInfo@1fbce70)): 
> expected: 1, actual: 1
> Tests run: 4225, Failures: 1, Errors: 0, Skipped: 32



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

[jira] [Resolved] (AMBARI-15873) Ambari-Server Unit Test failures in trunk

[Jayush Luniya (JIRA)]

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

Jayush Luniya resolved AMBARI-15873.

Resolution: Fixed

> Ambari-Server Unit Test failures in trunk
> -
>
> Key: AMBARI-15873
> URL: https://issues.apache.org/jira/browse/AMBARI-15873
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Blocker
> Fix For: 2.4.0
>
>
> Unit test failure in ambari-server in trunk
> https://builds.apache.org/job/Ambari-trunk-Commit/4650/console
> Results :
> Failed tests: 
>   UpgradeCatalog240Test.testExecuteDDLUpdates:227 
>   Unexpected method call DBAccessor.addColumn("viewinstanceentity", 
> org.apache.ambari.server.orm.DBAccessor$DBColumnInfo@1a3492):
> DBAccessor.addColumn("host_role_command", 
> capture(org.apache.ambari.server.orm.DBAccessor$DBColumnInfo@1fbce70)): 
> expected: 1, actual: 1
> Tests run: 4225, Failures: 1, Errors: 0, Skipped: 32



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

[jira] [Reopened] (AMBARI-15873) Ambari-Server Unit Test failures in trunk

[Jayush Luniya (JIRA)]

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

Jayush Luniya reopened AMBARI-15873:


> Ambari-Server Unit Test failures in trunk
> -
>
> Key: AMBARI-15873
> URL: https://issues.apache.org/jira/browse/AMBARI-15873
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Blocker
> Fix For: 2.4.0
>
>
> Unit test failure in ambari-server in trunk
> https://builds.apache.org/job/Ambari-trunk-Commit/4650/console
> Results :
> Failed tests: 
>   UpgradeCatalog240Test.testExecuteDDLUpdates:227 
>   Unexpected method call DBAccessor.addColumn("viewinstanceentity", 
> org.apache.ambari.server.orm.DBAccessor$DBColumnInfo@1a3492):
> DBAccessor.addColumn("host_role_command", 
> capture(org.apache.ambari.server.orm.DBAccessor$DBColumnInfo@1fbce70)): 
> expected: 1, actual: 1
> Tests run: 4225, Failures: 1, Errors: 0, Skipped: 32



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

[jira] [Updated] (AMBARI-17961) Create common-services/KAFKA/0.10.0 service definition

[Jayush Luniya (JIRA)]

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

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

> Create common-services/KAFKA/0.10.0 service definition
> --
>
> Key: AMBARI-17961
> URL: https://issues.apache.org/jira/browse/AMBARI-17961
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: trunk
>
> Attachments: AMBARI-17961.patch
>
>
> As per RR: https://reviews.apache.org/r/50445/ comment. Need to create new 
> common version for KAFKA service



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

[jira] [Reopened] (AMBARI-15660) Add Install Management Packs option (ambari-server install-mpack)

[Jayush Luniya (JIRA)]

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

Jayush Luniya reopened AMBARI-15660:


> Add Install Management Packs option (ambari-server install-mpack)
> -
>
> Key: AMBARI-15660
> URL: https://issues.apache.org/jira/browse/AMBARI-15660
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.4.0
>
>




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

[jira] [Resolved] (AMBARI-15661) Add Upgrade Management Pack option (ambari-server upgrade-mpack)

[Jayush Luniya (JIRA)]

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

Jayush Luniya resolved AMBARI-15661.

Resolution: Duplicate

> Add Upgrade Management Pack option (ambari-server upgrade-mpack)
> 
>
> Key: AMBARI-15661
> URL: https://issues.apache.org/jira/browse/AMBARI-15661
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.4.0
>
>




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

[jira] [Reopened] (AMBARI-15661) Add Upgrade Management Pack option (ambari-server upgrade-mpack)

[Jayush Luniya (JIRA)]

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

Jayush Luniya reopened AMBARI-15661:


> Add Upgrade Management Pack option (ambari-server upgrade-mpack)
> 
>
> Key: AMBARI-15661
> URL: https://issues.apache.org/jira/browse/AMBARI-15661
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.4.0
>
>




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

[jira] [Updated] (AMBARI-15699) Remove hdp specific hardcodings from common-services configs

[Jayush Luniya (JIRA)]

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

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

> Remove hdp specific hardcodings from common-services configs
> 
>
> Key: AMBARI-15699
> URL: https://issues.apache.org/jira/browse/AMBARI-15699
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.4.0
>
> Attachments: AMBARI-15699.patch
>
>
> Remove HDP specific config properties from common-services



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

[jira] [Updated] (AMBARI-16668) Create RANGER service versions in common-services

[Jayush Luniya (JIRA)]

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

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

> Create RANGER service versions in common-services
> -
>
> Key: AMBARI-16668
> URL: https://issues.apache.org/jira/browse/AMBARI-16668
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.4.0
>
> Attachments: AMBARI-16668.patch
>
>
> Create common-services/STORM/0.9.1 common-services/SOTRM/0.9.3 and 
> common-services/SOTRM/0.10.0 service versions and update HDP stack 
> inheritance to extend these service definitions



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

[jira] [Updated] (AMBARI-17357) Add wiki on management packs

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-17357:
---
Issue Type: Documentation  (was: Task)

> Add wiki on management packs
> 
>
> Key: AMBARI-17357
> URL: https://issues.apache.org/jira/browse/AMBARI-17357
> Project: Ambari
>  Issue Type: Documentation
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.4.0
>
>




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

[jira] [Updated] (AMBARI-17612) Update setup_ranger_plugin_xml for NiFI

[Jayush Luniya (JIRA)]

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

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

> Update setup_ranger_plugin_xml for NiFI
> ---
>
> Key: AMBARI-17612
> URL: https://issues.apache.org/jira/browse/AMBARI-17612
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17612.patch
>
>
> We need to update setup_ranger_plugin_xml to special case credentials library 
> and ranger_credential_helper.py paths for NIFI service.



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

[jira] [Updated] (AMBARI-18637) Management pack purge option should warn user and ask for confirmation before purging

[Jayush Luniya (JIRA)]

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

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

> Management pack purge option should warn user and ask for confirmation before 
> purging
> -
>
> Key: AMBARI-18637
> URL: https://issues.apache.org/jira/browse/AMBARI-18637
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.4.2
>
> Attachments: AMBARI-18637.patch
>
>




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

[jira] [Updated] (AMBARI-18637) Management pack purge option should warn user and ask for confirmation before purging

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-18637:
---
Attachment: (was: AMBARI-18637.patch)

> Management pack purge option should warn user and ask for confirmation before 
> purging
> -
>
> Key: AMBARI-18637
> URL: https://issues.apache.org/jira/browse/AMBARI-18637
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.4.2
>
> Attachments: AMBARI-18637.patch
>
>




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

[jira] [Updated] (AMBARI-18637) Management pack purge option should warn user and ask for confirmation before purging

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-18637:
---
Status: Patch Available  (was: In Progress)

> Management pack purge option should warn user and ask for confirmation before 
> purging
> -
>
> Key: AMBARI-18637
> URL: https://issues.apache.org/jira/browse/AMBARI-18637
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.4.2
>
> Attachments: AMBARI-18637.patch
>
>




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

[jira] [Updated] (AMBARI-18637) Management pack purge option should warn user and ask for confirmation before purging

[Jayush Luniya (JIRA)]

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

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

> Management pack purge option should warn user and ask for confirmation before 
> purging
> -
>
> Key: AMBARI-18637
> URL: https://issues.apache.org/jira/browse/AMBARI-18637
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.4.2
>
> Attachments: AMBARI-18637.patch
>
>




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

[jira] [Updated] (AMBARI-18637) Management pack purge option should warn user and ask for confirmation before purging

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-18637:
---
Status: Patch Available  (was: In Progress)

> Management pack purge option should warn user and ask for confirmation before 
> purging
> -
>
> Key: AMBARI-18637
> URL: https://issues.apache.org/jira/browse/AMBARI-18637
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.4.2
>
> Attachments: AMBARI-18637.patch
>
>




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

[jira] [Updated] (AMBARI-18637) Management pack purge option should warn user and ask for confirmation before purging

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-18637:
---
Attachment: (was: AMBARI-18637.patch)

> Management pack purge option should warn user and ask for confirmation before 
> purging
> -
>
> Key: AMBARI-18637
> URL: https://issues.apache.org/jira/browse/AMBARI-18637
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.4.2
>
>




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

[jira] [Updated] (AMBARI-18637) Management pack purge option should warn user and ask for confirmation before purging

[Jayush Luniya (JIRA)]

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

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

> Management pack purge option should warn user and ask for confirmation before 
> purging
> -
>
> Key: AMBARI-18637
> URL: https://issues.apache.org/jira/browse/AMBARI-18637
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.4.2
>
> Attachments: AMBARI-18637.patch
>
>




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

[jira] [Created] (AMBARI-18637) Management pack purge option should warn user and ask for confirmation before purging

[Jayush Luniya (JIRA)]

Jayush Luniya created AMBARI-18637:
--

 Summary: Management pack purge option should warn user and ask for 
confirmation before purging
 Key: AMBARI-18637
 URL: https://issues.apache.org/jira/browse/AMBARI-18637
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.0
Reporter: Jayush Luniya
Assignee: Jayush Luniya
 Fix For: 2.4.2






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

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

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-18613:


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

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

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



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

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

[Jayush Luniya (JIRA)]

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

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

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



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

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

[Jayush Luniya (JIRA)]

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

Jayush Luniya resolved AMBARI-18385.

Resolution: Fixed

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



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

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

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-18613:


[~sumitmohanty] can you review the patch?

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



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

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

[Jayush Luniya (JIRA)]

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

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

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



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

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

[Jayush Luniya (JIRA)]

Jayush Luniya created AMBARI-18613:
--

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


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



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

[jira] [Updated] (AMBARI-18461) NiFi CA Config Files printed to ambari log

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-18461:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> NiFi CA Config Files printed to ambari log
> --
>
> Key: AMBARI-18461
> URL: https://issues.apache.org/jira/browse/AMBARI-18461
> Project: Ambari
>  Issue Type: Bug
>  Components: contrib
>Affects Versions: trunk
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18461.patch
>
>
> NiFi CA client and server json files are printed to the ambari log when they 
> are created. They have sensitive information so this should be fixed



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

[jira] [Comment Edited] (AMBARI-18461) NiFi CA Config Files printed to ambari log

[Jayush Luniya (JIRA)]

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

Jayush Luniya edited comment on AMBARI-18461 at 9/24/16 2:56 AM:
-

Yes if you wrap a string around it it will be logged as [PROTECTED].

2016-09-24 02:27:28,523 - 
File['/usr/hdf/2.0.0.0-579/nifi/conf/nifi-certificate-authority.json'] 
{'content': [PROTECTED], 'owner': 'nifi', 'group': 'nifi', 'mode': 0600}


was (Author: jluniya):
Yes if you wrap a string around it it will be logged as [PROTECTED].

> NiFi CA Config Files printed to ambari log
> --
>
> Key: AMBARI-18461
> URL: https://issues.apache.org/jira/browse/AMBARI-18461
> Project: Ambari
>  Issue Type: Bug
>  Components: contrib
>Affects Versions: trunk
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18461.patch
>
>
> NiFi CA client and server json files are printed to the ambari log when they 
> are created. They have sensitive information so this should be fixed



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

[jira] [Commented] (AMBARI-18461) NiFi CA Config Files printed to ambari log

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-18461:


commit 1fee5ed34c6c41c40b550b5961e8b37aef0599d1
Author: Jayush Luniya 
Date:   Fri Sep 23 19:56:53 2016 -0700

AMBARI-18461: NiFi CA Config Files printed to ambari log (jluniya)

> NiFi CA Config Files printed to ambari log
> --
>
> Key: AMBARI-18461
> URL: https://issues.apache.org/jira/browse/AMBARI-18461
> Project: Ambari
>  Issue Type: Bug
>  Components: contrib
>Affects Versions: trunk
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18461.patch
>
>
> NiFi CA client and server json files are printed to the ambari log when they 
> are created. They have sensitive information so this should be fixed



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

[jira] [Comment Edited] (AMBARI-18461) NiFi CA Config Files printed to ambari log

[Jayush Luniya (JIRA)]

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

Jayush Luniya edited comment on AMBARI-18461 at 9/24/16 2:56 AM:
-

Yes if you wrap a string around it it will be logged as [PROTECTED].


was (Author: jluniya):
Yes if you wrap a string around it it will not be logged.

> NiFi CA Config Files printed to ambari log
> --
>
> Key: AMBARI-18461
> URL: https://issues.apache.org/jira/browse/AMBARI-18461
> Project: Ambari
>  Issue Type: Bug
>  Components: contrib
>Affects Versions: trunk
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18461.patch
>
>
> NiFi CA client and server json files are printed to the ambari log when they 
> are created. They have sensitive information so this should be fixed



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

[jira] [Commented] (AMBARI-18461) NiFi CA Config Files printed to ambari log

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-18461:


Yes if you wrap a string around it it will not be logged.

> NiFi CA Config Files printed to ambari log
> --
>
> Key: AMBARI-18461
> URL: https://issues.apache.org/jira/browse/AMBARI-18461
> Project: Ambari
>  Issue Type: Bug
>  Components: contrib
>Affects Versions: trunk
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18461.patch
>
>
> NiFi CA client and server json files are printed to the ambari log when they 
> are created. They have sensitive information so this should be fixed



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

[jira] [Updated] (AMBARI-18461) NiFi CA Config Files printed to ambari log

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-18461:
---
Status: Patch Available  (was: In Progress)

> NiFi CA Config Files printed to ambari log
> --
>
> Key: AMBARI-18461
> URL: https://issues.apache.org/jira/browse/AMBARI-18461
> Project: Ambari
>  Issue Type: Bug
>  Components: contrib
>Affects Versions: trunk
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18461.patch
>
>
> NiFi CA client and server json files are printed to the ambari log when they 
> are created. They have sensitive information so this should be fixed



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

[jira] [Commented] (AMBARI-18461) NiFi CA Config Files printed to ambari log

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-18461:


[~sumitmohanty] can you review this patch?

> NiFi CA Config Files printed to ambari log
> --
>
> Key: AMBARI-18461
> URL: https://issues.apache.org/jira/browse/AMBARI-18461
> Project: Ambari
>  Issue Type: Bug
>  Components: contrib
>Affects Versions: trunk
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18461.patch
>
>
> NiFi CA client and server json files are printed to the ambari log when they 
> are created. They have sensitive information so this should be fixed



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

[jira] [Updated] (AMBARI-18461) NiFi CA Config Files printed to ambari log

[Jayush Luniya (JIRA)]

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

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

> NiFi CA Config Files printed to ambari log
> --
>
> Key: AMBARI-18461
> URL: https://issues.apache.org/jira/browse/AMBARI-18461
> Project: Ambari
>  Issue Type: Bug
>  Components: contrib
>Affects Versions: trunk
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18461.patch
>
>
> NiFi CA client and server json files are printed to the ambari log when they 
> are created. They have sensitive information so this should be fixed



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

[jira] [Created] (AMBARI-18461) NiFi CA Config Files printed to ambari log

[Jayush Luniya (JIRA)]

Jayush Luniya created AMBARI-18461:
--

 Summary: NiFi CA Config Files printed to ambari log
 Key: AMBARI-18461
 URL: https://issues.apache.org/jira/browse/AMBARI-18461
 Project: Ambari
  Issue Type: Bug
  Components: contrib
Affects Versions: trunk
Reporter: Jayush Luniya
Assignee: Jayush Luniya
Priority: Critical
 Fix For: trunk


NiFi CA client and server json files are printed to the ambari log when they 
are created. They have sensitive information so this should be fixed



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