from:"Mahadev Konar"

Mahadev konar created AMBARI-15296:
--

 Summary: Missing property: 
hive.server2.authentication.kerberos.keytab
 Key: AMBARI-15296
 URL: https://issues.apache.org/jira/browse/AMBARI-15296
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.2.1
Reporter: Mahadev konar
 Fix For: 2.2.2






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

[jira] [Updated] (AMBARI-15296) Missing property: hive.server2.authentication.kerberos.keytab


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

Mahadev konar updated AMBARI-15296:
---
Assignee: Laszlo Puskas

> Missing property: hive.server2.authentication.kerberos.keytab
> -
>
> Key: AMBARI-15296
> URL: https://issues.apache.org/jira/browse/AMBARI-15296
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.2.1
>    Reporter: Mahadev konar
>Assignee: Laszlo Puskas
> Fix For: 2.2.2
>
>




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

[jira] [Created] (AMBARI-15295) HBase RS decommission issue in secure cluster

Mahadev konar created AMBARI-15295:
--

 Summary: HBase RS decommission issue in secure cluster
 Key: AMBARI-15295
 URL: https://issues.apache.org/jira/browse/AMBARI-15295
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.2.1
Reporter: Mahadev konar


rovision a cluster with a blueprint which has HBASE in it and kerberos enabled 
+ config recomm. strategy is stack defaults. Try to execute a hbase RS 
decommission to another node like:
/usr/bin/kinit -kt /etc/security/keytabs/hbase.service.keytab 
hbase/host-10-0-0-95.node.dc1.consul@NODE.DC1.CONSUL; 
/usr/hdp/current/hbase-master/bin/hbase --config 
/usr/hdp/current/hbase-master/conf org.jruby.Main 
/usr/hdp/current/hbase-master/bin/draining_servers.rb add 
host-10-0-0-74.node.dc1.consul
Exception is thrown. Log attached.



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

[jira] [Created] (AMBARI-15294) HBase RegionServer circular decommission

Mahadev konar created AMBARI-15294:
--

 Summary: HBase RegionServer circular decommission
 Key: AMBARI-15294
 URL: https://issues.apache.org/jira/browse/AMBARI-15294
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.2.1
Reporter: Mahadev konar


rovision a cluster with the attached blueprint with more than 2 hosts in the 
host_group_slave_1 host group. Put a few RegionServers to maintenance mode and 
try to decommission one of the RSs. It will try to find valid targets to move 
the data to, but it includes RSs in maintenance mode.
In case of larger number of decommission like 20, it leads to circular data 
movements as RSs which are decommissioning will copy their data to other RSs 
which are also decommissioning.
In the log you can see the selected targets and 80% of them is in maintenance 
mode. 15 nodes decommission 1 RS.




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

[jira] [Updated] (AMBARI-6432) FreeIPA Support in Ambari

2016-02-29 Thread Mahadev konar (JIRA)


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

Mahadev konar updated AMBARI-6432:
--
Fix Version/s: 2.4.0

> FreeIPA Support in Ambari
> -
>
> Key: AMBARI-6432
> URL: https://issues.apache.org/jira/browse/AMBARI-6432
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: jay vyas
> Fix For: 2.4.0
>
> Attachments: AMBARI-6432-FreeIPA.patch, AMBARI-6432.trunk.v1.patch, 
> AMBARI-6432.trunk.v2.patch, ipa-patch-v0.5.patch
>
>
> FreeIPA Is a powerful tool for unifying identity, kerberos credentials, 
> across a cluster.
> A great value add for ambari would be to provide support for using FreeIPA to 
> kerberize services.  This would allow for 
> 1) better HCFS interoperability, because first class GID/UID is critical for 
> certain file systems (GlusterFS, Lustre, and any other file system which uses 
> kernel / FUSE apis for determining identity)
> 2) better enterprise interoperability.  Because of the fact that FreeIPA 
> makes it easy to interop with different identity solutions (like active 
> directory), it would make ambari easier to adopt for various enterprises.
> 3) broadens ambaris scope.  Now ambari could also allow people to setup the 
> users of their clusters, and at least some of the security features of their 
> clusters, all from one interface (no more manual handling of TGTs and such - 
> it could all be done quite easily via the ambari UI which could make calls to 
> underlying FreeIPA clients).



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

Re: Review Request 44064: Unusable configs after creating override

2016-02-26 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/44064/#review120873
---


Ship it!




Ship It!

- Mahadev Konar


On Feb. 26, 2016, 12:29 p.m., Sebastian Toader wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/44064/
> ---
> 
> (Updated Feb. 26, 2016, 12:29 p.m.)
> 
> 
> Review request for Ambari, Daniel Gergely, Robert Levas, and Robert Nettleton.
> 
> 
> Bugs: AMBARI-15200
> https://issues.apache.org/jira/browse/AMBARI-15200
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Ambari server keeps all versions of service configurations. When the UI 
> requests all service configution versions for a service it expects in the 
> response an additional flag that marks which ones are the active ones. Since 
> this active flag is not stored in the database the server works out this flag 
> on demand based on the create time stamp, version of the service config 
> entity.
> 
> As part of AMBARI-15158 a bug has been introduce as it was assumed that there 
> is only one "current" service configuration version per service accross each 
> service configuration group.
> This is wrong assumption as there is always ine "current" service 
> configuration version per each configuration group for a service.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
>  4faee0e 
>   
> ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClusterTest.java
>  4d8e13b 
> 
> Diff: https://reviews.apache.org/r/44064/diff/
> 
> 
> Testing
> ---
> 
> Manual testing: created 3 node cluster and tested the fix with multiple 
> config groups and service configs.
> 
> All ambari server unit tests completed fine (branch-2.2 and 2.2.1-main; trunk)
> 
> 
> Thanks,
> 
> Sebastian Toader
> 
>

[jira] [Updated] (AMBARI-15200) Unusable configs after creating override

2016-02-26 Thread Mahadev konar (JIRA)


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

Mahadev konar updated AMBARI-15200:
---
Fix Version/s: (was: 2.2.1)
   2.2.2

> Unusable configs after creating override
> 
>
> Key: AMBARI-15200
> URL: https://issues.apache.org/jira/browse/AMBARI-15200
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.1
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15200.2.2.1-maint.v1.patch, 
> AMBARI-15200.branch-2.2.v1.patch, AMBARI-15200.trunk.v1.patch
>
>
> After creating override for any service (ZooKeeper for example) configs page 
> for this service becomes unusable: not all configs are loaded and button with 
> empty label is shown.
> The root cause of this issue is that the server API returns wrong is_current 
> flag for default config group after creating an override.



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

[jira] [Commented] (AMBARI-15151) Add PHD-3.4 and above stack definitions in pluggable stack config

2016-02-23 Thread Mahadev konar (JIRA)


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

Mahadev konar commented on AMBARI-15151:


+1 for hte patch.

> Add PHD-3.4 and above stack definitions in pluggable stack config
> -
>
> Key: AMBARI-15151
> URL: https://issues.apache.org/jira/browse/AMBARI-15151
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.1
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15151-2.2.2.patch, AMBARI-15151-trunk.patch
>
>
> PHD-3.4 and above stacks need to be added to PHD.json



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

Re: [VOTE] Apache Ambari 2.2.1 RC2

2016-02-03 Thread Mahadev Konar

+1




On 2/3/16, 9:59 AM, "Jayush Luniya"  wrote:

>+1 for RC2.
>
>On 2/3/16, 6:59 AM, "Nate Cole"  wrote:
>
>>+1 for RC2
>>
>>On 2/1/16, 5:44 PM, "Robert Levas"  wrote:
>>
>>>Team...
>>>
>>>I have created a new ambari-2.2.1 release candidate.
>>>
>>>GIT source tag (release-2.2.1-rc2)
>>>https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=
>>>r
>>>efs/tags/release-2.2.1-rc2
>>>
>>>Staging site: http://people.apache.org/~rlevas/apache-ambari-2.2.1-rc2
>>>
>>>PGP release keys (signed using 0EF56BD9)
>>>http://pgp.mit.edu:11371/pks/lookup?op=vindex=0x0EF56BD9
>>>
>>>One can look into the issues fixed in this release at
>>>https://issues.apache.org/jira/browse/AMBARI/fixforversion/12334307/?sele
>>>c
>>>tedTab=com.atlassian.jira.jira-projects-plugin:version-summary-panel
>>>
>>>Vote will be open for 72 hours.
>>>[ ] +1 approve
>>>[ ] +0 no opinion
>>>[ ] -1 disapprove (and reason why)
>>>
>>>
>>>
>>>Thanks
>>>Rob
>>>
>>>
>>>
>>
>>
>
>

Re: [VOTE] Apache Ambari 2.2.1 RC1

2016-02-01 Thread Mahadev Konar

+1




On 2/1/16, 12:19 PM, "Jayush Luniya"  wrote:

>+1 for RC1.
>
>On 2/1/16, 12:17 PM, "Robert Levas"  wrote:
>
>>+1 for RC1 - signature verified.
>>
>>Rob
>>
>>
>>
>>
>>
>>On 1/27/16, 5:57 PM, "Robert Levas"  wrote:
>>
>>>
>>>Team...
>>>
>>>I have created an ambari-2.2.1 release candidate.
>>>
>>>GIT source tag (release-2.2.1-rc1)
>>>https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=
>>>refs/tags/release-2.2.1-rc1
>>>
>>>Staging site: http://people.apache.org/~rlevas/apache-ambari-2.2.1-rc1
>>>
>>>PGP release keys (signed using 0EF56BD9)
>>>http://pgp.mit.edu:11371/pks/lookup?op=vindex=0x0EF56BD9
>>>
>>>One can look into the issues fixed in this release at
>>>https://issues.apache.org/jira/browse/AMBARI/fixforversion/12334307/?sele
>>>ctedTab=com.atlassian.jira.jira-projects-plugin:version-summary-panel
>>>
>>>Vote will be open for 72 hours.
>>>[ ] +1 approve
>>>[ ] +0 no opinion
>>>[ ] -1 disapprove (and reason why)
>>>
>>>
>>>
>>>Thanks
>>>Rob
>>>
>
>

Re: Review Request 42660: Remove hive.metastore.schema.verification as part of base config properties

2016-01-22 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/42660/#review115877
---

Ship it!


Ship It!

- Mahadev Konar


On Jan. 22, 2016, 5:11 p.m., Nate Cole wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/42660/
> ---
> 
> (Updated Jan. 22, 2016, 5:11 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez and Dmitro Lisnichenko.
> 
> 
> Bugs: BUG-14775
> https://issues.apache.org/jira/browse/BUG-14775
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Remove hive.metastore.schema.verification as base install as this can cause 
> issues with upgrade/downgrade.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/HIVE/configuration/hive-site.xml
>  8866606 
> 
> Diff: https://reviews.apache.org/r/42660/diff/
> 
> 
> Testing
> ---
> 
> Manual testing only.  No automated tests for XML change.
> 
> 
> Thanks,
> 
> Nate Cole
> 
>

[jira] [Reopened] (AMBARI-14718) on region server restart ambari is setting /tmp to hbase:hadoop

2016-01-20 Thread Mahadev konar (JIRA)


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

Mahadev konar reopened AMBARI-14718:


> on region server restart ambari is setting /tmp to hbase:hadoop
> ---
>
> Key: AMBARI-14718
> URL: https://issues.apache.org/jira/browse/AMBARI-14718
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.2.1
>
> Attachments: AMBARI-14718.patch
>
>
> On my hcube cluster what i am seeing is /tmp gets owned by hbase:hadoop. This
> is causing services like sssd to fail as /tmp is not owned by root. sssd is a
> service that we recommend users setup if they want to sync up with AD. With
> this service failing users are unable to login using AD credentials.
> Here is the corresponding log
> 
> 
>   owner = params.hbase_user,
>   group = params.user_group,
> 04:33:56,101 - Directory['/tmp'] {'owner': 'hbase', 'group': 'hadoop', 
> 'mode': 0777, 'recursive': True}
> 2016-01-19 04:33:56,101 - Changing owner for /tmp from 0 to hbase
> 2016-01-19 04:33:56,101 - Changing group for /tmp from 0 to hadoop
> 2016-01-19 04:33:56,102 - Changing permission for /tmp from 1777 to 777
> 2016-01-19 04:33:56,102 - Directory['/tmp'] {'recursive': True, 
> 'cd_access': 'a'}
> 2016-01-19 04:33:56,102 - Execute[('chmod', '1777', u'/tmp')] {'sudo': 
> True}
> 2016-01-19 04:33:56,110 - XmlConfig['hbase-site.xml'] {'owner': 'hbase', 
> 'group': 'hadoop', 'conf_dir': '/usr/hdp/current/hbase-regionserver/conf', 
> 'configuration_attributes': {}, 'configurations': ...}
> 2016-01-19 04:33:56,126 - Generating config: 
> /usr/hdp/current/hbase-regionserver/conf/hbase-site.xml
> 2016-01-19 04:33:56,127 - 
> File['/usr/hdp/current/hbase-regionserver/conf/hbase-site.xml'] {'owner': 
> 'hbase', 'content': InlineTemplate(...), 'group': 'hadoop', 'mode': None, 
> 'encoding': 'UTF-8'}
> 2016-01-19 04:33:56,174 - XmlConfig['core-site.xml'] {'owner': 'hbase', 
> 'group': 'hadoop', 'conf_dir': '/usr/hdp/current/hbase-regionserver/conf', 
> 'configuration_attributes': {}, 'configurations': ...}
> 2016-01-19 04:33:56,185 - Generating config: 
> /usr/hdp/current/hbase-regionserver/conf/core-site.xml
> 2016-01-19 04:33:56,185 - 
> File['/usr/hdp/current/hbase-regionserver/conf/core-site.xml'] {'owner': 
> 'hbase', 'content': InlineTemplate(...), 'group': 'hadoop', 'mode': None, 
> 'encoding': 'UTF-8'}
> 2016-01-19 04:33:56,210 - XmlConfig['hdfs-site.xml'] {'owner': 'hbase', 
> 'group': 'hadoop', 'conf_dir': '/usr/hdp/current/hbase-regionserver/conf', 
> 'configuration_attributes': {}, 'configurations': ...}
> 2016-01-19 04:33:56,221 - Generating config: 
> /usr/hdp/current/hbase-regionserver/conf/hdfs-site.xml
> 2016-01-19 04:33:56,222 - 
> File['/usr/hdp/current/hbase-regionserver/conf/hdfs-site.xml'] {'owner': 'hb
> 
> This is the cluster this happened on
> <https://hcube2-1n01.eng.hortonworks.com:8443> and ssh key for user root is
> attached



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

[jira] [Commented] (AMBARI-14718) on region server restart ambari is setting /tmp to hbase:hadoop

2016-01-20 Thread Mahadev konar (JIRA)


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

Mahadev konar commented on AMBARI-14718:


Reopening since the patch is reverted - looks like this is causing HBase issues.

> on region server restart ambari is setting /tmp to hbase:hadoop
> ---
>
> Key: AMBARI-14718
> URL: https://issues.apache.org/jira/browse/AMBARI-14718
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.2.1
>
> Attachments: AMBARI-14718.patch
>
>
> On my hcube cluster what i am seeing is /tmp gets owned by hbase:hadoop. This
> is causing services like sssd to fail as /tmp is not owned by root. sssd is a
> service that we recommend users setup if they want to sync up with AD. With
> this service failing users are unable to login using AD credentials.
> Here is the corresponding log
> 
> 
>   owner = params.hbase_user,
>   group = params.user_group,
> 04:33:56,101 - Directory['/tmp'] {'owner': 'hbase', 'group': 'hadoop', 
> 'mode': 0777, 'recursive': True}
> 2016-01-19 04:33:56,101 - Changing owner for /tmp from 0 to hbase
> 2016-01-19 04:33:56,101 - Changing group for /tmp from 0 to hadoop
> 2016-01-19 04:33:56,102 - Changing permission for /tmp from 1777 to 777
> 2016-01-19 04:33:56,102 - Directory['/tmp'] {'recursive': True, 
> 'cd_access': 'a'}
> 2016-01-19 04:33:56,102 - Execute[('chmod', '1777', u'/tmp')] {'sudo': 
> True}
> 2016-01-19 04:33:56,110 - XmlConfig['hbase-site.xml'] {'owner': 'hbase', 
> 'group': 'hadoop', 'conf_dir': '/usr/hdp/current/hbase-regionserver/conf', 
> 'configuration_attributes': {}, 'configurations': ...}
> 2016-01-19 04:33:56,126 - Generating config: 
> /usr/hdp/current/hbase-regionserver/conf/hbase-site.xml
> 2016-01-19 04:33:56,127 - 
> File['/usr/hdp/current/hbase-regionserver/conf/hbase-site.xml'] {'owner': 
> 'hbase', 'content': InlineTemplate(...), 'group': 'hadoop', 'mode': None, 
> 'encoding': 'UTF-8'}
> 2016-01-19 04:33:56,174 - XmlConfig['core-site.xml'] {'owner': 'hbase', 
> 'group': 'hadoop', 'conf_dir': '/usr/hdp/current/hbase-regionserver/conf', 
> 'configuration_attributes': {}, 'configurations': ...}
> 2016-01-19 04:33:56,185 - Generating config: 
> /usr/hdp/current/hbase-regionserver/conf/core-site.xml
> 2016-01-19 04:33:56,185 - 
> File['/usr/hdp/current/hbase-regionserver/conf/core-site.xml'] {'owner': 
> 'hbase', 'content': InlineTemplate(...), 'group': 'hadoop', 'mode': None, 
> 'encoding': 'UTF-8'}
> 2016-01-19 04:33:56,210 - XmlConfig['hdfs-site.xml'] {'owner': 'hbase', 
> 'group': 'hadoop', 'conf_dir': '/usr/hdp/current/hbase-regionserver/conf', 
> 'configuration_attributes': {}, 'configurations': ...}
> 2016-01-19 04:33:56,221 - Generating config: 
> /usr/hdp/current/hbase-regionserver/conf/hdfs-site.xml
> 2016-01-19 04:33:56,222 - 
> File['/usr/hdp/current/hbase-regionserver/conf/hdfs-site.xml'] {'owner': 'hb
> 
> This is the cluster this happened on
> <https://hcube2-1n01.eng.hortonworks.com:8443> and ssh key for user root is
> attached



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

Re: Review Request 42529: AMBARI-14730. After upgrade from 2.3.2 to 2.3.4, HBase fails to start, remove props for local indexing

2016-01-20 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/42529/#review115487
---

Ship it!


Ship It!

- Mahadev Konar


On Jan. 20, 2016, 9:32 p.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/42529/
> ---
> 
> (Updated Jan. 20, 2016, 9:32 p.m.)
> 
> 
> Review request for Ambari, Dmytro Grinenko, Jayush Luniya, Nate Cole, and 
> Swapan Shridhar.
> 
> 
> Bugs: AMBARI-14730
> https://issues.apache.org/jira/browse/AMBARI-14730
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Customer upgraded from HDP 2.3.2 to 2.3.4 and had some config changes for 
> local indexing that were not production ready.
> 
> The RegionServer will fail because some of the Phoenix observer 
> configurations are invalid because those classes no longer exist.
> 
> In each of the following upgrade paths,
> HDP 2.2 -> 2.3.*
> HDP 2.2 -> 2.4
> HDP 2.3.* -> 2.3*
> HDP 2.3.* -> 2.4
> 
> need change these properties,
> 
> * hbase.master.loadbalancer.class (will remove prop if value is 
> "org.apache.phoenix.hbase.index.balancer.IndexLoadBalancer")
> 
> * hbase.coprocessor.master.classes: "" (will remove 
> "org.apache.phoenix.hbase.index.master.IndexMasterObserver" from value )
> 
> * hbase.coprocessor.regionserver.classes (will remove 
> "org.apache.hadoop.hbase.regionserver.LocalIndexMerger" from value)
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.3.xml
>  df12920 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.4.xml
>  ff7e032 
>   ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.3.xml 
> 7e7138d 
>   ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.4.xml 
> 34e4848 
>   ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml 
> bdb4808 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml
>  57b2f42 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.4.xml
>  f58eb79 
>   ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml 
> ab955e4 
>   ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.4.xml 
> 573713c 
>   ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml 
> d5e4f78 
> 
> Diff: https://reviews.apache.org/r/42529/diff/
> 
> 
> Testing
> ---
> 
> Tested during RU from HDP 2.2 to 2.3
> 
> 
> Thanks,
> 
> Alejandro Fernandez
> 
>

[jira] [Updated] (AMBARI-14561) Configuration changes of spark thrift server for Spark 1.6

2016-01-18 Thread Mahadev konar (JIRA)


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

Mahadev konar updated AMBARI-14561:
---
Fix Version/s: 2.2.1

> Configuration changes of spark thrift server for Spark 1.6
> --
>
> Key: AMBARI-14561
> URL: https://issues.apache.org/jira/browse/AMBARI-14561
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Jeff Zhang
>Assignee: Jeff Zhang
> Fix For: 2.2.1
>
> Attachments: Ambari-14561-1.patch, Ambari-14561-2.patch
>
>
> This is for HDP stack, in HDP stack, we'd like to do following changes for 
> spark thrift server
> * Remove advanced properties except queue name
> * Use yarn-client mode 
> * Enable Dynamic Resource Allocation
> * Enable Fair scheduling policy
> * Use FileSystem as event logging destination
> * Copy spark-hdp-assembly.jar to hdfs



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

Re: Review Request 42258: CLONE - Ambari creates hdfs user despite ignore_groupsusers_create

2016-01-13 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/42258/#review114256
---

Ship it!


Ship It!

- Mahadev Konar


On Jan. 13, 2016, 6:56 p.m., Andrew Onischuk wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/42258/
> ---
> 
> (Updated Jan. 13, 2016, 6:56 p.m.)
> 
> 
> Review request for Ambari and Mahadev Konar.
> 
> 
> Bugs: AMBARI-14644
> https://issues.apache.org/jira/browse/AMBARI-14644
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py
>  42b2dd7 
> 
> Diff: https://reviews.apache.org/r/42258/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Andrew Onischuk
> 
>

Re: Review Request 42038: AMBARI-14581. EU - orchestration of Hive Server and MetaStore needs to be sequential

2016-01-11 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/42038/#review113905
---

Ship it!


Ship It!

- Mahadev Konar


On Jan. 12, 2016, 1:32 a.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/42038/
> ---
> 
> (Updated Jan. 12, 2016, 1:32 a.m.)
> 
> 
> Review request for Ambari, Dmytro Grinenko, Dmitro Lisnichenko, Jonathan 
> Hurley, Jayush Luniya, and Nate Cole.
> 
> 
> Bugs: AMBARI-14581
> https://issues.apache.org/jira/browse/AMBARI-14581
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> During an Express Upgrade, all of the tasks for Hive Server and Hive 
> MetaStore run in parallel, so if these components have multiple hosts, then 
> running in parallel can cause errors during the upgrade.
> E.g., Hive Server copies tarballs, which can only run one at a time. Hive 
> MetaStore updates the schema, and only one can run at a time.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/stacks/HDP/2.1/upgrades/nonrolling-upgrade-2.3.xml
>  c9f94c4 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.2.xml
>  e57b13f 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.3.xml
>  b1c3739 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.4.xml
>  2917de3 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml
>  6aff6ba 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.4.xml
>  9e81483 
>   
> ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.4.xml
>  3706f99 
> 
> Diff: https://reviews.apache.org/r/42038/diff/
> 
> 
> Testing
> ---
> 
> Ran unit tests in UpgradeHelperTest.java and UpgradePackTest.java
> Verified with EU from HDP 2.2->2.3 with multiple Hive MetaStores.
> 
> Waiting for unit test results.
> 
> 
> Thanks,
> 
> Alejandro Fernandez
> 
>

[jira] [Updated] (AMBARI-14437) Unable To Restart HCat Client When Not Colocated With WebHCat Server

2015-12-18 Thread Mahadev konar (JIRA)


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

Mahadev konar updated AMBARI-14437:
---
Fix Version/s: (was: 2.2.0)
   2.2.1

> Unable To Restart HCat Client When Not Colocated With WebHCat Server
> 
>
> Key: AMBARI-14437
> URL: https://issues.apache.org/jira/browse/AMBARI-14437
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.2.1
>
> Attachments: AMBARI-14437.patch
>
>
> Errors are encountered while restart Hive HCat client when it is not located 
> on a host which also has WebHCat daemon.
> {code:title=This is good - the pointers have moved for 2.3.4}
> root@os-d7-dkezlu-ambari-hv-r-upg-7-re1-5:/usr/hdp/current/hive-webhcat/etc# 
> ls -l /usr/hdp/2.3.4.0-3485/hive-hcatalog/etc
> total 4
> lrwxrwxrwx 1 root root   33 Dec 18 14:45 hcatalog -> 
> /etc/hive-hcatalog/2.3.4.0-3485/0
> drwxr-xr-x 2 root root 4096 Dec 18 14:45 init.d
> lrwxrwxrwx 1 root root   32 Dec 18 14:45 webhcat -> 
> /etc/hive-webhcat/2.3.4.0-3485/0
> {code}
> {code:title=This is bad - current for hcatalog is still 2.3.2, which has the 
> symlink issue}
> root@os-d7-dkezlu-ambari-hv-r-upg-7-re1-5:/usr/hdp/current/hive-webhcat/etc# 
> ls -l /usr/hdp/current | grep hive
> lrwxrwxrwx 1 root root 26 Dec 18 15:50 hive-client -> 
> /usr/hdp/2.3.4.0-3485/hive
> lrwxrwxrwx 1 root root 26 Dec 18 12:59 hive-metastore -> 
> /usr/hdp/2.3.2.0-2826/hive
> lrwxrwxrwx 1 root root 26 Dec 18 12:59 hive-server2 -> 
> /usr/hdp/2.3.2.0-2826/hive
> lrwxrwxrwx 1 root root 35 Dec 18 12:59 hive-webhcat -> 
> /usr/hdp/2.3.2.0-2826/hive-hcatalog
> {code}
> The problem is that {{hcat_client.py}} must write out configs to 
> {{/usr/hdp/current/hive-webhcat/etc/hcatalog}} but {{hcat_client.py}} doesn't 
> {{hdp-select}} anything.
> So that the "current" pointers are never changed. {{hcat_client.py}} should 
> probably {{hdp-select hive-webhcat}} since there is no {{hcat-client}} in 
> {{hdp-select}}.



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

Re: Review Request 41404: Revert AMBARI-14249 and ignore offending tests

2015-12-15 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/41404/#review110534
---

Ship it!


Ship It!

- Mahadev Konar


On Dec. 15, 2015, 4:37 p.m., Dmytro Sen wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41404/
> ---
> 
> (Updated Dec. 15, 2015, 4:37 p.m.)
> 
> 
> Review request for Ambari, Jonathan Hurley and Mahadev Konar.
> 
> 
> Bugs: AMBARI-14388
> https://issues.apache.org/jira/browse/AMBARI-14388
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Revert AMBARI-14249 and ignore offending tests
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/test/java/org/apache/ambari/server/orm/dao/AlertDefinitionDAOTest.java
>  d0ad386 
>   
> ambari-server/src/test/java/org/apache/ambari/server/orm/dao/AlertDispatchDAOTest.java
>  9b269b4 
>   
> ambari-server/src/test/java/org/apache/ambari/server/orm/dao/RequestDAOTest.java
>  384ef31 
> 
> Diff: https://reviews.apache.org/r/41404/diff/
> 
> 
> Testing
> ---
> 
> Unit tests passed
> 
> 
> Thanks,
> 
> Dmytro Sen
> 
>

Re: Review Request 41432: AMBARI-14390. EU from HDP 2.1 to 2.3 added NULL properties

2015-12-15 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/41432/#review110617
---

Ship it!


Ship It!

- Mahadev Konar


On Dec. 16, 2015, 4:25 a.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41432/
> ---
> 
> (Updated Dec. 16, 2015, 4:25 a.m.)
> 
> 
> Review request for Ambari, Dmytro Grinenko, Dmitro Lisnichenko, Jonathan 
> Hurley, Jayush Luniya, and Nate Cole.
> 
> 
> Bugs: AMBARI-14390
> https://issues.apache.org/jira/browse/AMBARI-14390
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> *Steps:*
> With Ambari 2.2.0, setup HDP 2.1 cluster (non HA, unsecure) with following 
> services: hbase,pig,slider,hive,oozie,sqoop,flume,falcon,storm
> Did Express Upgrade from HDP 2.1 to 2.3.4 and let it finish
> Observe the configs of various services
> 
> *Result:*
> Observed that the values of several properties showed up as blank and 
> required (mostly security related). Here is the list:
> 
> HDFS:
> 
> * hdfs_principal_name (hadoop-env, value is null, remove if not kerberized)
> * hdfs_user_keytab (hadoop-env, value is null, remove if not kerberized)
> * dfs.namenode.inode.attributes.provider.class (hdfs-site, value is null, set 
> to "org.apache.ranger.authorization.hadoop.RangerHdfsAuthorizer" if Ranger is 
> present, which it is not in HDP 2.1)
> 
> YARN:
> 
> * yarn.authorization-provider (yarn-site, value is null, set to 
> "org.apache.ranger.authorization.yarn.authorizer.RangerYarnAuthorizer" if 
> Ranger is present, which it is not in HDP 2.1)
> 
> Tez:
> 
> * tez.tez-ui.history-url.base (also tracked by AMBARI-14389, tez-site, value 
> is null, set to {code} 
> '{0}://{1}:{2}/#/main/views/TEZ/{3}/TEZ_CLUSTER_INSTANCE'.format(server_protocol,
>  server_host, server_port, latest_tez_jar_version) {code} by Stack Advisor)
> 
> HBase:
> 
> * hbase_principal_name (hbase-env, value is null, remove if not kerberized)
> * hbase_user_keytab (hbase-env, value is null, remove if not kerberized)
> 
> ZK:
> 
> * zookeeper_keytab_path (zookeeper-env, value is null, remove if not 
> kerberized)
> * zookeeper_principal_name (zookeeper-env, value is null, remove if not 
> kerberized)
> 
> Storm:
> 
> * nimbus_keytab  (storm-env, value is null, remove if not kerberized)
> * nimbus_principal_name (storm-env, value is null, remove if not kerberized)
> * storm_keytab (storm-env, value is null, remove if not kerberized)
> * storm_principal_name (storm-env, value is null, remove if not kerberized)
> * storm_ui_keytab (storm-env, value is null, remove if not kerberized)
> * storm_ui_principal_name (storm-env, value is null, remove if not kerberized)
> * nimbus.authorizer (storm-site, need help from Storm team on what to set 
> this to since it depends on whether kerberos is enabled and Ranger is present)
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
>  1e59b58 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/ConfigMergeHelper.java
>  b799bc7 
>   
> ambari-server/src/main/resources/stacks/HDP/2.1/upgrades/nonrolling-upgrade-2.3.xml
>  ef4b531 
>   ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/config-upgrade.xml 
> ab384db 
> 
> Diff: https://reviews.apache.org/r/41432/diff/
> 
> 
> Testing
> ---
> 
> Installed Ambari 2.2.0 with HDP 2.1 and all of the services listed above, 
> then performed Express Upgrade to HDP 2.3 and verified through the configs 
> page that no properties had null values.
> This happened because of all of the kerberos-related properties in stack HDP 
> 2.3 have null, so the merging of configurations was adding the property.
> 
> mvn clean test
> 
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 1:01:45.515s
> [INFO] Finished at: Tue Dec 15 20:24:13 PST 2015
> [INFO] Final Memory: 120M/4042M
> [INFO] 
> 
> 
> 
> Thanks,
> 
> Alejandro Fernandez
> 
>

Re: Review Request 41324: Ambari Agent UT failure for branch-2.2: test_do_cleanup_with_skip

2015-12-13 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/41324/#review110123
---

Ship it!


Ship It!

- Mahadev Konar


On Dec. 13, 2015, 11:57 a.m., Dmytro Sen wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41324/
> ---
> 
> (Updated Dec. 13, 2015, 11:57 a.m.)
> 
> 
> Review request for Ambari and Andrew Onischuk.
> 
> 
> Bugs: AMBARI-14359
> https://issues.apache.org/jira/browse/AMBARI-14359
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> https://builds.apache.org/job/Ambari-branch-2.2/62/console
> 
> ==
> ERROR: test_do_cleanup_with_skip (TestHostCleanup.TestHostCleanup)
> --
> Traceback (most recent call last):
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-branch-2.2/ambari-common/src/test/python/mock/mock.py",
>  line 1199, in patched
> return func(*args, **keywargs)
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-branch-2.2/ambari-agent/src/test/python/ambari_agent/TestHostCleanup.py",
>  line 315, in test_do_cleanup_with_skip
> self.hostcleanup.do_cleanup(propertyMap)
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-branch-2.2/ambari-agent/src/main/python/ambari_agent/HostCleanup.py",
>  line 157, in do_cleanup
> self.do_delete_by_owner(userIds, FOLDER_LIST)
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-branch-2.2/ambari-agent/src/main/python/ambari_agent/HostCleanup.py",
>  line 441, in do_delete_by_owner
> stat = os.stat(fileToCheck)
> OSError: [Errno 2] No such file or directory: 
> '/tmp/Jetty_localhost_51472_hdfs.hiatsz'
> 
> --
> Ran 420 tests in 12.336s
> 
> 
> Diffs
> -
> 
>   ambari-agent/src/test/python/ambari_agent/TestHostCleanup.py 78cf4c2 
> 
> Diff: https://reviews.apache.org/r/41324/diff/
> 
> 
> Testing
> ---
> 
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 16.884s
> [INFO] Finished at: Sun Dec 13 13:53:49 EET 2015
> [INFO] Final Memory: 12M/192M
> [INFO] 
> 
> 
> Thanks,
> 
> Dmytro Sen
> 
>

Re: Review Request 41329: Cannot save KDC admin creds

2015-12-13 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/41329/#review110128
---

Ship it!


Ship It!

- Mahadev Konar


On Dec. 13, 2015, 6:56 p.m., Andrew Onischuk wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41329/
> ---
> 
> (Updated Dec. 13, 2015, 6:56 p.m.)
> 
> 
> Review request for Ambari and Robert Levas.
> 
> 
> Bugs: AMBARI-14363
> https://issues.apache.org/jira/browse/AMBARI-14363
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/security/encryption/CredentialStoreServiceImpl.java
>  fe14004 
>   ambari-server/src/main/python/ambari_server/setupSecurity.py 19febcf 
> 
> Diff: https://reviews.apache.org/r/41329/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Andrew Onischuk
> 
>

Re: Review Request 41329: Cannot save KDC admin creds

2015-12-13 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/41329/#review110133
---

Ship it!


Ship It!

- Mahadev Konar


On Dec. 13, 2015, 7:31 p.m., Andrew Onischuk wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41329/
> ---
> 
> (Updated Dec. 13, 2015, 7:31 p.m.)
> 
> 
> Review request for Ambari, Mahadev Konar and Robert Levas.
> 
> 
> Bugs: AMBARI-14363
> https://issues.apache.org/jira/browse/AMBARI-14363
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> .
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/security/encryption/CredentialStoreServiceImpl.java
>  fe14004 
>   
> ambari-server/src/main/java/org/apache/ambari/server/security/encryption/MasterKeyServiceImpl.java
>  759fd8e 
>   ambari-server/src/main/python/ambari_server/setupSecurity.py 19febcf 
> 
> Diff: https://reviews.apache.org/r/41329/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Andrew Onischuk
> 
>

[jira] [Updated] (AMBARI-14331) Ambari local admin endpoint doesn’t work when sso is enabled.

2015-12-10 Thread Mahadev konar (JIRA)


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

Mahadev konar updated AMBARI-14331:
---
Description: 


 Ambari local admin endpoint doesn’t work when sso is enabled.



  was:
This issue is part of the preview build given to EMC 
Ambari Build

http://private-repo-1.hortonworks.com/ambari/centos6/2.x/updates/2.2.0.0/ambari.repo
http://private-repo-1.hortonworks.com/ambari/debian6/2.x/updates/2.2.0.0/ambari.list
http://private-repo-1.hortonworks.com/ambari/suse11/2.x/updates/2.2.0.0/ambari.repo
http://private-repo-1.hortonworks.com/ambari/ubuntu12/2.x/updates/2.2.0.0/ambari.list
 

 Ambari local admin endpoint doesn’t work when sso is enabled.




> Ambari local admin endpoint doesn’t work when sso is enabled.
> -
>
> Key: AMBARI-14331
> URL: https://issues.apache.org/jira/browse/AMBARI-14331
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Zehava Vardy
>  Labels: test
> Fix For: 2.4.0
>
>
>  Ambari local admin endpoint doesn’t work when sso is enabled.



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

[jira] [Commented] (AMBARI-14337) Add service wizard hangs up on Customize Services step on secure cluster after RU

2015-12-10 Thread Mahadev konar (JIRA)


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

Mahadev konar commented on AMBARI-14337:


+1 for the patch

> Add service wizard hangs up on Customize Services step on secure cluster 
> after RU
> -
>
> Key: AMBARI-14337
> URL: https://issues.apache.org/jira/browse/AMBARI-14337
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
>Priority: Critical
> Fix For: 2.2.0
>
> Attachments: AMBARI-14337.patch
>
>
> After RU on secured cluster failed to add SmartSense service. 
> Add Service Wizard not loading  on Customize Services step.



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

Re: Review Request 41217: RESTART STORM/NIMBUS fails during EU, 2.1 --> 2.3

2015-12-10 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/41217/#review109814
---

Ship it!


Ship It!

- Mahadev Konar


On Dec. 10, 2015, 6:19 p.m., Dmitro Lisnichenko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41217/
> ---
> 
> (Updated Dec. 10, 2015, 6:19 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jonathan Hurley, Jayush 
> Luniya, and Nate Cole.
> 
> 
> Bugs: AMBARI-14326
> https://issues.apache.org/jira/browse/AMBARI-14326
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> {code}
> Traceback (most recent call last):
> File 
> "/var/lib/ambari-agent/cache/common-services/STORM/0.9.1.2.1/package/scripts/nimbus.py",
>  line 149, in 
> Nimbus().execute()
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 218, in execute
> method(env)
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 514, in restart
> self.start(env, upgrade_type=upgrade_type)
> File 
> "/var/lib/ambari-agent/cache/common-services/STORM/0.9.1.2.1/package/scripts/nimbus.py",
>  line 68, in start
> self.configure(env)
> File 
> "/var/lib/ambari-agent/cache/common-services/STORM/0.9.1.2.1/package/scripts/nimbus.py",
>  line 50, in configure
> storm("nimbus")
> 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/STORM/0.9.1.2.1/package/scripts/storm.py",
>  line 103, in storm
> only_if=format("ls {metric_collector_sink_jar}")
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 154, in __init__
> self.env.run()
> File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 158, in run
> self.run_action(resource, action)
> File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 121, in run_action
> provider_action()
> File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 238, 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 291, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'ambari-sudo.sh ln -s 
> /usr/lib/storm/lib/ambari-metrics-storm-sink*.jar 
> /usr/hdp/current/storm-nimbus/lib/ambari-metrics-storm-sink.jar' returned 1. 
> ln: target `/usr/hdp/current/storm-nimbus/lib/ambari-metrics-storm-sink.jar' 
> is not a directory
> {code}
> 
> Perhaps because there are two files that satisfy the wildcard:
> {code}
> ls /usr/lib/storm/lib/ambari-metrics-storm-sink*.jar
> /usr/lib/storm/lib/ambari-metrics-storm-sink.jar  
> /usr/lib/storm/lib/ambari-metrics-storm-sink-with-common-2.2.0.0.1262.jar
> {code}
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/package/scripts/storm.py
>  4e97c65 
> 
> Diff: https://reviews.apache.org/r/41217/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> Checked upgrade on live cluster
> 
> 
> Thanks,
> 
> Dmitro Lisnichenko
> 
>

Re: Review Request 41238: Kerberos: all ambari server host ops are broken

2015-12-10 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/41238/#review109921
---

Ship it!


Ship It!

- Mahadev Konar


On Dec. 11, 2015, 4:24 a.m., Robert Levas wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41238/
> ---
> 
> (Updated Dec. 11, 2015, 4:24 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jonathan Hurley, Mahadev 
> Konar, Myroslav Papirkovskyy, Nate Cole, and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-14327
> https://issues.apache.org/jira/browse/AMBARI-14327
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> 1) Test Kerberos Client dialog shows an "n/a" entry and when you click on it, 
> throws a JS error. See attached. The n/a appears to represent the command run 
> on the Ambari Server itself.
> 2) All Ambari server ops throw JS error. On other places in the wizard, it 
> shows "Ambari Server Host" but that throws JS.
> 3) same for regen keytabs. basically all over the place 
>  
> See attached.
> 
> ```
> {
>   "Requests" : {
> "aborted_task_count" : 0,
> "cluster_name" : "MyCluster",
> "completed_task_count" : 10,
> "create_time" : 1449759400223,
> "end_time" : 1449759448232,
> "exclusive" : false,
> "failed_task_count" : 0,
> "id" : 17,
> "inputs" : "{}",
> "operation_level" : "CLUSTER",
> "progress_percent" : 100.0,
> "queued_task_count" : 0,
> "request_context" : "Kerberos Service Check",
> "request_schedule" : null,
> "request_status" : "COMPLETED",
> "resource_filters" : [
>   {
> "service_name" : "KERBEROS"
>   }
> ],
> "start_time" : 1449759400313,
> "task_count" : 10,
> "timed_out_task_count" : 0,
> "type" : "COMMAND"
>   },
>   "stages" : [
> { },
> { },
> { },
> { },
> { },
> { },
> { },
> { },
> { },
> { }
>   ],
>   "tasks" : [
> {
>   "Tasks" : {
> "command" : "EXECUTE",
> "command_detail" : "Preparing Operations",
> "host_name" : null,
> "id" : 153,
> "request_id" : 17,
> "role" : "AMBARI_SERVER_ACTION",
> "status" : "COMPLETED"
>   }
> },
> {
>   "Tasks" : {
> "command" : "EXECUTE",
> "command_detail" : "Create Principals",
> "host_name" : null,
> "id" : 154,
> "request_id" : 17,
> "role" : "AMBARI_SERVER_ACTION",
> "status" : "COMPLETED"
>   }
> },
> {
>   "Tasks" : {
> "command" : "EXECUTE",
> "command_detail" : "Create Keytabs",
> "host_name" : null,
> "id" : 155,
> "request_id" : 17,
> "role" : "AMBARI_SERVER_ACTION",
> "status" : "COMPLETED"
>   }
> },
> {
>   "Tasks" : {
> "command" : "CUSTOM_COMMAND",
> "command_detail" : "SET_KEYTAB KERBEROS/KERBEROS_CLIENT",
> "host_name" : "c6402.ambari.apache.org",
> "id" : 156,
> "request_id" : 17,
> "role" : "KERBEROS_CLIENT",
> "status" : "COMPLETED"
>   }
> },
> {
>   "Tasks" : {
> "command" : "EXECUTE",
> "command_detail" : "Finalize Operations",
> "host_name" : null,
> "id" : 157,
> "request_id" : 17,
> "role" : "AMBARI_SERVER_ACTION",
> "status" : "COMPLETED"
>   }
> },
> {
>

[jira] [Commented] (AMBARI-14312) Express Upgrade: Failure during restart of all Node Managers during EU from 2.1 to 2.3.4 with timeout error

2015-12-09 Thread Mahadev konar (JIRA)


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

Mahadev konar commented on AMBARI-14312:


+1 for the aptch.

> Express Upgrade: Failure during restart of all Node Managers during EU from 
> 2.1 to 2.3.4 with timeout error
> ---
>
> Key: AMBARI-14312
> URL: https://issues.apache.org/jira/browse/AMBARI-14312
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Blocker
> Fix For: 2.2.0
>
> Attachments: AMBARI-14300.patch
>
>
> *Steps:*
> Setup HDP 2.1 cluster with Ambari 2.2.0
> Modify the relevant DB tables
> Start Express Upgrade to 2.3.4
> Result:
> EU reported failures during restart of all NameNodes
> *stderr*
> {code}
> Python script has been killed due to timeout after waiting 1200 secs
> {code}
> *stdout*
> {code}
> 2015-12-09 10:58:32,783 - 
> File['/var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'] {'action': 
> ['delete'], 'not_if': "ambari-sudo.sh su yarn -l -s /bin/bash -c 'ls 
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ps -p `cat 
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid`'"}
> 2015-12-09 10:58:32,844 - Execute['ulimit -c unlimited; export 
> HADOOP_LIBEXEC_DIR=/usr/hdp/2.3.4.0-3426/hadoop/libexec && 
> /usr/hdp/current/hadoop-yarn-nodemanager/sbin/yarn-daemon.sh --config 
> /usr/hdp/2.3.4.0-3426/hadoop/conf start nodemanager'] {'not_if': 
> "ambari-sudo.sh su yarn -l -s /bin/bash -c 'ls 
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ps -p `cat 
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid`'", 'user': 'yarn'}
> 2015-12-09 10:58:34,031 - Execute['ambari-sudo.sh su yarn -l -s /bin/bash -c 
> 'ls /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ps -p `cat 
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid`''] {'not_if': 
> "ambari-sudo.sh su yarn -l -s /bin/bash -c 'ls 
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ps -p `cat 
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid`'", 'tries': 5, 
> 'try_sleep': 1}
> 2015-12-09 10:58:34,081 - Skipping Execute['ambari-sudo.sh su yarn -l -s 
> /bin/bash -c 'ls /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ps -p 
> `cat /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid`''] due to not_if
> 2015-12-09 10:58:34,081 - Executing NodeManager Stack Upgrade post-restart
> 2015-12-09 10:58:34,083 - NodeManager executing "yarn node -list 
> -states=RUNNING" to verify the node has rejoined the cluster...
> 2015-12-09 10:58:34,083 - call['yarn node -list -states=RUNNING'] {'user': 
> 'yarn'}
> {code}
> Attachments: stdout and screenshots



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

[jira] [Commented] (AMBARI-14300) Fix discrepancies in branch-2.2 config-upgrades

2015-12-09 Thread Mahadev konar (JIRA)


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

Mahadev konar commented on AMBARI-14300:


+1 - looks good.

> Fix discrepancies in branch-2.2 config-upgrades 
> 
>
> Key: AMBARI-14300
> URL: https://issues.apache.org/jira/browse/AMBARI-14300
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Blocker
> Fix For: 2.2.0
>
> Attachments: AMBARI-14300.patch
>
>
> Storm Logviewer does not start. This is because of in AMBARI-13688 
> config-upgrade changes were committed to trunk but not in branch-2.2
> Trunk:
> https://git1-us-west.apache.org/repos/asf?p=ambari.git=commit=efca65bfff18c8fe1340d5923a91726121359d93
> Branch-2.1:
> http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=81b912a9525ac788d8b747b54b8bd12a53ef7976
> The changes to 
> ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml 
> were missed.



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

Re: Review Request 40931: AMBARI-14203. EU: NFS_GATEWAY not restarted since not orchestrated in upgrade pack

2015-12-03 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40931/#review108900
---

Ship it!


Ship It!

- Mahadev Konar


On Dec. 3, 2015, 10:36 p.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40931/
> ---
> 
> (Updated Dec. 3, 2015, 10:36 p.m.)
> 
> 
> Review request for Ambari, Dmytro Grinenko, Dmitro Lisnichenko, Jonathan 
> Hurley, Nate Cole, and Swapan Shridhar.
> 
> 
> Bugs: AMBARI-14203
> https://issues.apache.org/jira/browse/AMBARI-14203
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Express Upgrade from HDP 2.3 to 2.3* with HDFS NFS_GATEWAY isn't actually 
> restarted during the orchestration.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml
>  0df26c5 
> 
> Diff: https://reviews.apache.org/r/40931/diff/
> 
> 
> Testing
> ---
> 
> Tested during Express Upgrade from HDP 2.3.0.0 to 2.3.4.0, and then downgrade.
> 
> 
> Thanks,
> 
> Alejandro Fernandez
> 
>

Re: Review Request 40855: Exported blueprint does not contain "policymgr_external_url" property

2015-12-02 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40855/#review108781
---

Ship it!


Ship It!

- Mahadev Konar


On Dec. 2, 2015, 3:35 p.m., Sebastian Toader wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40855/
> ---
> 
> (Updated Dec. 2, 2015, 3:35 p.m.)
> 
> 
> Review request for Ambari, Dmitro Lisnichenko and Robert Nettleton.
> 
> 
> Bugs: AMBARI-14148
> https://issues.apache.org/jira/browse/AMBARI-14148
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> In case of HA deployment the "policy_external_url" is not automatically 
> constructed from the host and port of Ranger Admin but rather is the load 
> balancer URL that is on front of the Ranger Admin instances which is provided 
> by user. 
> 
> This property has been added to the list of properties that can support HA 
> using a nameservice name otherwise this property is ignored by Blueprint 
> export when it's format differs from cluster_host:port
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java
>  7f11bb9 
>   ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py 
> d4d0e83 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java
>  17c0157 
> 
> Diff: https://reviews.apache.org/r/40855/diff/
> 
> 
> Testing
> ---
> 
> Manual testing:
> 1. Verified export with both cases when Ranger is deployed with UI and using 
> Blueprint
> 
> Unit tests:
> --
> Total run:804
> Total errors:0
> Total failures:0
> OK
> 
> 
> Thanks,
> 
> Sebastian Toader
> 
>

[jira] [Commented] (AMBARI-13895) Unit Test failure in Ambari Server python tests

2015-11-14 Thread Mahadev konar (JIRA)


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

Mahadev konar commented on AMBARI-13895:


+1 for the patch.

> Unit Test failure in Ambari Server python tests
> ---
>
> Key: AMBARI-13895
> URL: https://issues.apache.org/jira/browse/AMBARI-13895
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Jayush Luniya
>Assignee: Sumit Mohanty
>Priority: Blocker
> Fix For: 2.1.3
>
> Attachments: AMBARI-13895.patch
>
>
> See following python UT failures
> {noformat}
> --
> Failed tests:
> FAIL: test_configure_default (test_historyserver.TestHistoryServer)
> --
> Traceback (most recent call last):
>   File 
> "/Users/jluniya/merge/trunk/ambari/ambari-common/src/test/python/mock/mock.py",
>  line 1199, in patched
> return func(*args, **keywargs)
>   File 
> "/Users/jluniya/merge/trunk/ambari/ambari-server/src/test/python/stacks/2.0.6/YARN/test_historyserver.py",
>  line 45, in test_configure_default
> self.assert_configure_default()
>   File 
> "/Users/jluniya/merge/trunk/ambari/ambari-server/src/test/python/stacks/2.0.6/YARN/test_historyserver.py",
>  line 222, in assert_configure_default
> action = ['create_on_execute'],
>   File 
> "/Users/jluniya/merge/trunk/ambari/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
>  line 254, in assertResourceCalled
> self.assertEquals(kwargs, resource.arguments)
> AssertionError: {'security_enabled': False, 'hadoop_conf_dir': 
> '/etc/hadoop/conf', 'keytab': UnknownConfigurationMock(), 'default_fs': 
> 'hdfs://c6401.ambari.apache.org:8020', 'hdfs_site': 
> {u'dfs.namenode.checkpoint.period': u'21600', 
> u'dfs.namenode.avoid.write.stale.datanode': u'true', 
> u'dfs.block.access.token.enable': u'true', u'dfs.support.append': u'true', 
> u'dfs.datanode.address': u'0.0.0.0:${ambari.dfs.datanode.port}', 
> u'dfs.cluster.administrators': u'test_user1,test_user2 hdfs,test_group', 
> u'dfs.replication': u'3', u'ambari.dfs.datanode.http.port': u'50075', 
> u'dfs.datanode.balance.bandwidthPerSec': u'625', 
> u'dfs.namenode.safemode.threshold-pct': u'1.0f', 
> u'dfs.namenode.checkpoint.edits.dir': u'${dfs.namenode.checkpoint.dir}', 
> u'dfs.permissions.enabled': u'true', u'fs.checkpoint.size': u'67108864', 
> u'dfs.client.read.shortcircuit': u'true', u'dfs.namenode.https-address': 
> u'c6401.ambari.apache.org:50470', u'dfs.journalnode.edits.dir': 
> u'/grid/0/hdfs/journal', u'dfs.blocksize': u'134217728', 
> u'dfs.datanode.max.transfer.threads': u'1024', u'dfs.datanode.du.reserved': 
> u'1073741824', u'dfs.webhdfs.enabled': u'true', 
> u'dfs.namenode.handler.count': u'100', u'dfs.namenode.checkpoint.dir': 
> u'/hadoop/hdfs/namesecondary,/hadoop/hdfs/namesecondary2', 
> u'fs.permissions.umask-mode': u'022', u'dfs.datanode.http.address': 
> u'0.0.0.0:50075', u'dfs.datanode.ipc.address': u'0.0.0.0:8010', 
> u'dfs.datanode.data.dir': u'/hadoop/hdfs/data', u'dfs.namenode.http-address': 
> u'c6401.ambari.apache.org:50070', u'dfs.blockreport.initialDelay': u'120', 
> u'dfs.datanode.failed.volumes.tolerated': u'0', 
> u'dfs.namenode.accesstime.precision': u'0', u'ambari.dfs.datanode.port': 
> u'50010', u'dfs.namenode.avoid.read.stale.datanode': u'true', 
> u'dfs.namenode.secondary.http-address': u'c6402.ambari.apache.org:50090', 
> u'dfs.namenode.stale.datanode.interval': u'3', u'dfs.heartbeat.interval': 
> u'3', u'dfs.client.read.shortcircuit.streams.cache.size': u'4096', 
> u'dfs.permissions.superusergroup': u'hdfs', u'dfs.https.port': u'50470', 
> u'dfs.journalnode.http-address': u'0.0.0.0:8480', u'dfs.domain.socket.path': 
> u'/var/lib/hadoop-hdfs/dn_socket', 
> u'dfs.namenode.write.stale.datanode.ratio': u'1.0f', u'dfs.hosts.exclude': 
> u'/etc/hadoop/conf/dfs.exclude', u'dfs.datanode.data.dir.perm': u'750', 
> u'dfs.namenode.name.dir.restore': u'true', u'dfs.replication.max': u'50', 
> u'dfs.namenode.name.dir': u'/hadoop/hdfs/namenode'}, 'kinit_path_local': 
> '/usr/bin/kinit', 'principal_name': UnknownConfigurationMock(), 'user': 
> 'hdfs', 'owner': 'yarn', 'group': 'hadoop', 'hadoop_bin_dir': '/usr/bin', 
> 'type': 'directory', 'action': ['create_on_execute']} != {'security_enabled': 
> False, 'hadoop_bin_dir': '/usr/bin', 'keytab': UnknownConfiguration(), 
> 'dfs_type': '', '

Re: Review Request 40298: SmartSense install fails as archive.zip fails to download

2015-11-13 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40298/#review106450
---

Ship it!


Ship It!

- Mahadev Konar


On Nov. 13, 2015, 4:20 p.m., Dmitro Lisnichenko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40298/
> ---
> 
> (Updated Nov. 13, 2015, 4:20 p.m.)
> 
> 
> Review request for Ambari, Andrew Onischuk and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-13887
> https://issues.apache.org/jira/browse/AMBARI-13887
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Try to install Smart Sense when trying to deploy HDP 2.3 and the server and 
> agent install fails
> 
> Caught an exception while executing custom service command:  'ambari_agent.AgentException.AgentException'>: 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_agent.py
>  does not exist'; 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_agent.py
>  does not exist'
> 
> Caught an exception while executing custom service command:  'ambari_agent.AgentException.AgentException'>: 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_server.py
>  does not exist'; 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_server.py
>  does not exist'
> 
> server is running under user slava:
> slava23129  3.3  4.2 4768512 686808 ?  Sl   02:28  25:37 
> /usr/jdk64/jdk1.8.0_45/bin/java -server -XX:NewRatio=3 
> -XX:+UseConcMarkSweepGC -XX:-UseGCOverheadLimit 
> -XX:CMSInitiatingOccupancyFraction=60 -Dsun.zip.disableMemoryMapping=true 
> -Xms512m -Xmx2048m 
> -Djava.security.auth.login.config=/etc/ambari-server/conf/krb5JAASLogin.conf 
> -Djava.security.krb5.conf=/etc/krb5.conf 
> -Djavax.security.auth.useSubjectCredsOnly=false -Xms512m -Xmx2048m 
> -Djava.security.auth.login.config=/etc/ambari-server/conf/krb5JAASLogin.conf 
> -Djava.security.krb5.conf=/etc/krb5.conf 
> -Djavax.security.auth.useSubjectCredsOnly=false -cp 
> /etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/mysql-connector-java.jar
>  org.apache.ambari.server.controller.AmbariServer
> 
> Files generated by ambari-server script have wrong permissions:
> [root@os-r6-stest-5 tmp]# ll 
> /var/lib/ambari-server/resources/stacks/HDP/2.1/services/SMARTSENSE/package/
> total 840
> -rw-r-. 1 root  root  0 2015-11-13 02:27 abc.txt
> -rw-r-. 1 root  root 850974 2015-11-12 22:26 archive.zip
> drwxr-xr-x. 4 slava root   4096 2015-11-12 22:25 files
> drwxr-xr-x. 2 slava root   4096 2015-11-12 22:25 scripts
> 
> [root@os-r6-stest-5 tmp]# umask
> 0027
> And that's why file can not be read by server process.
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/python/ambari_server/resourceFilesKeeper.py fe80723 
> 
> Diff: https://reviews.apache.org/r/40298/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Dmitro Lisnichenko
> 
>

[jira] [Commented] (AMBARI-13846) Spark thrift server should be a slave component

2015-11-11 Thread Mahadev konar (JIRA)


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

Mahadev konar commented on AMBARI-13846:


+1 for the fix.

> Spark thrift server should be a slave component
> ---
>
> Key: AMBARI-13846
> URL: https://issues.apache.org/jira/browse/AMBARI-13846
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.1.3
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.1.3
>
> Attachments: AMBARI-13846.patch
>
>
> Spark thrift server is an optional component. As a MASTER component it cannot 
> be optional even with cardinality as {{0+}}. It should be a component of type 
> SLAVE.



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

[jira] [Updated] (AMBARI-13679) UpgradeCatalog212 not idempotent

2015-11-09 Thread Mahadev konar (JIRA)


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

Mahadev konar updated AMBARI-13679:
---
Fix Version/s: 2.1.3

> UpgradeCatalog212 not idempotent
> 
>
> Key: AMBARI-13679
> URL: https://issues.apache.org/jira/browse/AMBARI-13679
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Laszlo Puskas
>Assignee: Laszlo Puskas
>  Labels: patch
> Fix For: 2.1.3
>
> Attachments: AMBARI-13679.v1.patch, AMBARI-13679.v2.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> The UpgradeCatalog212 logic is not idempotent:
> - the executePreDMLUpdate logic relies on a column that could potentially be 
> deleted by a previously ran upgrade



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

Re: Review Request 39786: Fix ClusterStackVersionResourceProviderTest#testUpdateResourcesWithForce test case compile issues

2015-10-29 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39786/#review104488
---

Ship it!


Ship It!

- Mahadev Konar


On Oct. 29, 2015, 10:40 p.m., Robert Levas wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39786/
> ---
> 
> (Updated Oct. 29, 2015, 10:40 p.m.)
> 
> 
> Review request for Ambari, Mahadev Konar, Nate Cole, Sid Wagle, and Yusaku 
> Sako.
> 
> 
> Bugs: AMBARI-13646
> https://issues.apache.org/jira/browse/AMBARI-13646
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Fix ClusterStackVersionResourceProviderTest#testUpdateResourcesWithForce test 
> case compile issues
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProviderTest.java
>  b41416e 
> 
> Diff: https://reviews.apache.org/r/39786/diff/
> 
> 
> Testing
> ---
> 
> Ran test case... passed.
> 
> 
> Thanks,
> 
> Robert Levas
> 
>

[jira] [Updated] (AMBARI-13584) Ambari stack definition for Spark has incorrect value for SPARK_CONF_DIR

2015-10-28 Thread Mahadev konar (JIRA)


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

Mahadev konar updated AMBARI-13584:
---
Assignee: Ram Venkatesh

> Ambari stack definition for Spark has incorrect value for SPARK_CONF_DIR
> 
>
> Key: AMBARI-13584
> URL: https://issues.apache.org/jira/browse/AMBARI-13584
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Reporter: Ram Venkatesh
>Assignee: Ram Venkatesh
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13584.0.patch
>
>
> The Ambari Spark stack definition always sets SPARK_CONF_DIR to an incorrect 
> value regardless of what the user set. So users have no way to override 
> configs for their jobs.
> Simple patch attached.



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

[jira] [Updated] (AMBARI-13584) Ambari stack definition for Spark has incorrect value for SPARK_CONF_DIR

2015-10-28 Thread Mahadev konar (JIRA)


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

Mahadev konar updated AMBARI-13584:
---
Fix Version/s: 2.1.3

> Ambari stack definition for Spark has incorrect value for SPARK_CONF_DIR
> 
>
> Key: AMBARI-13584
> URL: https://issues.apache.org/jira/browse/AMBARI-13584
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Reporter: Ram Venkatesh
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13584.0.patch
>
>
> The Ambari Spark stack definition always sets SPARK_CONF_DIR to an incorrect 
> value regardless of what the user set. So users have no way to override 
> configs for their jobs.
> Simple patch attached.



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

[jira] [Commented] (AMBARI-12701) Stop-and-Start Upgrade: Handle Core Services

2015-10-25 Thread Mahadev konar (JIRA)


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

Mahadev konar commented on AMBARI-12701:


+1 o nthe addendum.

> Stop-and-Start Upgrade: Handle Core Services
> 
>
> Key: AMBARI-12701
> URL: https://issues.apache.org/jira/browse/AMBARI-12701
> Project: Ambari
>  Issue Type: Story
>  Components: ambari-server
>Affects Versions: 2.2.0, 2.1.3
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>  Labels: branch:branch-dev-stop-all-upgrade
> Fix For: 2.2.0, 2.1.3
>
> Attachments: AMBARI-12701.additional.fix.patch, 
> AMBARI-12701.branch-2.1.patch, AMBARI-12701.trunk.patch
>
>
> Stop-and-Start Upgrade of the Stack to handle core services: HDFS, YARN, MR, 
> ZK



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

Re: Review Request 39244: Stop-and-Start Upgrade: Merge branch branch-dev-stop-all-upgrade to branch-2.1 for feature Stop-the-World Upgrade, aka Express Upgrade

2015-10-12 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39244/#review102316
---

Ship it!


Ship It!

- Mahadev Konar


On Oct. 12, 2015, 8:37 p.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39244/
> ---
> 
> (Updated Oct. 12, 2015, 8:37 p.m.)
> 
> 
> Review request for Ambari, Dmytro Grinenko, Dmitro Lisnichenko, Jonathan 
> Hurley, and Nate Cole.
> 
> 
> Bugs: AMBARI-13392
> https://issues.apache.org/jira/browse/AMBARI-13392
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Merge branch branch-dev-sotp-all-upgrade to branch-2.1
> This contains all of the work that Dmitry Lisnichenko, Dmytro Grinenko, and I 
> have done for the past 2 months.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/services/AmbariMetaInfo.java
>  561b3f4 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/AbstractCheckDescriptor.java
>  2f0bc94 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/ClientRetryPropertyCheck.java
>  52fca40 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/ConfigurationMergeCheck.java
>  b81ca11 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/HiveDynamicServiceDiscoveryCheck.java
>  4ea5484 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/HiveMultipleMetastoreCheck.java
>  c387a4b 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/HostsHeartbeatCheck.java
>  a8600c4 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/HostsMasterMaintenanceCheck.java
>  ef93337 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/HostsRepositoryVersionCheck.java
>  eaa0096 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/MapReduce2JobHistoryStatePreservingCheck.java
>  5f02c4f 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/SecondaryNamenodeDeletedCheck.java
>  493042f 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/ServicesMaintenanceModeCheck.java
>  5108afd 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/ServicesMapReduceDistributedCacheCheck.java
>  be5d11a 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/ServicesNamenodeHighAvailabilityCheck.java
>  d92f12d 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/ServicesNamenodeTruncateCheck.java
>  51369c9 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/ServicesTezDistributedCacheCheck.java
>  68a7103 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/ServicesUpCheck.java
>  70b8884 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/ServicesYarnWorkPreservingCheck.java
>  a0b2b59 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/UpgradeCheck.java 
> 9fa8916 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/UpgradeCheckRegistry.java
>  8be572c 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/YarnRMHighAvailabilityCheck.java
>  bf25f9f 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/YarnTimelineServerStatePreservingCheck.java
>  eca0967 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java
>  2bda16e 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
>  aa51d4e 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/PrereqCheckRequest.java
>  f8c5316 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java
>  7030d23 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/CompatibleRepositoryVersionResourceProvider.java
>  6344aa2 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/PreUpgradeCheckResourceProvider.java
>  ce58e1e 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProvider.java
>  f1fa3bf 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
>  c00e64b 
>   
> ambari-server/src/main/java/org/apache/ambari/server/metadata/ActionMetadata.java
>

Re: Review Request 39244: Stop-and-Start Upgrade: Merge branch branch-dev-stop-all-upgrade to branch-2.1 for feature Stop-the-World Upgrade, aka Express Upgrade

2015-10-12 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39244/#review102322
---

Ship it!


Ship It!

- Mahadev Konar


On Oct. 12, 2015, 9:05 p.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39244/
> ---
> 
> (Updated Oct. 12, 2015, 9:05 p.m.)
> 
> 
> Review request for Ambari, Dmytro Grinenko, Dmitro Lisnichenko, Jonathan 
> Hurley, and Nate Cole.
> 
> 
> Bugs: AMBARI-13392
> https://issues.apache.org/jira/browse/AMBARI-13392
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Merge branch branch-dev-sotp-all-upgrade to branch-2.1
> This contains all of the work that Dmitry Lisnichenko, Dmytro Grinenko, and I 
> have done for the past 2 months.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/services/AmbariMetaInfo.java
>  561b3f4 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/AbstractCheckDescriptor.java
>  2f0bc94 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/ClientRetryPropertyCheck.java
>  52fca40 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/ConfigurationMergeCheck.java
>  b81ca11 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/HiveDynamicServiceDiscoveryCheck.java
>  4ea5484 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/HiveMultipleMetastoreCheck.java
>  c387a4b 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/HostsHeartbeatCheck.java
>  a8600c4 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/HostsMasterMaintenanceCheck.java
>  ef93337 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/HostsRepositoryVersionCheck.java
>  eaa0096 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/MapReduce2JobHistoryStatePreservingCheck.java
>  5f02c4f 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/SecondaryNamenodeDeletedCheck.java
>  493042f 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/ServicesMaintenanceModeCheck.java
>  5108afd 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/ServicesMapReduceDistributedCacheCheck.java
>  be5d11a 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/ServicesNamenodeHighAvailabilityCheck.java
>  d92f12d 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/ServicesNamenodeTruncateCheck.java
>  51369c9 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/ServicesTezDistributedCacheCheck.java
>  68a7103 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/ServicesUpCheck.java
>  70b8884 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/ServicesYarnWorkPreservingCheck.java
>  a0b2b59 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/UpgradeCheck.java 
> 9fa8916 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/UpgradeCheckRegistry.java
>  8be572c 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/YarnRMHighAvailabilityCheck.java
>  bf25f9f 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/YarnTimelineServerStatePreservingCheck.java
>  eca0967 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java
>  2bda16e 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
>  aa51d4e 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/PrereqCheckRequest.java
>  f8c5316 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java
>  7030d23 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/CompatibleRepositoryVersionResourceProvider.java
>  6344aa2 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/PreUpgradeCheckResourceProvider.java
>  ce58e1e 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProvider.java
>  f1fa3bf 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
>  c00e64b 
>   
> ambari-server/src/main/java/org/apache/ambari/server/metadata/ActionMetadata.java
>

[jira] [Updated] (AMBARI-13253) HBase service start fails after manual upgrade due to missing HBASE_REGION_SERVER_RPC_SCHEDULER_FACTORY_CLASS class

2015-09-27 Thread Mahadev konar (JIRA)


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

Mahadev konar updated AMBARI-13253:
---
Attachment: AMBARI-13253.patch

> HBase service start fails after manual upgrade due to missing 
> HBASE_REGION_SERVER_RPC_SCHEDULER_FACTORY_CLASS class
> ---
>
> Key: AMBARI-13253
> URL: https://issues.apache.org/jira/browse/AMBARI-13253
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.1.2
>    Reporter: Mahadev konar
>    Assignee: Mahadev konar
> Fix For: 2.1.2
>
> Attachments: AMBARI-13253.patch
>
>
> HBase service start fails after manual upgrade due to missing 
> HBASE_REGION_SERVER_RPC_SCHEDULER_FACTORY_CLASS class



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

[jira] [Created] (AMBARI-13253) HBase service start fails after manual upgrade due to missing HBASE_REGION_SERVER_RPC_SCHEDULER_FACTORY_CLASS class

2015-09-27 Thread Mahadev konar (JIRA)

Mahadev konar created AMBARI-13253:
--

 Summary: HBase service start fails after manual upgrade due to 
missing HBASE_REGION_SERVER_RPC_SCHEDULER_FACTORY_CLASS class
 Key: AMBARI-13253
 URL: https://issues.apache.org/jira/browse/AMBARI-13253
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.1.2
Reporter: Mahadev konar
Assignee: Mahadev konar
 Fix For: 2.1.2


HBase service start fails after manual upgrade due to missing 
HBASE_REGION_SERVER_RPC_SCHEDULER_FACTORY_CLASS class



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

Re: Review Request 38788: RU - HDFS_Client restart and hdp-select causes dfs_data_dir_mount.hist to be lost

2015-09-26 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/38788/#review100769
---


Is there a default for hadoop-env we need to change?

- Mahadev Konar


On Sept. 27, 2015, 2:36 a.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/38788/
> ---
> 
> (Updated Sept. 27, 2015, 2:36 a.m.)
> 
> 
> Review request for Ambari, Dmytro Sen, Jayush Luniya, Mahadev Konar, and 
> Sumit Mohanty.
> 
> 
> Bugs: AMBARI-13251
> https://issues.apache.org/jira/browse/AMBARI-13251
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> During the Clients group of RU, restarting hdfs_client changes changes the 
> symlink /usr/hdp/current/hadoop-client/ from the old version to the new 
> version.
> 
> Because the Data Dir Mount History file is stored at 
> /etc/hadoop/conf/dfs_data_dir_mount.hist and
> /etc/hadoop/conf symlinks to /usr/hdp/current/hadoop-client/conf 
> it means that the file must be copied to the new location.
> 
> Multiple clients (HDFS, HBase, Hive, YARN, MapReduce, Pig, Slider, Tez) 
> actually end up calling
> {code}
> hdp_select.select("hadoop-client", params.version)
> {code}
> that changes the symlink, so the first one to be ran during RU must copy the 
> file. If DataNode is present, it means that HDFS Client is guaranteed to be 
> there, and from all of those clients it is the first one in the Upgrade Pack.
> 
> During a Rolling Downgrade, the file should already exist in the previous 
> version, and the file is only written to when DataNode is restarted, so we 
> are ok.
> 
> 
> Diffs
> -
> 
>   ambari-agent/src/main/python/ambari_agent/Controller.py 8746172 
>   
> ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog212.java
>  37a87ab 
> 
> Diff: https://reviews.apache.org/r/38788/diff/
> 
> 
> Testing
> ---
> 
> Tested the alert during RU, and the mount history file was copied to the new 
> location, so no warnings were generated.
> 
> Python unit tests passed,
> --
> Total run:805
> Total errors:0
> Total failures:0
> OK
> 
> 
> Thanks,
> 
> Alejandro Fernandez
> 
>

[jira] [Commented] (AMBARI-13249) Fix unit test failure in trunk

2015-09-26 Thread Mahadev konar (JIRA)


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

Mahadev konar commented on AMBARI-13249:


+1

> Fix unit test failure in trunk
> --
>
> Key: AMBARI-13249
> URL: https://issues.apache.org/jira/browse/AMBARI-13249
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.2.0
>
> Attachments: AMBARI-13249.patch
>
>
> Fix unit test failure caused by AMBARI-12510
> ==
> FAIL: test_get_postgre_status (TestAmbariServer.TestAmbariServer)
> --
> Traceback (most recent call last):
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-common/src/test/python/mock/mock.py",
>  line 1199, in patched
> return func(*args, **keywargs)
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/TestAmbariServer.py",
>  line 2916, in test_get_postgre_status
> self.assertEqual("running", pg_status)
> AssertionError: 'running' != None



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

Re: Review Request 38676: [SWU] multiple service checks failed (possibly, Illegal capacity of 0.0 for children)

2015-09-23 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/38676/#review100243
---

Ship it!


Ship It!

- Mahadev Konar


On Sept. 23, 2015, 5:44 p.m., Dmitro Lisnichenko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/38676/
> ---
> 
> (Updated Sept. 23, 2015, 5:44 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Dmytro Grinenko, Jonathan 
> Hurley, and Nate Cole.
> 
> 
> Bugs: AMBARI-13207
> https://issues.apache.org/jira/browse/AMBARI-13207
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Multiple service checks failed during RU.
> 
> Root cause is two properties that should not be present in YARN config
> 
> Current review request applies to branch-dev-stop-all-upgrade
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml 
> d482c09 
> 
> Diff: https://reviews.apache.org/r/38676/diff/
> 
> 
> Testing
> ---
> 
> Running manual test of RU on live cluster
> 
> 
> Thanks,
> 
> Dmitro Lisnichenko
> 
>

Re: Review Request 38677: RU multiple service checks failed (possibly, Illegal capacity of 0.0 for children)

2015-09-23 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/38677/#review100242
---

Ship it!


Ship It!

- Mahadev Konar


On Sept. 23, 2015, 5:44 p.m., Dmitro Lisnichenko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/38677/
> ---
> 
> (Updated Sept. 23, 2015, 5:44 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Dmytro Grinenko, Jonathan 
> Hurley, and Nate Cole.
> 
> 
> Bugs: AMBARI-13207
> https://issues.apache.org/jira/browse/AMBARI-13207
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Multiple service checks failed during RU.
> 
> Root cause is two properties that should not be present in YARN config
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.3.xml 
> 62d26a2 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3.GlusterFS/services/YARN/configuration/capacity-scheduler.xml
>  1642746 
>   
> ambari-server/src/main/resources/upgrade/catalog/UpgradeCatalog_2.1_to_2.3.json
>  9d2fcd1 
>   
> ambari-server/src/main/resources/upgrade/catalog/UpgradeCatalog_2.2_to_2.3.json
>  6b8809a 
> 
> Diff: https://reviews.apache.org/r/38677/diff/
> 
> 
> Testing
> ---
> 
> Still running manual check of RU on live cluster using the same HDP build 
> versions as at initial test case
> 
> 
> Thanks,
> 
> Dmitro Lisnichenko
> 
>

Re: Review Request 38559: [Upgrade] Check CONFIG_MERGE failed error message is consistently reported in ambari-server log

2015-09-21 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/38559/#review99769
---

Ship it!


Ship It!

- Mahadev Konar


On Sept. 21, 2015, 5:19 p.m., Dmitro Lisnichenko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/38559/
> ---
> 
> (Updated Sept. 21, 2015, 5:19 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Andrew Onischuk, Jaimin 
> Jetly, Jonathan Hurley, and Nate Cole.
> 
> 
> Bugs: AMBARI-13152
> https://issues.apache.org/jira/browse/AMBARI-13152
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Current issue is caused by commit AMBARI-13107 ("After successful install of 
> Oozie via blueprint, oozie has an invalid configuration") . Mentioned commit 
> removes few "value" sections from service metainfo. That's why some 
> properties in stack metainfo may have null values. 
> 
> A litle more details about the case I'm fixing:
> Both previous stack value and next stack value are null (not defined in 
> metainfo to avoid parsing by blueprint). But runtime property value after 
> upgrade is not-null (added by UpgradeCatalog). I'm fixing exactly this case, 
> other cases (only new or old stack property value is null and other is not) 
> are a way different because of bug nature.
> 
> UPD we decided to commit the fix to 2.1.2 as well since mentioned patch is 
> hard to revert (other patches are based on it)
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/ConfigMergeHelper.java
>  9a2c604 
> 
> Diff: https://reviews.apache.org/r/38559/diff/
> 
> 
> Testing
> ---
> 
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Ambari Views .. SUCCESS [3.262s]
> [INFO] Ambari Metrics Common . SUCCESS [1.659s]
> [INFO] Ambari Server . SUCCESS 
> [53:43.587s]
> [INFO] Ambari Agent .. SUCCESS [9.281s]
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 53:58.376s
> [INFO] Finished at: Mon Sep 21 18:54:27 EEST 2015
> [INFO] Final Memory: 73M/1692M
> 
> 
> Thanks,
> 
> Dmitro Lisnichenko
> 
>

[jira] [Commented] (AMBARI-13069) Attributes of configuration property should be stack API driven

2015-09-18 Thread Mahadev konar (JIRA)


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

Mahadev konar commented on AMBARI-13069:


+1 on the patch for backport to 2.1.

> Attributes of configuration property should be stack API driven
> ---
>
> Key: AMBARI-13069
> URL: https://issues.apache.org/jira/browse/AMBARI-13069
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server, ambari-web, stacks
>Affects Versions: 2.1.3
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
> Fix For: 2.1.3
>
> Attachments: AMBARI-13069.patch, AMBARI-13069_2.patch, 
> AMBARI-13069_3.patch, AMBARI-13069_4.patch, AMBARI-13069_branch-2.1.3.patch
>
>
> *Following attributes of configuration properties should be made stack API 
> driven:*
> # Visibility of configuration property
> # display name of configuration property
> # Empty value validity of configuration property
> # Restriction of being configured only once on installation
> # overridable in config host group
> # Name of the property should be hidden
> # Unit of the property
> *Achieving this task will be useful in following scenarios:*
> # custom services could be added with less changes in ambari-web code
> # Any issues related to configuration property attributes encountered on a 
> deployed cluster can be addressed by making stack changes rather than 
> redeploying ambari-web code with a fix. For example if a property tagged as 
> not overridable if later desired to be made overridable on a deployed cluster 
> will now require changing a boolean flag in stack configuration property 
> rather than changing ambari-web code. 
> # Config property only in a specific stack can be attributed without writing 
> stack specific logic in ambari-web



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

Re: Review Request 38310: RU: Debian7 fails with multiple service check issues

2015-09-11 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/38310/#review98637
---

Ship it!


Ship It!

- Mahadev Konar


On Sept. 11, 2015, 5:40 p.m., Andrew Onischuk wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/38310/
> ---
> 
> (Updated Sept. 11, 2015, 5:40 p.m.)
> 
> 
> Review request for Ambari and Mahadev Konar.
> 
> 
> Bugs: AMBARI-13077
> https://issues.apache.org/jira/browse/AMBARI-13077
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> -
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/package/scripts/service_check.py
>  e633dcb 
>   ambari-server/src/test/python/stacks/2.1/FALCON/test_service_check.py 
> bb0ce90 
> 
> Diff: https://reviews.apache.org/r/38310/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Andrew Onischuk
> 
>

Re: Review Request 38310: RU: Debian7 fails with multiple service check issues

2015-09-11 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/38310/#review98639
---


Please make sure HDP 2.2 works fine with these changes.

- Mahadev Konar


On Sept. 11, 2015, 5:40 p.m., Andrew Onischuk wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/38310/
> ---
> 
> (Updated Sept. 11, 2015, 5:40 p.m.)
> 
> 
> Review request for Ambari and Mahadev Konar.
> 
> 
> Bugs: AMBARI-13077
> https://issues.apache.org/jira/browse/AMBARI-13077
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> -
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/package/scripts/service_check.py
>  e633dcb 
>   ambari-server/src/test/python/stacks/2.1/FALCON/test_service_check.py 
> bb0ce90 
> 
> Diff: https://reviews.apache.org/r/38310/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Andrew Onischuk
> 
>

[jira] [Commented] (AMBARI-13062) Ambari Headless principal for Storm should include cluster name

2015-09-10 Thread Mahadev konar (JIRA)


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

Mahadev konar commented on AMBARI-13062:


+1 for the patch.

> Ambari Headless principal for Storm should include cluster name
> ---
>
> Key: AMBARI-13062
> URL: https://issues.apache.org/jira/browse/AMBARI-13062
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.1.2
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
> Fix For: 2.1.2
>
> Attachments: AMBARI-13062.patch
>
>




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

[jira] [Updated] (AMBARI-13017) Installing falcon with blueprint, oozie extensions are missing, hence causing misconfigured installations that are using blueprint

2015-09-08 Thread Mahadev konar (JIRA)


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

Mahadev konar updated AMBARI-13017:
---
Assignee: Sandor Magyari

> Installing falcon with blueprint, oozie extensions are missing, hence causing 
> misconfigured installations that are using blueprint
> --
>
> Key: AMBARI-13017
> URL: https://issues.apache.org/jira/browse/AMBARI-13017
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0
> Environment: all
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
>Priority: Critical
> Fix For: 2.2.0
>
> Attachments: AMBARI-13017.patch
>
>
> PROBLEM: Installing falcon with blueprint, oozie extensions are missing, 
> hence causing misconfigured installations that are using blueprint. 
> For instance, on the sandbox which uses blueprint to install falcon(attached 
> to this bug) outputs the following for 
> grep -i ext /etc/oozie/conf/oozie-site.xml
> oozie.services.ext
> on a cluster that install falcon via add service via the webui, running grep 
> -i ext /etc/oozie/conf/oozie-site.xml produces 
> oozie.service.ELService.ext.functions.coord-action-create
> oozie.service.ELService.ext.functions.coord-sla-create
> oozie.service.ELService.ext.functions.coord-sla-submit
> Hence, the blueprint install will be missing needed properties.
> IMPACT: falcon will not operate as expected
> STEPS TO REPRODUCE:
> 1. Install cluster via ambari blueprint attached. 
> 2. view the oozie site and do grep -i ext /etc/oozie/conf/oozie-site.xml
> 3. Install cluster via ambari webui UI 
> 4. view the oozie site and do grep -i ext /etc/oozie/conf/oozie-site.xml you 
> should proper complete set of configs.



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

[jira] [Updated] (AMBARI-13017) Installing falcon with blueprint, oozie extensions are missing, hence causing misconfigured installations that are using blueprint

2015-09-08 Thread Mahadev konar (JIRA)


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

Mahadev konar updated AMBARI-13017:
---
Fix Version/s: 2.2.0

> Installing falcon with blueprint, oozie extensions are missing, hence causing 
> misconfigured installations that are using blueprint
> --
>
> Key: AMBARI-13017
> URL: https://issues.apache.org/jira/browse/AMBARI-13017
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0
> Environment: all
>Reporter: Sandor Magyari
>Priority: Critical
> Fix For: 2.2.0
>
> Attachments: AMBARI-13017.patch
>
>
> PROBLEM: Installing falcon with blueprint, oozie extensions are missing, 
> hence causing misconfigured installations that are using blueprint. 
> For instance, on the sandbox which uses blueprint to install falcon(attached 
> to this bug) outputs the following for 
> grep -i ext /etc/oozie/conf/oozie-site.xml
> oozie.services.ext
> on a cluster that install falcon via add service via the webui, running grep 
> -i ext /etc/oozie/conf/oozie-site.xml produces 
> oozie.service.ELService.ext.functions.coord-action-create
> oozie.service.ELService.ext.functions.coord-sla-create
> oozie.service.ELService.ext.functions.coord-sla-submit
> Hence, the blueprint install will be missing needed properties.
> IMPACT: falcon will not operate as expected
> STEPS TO REPRODUCE:
> 1. Install cluster via ambari blueprint attached. 
> 2. view the oozie site and do grep -i ext /etc/oozie/conf/oozie-site.xml
> 3. Install cluster via ambari webui UI 
> 4. view the oozie site and do grep -i ext /etc/oozie/conf/oozie-site.xml you 
> should proper complete set of configs.



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

[jira] [Commented] (AMBARI-12985) Ranger KMS server install fails for PHD

2015-09-02 Thread Mahadev konar (JIRA)


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

Mahadev konar commented on AMBARI-12985:


+1 looks good.

> Ranger KMS server install fails for PHD
> ---
>
> Key: AMBARI-12985
> URL: https://issues.apache.org/jira/browse/AMBARI-12985
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.2
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.1.2
>
> Attachments: BUG-43792.patch
>
>
> Incorrect package version.



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

[jira] [Commented] (AMBARI-12952) Add SPARK and RANGER services to PHD

2015-08-31 Thread Mahadev konar (JIRA)


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

Mahadev konar commented on AMBARI-12952:


+1 for the patch.

> Add SPARK and RANGER services to PHD
> 
>
> Key: AMBARI-12952
> URL: https://issues.apache.org/jira/browse/AMBARI-12952
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.1
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Blocker
> Fix For: 2.1.2
>
> Attachments: phd_ranger_spark.patch
>
>




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

[jira] [Commented] (AMBARI-12925) [PluggableStackDefinition] Update SAPHD versioning

2015-08-28 Thread Mahadev konar (JIRA)


[ 
https://issues.apache.org/jira/browse/AMBARI-12925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14720633#comment-14720633
 ] 

Mahadev konar commented on AMBARI-12925:


+1 for the patch.

 [PluggableStackDefinition] Update SAPHD versioning
 --

 Key: AMBARI-12925
 URL: https://issues.apache.org/jira/browse/AMBARI-12925
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.1.2
Reporter: Jayush Luniya
Assignee: Jayush Luniya
 Fix For: 2.1.2

 Attachments: AMBARI-12925.patch






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

Re: Review Request 37901: Update Apache site with 2.1.1 release

2015-08-28 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/37901/#review96918
---

Ship it!


Ship It!

- Mahadev Konar


On Aug. 28, 2015, 7:05 p.m., Nate Cole wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/37901/
 ---
 
 (Updated Aug. 28, 2015, 7:05 p.m.)
 
 
 Review request for Ambari, Jayush Luniya and Mahadev Konar.
 
 
 Bugs: AMBARI-12922
 https://issues.apache.org/jira/browse/AMBARI-12922
 
 
 Repository: ambari
 
 
 Description
 ---
 
 Updated various files for 2.1.1.
 
 
 Diffs
 -
 
   docs/pom.xml 0ab6bf0 
   docs/src/site/apt/index.apt 761b6f3 
   docs/src/site/apt/whats-new.apt 1bd87f2 
   docs/src/site/site.xml 24a9a34 
 
 Diff: https://reviews.apache.org/r/37901/diff/
 
 
 Testing
 ---
 
 No tests, only doc.
 
 
 Thanks,
 
 Nate Cole

[jira] [Commented] (AMBARI-12775) [PluggableStackDefinition] Update PHD version mapping

2015-08-14 Thread Mahadev konar (JIRA)


[ 
https://issues.apache.org/jira/browse/AMBARI-12775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697925#comment-14697925
 ] 

Mahadev konar commented on AMBARI-12775:


+1 for the patch.

 [PluggableStackDefinition] Update PHD version mapping
 -

 Key: AMBARI-12775
 URL: https://issues.apache.org/jira/browse/AMBARI-12775
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.1.1
Reporter: Jayush Luniya
Assignee: Jayush Luniya
Priority: Critical
 Fix For: 2.1.1

 Attachments: AMBARI-12775.patch






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

[jira] [Commented] (AMBARI-12728) Review Page at the Install wizard doesn't load completely when oozie is selected for installation

2015-08-11 Thread Mahadev konar (JIRA)


[ 
https://issues.apache.org/jira/browse/AMBARI-12728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14692320#comment-14692320
 ] 

Mahadev konar commented on AMBARI-12728:


+1 for the patch.

 Review Page at the Install wizard doesn't load completely when oozie is 
 selected for installation
 -

 Key: AMBARI-12728
 URL: https://issues.apache.org/jira/browse/AMBARI-12728
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.1.1
Reporter: Jaimin D Jetly
Assignee: Jaimin D Jetly
Priority: Critical
 Fix For: 2.1.1

 Attachments: AMBARI-12728.patch






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

Re: Review Request 37359: Remove Debian + Ubuntu support for HDP 2.3 in Ambari 2.1.1.

2015-08-11 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/37359/#review94945
---

Ship it!


Ship It!

- Mahadev Konar


On Aug. 11, 2015, 5:22 p.m., Dmytro Sen wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/37359/
 ---
 
 (Updated Aug. 11, 2015, 5:22 p.m.)
 
 
 Review request for Ambari, Mahadev Konar and Vitalyi Brodetskyi.
 
 
 Bugs: AMBARI-12725
 https://issues.apache.org/jira/browse/AMBARI-12725
 
 
 Repository: ambari
 
 
 Description
 ---
 
 Remove Debian + Ubuntu support for HDP 2.3 in Ambari 2.1.1.
 
 
 Diffs
 -
 
   ambari-server/src/main/resources/stacks/HDP/2.3/repos/repoinfo.xml 142b87d 
 
 Diff: https://reviews.apache.org/r/37359/diff/
 
 
 Testing
 ---
 
 Unit tests passed
 
 
 Thanks,
 
 Dmytro Sen

Re: [VOTE] Apache Ambari Release 2.0.2 RC2

2015-08-04 Thread Mahadev Konar

+1

On 8/3/15, 6:39 PM, Alejandro Fernandez alejan...@apache.org wrote:

Hi,

I have created an Apache Ambari 2.0.2 Release Candidate (RC2). This is a
maintenance release for branch-2.0.maint

GIT source tag:
*https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=
refs/tags/release-2.0.2-rc2
https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=
refs/tags/release-2.0.2-rc2*

Staging site: http://people.apache.org/~alejandro/apache-ambari-2.0.2-rc2/

PGP release key used (signed using 392F57AC):
http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x2147F220392F57AC

Updated KEYS file: https://dist.apache.org/repos/dist/release/ambari/KEYS

One can look into the issues fixed in this release at
https://issues.apache.org/jira/browse/AMBARI/fixforversion/12332747
Total 2.0.2 JIRAs: 13
Total JIRAs Resolved as Fixed: 13

Vote will be open for 72 hours.
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Here's my vote to start: +1

Here's how to verify the tarball hashes:

git clone --branch release-2.0.2-rc2
https://git-wip-us.apache.org/repos/asf/ambari.git apache-ambari-2.0.2-src
cd apache-ambari-2.0.2-src
git clean -xdf
cd ambari-web
npm install
ulimit -n 2048
brunch build
rm -rf node_modules
mv public public-static
cd ../..
tar --exclude=.git --exclude=.gitignore --exclude=.gitattributes -zcvf
apache-ambari-2.0.2-src.tar.gz apache-ambari-2.0.2-src

# Verify my signature,
gpg --verify apache-ambari-2.0.2-src.tar.gz.asc
apache-ambari-2.0.2-src.tar.gz
gpg: Signature made Fri Jul 31 18:36:49 2015 PDT using RSA key ID 392F57AC
gpg: Good signature from Alejandro Fernandez (Apache Ambari Release
Management) alejan...@apache.org

openssl md5 apache-ambari-2.0.2-src.tar.gz 
apache-ambari-2.0.2-src.tar.gz.md5# and compare to the file I provided
openssl sha1 apache-ambari-2.0.2-src.tar.gz 
apache-ambari-2.0.2-src.tar.gz.sha1  # and compare to the file I provided

# I made sure ratcheck passes
cp -R apache-ambari-2.0.2-src apache-ambari-2.0.2-ratcheck
cd apache-ambari-2.0.2-ratcheck
mvn clean apache-rat:check

Thanks,
Alejandro Fernandez
Apache Ambari PMC

Re: Review Request 36882: Ambari-server reset action works incorrectly for external DB

2015-08-03 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36882/#review93870
---

Ship it!


Ship It!

- Mahadev Konar


On July 28, 2015, 9:12 a.m., Vitalyi Brodetskyi wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/36882/
 ---
 
 (Updated July 28, 2015, 9:12 a.m.)
 
 
 Review request for Ambari, Andrew Onischuk and Dmytro Sen.
 
 
 Bugs: AMBARI-12560
 https://issues.apache.org/jira/browse/AMBARI-12560
 
 
 Repository: ambari
 
 
 Description
 ---
 
 Ambari tries to drop DB schema during reset ever it is external DB, and fails 
 during this process.
 
 {code}
 ambari-framework-selftest-sle113-8508-split1-re2-5:~ # cat 
 /etc/ambari-server/conf/ambari.properties |grep server.persistence.type
 server.persistence.type=remote
 ambari-framework-selftest-sle113-8508-split1-re2-5:~ # ambari-server reset -s
 Using python  /usr/bin/python2.6
 Resetting ambari-server
  WARNING  You are about to reset and clear the Ambari Server 
 database. This will remove all cluster host and configuration information 
 from the database. You will be required to re-configure the Ambari server and 
 re-run the cluster wizard. 
 Are you SURE you want to perform the reset [yes/no] (yes)? 
 Confirm server reset [yes/no](yes)? 
 Resetting the Server database...
 ERROR: Exiting with exit code 1. 
 REASON: psql: could not connect to server: No such file or directory
   Is the server running locally and accepting
   connections on Unix domain socket /tmp/.s.PGSQL.5432?
 {code}
 
 
 Diffs
 -
 
   ambari-server/src/main/python/ambari_server/serverSetup.py e76d2bc 
 
 Diff: https://reviews.apache.org/r/36882/diff/
 
 
 Testing
 ---
 
 mvn clean test
 
 
 Thanks,
 
 Vitalyi Brodetskyi

[jira] [Commented] (AMBARI-12623) [PluggableStackDefinition] Integrate pluggable stack definition into build

2015-08-03 Thread Mahadev konar (JIRA)


[ 
https://issues.apache.org/jira/browse/AMBARI-12623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652113#comment-14652113
 ] 

Mahadev konar commented on AMBARI-12623:


+1 for the patch.

 [PluggableStackDefinition] Integrate pluggable stack definition into build
 --

 Key: AMBARI-12623
 URL: https://issues.apache.org/jira/browse/AMBARI-12623
 Project: Ambari
  Issue Type: Bug
  Components: stacks
Affects Versions: 2.1.0
Reporter: Sumit Mohanty
Assignee: Sumit Mohanty
 Fix For: 2.1.1

 Attachments: AMBARI-12623.patch


 Locations of resources in a stack deployed by Ambari should be pluggable to 
 allow for different stack layouts.



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

Re: [VOTE] Apache Ambari Release 2.0.2 RC1

2015-08-02 Thread Mahadev Konar

+1 for the release. Downloaded and checked for the signature.



On 7/31/15, 6:47 PM, Alejandro Fernandez alejan...@apache.org wrote:

Hi,

I have created an Apache Ambari 2.0.2 Release Candidate (RC1). This is a
maintenance release for branch-2.0.maint

GIT source tag:
*https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=
refs/tags/release-2.0.2-rc1
https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=
refs/tags/release-2.0.2-rc1*

Staging site: http://people.apache.org/~alejandro/apache-ambari-2.0.2-rc1/

PGP release key used (signed using 392F57AC):
http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x2147F220392F57AC

Updated KEYS file: https://dist.apache.org/repos/dist/release/ambari/KEYS

One can look into the issues fixed in this release at
https://issues.apache.org/jira/browse/AMBARI/fixforversion/12332747
Total 2.0.2 JIRAs: 12
Total JIRAs Resolved as Fixed: 12

Vote will be open for 72 hours.
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Here's my vote to start: +1

Here's how to verify the tarball hashes:

git clone --branch release-2.0.2-rc1
https://git-wip-us.apache.org/repos/asf/ambari.git apache-ambari-2.0.2-src
cd apache-ambari-2.0.2-src
git clean -xdf
cd ambari-web
npm install
ulimit -n 2048
brunch build
rm -rf node_modules
mv public public-static
cd ../..
tar --exclude=.git --exclude=.gitignore --exclude=.gitattributes -zcvf
apache-ambari-2.0.2-src.tar.gz apache-ambari-2.0.2-src

# Verify my signature,
gpg --verify apache-ambari-2.0.2-src.tar.gz.asc
apache-ambari-2.0.2-src.tar.gz
gpg: Signature made Fri Jul 31 18:36:49 2015 PDT using RSA key ID 392F57AC
gpg: Good signature from Alejandro Fernandez (Apache Ambari Release
Management) alejan...@apache.org

openssl md5 apache-ambari-2.0.2-src.tar.gz 
apache-ambari-2.0.2-src.tar.gz.md5# and compare to the file I provided
openssl sha1 apache-ambari-2.0.2-src.tar.gz 
apache-ambari-2.0.2-src.tar.gz.sha1  # and compare to the file I provided

# I made sure ratcheck passes
cp -R apache-ambari-2.0.2-src apache-ambari-2.0.2-ratcheck
cd apache-ambari-2.0.2-ratcheck
mvn clean apache-rat:check

Thanks,
Alejandro Fernandez
Apache Ambari PMC

[jira] [Resolved] (AMBARI-12538) Attempting to access the Ambari Dashboard results in an HTTP 500 Error after changing cluster name and restarting the Ambari server

2015-07-31 Thread Mahadev konar (JIRA)


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

Mahadev konar resolved AMBARI-12538.

Resolution: Fixed

Resolved via: 

{{b04fb76 Thu May 28 17:53:02 EEST 2015 Jonathan Hurley 
jhur...@hortonworks.com AMBARI-11487 - Changed Configurations During Upgrade 
Are Reverted During Finalize (jonathanhurley)}}
Anyway, cluster name was updated successfully at DB

 Attempting to access the Ambari Dashboard results in an HTTP 500 Error after 
 changing cluster name and restarting the Ambari server
 ---

 Key: AMBARI-12538
 URL: https://issues.apache.org/jira/browse/AMBARI-12538
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.1.0
 Environment: SLES11 SP3
Reporter: Zack Marsh
Priority: Critical
 Fix For: 2.1.1


 Steps to reproduce:
 * Login to Ambari Web UI
 * Rename cluster  (Admin - Manage Ambari - Rename Cluister - Enter new 
 name )
 * Restart Ambari Server via CLI (ambari-server restart)
 * Login to Ambari Web UI again
 * When attempting to access the Ambari Dashboard an HTTP 500 Error will occur:
 {code}
 Error
 500 status code received on GET method for API: 
 /api/v1/clusters/CLUSTERNAME/requests?to=endpage_size=10fields=Requests 
 Error message: Server Error
 {code}
 Excerpt from the Ambari Server log:
 {code}
 24 Jul 2015 16:40:41,013 ERROR [qtp-client-25] ReadHandler:91 - Caught a 
 runtime exception executing a query
 java.lang.RuntimeException: Failed to construct logical request during 
 replay: org.apache.ambari.server.ClusterNotFoundException: Cluster not found, 
 clusterName=PIRIPIRI
 at 
 org.apache.ambari.server.topology.PersistedStateImpl.getAllRequests(PersistedStateImpl.java:167)
 at 
 org.apache.ambari.server.topology.TopologyManager.ensureInitialized(TopologyManager.java:91)
 at 
 org.apache.ambari.server.topology.TopologyManager.getRequests(TopologyManager.java:198)
 at 
 org.apache.ambari.server.actionmanager.ActionManager.getRequestsByStatus(ActionManager.java:232)
 at 
 org.apache.ambari.server.controller.internal.RequestResourceProvider.getRequestResources(RequestResourceProvider.java:414)
 at 
 org.apache.ambari.server.controller.internal.RequestResourceProvider.getResources(RequestResourceProvider.java:200)
 at 
 org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:945)
 at 
 org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:132)
 at 
 org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:482)
 at 
 org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:381)
 at 
 org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:217)
 at 
 org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:68)
 at 
 org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:135)
 at 
 org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:105)
 at 
 org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:74)
 at 
 org.apache.ambari.server.api.services.RequestService.getRequests(RequestService.java:95)
 at sun.reflect.GeneratedMethodAccessor112.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:483)
 at 
 com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
 at 
 com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
 at 
 com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
 at 
 com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
 at 
 com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
 at 
 com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
 at 
 com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
 at 
 com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
 at 
 com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
 at 
 com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest

[jira] [Updated] (AMBARI-12538) Attempting to access the Ambari Dashboard results in an HTTP 500 Error after changing cluster name and restarting the Ambari server

2015-07-31 Thread Mahadev konar (JIRA)


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

Mahadev konar updated AMBARI-12538:
---
Fix Version/s: 2.1.1

 Attempting to access the Ambari Dashboard results in an HTTP 500 Error after 
 changing cluster name and restarting the Ambari server
 ---

 Key: AMBARI-12538
 URL: https://issues.apache.org/jira/browse/AMBARI-12538
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.1.0
 Environment: SLES11 SP3
Reporter: Zack Marsh
Priority: Critical
 Fix For: 2.1.1


 Steps to reproduce:
 * Login to Ambari Web UI
 * Rename cluster  (Admin - Manage Ambari - Rename Cluister - Enter new 
 name )
 * Restart Ambari Server via CLI (ambari-server restart)
 * Login to Ambari Web UI again
 * When attempting to access the Ambari Dashboard an HTTP 500 Error will occur:
 {code}
 Error
 500 status code received on GET method for API: 
 /api/v1/clusters/CLUSTERNAME/requests?to=endpage_size=10fields=Requests 
 Error message: Server Error
 {code}
 Excerpt from the Ambari Server log:
 {code}
 24 Jul 2015 16:40:41,013 ERROR [qtp-client-25] ReadHandler:91 - Caught a 
 runtime exception executing a query
 java.lang.RuntimeException: Failed to construct logical request during 
 replay: org.apache.ambari.server.ClusterNotFoundException: Cluster not found, 
 clusterName=PIRIPIRI
 at 
 org.apache.ambari.server.topology.PersistedStateImpl.getAllRequests(PersistedStateImpl.java:167)
 at 
 org.apache.ambari.server.topology.TopologyManager.ensureInitialized(TopologyManager.java:91)
 at 
 org.apache.ambari.server.topology.TopologyManager.getRequests(TopologyManager.java:198)
 at 
 org.apache.ambari.server.actionmanager.ActionManager.getRequestsByStatus(ActionManager.java:232)
 at 
 org.apache.ambari.server.controller.internal.RequestResourceProvider.getRequestResources(RequestResourceProvider.java:414)
 at 
 org.apache.ambari.server.controller.internal.RequestResourceProvider.getResources(RequestResourceProvider.java:200)
 at 
 org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:945)
 at 
 org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:132)
 at 
 org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:482)
 at 
 org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:381)
 at 
 org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:217)
 at 
 org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:68)
 at 
 org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:135)
 at 
 org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:105)
 at 
 org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:74)
 at 
 org.apache.ambari.server.api.services.RequestService.getRequests(RequestService.java:95)
 at sun.reflect.GeneratedMethodAccessor112.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:483)
 at 
 com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
 at 
 com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
 at 
 com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
 at 
 com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
 at 
 com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
 at 
 com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
 at 
 com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
 at 
 com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
 at 
 com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
 at 
 com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
 at 
 com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
 at 
 com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest

[jira] [Updated] (AMBARI-12598) kafka_client_jaas.conf not being managed by Ambari

2015-07-31 Thread Mahadev konar (JIRA)


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

Mahadev konar updated AMBARI-12598:
---
Fix Version/s: (was: 2.1.0)
   2.1.1

 kafka_client_jaas.conf not being managed by Ambari
 --

 Key: AMBARI-12598
 URL: https://issues.apache.org/jira/browse/AMBARI-12598
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.1.0
Reporter: Sriharsha Chintalapani
Assignee: Sriharsha Chintalapani
 Fix For: 2.1.1


 when kafka gets kerberized we need 2 jaas files
 kafka_jaas.conf used by server
 kafka_client_jaas.conf used by kafka command line tools to connect to 
 kafka server.
 Only kafka_jaas.conf is being generated by Ambari where as 
 kafka_client_jaas.conf is coming from rpm. When user changes kafka service 
 principal names kafka_client_jaas.conf values are not being reflected causing 
 kafka-console-producer.sh and kafka-console-consumer.sh throw kerberos 
 exception UNKNOWN_SERVER.



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

[jira] [Commented] (AMBARI-12585) Flume cannot be deployed without HDFS

2015-07-29 Thread Mahadev konar (JIRA)


[ 
https://issues.apache.org/jira/browse/AMBARI-12585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646798#comment-14646798
 ] 

Mahadev konar commented on AMBARI-12585:


+1 for the patch.

 Flume cannot be deployed without HDFS
 -

 Key: AMBARI-12585
 URL: https://issues.apache.org/jira/browse/AMBARI-12585
 Project: Ambari
  Issue Type: Bug
  Components: stacks
Affects Versions: 2.1.0
Reporter: Sumit Mohanty
Assignee: Sumit Mohanty
Priority: Critical
 Fix For: 2.1.1

 Attachments: AMBARI-12585.patch


 Currently if user wants to install Flume they have to deploy HDFS. This is 
 unnecessary as Flume can write to remote HDFS locations and does not have 
 HDFS as dependency. For now user needs to deploy Flume with HDFS and shutdown 
 HDFS along with turning on maintenance mode. Storm and Kafka do not require 
 HDFS now.



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

[jira] [Updated] (AMBARI-12179) Tez View should automatically configuration settings based on http/https policy

2015-07-26 Thread Mahadev konar (JIRA)


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

Mahadev konar updated AMBARI-12179:
---
Fix Version/s: 2.1.1

 Tez View should automatically configuration settings based on http/https 
 policy
 ---

 Key: AMBARI-12179
 URL: https://issues.apache.org/jira/browse/AMBARI-12179
 Project: Ambari
  Issue Type: Bug
Reporter: Hitesh Shah
Assignee: Hitesh Shah
 Fix For: 2.1.1

 Attachments: AMBARI-12179.1.patch, AMBARI-12179.2.patch


 The current tez view impl always defaults to the http addresses instead of  
 relying on the http policy setting. 



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

[jira] [Commented] (AMBARI-12179) Tez View should automatically configuration settings based on http/https policy

2015-07-26 Thread Mahadev konar (JIRA)


[ 
https://issues.apache.org/jira/browse/AMBARI-12179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14642096#comment-14642096
 ] 

Mahadev konar commented on AMBARI-12179:


+1 the patch looks good. [~hitesh] wnat to go ahead and commit to trunk adn 
branch-2.1? 

 Tez View should automatically configuration settings based on http/https 
 policy
 ---

 Key: AMBARI-12179
 URL: https://issues.apache.org/jira/browse/AMBARI-12179
 Project: Ambari
  Issue Type: Bug
Reporter: Hitesh Shah
Assignee: Hitesh Shah
 Fix For: 2.1.1

 Attachments: AMBARI-12179.1.patch, AMBARI-12179.2.patch


 The current tez view impl always defaults to the http addresses instead of  
 relying on the http policy setting. 



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

Re: Review Request 36779: Ambari Cluster Deployment Stuck At 2% With A SQL Deadlock When Talking to SQL Azure

2015-07-24 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36779/#review92968
---

Ship it!


Ship It!

- Mahadev Konar


On July 24, 2015, 1:05 p.m., Jonathan Hurley wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/36779/
 ---
 
 (Updated July 24, 2015, 1:05 p.m.)
 
 
 Review request for Ambari, Alejandro Fernandez, Nate Cole, and Sumit Mohanty.
 
 
 Bugs: AMBARI-12526
 https://issues.apache.org/jira/browse/AMBARI-12526
 
 
 Repository: ambari
 
 
 Description
 ---
 
 When deploying a new cluster on SQL Azure, there is a recurring deadlock on 
 the SQL Server. 
 
 Essentially, we have concurrent UPDATE statements in separate transactions 
 acting on different rows of hostcomponentstate. This seems to cause a 
 deadlock because both processes have an X lock and then try to acquire a U 
 lock. The U lock is what is making me think they are trying to acquire the 
 table lock in order to update the cluster index.
 
 The solution was to:
 - Ensure that some of the failing transactions were placed within the scope 
 of our internal Java locks
 - flush writing to the problem table
 
 
 Diffs
 -
 
   
 ambari-server/src/main/java/org/apache/ambari/server/events/listeners/upgrade/HostVersionOutOfSyncListener.java
  c016cbd 
   
 ambari-server/src/main/java/org/apache/ambari/server/orm/dao/HostComponentStateDAO.java
  00ffd5a 
   ambari-server/src/main/java/org/apache/ambari/server/state/Host.java 
 7a53c21 
   ambari-server/src/main/java/org/apache/ambari/server/state/Service.java 
 1137cba 
   
 ambari-server/src/main/java/org/apache/ambari/server/state/ServiceComponent.java
  60a16eb 
   
 ambari-server/src/main/java/org/apache/ambari/server/state/ServiceComponentHost.java
  6917a15 
   
 ambari-server/src/main/java/org/apache/ambari/server/state/ServiceComponentImpl.java
  aa147de 
   ambari-server/src/main/java/org/apache/ambari/server/state/ServiceImpl.java 
 6484c9f 
   
 ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
  2b3bf05 
   
 ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClustersImpl.java
  90fdbec 
   
 ambari-server/src/main/java/org/apache/ambari/server/state/configgroup/ConfigGroupImpl.java
  a01f4d4 
   
 ambari-server/src/main/java/org/apache/ambari/server/state/host/HostImpl.java 
 e59f4aa 
   
 ambari-server/src/main/java/org/apache/ambari/server/state/svccomphost/ServiceComponentHostImpl.java
  b623479 
   
 ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ServiceComponentHostConcurrentWriteDeadlockTest.java
  PRE-CREATION 
 
 Diff: https://reviews.apache.org/r/36779/diff/
 
 
 Testing
 ---
 
 Deployed on SQL Azure about 50 times and did not see the deadlock occur. It 
 would normally occur in the first 5 cluster deployments.
 
 
 Thanks,
 
 Jonathan Hurley

Re: Review Request 36786: Update Blueprint deployment to wait for the configuration to be fully resolved prior to first install task

2015-07-24 Thread Mahadev Konar

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36786/#review92969
---

Ship it!

Ship It!

- Mahadev Konar

On July 24, 2015, 7:07 p.m., Robert Nettleton wrote:

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36786/
---

(Updated July 24, 2015, 7:07 p.m.)

Review request for Ambari, Jonathan Hurley, Mahadev Konar, Nate Cole, and
Sumit Mohanty.

Bugs: AMBARI-12532
https://issues.apache.org/jira/browse/AMBARI-12532

Repository: ambari

Description
---

This patch resolved AMBARI-12532.

When creating larger clusters (50+ nodes), there is an intermittent failure
that occurs, in which the configurations on the cluster are not always
completely resolved. This causes the Blueprint service install and host
tasks to sometimes fail, since the expected configuration is not yet present
across the entire cluster.

This is potentially a timing issue between the Blueprints processor and the
Ambari configuration engine.

This patch implements the following:
1. Adds a new method to the AmbariContext class, that will wait until all the
required configuration types enter the TOPOLOGY_RESOLVED phase, which
indicates that the configuration is ready across the entire cluster.
2. Calls this new method from within the Cluster configuration task. The
wait method will block until the desired configuration status is reached.
3. Adds new logging code in the Blueprints to show the status of the
configuration types and their resolution at cluster deployment time. Also
added logging throughout relevant classes in this area, in order to simplify
debugging of concurrency problems in the future.
4. Adds new unit tests, and updates existing tests to verify this change.

Diffs
-

ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
1ded566

ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java
14b13ef

ambari-server/src/main/java/org/apache/ambari/server/topology/AmbariContext.java
42676aa

ambari-server/src/main/java/org/apache/ambari/server/topology/ClusterConfigurationRequest.java
eb583fd

ambari-server/src/main/java/org/apache/ambari/server/topology/HostRequest.java
5d76f7a

ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java
7117b05

ambari-server/src/test/java/org/apache/ambari/server/topology/AmbariContextTest.java
4ebf9a9

Diff: https://reviews.apache.org/r/36786/diff/

Testing
---

1. Ran the ambari-server unit tests (mvn clean test), and all tests were
passing

Java unit test results:

Results :

Tests run: 3135, Failures: 0, Errors: 0, Skipped: 27

Python tests:

Total run:807
Total errors:0
Total failures:0
OK

2. Deployed a 3-node HDFS NameNode HA cluster using Blueprints, and verified
that this deployment completed successfully, and that the new expected
logging output is present in ambari-server.log.

Thanks,

Robert Nettleton

[jira] [Updated] (AMBARI-11526) Pluggable Stack Definition

2015-07-24 Thread Mahadev konar (JIRA)


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

Mahadev konar updated AMBARI-11526:
---
Summary: Pluggable Stack Definition  (was: White Label Stack Definition)

 Pluggable Stack Definition
 --

 Key: AMBARI-11526
 URL: https://issues.apache.org/jira/browse/AMBARI-11526
 Project: Ambari
  Issue Type: Task
  Components: ambari-server
Affects Versions: 2.1.0
Reporter: Eugene Chekanskiy
Assignee: Eugene Chekanskiy
 Fix For: 2.1.0






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

[jira] [Updated] (AMBARI-12490) Ranger plugin enable script in ambari tries to create amb_ranger_admin user even if it already exists

2015-07-22 Thread Mahadev konar (JIRA)


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

Mahadev konar updated AMBARI-12490:
---
Fix Version/s: 2.0.2

 Ranger plugin enable script in ambari tries to create amb_ranger_admin user 
 even if it already exists
 -

 Key: AMBARI-12490
 URL: https://issues.apache.org/jira/browse/AMBARI-12490
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.0.0
Reporter: Gautam Borad
Assignee: Gautam Borad
 Fix For: 2.0.2

 Attachments: AMBARI-12490.patch


 Since Ranger has api to get user by name, that can be used to get a 
 particular user rather than fetching a predefined number of users. 
 This will be a more robust design, compared to current one.



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

[jira] [Created] (AMBARI-12459) Change latest and baserurl to point to public json and public repo urls.

Mahadev konar created AMBARI-12459:
--

 Summary: Change latest and baserurl to point to public json and 
public repo urls.
 Key: AMBARI-12459
 URL: https://issues.apache.org/jira/browse/AMBARI-12459
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.1.0
Reporter: Mahadev konar
Assignee: Mahadev konar
 Fix For: 2.1.1


Change latest and baserurl to point to public json and public repo urls.



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

[jira] [Updated] (AMBARI-12459) Change latest and baserurl to point to public json and public repo urls.


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

Mahadev konar updated AMBARI-12459:
---
Attachment: AMBARI-12459.patch

 Change latest and baserurl to point to public json and public repo urls.
 

 Key: AMBARI-12459
 URL: https://issues.apache.org/jira/browse/AMBARI-12459
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.1.0
Reporter: Mahadev konar
Assignee: Mahadev konar
 Fix For: 2.1.1

 Attachments: AMBARI-12459.patch


 Change latest and baserurl to point to public json and public repo urls.



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

[jira] [Commented] (AMBARI-12459) Change latest and baserurl to point to public json and public repo urls.


[ 
https://issues.apache.org/jira/browse/AMBARI-12459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14633052#comment-14633052
 ] 

Mahadev konar commented on AMBARI-12459:


{code}
INFO] Reactor Summary:
[INFO] 
[INFO] Ambari Main ... SUCCESS [3.351s]
[INFO] Apache Ambari Project POM . SUCCESS [0.033s]
[INFO] Ambari Web  SUCCESS [33.129s]
[INFO] Ambari Views .. SUCCESS [1.257s]
[INFO] Ambari Admin View . SUCCESS [9.729s]
[INFO] ambari-metrics  SUCCESS [0.437s]
[INFO] Ambari Metrics Common . SUCCESS [0.604s]
[INFO] Ambari Metrics Hadoop Sink  SUCCESS [0.494s]
[INFO] Ambari Metrics Flume Sink . SUCCESS [0.334s]
[INFO] Ambari Metrics Kafka Sink . SUCCESS [0.351s]
[INFO] Ambari Metrics Storm Sink . SUCCESS [0.433s]
[INFO] Ambari Metrics Collector .. SUCCESS [41.015s]
[INFO] Ambari Metrics Monitor  SUCCESS [1.541s]
[INFO] Ambari Metrics Assembly ... SUCCESS [3:07.887s]
[INFO] Ambari Server . SUCCESS [38.039s]
[INFO] Ambari Agent .. SUCCESS [22.767s]
[INFO] Ambari Client . SUCCESS [0.030s]
[INFO] Ambari Python Client .. SUCCESS [0.341s]
[INFO] Ambari Groovy Client .. SUCCESS [2.093s]
[INFO] Ambari Shell .. SUCCESS [0.025s]
[INFO] Ambari Python Shell ... SUCCESS [0.030s]
[INFO] Ambari Groovy Shell ... SUCCESS [0.434s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 5:44.993s
[INFO] Finished at: Sun Jul 19 20:49:22 PDT 2015
[INFO] Final Memory: 132M/1534M

{code}

 Change latest and baserurl to point to public json and public repo urls.
 

 Key: AMBARI-12459
 URL: https://issues.apache.org/jira/browse/AMBARI-12459
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.1.0
Reporter: Mahadev konar
Assignee: Mahadev konar
 Fix For: 2.1.1

 Attachments: AMBARI-12459.patch


 Change latest and baserurl to point to public json and public repo urls.



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

[jira] [Commented] (AMBARI-12459) Change latest and baserurl to point to public json and public repo urls.


[ 
https://issues.apache.org/jira/browse/AMBARI-12459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14633051#comment-14633051
 ] 

Mahadev konar commented on AMBARI-12459:


Committed ot trunk and branch-2.1.

 Change latest and baserurl to point to public json and public repo urls.
 

 Key: AMBARI-12459
 URL: https://issues.apache.org/jira/browse/AMBARI-12459
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.1.0
Reporter: Mahadev konar
Assignee: Mahadev konar
 Fix For: 2.1.1

 Attachments: AMBARI-12459.patch


 Change latest and baserurl to point to public json and public repo urls.



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

[jira] [Resolved] (AMBARI-12459) Change latest and baserurl to point to public json and public repo urls.


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

Mahadev konar resolved AMBARI-12459.

Resolution: Fixed

 Change latest and baserurl to point to public json and public repo urls.
 

 Key: AMBARI-12459
 URL: https://issues.apache.org/jira/browse/AMBARI-12459
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.1.0
Reporter: Mahadev konar
Assignee: Mahadev konar
 Fix For: 2.1.1

 Attachments: AMBARI-12459.patch


 Change latest and baserurl to point to public json and public repo urls.



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

[jira] [Updated] (AMBARI-12457) HDP-2.2 deployment of webhcat should use /etc/tez/conf

2015-07-18 Thread Mahadev konar (JIRA)


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

Mahadev konar updated AMBARI-12457:
---
Assignee: Sumit Mohanty

 HDP-2.2 deployment of webhcat should use /etc/tez/conf
 --

 Key: AMBARI-12457
 URL: https://issues.apache.org/jira/browse/AMBARI-12457
 Project: Ambari
  Issue Type: Bug
  Components: stacks
Affects Versions: 2.1.0
Reporter: Sumit Mohanty
Assignee: Sumit Mohanty
Priority: Critical
 Fix For: 2.1.1

 Attachments: AMBARI-12457.patch


 For a HDP-2.2 deployment, webhcat-site config specifies:
 templeton.hive.extra.files= 
 {{/usr/hdp/$\{hdp.version\}/tez/conf/tez-site.xml}},/usr/hdp/$\{hdp.version\}/tez,/usr/hdp/$\{hdp.version\}/tez/lib
 However, {{/usr/hdp/$\{hdp.version\}/tez/conf/tez-site.xml}} does not exist. 
 Instead the reference should be to {{/etc/tez/conf}}.



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

[jira] [Commented] (AMBARI-12457) HDP-2.2 deployment of webhcat should use /etc/tez/conf

2015-07-18 Thread Mahadev konar (JIRA)


[ 
https://issues.apache.org/jira/browse/AMBARI-12457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14632488#comment-14632488
 ] 

Mahadev konar commented on AMBARI-12457:


+1 for the patch.

 HDP-2.2 deployment of webhcat should use /etc/tez/conf
 --

 Key: AMBARI-12457
 URL: https://issues.apache.org/jira/browse/AMBARI-12457
 Project: Ambari
  Issue Type: Bug
  Components: stacks
Affects Versions: 2.1.0
Reporter: Sumit Mohanty
Assignee: Sumit Mohanty
Priority: Critical
 Fix For: 2.1.1

 Attachments: AMBARI-12457.patch


 For a HDP-2.2 deployment, webhcat-site config specifies:
 templeton.hive.extra.files= 
 {{/usr/hdp/$\{hdp.version\}/tez/conf/tez-site.xml}},/usr/hdp/$\{hdp.version\}/tez,/usr/hdp/$\{hdp.version\}/tez/lib
 However, {{/usr/hdp/$\{hdp.version\}/tez/conf/tez-site.xml}} does not exist. 
 Instead the reference should be to {{/etc/tez/conf}}.



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

[jira] [Commented] (AMBARI-12451) Ranger configurations missing after HDP 2.2-2.3 upgrade

2015-07-17 Thread Mahadev konar (JIRA)


[ 
https://issues.apache.org/jira/browse/AMBARI-12451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631775#comment-14631775
 ] 

Mahadev konar commented on AMBARI-12451:


+1 for the patch.

 Ranger configurations missing after HDP 2.2-2.3 upgrade
 

 Key: AMBARI-12451
 URL: https://issues.apache.org/jira/browse/AMBARI-12451
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.1.0
Reporter: Myroslav Papirkovskyy
Assignee: Myroslav Papirkovskyy
Priority: Blocker
 Fix For: 2.1.0

 Attachments: AMBARI-12451.patch


 After 2.2-2.3 manual upgrade, 2.3 Advanced properties for Ranger Service and 
 plugin related config on components (hdfs,hive,hbase,knox,storm,yarn,kafka) 
 Ambari UI after successful Set Current HDP Version.



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

Re: Review Request 36553: Manual Stack Upgrade to HDP 2.3 - HBase coprocessor properties are not set to proper values

2015-07-16 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36553/#review91943
---

Ship it!


Ship It!

- Mahadev Konar


On July 16, 2015, 6:51 p.m., Dmitro Lisnichenko wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/36553/
 ---
 
 (Updated July 16, 2015, 6:51 p.m.)
 
 
 Review request for Ambari, Mahadev Konar and Velmurugan Periasamy.
 
 
 Bugs: AMBARI-12437
 https://issues.apache.org/jira/browse/AMBARI-12437
 
 
 Repository: ambari
 
 
 Description
 ---
 
 HBase coprocessor properties are not set to proper values after upgrade - 
 please let us know if there is bug/workaround for this
 Observation for Hbase
 After this step 2.4.6. Upgrade HBase, below properties didn't have expected 
 ranger hbase plugin values (attached screenshot)
 hbase.coprocessor.master.classes
 hbase.coprocessor.region.classes
 Ranger hbase plugin was enabled on Ambari 2.0.1
 
 
 Diffs
 -
 
   
 ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog210.java
  7967f7f 
   ambari-server/src/main/python/upgradeHelper.py bd6d632 
   
 ambari-server/src/main/resources/upgrade/catalog/UpgradeCatalog_2.2_to_2.3.json
  8ce2194 
 
 Diff: https://reviews.apache.org/r/36553/diff/
 
 
 Testing
 ---
 
 [12:41:52] :   [Step 1/1] [INFO]
 [12:41:52] :   [Step 1/1] [INFO] Ambari Views 
 .. SUCCESS [4.298s]
 [12:41:52] :   [Step 1/1] [INFO] Ambari Metrics Common 
 . SUCCESS [1.567s]
 [12:41:52] :   [Step 1/1] [INFO] Ambari Server 
 . SUCCESS [1:31:10.151s]
 [12:41:52] :   [Step 1/1] [INFO] 
 
 [12:41:52] :   [Step 1/1] [INFO] BUILD SUCCESS
 [12:41:52] :   [Step 1/1] [INFO] 
 
 
 
 Thanks,
 
 Dmitro Lisnichenko

[jira] [Created] (AMBARI-12436) Falcon service check failed / daemon crashed during RU

Mahadev konar created AMBARI-12436:
--

 Summary: Falcon service check failed / daemon crashed during RU
 Key: AMBARI-12436
 URL: https://issues.apache.org/jira/browse/AMBARI-12436
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.1.0
Reporter: Mahadev konar
 Fix For: 2.1.1


Falcon service check failed / daemon crashed during RU

This is a cluster going through upgrade - downgrade - upgrade 
Falcon service check failed and the daemon itself crashed.



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

[jira] [Created] (AMBARI-12435) oozie prepare-war secure not executed after disabling and re-enabling HTTPS

Mahadev konar created AMBARI-12435:
--

 Summary: oozie prepare-war secure not executed after disabling and 
re-enabling HTTPS
 Key: AMBARI-12435
 URL: https://issues.apache.org/jira/browse/AMBARI-12435
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.1.0
Reporter: Mahadev konar
 Fix For: 2.1.1


After enabling HTTPS for Oozie, removing the parameters to disable and reenable 
security does not work. This issue is more easily reproducible like below
Instead of all the required steps  when only 2 of the env parameters are 
changed - then Ambari sets HTTP port to the HTTPS port and oozie usage fails 
with Plaintext message to a SSL port
Any attempt to reenable security fails



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

[jira] [Created] (AMBARI-12434) UI doesn't reload after closing Ranger Admin wizard

Mahadev konar created AMBARI-12434:
--

 Summary: UI doesn't reload after closing Ranger Admin wizard
 Key: AMBARI-12434
 URL: https://issues.apache.org/jira/browse/AMBARI-12434
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.1.0
Reporter: Mahadev konar
 Fix For: 2.1.1


UI doesn't reload after closing Ranger Admin wizard



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

[jira] [Updated] (AMBARI-12434) UI doesn't reload after closing Ranger Admin wizard


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

Mahadev konar updated AMBARI-12434:
---
Description: 
Deploy cluster
Start enabling Ranger HA
Proceed to 2 step (Select hosts)
Close the wizard.
UI doesn't reload, how it is happening with other HA's.
So, when you try to enable Ranger HA again, it loads the same state you 
abandoned.

  was:UI doesn't reload after closing Ranger Admin wizard


 UI doesn't reload after closing Ranger Admin wizard
 ---

 Key: AMBARI-12434
 URL: https://issues.apache.org/jira/browse/AMBARI-12434
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.1.0
Reporter: Mahadev konar
 Fix For: 2.1.1


 Deploy cluster
 Start enabling Ranger HA
 Proceed to 2 step (Select hosts)
 Close the wizard.
 UI doesn't reload, how it is happening with other HA's.
 So, when you try to enable Ranger HA again, it loads the same state you 
 abandoned.



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

Re: Review Request 36551: Manual Stack Upgrade - Unable to set current after upgrade from 2.2 - 2.3. Additional changes

2015-07-16 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36551/#review91941
---

Ship it!


Ship It!

- Mahadev Konar


On July 16, 2015, 6:45 p.m., Dmitro Lisnichenko wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/36551/
 ---
 
 (Updated July 16, 2015, 6:45 p.m.)
 
 
 Review request for Ambari, Alejandro Fernandez, Jonathan Hurley, Mahadev 
 Konar, and Nate Cole.
 
 
 Bugs: AMBARI-12425
 https://issues.apache.org/jira/browse/AMBARI-12425
 
 
 Repository: ambari
 
 
 Description
 ---
 
 1) Ambari 2.0.0 + HDP 2.2.6, hdfs, yarn, mr, zk
 2) upgrade to Ambari 2.1.0 build #1455
 3) All looks good. Perform manual upgrade to HDP 2.3 #2557
 4) All looks good. Go to finish and set-current. fails.
 [root@c6401 conf]# ambari-server set-current --cluster-name=MyCluster 
 --version-display-name=HDP-2.3.0.0
 Using python  /usr/bin/python2.6
 Setting current version...
 Enter Ambari Admin login: admin
 Enter Ambari Admin password: 
 ERROR: Exiting with exit code 1. 
 REASON: Error during setting current version. Http status code - 500. 
  {
   status : 500,
   message : org.apache.ambari.server.controller.spi.SystemException: 
 Finalization failed. More details: \nSTDOUT: Begin finalizing the upgrade of 
 cluster MyCluster to version 2.3.0.0-2557\n\nSTDERR: Cluster stack version 
 2.3.0.0-2557 not found
 }
 
 
 Previous patch was not fully correct: it accessed ClusterEntity directly, not 
 modifying our application-level cache (ClusterImplementation). I missed this 
 issue when testing patch yesterday, because I redeployed jar and restarted 
 server every time after jar replacement.
 
 
 Diffs
 -
 
   
 ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java
  8f50004 
 
 Diff: https://reviews.apache.org/r/36551/diff/
 
 
 Testing
 ---
 
 I verified that my fix works without ambari-server restart (testing old 
 version and new version on the same VM snapshot).
 
 [INFO] 
 
 [INFO] Reactor Summary:
 [INFO] 
 [INFO] Ambari Views .. SUCCESS [2.924s]
 [INFO] Ambari Metrics Common . SUCCESS [1.625s]
 [INFO] Ambari Server . SUCCESS 
 [48:46.490s]
 [INFO] 
 
 [INFO] BUILD SUCCESS
 [INFO] 
 
 [INFO] Total time: 48:54.697s
 [INFO] Finished at: Thu Jul 16 21:31:04 EEST 2015
 [INFO] Final Memory: 66M/1153M
 [INFO] 
 
 
 
 Thanks,
 
 Dmitro Lisnichenko

Re: Review Request 36564: Deleting a host using the API causes NPE

2015-07-16 Thread Mahadev Konar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36564/#review92014
---

Ship it!


Ship It!

- Mahadev Konar


On July 17, 2015, 1:25 a.m., Alejandro Fernandez wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/36564/
 ---
 
 (Updated July 17, 2015, 1:25 a.m.)
 
 
 Review request for Ambari, Dmitro Lisnichenko, Jonathan Hurley, John Speidel, 
 Nate Cole, Sumit Mohanty, and Sid Wagle.
 
 
 Bugs: AMBARI-12429
 https://issues.apache.org/jira/browse/AMBARI-12429
 
 
 Repository: ambari
 
 
 Description
 ---
 
 There are 3 issues while deleting hosts.
 1. Created a cluster with multiple hosts, then stopped all of the services on 
 1 host (preferably one with only clients so it has nothing to stop). Then 
 deleted the host using the API.
 E.g., curl -u admin:admin -H X-Requested-By: ambari -X DELETE 
 http://c6401.ambari.apache.org:8080/api/v1/hosts/c6404.ambari.apache.org
 This led to Null Pointer Exceptions in ambari-server because the UI is still 
 generating requests to get the ServiceComponentHost response, which isn't 
 locking code, and makes request to get the HostState (this record has been 
 deleted), so a NPE is thrown. This needs to be more robust; adding locks 
 around here may have other repercussions, so I decided to just check for != 
 null.
 
 2. If a Host with DataNode  becomes decommissioned, it will have a record in 
 the requestoperationlevel table, whose records are not currently being 
 deleted when a Host is deleted.
 
 3. There are differences between deleting a Host using the /hosts/name and 
 /clusters/name/hosts/name API. In the former, since no cluster is provided, 
 it blindly deletes the host without checking if it has any masters/slaves on 
 it, which need to be stopped and deleted first.
 
 
 Diffs
 -
 
   
 ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
  de9ae52 
   
 ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostResourceProvider.java
  4c14426 
   
 ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RequestOperationLevel.java
  c7c0160 
   
 ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RequestResourceProvider.java
  fa49d7f 
   
 ambari-server/src/main/java/org/apache/ambari/server/orm/dao/RequestOperationLevelDAO.java
  PRE-CREATION 
   
 ambari-server/src/main/java/org/apache/ambari/server/orm/entities/RequestOperationLevelEntity.java
  2c11e55 
   
 ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClustersImpl.java
  665dd56 
   
 ambari-server/src/main/java/org/apache/ambari/server/state/svccomphost/ServiceComponentHostImpl.java
  9f25ad7 
   
 ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RequestOperationLevelTest.java
  bd4ad90 
   
 ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RequestResourceProviderTest.java
  ed8336e 
 
 Diff: https://reviews.apache.org/r/36564/diff/
 
 
 Testing
 ---
 
 System tests passed, see test matrix in comments of AMBARI-12429.
 
 Waiting for unit test results.
 
 
 Thanks,
 
 Alejandro Fernandez

[jira] [Commented] (AMBARI-12444) Manual Stack Upgrade 2.2 - 2.3: Storm service check through Ambari UI fails after upgrading