[jira] [Created] (AMBARI-15296) Missing property: hive.server2.authentication.kerberos.keytab
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
[ 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)
[jira] [Updated] (AMBARI-15200) Unusable configs after creating override
[ 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
[ 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)
[jira] [Reopened] (AMBARI-14718) on region server restart ambari is setting /tmp to hbase:hadoop
[
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
> 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
[
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
> and ssh key for user root is
> attached
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-14561) Configuration changes of spark thrift server for Spark 1.6
[ 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)
[jira] [Updated] (AMBARI-14437) Unable To Restart HCat Client When Not Colocated With WebHCat Server
[
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)
[jira] [Updated] (AMBARI-14331) Ambari local admin endpoint doesn’t work when sso is enabled.
[ 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
[ 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)
[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
[
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
[ 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)
[jira] [Commented] (AMBARI-13895) Unit Test failure in Ambari Server python tests
[
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': '', 'default_fs': u'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':
[jira] [Commented] (AMBARI-13846) Spark thrift server should be a slave component
[
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
[ 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)
[jira] [Updated] (AMBARI-13584) Ambari stack definition for Spark has incorrect value for SPARK_CONF_DIR
[ 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
[ 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
[ 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)
[jira] [Updated] (AMBARI-13253) HBase service start fails after manual upgrade due to missing HBASE_REGION_SERVER_RPC_SCHEDULER_FACTORY_CLASS class
[ 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
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)
[jira] [Commented] (AMBARI-13249) Fix unit test failure in trunk
[
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)
[jira] [Commented] (AMBARI-13069) Attributes of configuration property should be stack API driven
[ 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)
[jira] [Commented] (AMBARI-13062) Ambari Headless principal for Storm should include cluster name
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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)
[jira] [Commented] (AMBARI-12775) [PluggableStackDefinition] Update PHD version mapping
[ 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
[ 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)
[jira] [Commented] (AMBARI-12623) [PluggableStackDefinition] Integrate pluggable stack definition into build
[ 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)
[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
[
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
[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
[
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
[jira] [Updated] (AMBARI-12598) kafka_client_jaas.conf not being managed by Ambari
[ 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
[ 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
[ 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
[ 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)
[jira] [Updated] (AMBARI-11526) Pluggable Stack Definition
[ 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
[ 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
[
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
[
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
[ 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)
[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)
[jira] [Commented] (AMBARI-12444) Manual Stack Upgrade 2.2 - 2.3: Storm service check through Ambari UI fails after upgrading
[
https://issues.apache.org/jira/browse/AMBARI-12444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14630570#comment-14630570
]
Mahadev konar commented on AMBARI-12444:
+1 for the patch.
Manual Stack Upgrade 2.2 - 2.3: Storm service check through Ambari UI fails
after upgrading
Key: AMBARI-12444
URL: https://issues.apache.org/jira/browse/AMBARI-12444
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-12444.patch
The storm service check under service actions for storm in Ambari UI fails.
One thing to note here is that service check throws an exception trying to
kill a topology but i did not see anywhere in the logs that it tried to
submit a topology in first place.
{noformat}
Traceback (most recent call last):
File
/var/lib/ambari-agent/cache/common-services/STORM/0.9.1.2.1/package/scripts/service_check.py,
line 79, in module
ServiceCheck().execute()
File
/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py,
line 218, in execute
method(env)
File
/var/lib/ambari-agent/cache/common-services/STORM/0.9.1.2.1/package/scripts/service_check.py,
line 75, in service_check
user=params.storm_user
File /usr/lib/python2.6/site-packages/resource_management/core/base.py,
line 157, in __init__
self.env.run()
File
/usr/lib/python2.6/site-packages/resource_management/core/environment.py,
line 152, in run
self.run_action(resource, action)
File
/usr/lib/python2.6/site-packages/resource_management/core/environment.py,
line 118, in run_action
provider_action()
File
/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py,
line 258, 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 'storm kill
WordCountidf00a2020_date361615' returned 1
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-12427) Incorrect listeners property in file /etc/kafka/conf/server.properties
[ https://issues.apache.org/jira/browse/AMBARI-12427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14628665#comment-14628665 ] Mahadev konar commented on AMBARI-12427: +1 Incorrect listeners property in file /etc/kafka/conf/server.properties -- Key: AMBARI-12427 URL: https://issues.apache.org/jira/browse/AMBARI-12427 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-12427.patch The file /etc/kafka/conf/server.properties that gets created after running the script upgradeHelper.py has the following property: listeners=PLAINTEXT://hmcl-amb-201-hdp-2260-to-amb-21-hdp-2300-1-1:6667,PLAINTEXT://hmcl-amb-201-hdp-2260-to-amb-21-hdp-2300-1-4:6667 The value for this property is exactly the same in all the hosts running the kafka-broker, which causes the following exception in var/log/kafka/server.log java.lang.IllegalArgumentException: requirement failed: Each listener must have a different port The correct value for the listeners property should be HOST_NAME:PORT where HOST_NAME is the host name of the node corresponding to that kafka broker, and PORT is the kafka broker port Please see attached screenshots for details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12415) Ambari should set dr. who in the admin acl by default in the secure cluster
[ https://issues.apache.org/jira/browse/AMBARI-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14626985#comment-14626985 ] Mahadev konar commented on AMBARI-12415: +1 for the patch. Ambari should set dr. who in the admin acl by default in the secure cluster --- Key: AMBARI-12415 URL: https://issues.apache.org/jira/browse/AMBARI-12415 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.1.0 Reporter: Jaimin D Jetly Assignee: Jaimin D Jetly Priority: Critical Fix For: 2.1.1 Attachments: AMBARI-12415.patch, dr.who logged in (with fix).png, kerberized cluster(with fix).png In a secure cluster, user access the UI by default as dr. who. Since dr. who by default is not allowed to view the app info, user cannot view the apps. The proposal is to always add dr who. as the admin user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12401) Oozie Server start failed and RegionServers down after Node Labels enabled
[
https://issues.apache.org/jira/browse/AMBARI-12401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14625394#comment-14625394
]
Mahadev konar commented on AMBARI-12401:
+1 for the patch.
Oozie Server start failed and RegionServers down after Node Labels enabled
Key: AMBARI-12401
URL: https://issues.apache.org/jira/browse/AMBARI-12401
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.1.0
Reporter: Sumit Mohanty
Assignee: Sumit Mohanty
Fix For: 2.1.0
Attachments: AMBARI-12401.patch
*scenario*
# install ambari
# deploy cluster
# navigate YARN configs tab
# set Node Labels property to Enabled
# restart YARN and Oozie
*expected* restart success
*actual* *Oozie* restart failed and *RegionServers* randomly shut down
{code}stderr: /var/lib/ambari-agent/data/errors-227.txt
Traceback (most recent call last):
File
/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py,
line 181, in module
OozieServer().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 459, in restart
self.start(env)
File
/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py,
line 64, in start
oozie_service(action='start', rolling_restart=rolling_restart)
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/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py,
line 102, in oozie_service
list_status = util.run_command(params.hdfs_share_dir, 'GETFILESTATUS',
method='GET', ignore_status_codes=['404'], assertable_result=False)
File
/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py,
line 201, in run_command
raise Fail(err_msg)
resource_management.core.exceptions.Fail: Execution of 'curl -sS -L -w
'%{http_code}' -X GET
'http://ip-x-x-x-x.ec2.internal:50070/webhdfs/v1/user/oozie/share?op=GETFILESTATUSuser.name=oozie''
returned status_code=403.
{
RemoteException: {
exception: AccessControlException,
javaClassName: org.apache.hadoop.security.AccessControlException,
message: Permission denied: user=oozie, access=EXECUTE,
inode=\/user/oozie/share\:yarn:hadoop:drwx--
}
}
stdout: /var/lib/ambari-agent/data/output-227.txt
2015-07-13 13:01:16,044 - Group['hadoop'] {'ignore_failures': False}
2015-07-13 13:01:16,060 - Group['users'] {'ignore_failures': False}
2015-07-13 13:01:16,060 - Group['knox'] {'ignore_failures': False}
2015-07-13 13:01:16,061 - Group['spark'] {'ignore_failures': False}
2015-07-13 13:01:16,061 - User['oozie'] {'gid': 'hadoop', 'ignore_failures':
False, 'groups': ['users']}
2015-07-13 13:01:16,063 - User['hive'] {'gid': 'hadoop', 'ignore_failures':
False, 'groups': ['hadoop']}
2015-07-13 13:01:16,064 - User['ambari-qa'] {'gid': 'hadoop',
'ignore_failures': False, 'groups': ['users']}
2015-07-13 13:01:16,065 - User['flume'] {'gid': 'hadoop', 'ignore_failures':
False, 'groups': ['hadoop']}
2015-07-13 13:01:16,066 - User['hdfs'] {'gid': 'hadoop', 'ignore_failures':
False, 'groups': ['hadoop']}
2015-07-13 13:01:16,068 - User['knox'] {'gid': 'hadoop', 'ignore_failures':
False, 'groups': ['hadoop']}
2015-07-13 13:01:16,069 - User['storm'] {'gid': 'hadoop', 'ignore_failures':
False, 'groups': ['hadoop']}
2015-07-13 13:01:16,070 - User['spark'] {'gid': 'hadoop', 'ignore_failures':
False, 'groups': ['hadoop']}
2015-07-13 13:01:16,071 - User['mapred'] {'gid': 'hadoop', 'ignore_failures':
False, 'groups': ['hadoop']}
2015-07-13 13:01:16,073 - User['accumulo'] {'gid': 'hadoop',
'ignore_failures': False, 'groups': ['hadoop']}
2015-07-13 13:01:16,074 - User['hbase'] {'gid': 'hadoop', 'ignore_failures':
False, 'groups': ['hadoop']}
2015-07-13 13:01:16,075 - User['tez'] {'gid': 'hadoop', 'ignore_failures':
False, 'groups': ['users']}
2015-07-13 13:01:16,076 - User['zookeeper'] {'gid': 'hadoop',
'ignore_failures': False, 'groups': ['hadoop']}
2015-07-13 13:01:16,077 - User['falcon'] {'gid': 'hadoop', 'ignore_failures':
False, 'groups': ['users']}
2015-07-13 13:01:16,078 - User['sqoop'] {'gid': 'hadoop', 'ignore_failures':
False, 'groups': ['hadoop']}
2015-07-13 13:01:16,079 - User['yarn'] {'gid': 'hadoop', 'ignore_failures':
False, 'groups': ['hadoop']}
2015-07-13 13:01:16,080 - User['hcat'] {'gid': 'hadoop', 'ignore_failures':
False, 'groups': ['hadoop']}
2015-07-13
[jira] [Commented] (AMBARI-4320) Add separate CONFIGURE command support to server
[ https://issues.apache.org/jira/browse/AMBARI-4320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14624226#comment-14624226 ] Mahadev konar commented on AMBARI-4320: --- [~jhalterman] this is a good start. It still a little high level though - I'd say try out implmenting a command for HDFS for example then itllgive us an idea of the extent of changes we need and will help further the design. Add separate CONFIGURE command support to server Key: AMBARI-4320 URL: https://issues.apache.org/jira/browse/AMBARI-4320 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: 1.5.0 Reporter: Dmitry Lysnichenko Fix For: 2.2.0 Attachments: Proposed CONFIGURE changes.txt CONFIGURE command is responsible for creating files/dirs, adjusting ownership, generating config files etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12377) Installer wizard: webhcat server start fails
[ https://issues.apache.org/jira/browse/AMBARI-12377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14622724#comment-14622724 ] Mahadev konar commented on AMBARI-12377: +1 for the patch. Installer wizard: webhcat server start fails Key: AMBARI-12377 URL: https://issues.apache.org/jira/browse/AMBARI-12377 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.1.0 Attachments: AMBARI-12377.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12362) Manual upgrade fails - YARN RM restart failed due to yarn node labels error
[
https://issues.apache.org/jira/browse/AMBARI-12362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14621199#comment-14621199
]
Mahadev konar commented on AMBARI-12362:
+1 for the patch.
Manual upgrade fails - YARN RM restart failed due to yarn node labels error
---
Key: AMBARI-12362
URL: https://issues.apache.org/jira/browse/AMBARI-12362
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.1.0
Reporter: Siddharth Wagle
Assignee: Siddharth Wagle
Priority: Critical
Fix For: 2.1.0
Attachments: AMBARI-12362.patch
Error:
{code}
java.lang.IllegalArgumentException: Illegal capacity of -1.0 for
node-label=default in queue=root, valid capacity should in range of [0, 100].
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacitySchedulerConfiguration.internalGetLabeledQueueCapacity(CapacitySchedulerConfiguration.java:507)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacitySchedulerConfiguration.getLabeledQueueCapacity(CapacitySchedulerConfiguration.java:519)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CSQueueUtils.loadCapacitiesByLabelsFromConf(CSQueueUtils.java:142)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CSQueueUtils.loadUpdateAndCheckCapacities(CSQueueUtils.java:121)
{code}
Configs attached.
Issue needs to be fixed in both YARN and Ambari.
YARN should be ignoring these settings if node labels are disabled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-12336) Ensure HDP-2.3 has correct version number for member services
[ https://issues.apache.org/jira/browse/AMBARI-12336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14619079#comment-14619079 ] Mahadev konar commented on AMBARI-12336: +1 for the patch. Ensure HDP-2.3 has correct version number for member services - Key: AMBARI-12336 URL: https://issues.apache.org/jira/browse/AMBARI-12336 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.1.0 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Priority: Critical Fix For: 2.1.0 Attachments: AMBARI-12336.patch Checked and found that few services do not have the right display version number for HDP-2.3. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12343) Ambari storm deployment fails in secure mode due to storm principal name
[ https://issues.apache.org/jira/browse/AMBARI-12343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated AMBARI-12343: --- Fix Version/s: 2.1.0 Ambari storm deployment fails in secure mode due to storm principal name Key: AMBARI-12343 URL: https://issues.apache.org/jira/browse/AMBARI-12343 Project: Ambari Issue Type: Bug Reporter: Sriharsha Chintalapani Assignee: Sriharsha Chintalapani Fix For: 2.1.0 Attachments: AMBARI-12343.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-12324) Oozie service check fails after Moving Oozie Server
Mahadev konar created AMBARI-12324: -- Summary: Oozie service check fails after Moving Oozie Server Key: AMBARI-12324 URL: https://issues.apache.org/jira/browse/AMBARI-12324 Project: Ambari Issue Type: Bug Reporter: Mahadev konar Fix For: 2.2.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12302) Fix Kafka metrics.json file based on changes to Kafka metrics
[ https://issues.apache.org/jira/browse/AMBARI-12302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14615948#comment-14615948 ] Mahadev konar commented on AMBARI-12302: +1 for the patch. Fix Kafka metrics.json file based on changes to Kafka metrics - Key: AMBARI-12302 URL: https://issues.apache.org/jira/browse/AMBARI-12302 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.1.0 Reporter: Siddharth Wagle Assignee: Siddharth Wagle Fix For: 2.1.0 Attachments: AMBARI-12302.patch The Kafka metrics.json file needs to be modified based on changed to Kafka metrics. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-12282) Ambari JDK8 upgrade does not deploy JDK8 on DataNodes/NodeManager on rerun of setup.
Mahadev konar created AMBARI-12282: -- Summary: Ambari JDK8 upgrade does not deploy JDK8 on DataNodes/NodeManager on rerun of setup. Key: AMBARI-12282 URL: https://issues.apache.org/jira/browse/AMBARI-12282 Project: Ambari Issue Type: Bug Affects Versions: 2.0.0 Reporter: Mahadev konar Fix For: 2.1.1 Ambari JDK8 upgrade does not deploy JDK8 on DataNodes/NodeManager on rerun of setup. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-12281) Not prompted to restart after modifying configs
Mahadev konar created AMBARI-12281: -- Summary: Not prompted to restart after modifying configs Key: AMBARI-12281 URL: https://issues.apache.org/jira/browse/AMBARI-12281 Project: Ambari Issue Type: Bug Affects Versions: 2.1.0 Reporter: Andrew Grande Fix For: 2.1.1 When I change a property in Kafka, Ambari doesn’t asked me to restart services. I’ve modified the listener in KAFKA ( from PLAINTEXT to KERBEROS ) and I’m not being asked to restart the service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-12283) ZooKeeper Server check fails on adding/deleting zk server (or host with it) when zk ids interfere
Mahadev konar created AMBARI-12283: -- Summary: ZooKeeper Server check fails on adding/deleting zk server (or host with it) when zk ids interfere Key: AMBARI-12283 URL: https://issues.apache.org/jira/browse/AMBARI-12283 Project: Ambari Issue Type: Bug Affects Versions: 2.0.0 Reporter: Mahadev konar Fix For: 2.2.0 ZooKeeper Server check fails on adding/deleting zk server (or host with it) when zk ids interfere -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12282) Ambari JDK8 upgrade does not deploy JDK8 on DataNodes/NodeManager on rerun of setup.
[ https://issues.apache.org/jira/browse/AMBARI-12282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated AMBARI-12282: --- Fix Version/s: (was: 2.1.1) 2.2.0 Ambari JDK8 upgrade does not deploy JDK8 on DataNodes/NodeManager on rerun of setup. Key: AMBARI-12282 URL: https://issues.apache.org/jira/browse/AMBARI-12282 Project: Ambari Issue Type: Bug Affects Versions: 2.0.0 Reporter: Mahadev konar Fix For: 2.2.0 Ambari JDK8 upgrade does not deploy JDK8 on DataNodes/NodeManager on rerun of setup. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-12284) Ambari omits the line to enable kerberos on the Spark History Service
Mahadev konar created AMBARI-12284: -- Summary: Ambari omits the line to enable kerberos on the Spark History Service Key: AMBARI-12284 URL: https://issues.apache.org/jira/browse/AMBARI-12284 Project: Ambari Issue Type: Bug Affects Versions: 2.1.0 Reporter: Steve Loughran Fix For: 2.2.0 Ambari omits the line to enable kerberos on the Spark History Service When Ambari sets up a secure spark cluster, it doesn't set This will still fail tests unless the line spark.history.kerberos.enabled true is added to spark-defaults.conf without this the Spark History Service will not log in with the keytab, and so not set up a long-lived secure connection to a Yarn History Server with encryption on. This isn't immediately visible (and hard to sport in the tests), because if the user spark has logged in with kinit, the TGT is picked up and used —which works until the ticket expires. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12208) Disable ACCUMULO in HDP-2.2
[ https://issues.apache.org/jira/browse/AMBARI-12208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608359#comment-14608359 ] Mahadev konar commented on AMBARI-12208: +1 for the new patch. Disable ACCUMULO in HDP-2.2 --- Key: AMBARI-12208 URL: https://issues.apache.org/jira/browse/AMBARI-12208 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.1.0 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Priority: Critical Fix For: 2.1.0 Attachments: AMBARI-12208.2.patch, AMBARI-12208.patch, Screen Shot 2015-06-30 at 7.07.03 AM.png, eaHZNQrjERpn3941VcJ4L5OfXZTdBt3WtD8axIsIMn0.png Accumulo should not be supported in HDP-2.2 to maintain sync with earlier releases of Ambari support for HDP-2.2. In addition this is blocking RU from HDP-2.2.x to HDP-2.2.y as the upgrade directive for Accumulo does not exist. The change will only hide Accumulo service from HDP-2.2. No code change will be made to the underlying Accumulo stack scripts. Accumulo will continue to be supported in HDP-2.3 by Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12208) Disable ACCUMULO in HDP-2.2
[ https://issues.apache.org/jira/browse/AMBARI-12208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14606816#comment-14606816 ] Mahadev konar commented on AMBARI-12208: +1 for the patch. Disable ACCUMULO in HDP-2.2 --- Key: AMBARI-12208 URL: https://issues.apache.org/jira/browse/AMBARI-12208 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.1.0 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Priority: Critical Fix For: 2.1.0 Attachments: AMBARI-12208.patch Accumulo should not be supported in HDP-2.2 to maintain sync with earlier releases of Ambari support for HDP-2.2. In addition this is blocking RU from HDP-2.2.x to HDP-2.2.y as the upgrade directive for Accumulo does not exist. The change will only hide Accumulo service from HDP-2.2. No code change will be made to the underlying Accumulo stack scripts. Accumulo will continue to be supported in HDP-2.3 by Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12196) Ambari-server component build fails with 'maven-surefire-plugin' failing with more than 500 tests
[
https://issues.apache.org/jira/browse/AMBARI-12196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14605058#comment-14605058
]
Mahadev konar commented on AMBARI-12196:
+1 for the patch.
Ambari-server component build fails with 'maven-surefire-plugin' failing with
more than 500 tests
-
Key: AMBARI-12196
URL: https://issues.apache.org/jira/browse/AMBARI-12196
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.1.0
Reporter: Srimanth Gunturi
Assignee: Srimanth Gunturi
Priority: Critical
Fix For: 2.1.0
Attachments: AMBARI-12196.patch
Ambari-server component fails to build in
[https://builds.apache.org/job/Ambari-trunk-Commit/3028/consoleFull]. The
message given during build is:
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on
project ambari-server: Execution default-test of goal
org.apache.maven.plugins:maven-surefire-plugin:2.12:test failed: Task
java.util.concurrent.FutureTask@dc688d rejected from
java.util.concurrent.ThreadPoolExecutor@542e8e[Running, pool size = 1, active
threads = 1, queued tasks = 500, completed tasks = 0] - [Help 1]
{code}
It turns out that _maven-surefire-plugin_ version 2.12 has an issue with
having more than 500 tests and having {{forkMode=always}}. The issue is
[https://issues.apache.org/jira/browse/SUREFIRE-913].
Updating _maven-surefire-plugin_ version to 2.13 should fix this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-12158) Support Kafka rolling upgrade in secure cluster for older version of kafka
[ https://issues.apache.org/jira/browse/AMBARI-12158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated AMBARI-12158: --- Fix Version/s: 2.1.0 Support Kafka rolling upgrade in secure cluster for older version of kafka -- Key: AMBARI-12158 URL: https://issues.apache.org/jira/browse/AMBARI-12158 Project: Ambari Issue Type: Bug Reporter: Sriharsha Chintalapani Assignee: Sriharsha Chintalapani Fix For: 2.1.0 Attachments: AMBARI-12158.patch Kafka 0.8.1.1 doesn't have security features but can still be installed by ambari in a secure cluster. When user upgrades this cluster to newer version there are issues in running service check. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12128) Falcon Server Web UI alert fails when Kerberos is enabled
[
https://issues.apache.org/jira/browse/AMBARI-12128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14599756#comment-14599756
]
Mahadev konar commented on AMBARI-12128:
+1 for the patch.
Falcon Server Web UI alert fails when Kerberos is enabled
-
Key: AMBARI-12128
URL: https://issues.apache.org/jira/browse/AMBARI-12128
Project: Ambari
Issue Type: Bug
Components: ambari-agent, ambari-server
Affects Versions: 2.1.0
Reporter: Robert Levas
Assignee: Robert Levas
Priority: Blocker
Labels: alerts, kerberos
Fix For: 2.1.0
Attachments: AMBARI-12128_01.patch
Falcon Server Web UI alert fails when Kerberos is enabled. The error message
is
{noformat}
agent/data/tmp/web_alert_cc_2144dc375b8556f5a0c2629adedd2a99 -kt
{{falcon-startup.properties/*.falcon.http.authentication.kerberos.keytab}}
{{falcon-startup.properties/*.falcon.http.authentication.kerberos.principal}}
/dev/null' returned 1. kinit: Client not found in Kerberos database while
getting initial credentials)
{noformat}
*Cause*
This issue was introduced when the patch for AMBARI-11656 was applied.
The issue is related to this line:
{code:title=ambari_agent/alerts/base_alert.py:217}
replacement_match_regex = r{{(%s)}} % placeholder_key
{code}
When the relative falcon properties are applied, the generated regular
expression becomes
{noformat}
{{(falcon-startup.properties/*.falcon.http.authentication.kerberos.keytab)}}
{noformat}
Which wants to match on values like:
* falcon-startup.properties.falcon.http.authentication.kerberos.keytab
* falcon-startup.properties/.falcon.http.authentication.kerberos.keytab
*
falcon-startup.properties/Rfalcon.http.authentication.kerberos.keytab
Not the one we really want -
falcon-startup.properties/*.falcon.http.authentication.kerberos.keytab
Either the {{*}} needs to be escaped or the use of regular expressions needs
to be changed.
*Solution*
Remove the regular expression replacement and use somple string replacement
instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-12130) Ambari Upgrade: oozie alert broken URL
[ https://issues.apache.org/jira/browse/AMBARI-12130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14599804#comment-14599804 ] Mahadev konar commented on AMBARI-12130: +1 for the patch. Ambari Upgrade: oozie alert broken URL -- Key: AMBARI-12130 URL: https://issues.apache.org/jira/browse/AMBARI-12130 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.1.0 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Priority: Critical Fix For: 2.1.0 Attachments: AMBARI-12130.patch, oozie-alert.tiff 1) Upgraded from Ambari 201 + HDP 2.2 - Ambari 2.1.0 (ambari only upgrade) 2) Oozie alert shows warning. Looks like the URL it's checking is now wrong. has an extra /oozie. FWIW, The oozie.base.url config is http://c6402.ambari.apache.org:11000/oozie; -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12031) Remove the need for HDP-2.x deployment to deploy ambari-log4j
[ https://issues.apache.org/jira/browse/AMBARI-12031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14594071#comment-14594071 ] Mahadev konar commented on AMBARI-12031: +1 for the patch. Remove the need for HDP-2.x deployment to deploy ambari-log4j - Key: AMBARI-12031 URL: https://issues.apache.org/jira/browse/AMBARI-12031 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.1.0 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Priority: Critical Fix For: 2.1.0 Attachments: AMBARI-12031.patch HDP-2.x no longer needs ambari-log4j package. It should be removed from the metainfo files in the various 2.x stack definitions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-11960) NonRoot: Address ambari-server and ambari-agent non-root issues
[ https://issues.apache.org/jira/browse/AMBARI-11960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated AMBARI-11960: --- Priority: Critical (was: Major) NonRoot: Address ambari-server and ambari-agent non-root issues --- Key: AMBARI-11960 URL: https://issues.apache.org/jira/browse/AMBARI-11960 Project: Ambari Issue Type: Bug Components: ambari-agent, ambari-server Affects Versions: 2.1.0 Reporter: Jayush Luniya Assignee: Jayush Luniya Priority: Critical Fix For: 2.1.0 Attachments: AMBARI-11960.patch 1. Ambari Server fails to start with non-root user, umask 027, because the JDK + JCE files are not accessbile. 2. Stack Advisor fails because /var/run/ambari-server/stack-recommendations/ cannot be deleted by the non-root user (Permission denied) 3. Ambari Agent fails to run check_db_connection test because as non-root user, it cannot create /usr/jdk64 (Permission denied) and hence fails to install the JAVA JDK. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-11903) metrics-collector in distributed mode fails to stop
[
https://issues.apache.org/jira/browse/AMBARI-11903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mahadev konar resolved AMBARI-11903.
Resolution: Fixed
metrics-collector in distributed mode fails to stop
---
Key: AMBARI-11903
URL: https://issues.apache.org/jira/browse/AMBARI-11903
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Environment: sles11sp3
ambari-server-2.1.0-1064
2.3.0.0-2346
Reporter: Michael Harp
Priority: Critical
Fix For: 2.1.0
Stopping metrics-collector is slow and mostly fails when configured in
distributed mode. I believe the reason is the hbase stop order is the same as
start order which results in zookeeper stopping fist instead of last.
{code}
# ams_service.py
if params.is_hbase_distributed:
hbase_service('zookeeper', action=action)
hbase_service('master', action=action)
hbase_service('regionserver', action=action)
cmd = format({cmd} --distributed)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-11907) Active hbase-master takes 20 minutes to stop from Stop All
[
https://issues.apache.org/jira/browse/AMBARI-11907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mahadev konar resolved AMBARI-11907.
Resolution: Fixed
Active hbase-master takes 20 minutes to stop from Stop All
Key: AMBARI-11907
URL: https://issues.apache.org/jira/browse/AMBARI-11907
Project: Ambari
Issue Type: Bug
Environment: sles11sp3
hdp-2.3.0.0-2346
ambari-2.1.0-1064
Reporter: Michael Harp
Priority: Critical
Fix For: 2.1.0
When Namenode HA and Hbase HA are enabled the active hbase-master takes 20
plus minutes to stop.
{code}
2015-06-13 14:16:06,183 -
Execute['/usr/hdp/current/hbase-master/bin/hbase-daemon.sh --config
/usr/hdp/current/hbase-master/conf stop master'] {'on_timeout': '! ( ls
/var/run/hbase/hbase-hbase-master.pid /dev/null 21 ps -p `cat
/var/run/hbase/hbase-hbase-master.pid` /dev/null 21 ) || ambari-sudo.sh -H
-E kill -9 `cat /var/run/hbase/hbase-hbase-master.pid`', 'timeout': 30,
'user': 'hbase'}
2015-06-13 14:36:13,274 -
Execute['/usr/hdp/current/hbase-master/bin/hbase-daemon.sh --config
/usr/hdp/current/hbase-master/conf stop master'] {'on_timeout': '! ( ls
/var/run/hbase/hbase-hbase-master.pid /dev/null 21 ps -p `cat
/var/run/hbase/hbase-hbase-master.pid` /dev/null 21 ) || ambari-sudo.sh -H
-E kill -9 `cat /var/run/hbase/hbase-hbase-master.pid`', 'timeout': 30,
'user': 'hbase'}
2015-06-13 14:36:13,340 - Execute['rm -f
/var/run/hbase/hbase-hbase-master.pid'] {}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-11940) Automatic retry of commands should be limited to initial INSTALL and START only
[
https://issues.apache.org/jira/browse/AMBARI-11940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14587418#comment-14587418
]
Mahadev konar commented on AMBARI-11940:
+1 for the patch. Looks good to me.
Automatic retry of commands should be limited to initial INSTALL and START
only
---
Key: AMBARI-11940
URL: https://issues.apache.org/jira/browse/AMBARI-11940
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.1.0
Reporter: Sumit Mohanty
Assignee: Sumit Mohanty
Priority: Critical
Fix For: 2.1.0
Attachments: AMBARI-11940.patch
The automatic retry of the tasks at the agent should be limited to the
initial INSTALL and START commands only.
Retry is only needed during the initial install using blueprints to get
around the lack of role command order enforcements. Beyond the initial
install/start automatic retry can actually be hinderance to debugging errors.
While it is possible to modify {{cluster-env}} to disable this capability, by
default disabling auto-retry post initial INSTALL/START makes more sense.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-11923) Storm version is for 2.3 Stack
Mahadev konar created AMBARI-11923: -- Summary: Storm version is for 2.3 Stack Key: AMBARI-11923 URL: https://issues.apache.org/jira/browse/AMBARI-11923 Project: Ambari Issue Type: Bug Reporter: Mahadev konar Assignee: Mahadev konar Fix For: 2.1.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-11923) Storm version is for 2.3 Stack
[ https://issues.apache.org/jira/browse/AMBARI-11923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated AMBARI-11923: --- Attachment: AMBARI-11923.patch Storm version is for 2.3 Stack -- Key: AMBARI-11923 URL: https://issues.apache.org/jira/browse/AMBARI-11923 Project: Ambari Issue Type: Bug Reporter: Mahadev konar Assignee: Mahadev konar Fix For: 2.1.0 Attachments: AMBARI-11923.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-10977) HDFS Rebalance failed with IllegalArgumentException: Does not contain a valid host:port authority
[
https://issues.apache.org/jira/browse/AMBARI-10977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mahadev konar updated AMBARI-10977:
---
Fix Version/s: 2.1.0
HDFS Rebalance failed with IllegalArgumentException: Does not contain a valid
host:port authority
-
Key: AMBARI-10977
URL: https://issues.apache.org/jira/browse/AMBARI-10977
Project: Ambari
Issue Type: Bug
Environment: ambari-2.1.0-376, hdp-2.3.0.0-1880, sles11sp3
Reporter: Zack Marsh
Fix For: 2.1.0
The HDFS Rebalance is failing with the following error messages:
stderr:
{code}
2015-05-06 12:31:46,656 - Error while executing command 'rebalancehdfs':
Traceback (most recent call last):
File
/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py,
line 214, in execute
method(env)
File
/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py,
line 243, in rebalancehdfs
logoutput = False,
File /usr/lib/python2.6/site-packages/resource_management/core/base.py,
line 148, in __init__
self.env.run()
File
/usr/lib/python2.6/site-packages/resource_management/core/environment.py,
line 152, in run
self.run_action(resource, action)
File
/usr/lib/python2.6/site-packages/resource_management/core/environment.py,
line 118, in run_action
provider_action()
File
/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py,
line 269, in action_run
raise ex
Fail: Execution of 'ambari-sudo.sh su hdfs -l -s /bin/bash -c 'export
PATH='''/usr/sbin:/sbin:/usr/lib/ambari-server/*:/usr/sbin:/sbin:/usr/lib/ambari-server/*:/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/opt/teradata/bynet/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin:.:/opt/teradata/sm3g/bin:/opt/dell/srvadmin/bin:/opt/dell/srvadmin/sbin:/opt/teradata/dswap/sbin:/usr/tdbms/bin:/opt/teradata/gsctools/bin:/opt/teradata/vmf/bin:/opt/teradata/bin:/var/lib/ambari-agent:/var/lib/ambari-agent:/usr/hdp/current/hadoop-client/bin'''
; hdfs --config /usr/hdp/current/hadoop-client/conf balancer -threshold 10''
returned 255. May 6, 2015 12:31:46 PM Balancing took 888.0 milliseconds
15/05/06 12:31:46 ERROR balancer.Balancer: Exiting balancer due an exception
java.lang.IllegalArgumentException: Does not contain a valid host:port
authority: jolokia1.labs.teradata.com
at org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java:213)
at org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java:164)
at org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java:153)
at org.apache.hadoop.hdfs.DFSUtil.getNameServiceUris(DFSUtil.java:1037)
at org.apache.hadoop.hdfs.DFSUtil.getNsServiceRpcUris(DFSUtil.java:978)
at
org.apache.hadoop.hdfs.server.balancer.Balancer$Cli.run(Balancer.java:682)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at
org.apache.hadoop.hdfs.server.balancer.Balancer.main(Balancer.java:794)
{code}
stdout:
{code}
Starting balancer with threshold = 10
Executing command ambari-sudo.sh su hdfs -l -s /bin/bash -c 'export
PATH='''/usr/sbin:/sbin:/usr/lib/ambari-server/*:/usr/sbin:/sbin:/usr/lib/ambari-server/*:/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/opt/teradata/bynet/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin:.:/opt/teradata/sm3g/bin:/opt/dell/srvadmin/bin:/opt/dell/srvadmin/sbin:/opt/teradata/dswap/sbin:/usr/tdbms/bin:/opt/teradata/gsctools/bin:/opt/teradata/vmf/bin:/opt/teradata/bin:/var/lib/ambari-agent:/var/lib/ambari-agent:/usr/hdp/current/hadoop-client/bin'''
; hdfs --config /usr/hdp/current/hadoop-client/conf balancer -threshold 10'
2015-05-06 12:31:43,096 - Execute['ambari-sudo.sh su hdfs -l -s /bin/bash -c
'export
PATH='''/usr/sbin:/sbin:/usr/lib/ambari-server/*:/usr/sbin:/sbin:/usr/lib/ambari-server/*:/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/opt/teradata/bynet/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin:.:/opt/teradata/sm3g/bin:/opt/dell/srvadmin/bin:/opt/dell/srvadmin/sbin:/opt/teradata/dswap/sbin:/usr/tdbms/bin:/opt/teradata/gsctools/bin:/opt/teradata/vmf/bin:/opt/teradata/bin:/var/lib/ambari-agent:/var/lib/ambari-agent:/usr/hdp/current/hadoop-client/bin'''
; hdfs --config /usr/hdp/current/hadoop-client/conf balancer -threshold
10''] {'logoutput': False, 'on_new_line': handle_new_line}
[balancer] May 6, 2015 12:31:46 PM [balancer] [balancer] Balancing took
888.0 milliseconds[balancer]
[balancer] 15/05/06 12:31:46 ERROR balancer.Balancer: Exiting balancer due an
exception
[jira] [Resolved] (AMBARI-10977) HDFS Rebalance failed with IllegalArgumentException: Does not contain a valid host:port authority
[
https://issues.apache.org/jira/browse/AMBARI-10977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mahadev konar resolved AMBARI-10977.
Resolution: Fixed
Fixed in 2.1..
HDFS Rebalance failed with IllegalArgumentException: Does not contain a valid
host:port authority
-
Key: AMBARI-10977
URL: https://issues.apache.org/jira/browse/AMBARI-10977
Project: Ambari
Issue Type: Bug
Environment: ambari-2.1.0-376, hdp-2.3.0.0-1880, sles11sp3
Reporter: Zack Marsh
The HDFS Rebalance is failing with the following error messages:
stderr:
{code}
2015-05-06 12:31:46,656 - Error while executing command 'rebalancehdfs':
Traceback (most recent call last):
File
/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py,
line 214, in execute
method(env)
File
/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py,
line 243, in rebalancehdfs
logoutput = False,
File /usr/lib/python2.6/site-packages/resource_management/core/base.py,
line 148, in __init__
self.env.run()
File
/usr/lib/python2.6/site-packages/resource_management/core/environment.py,
line 152, in run
self.run_action(resource, action)
File
/usr/lib/python2.6/site-packages/resource_management/core/environment.py,
line 118, in run_action
provider_action()
File
/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py,
line 269, in action_run
raise ex
Fail: Execution of 'ambari-sudo.sh su hdfs -l -s /bin/bash -c 'export
PATH='''/usr/sbin:/sbin:/usr/lib/ambari-server/*:/usr/sbin:/sbin:/usr/lib/ambari-server/*:/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/opt/teradata/bynet/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin:.:/opt/teradata/sm3g/bin:/opt/dell/srvadmin/bin:/opt/dell/srvadmin/sbin:/opt/teradata/dswap/sbin:/usr/tdbms/bin:/opt/teradata/gsctools/bin:/opt/teradata/vmf/bin:/opt/teradata/bin:/var/lib/ambari-agent:/var/lib/ambari-agent:/usr/hdp/current/hadoop-client/bin'''
; hdfs --config /usr/hdp/current/hadoop-client/conf balancer -threshold 10''
returned 255. May 6, 2015 12:31:46 PM Balancing took 888.0 milliseconds
15/05/06 12:31:46 ERROR balancer.Balancer: Exiting balancer due an exception
java.lang.IllegalArgumentException: Does not contain a valid host:port
authority: jolokia1.labs.teradata.com
at org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java:213)
at org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java:164)
at org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java:153)
at org.apache.hadoop.hdfs.DFSUtil.getNameServiceUris(DFSUtil.java:1037)
at org.apache.hadoop.hdfs.DFSUtil.getNsServiceRpcUris(DFSUtil.java:978)
at
org.apache.hadoop.hdfs.server.balancer.Balancer$Cli.run(Balancer.java:682)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at
org.apache.hadoop.hdfs.server.balancer.Balancer.main(Balancer.java:794)
{code}
stdout:
{code}
Starting balancer with threshold = 10
Executing command ambari-sudo.sh su hdfs -l -s /bin/bash -c 'export
PATH='''/usr/sbin:/sbin:/usr/lib/ambari-server/*:/usr/sbin:/sbin:/usr/lib/ambari-server/*:/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/opt/teradata/bynet/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin:.:/opt/teradata/sm3g/bin:/opt/dell/srvadmin/bin:/opt/dell/srvadmin/sbin:/opt/teradata/dswap/sbin:/usr/tdbms/bin:/opt/teradata/gsctools/bin:/opt/teradata/vmf/bin:/opt/teradata/bin:/var/lib/ambari-agent:/var/lib/ambari-agent:/usr/hdp/current/hadoop-client/bin'''
; hdfs --config /usr/hdp/current/hadoop-client/conf balancer -threshold 10'
2015-05-06 12:31:43,096 - Execute['ambari-sudo.sh su hdfs -l -s /bin/bash -c
'export
PATH='''/usr/sbin:/sbin:/usr/lib/ambari-server/*:/usr/sbin:/sbin:/usr/lib/ambari-server/*:/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/opt/teradata/bynet/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin:.:/opt/teradata/sm3g/bin:/opt/dell/srvadmin/bin:/opt/dell/srvadmin/sbin:/opt/teradata/dswap/sbin:/usr/tdbms/bin:/opt/teradata/gsctools/bin:/opt/teradata/vmf/bin:/opt/teradata/bin:/var/lib/ambari-agent:/var/lib/ambari-agent:/usr/hdp/current/hadoop-client/bin'''
; hdfs --config /usr/hdp/current/hadoop-client/conf balancer -threshold
10''] {'logoutput': False, 'on_new_line': handle_new_line}
[balancer] May 6, 2015 12:31:46 PM [balancer] [balancer] Balancing took
888.0 milliseconds[balancer]
[balancer] 15/05/06 12:31:46 ERROR balancer.Balancer: Exiting balancer due an
exception
java.lang.IllegalArgumentException: Does not
[jira] [Commented] (AMBARI-11747) Modify resource pre-upload script to handle recent changes to stack and HdfsResource
[ https://issues.apache.org/jira/browse/AMBARI-11747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575496#comment-14575496 ] Mahadev konar commented on AMBARI-11747: +1 for the patch. Modify resource pre-upload script to handle recent changes to stack and HdfsResource Key: AMBARI-11747 URL: https://issues.apache.org/jira/browse/AMBARI-11747 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.1.0 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Priority: Critical Fix For: 2.1.0 Attachments: AMBARI-11747.1.patch This JIRA will be used to track changes to Ambaripreupload.py script that allows uploading various artifacts to the file system outside the regular workflow of install/configure/start. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-11548) DN Decommission does not work when default file system is not hdfs
[ https://issues.apache.org/jira/browse/AMBARI-11548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14569560#comment-14569560 ] Mahadev konar commented on AMBARI-11548: +1 for the patch. DN Decommission does not work when default file system is not hdfs -- Key: AMBARI-11548 URL: https://issues.apache.org/jira/browse/AMBARI-11548 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.1.0 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Priority: Critical Fix For: 2.1.0 Attachments: AMBARI-11548.patch On HDInsight clusters, WASB is the default filesystem. Hence, decommission command should specify -fs parameter. In absence of that, we see errors of the form: Fail: Execution of 'hadoop --config /etc/hadoop/conf dfsadmin -refreshNodes' returned 255. DEPRECATED: Use of this script to execute hdfs command is deprecated. Instead use the hdfs command for it. refreshNodes: FileSystem wasb://vhhdfst...@vhamineseasia.blob.core.windows.net is not an HDFS file system Usage: hdfs dfsadmin [-refreshNodes] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-11567) Improve logging for auto recovery and record desired state for RESTART
[ https://issues.apache.org/jira/browse/AMBARI-11567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14566691#comment-14566691 ] Mahadev konar commented on AMBARI-11567: +1 for the patch Improve logging for auto recovery and record desired state for RESTART -- Key: AMBARI-11567 URL: https://issues.apache.org/jira/browse/AMBARI-11567 Project: Ambari Issue Type: Bug Components: ambari-agent Affects Versions: 2.1.0 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Fix For: 2.1.0 Attachments: AMBARI-11567.patch Add logs indicating current/desired state for EXCUTION_COMMANDS. Record desired state when RESTART is issued. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-11539) Auto recovery should recover components to INSTALLED if desired state is INSTALLED but the component instance is running
[ https://issues.apache.org/jira/browse/AMBARI-11539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14564965#comment-14564965 ] Mahadev konar commented on AMBARI-11539: +1 for the patch. Auto recovery should recover components to INSTALLED if desired state is INSTALLED but the component instance is running Key: AMBARI-11539 URL: https://issues.apache.org/jira/browse/AMBARI-11539 Project: Ambari Issue Type: Bug Components: ambari-agent Affects Versions: 2.1.0 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Priority: Critical Fix For: 2.1.0 Attachments: AMBARI-11539.patch Node recovery should also bring host components back to INSTALLED if the host component is not in INSTALLED state. If node is reset then getting to INSTALLED state is a must to get to STARTED. However, even if node is not reset it is possible that a host component may get STARTED inadvertently. Node recovery should bring it back to INSTALLED. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-11547) Bad relative path in the views pom resulting in build failure
[
https://issues.apache.org/jira/browse/AMBARI-11547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14565290#comment-14565290
]
Mahadev konar commented on AMBARI-11547:
+1
Bad relative path in the views pom resulting in build failure
-
Key: AMBARI-11547
URL: https://issues.apache.org/jira/browse/AMBARI-11547
Project: Ambari
Issue Type: Bug
Components: contrib
Affects Versions: 2.1.0
Reporter: Sumit Mohanty
Assignee: Sumit Mohanty
Priority: Critical
Fix For: 2.1.0
Attachments: AMBARI-11547.patch
{noformat}
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Ambari Project POM . SUCCESS [2.061s]
[INFO] Ambari Web SUCCESS [30.878s]
[INFO] Ambari Views .. SUCCESS [1.973s]
[INFO] Ambari Admin View . SUCCESS [53.557s]
[INFO] Ambari View Utils . FAILURE [3.265s]
[INFO] Files . SKIPPED
[INFO] Pig ... SKIPPED
[INFO] Slider SKIPPED
[INFO] Capacity Scheduler SKIPPED
[INFO] Hive .. SKIPPED
[INFO] Tez ... SKIPPED
[INFO] Ambari Metrics Common . SKIPPED
[INFO] Ambari Server . SKIPPED
[INFO] Ambari Agent .. SKIPPED
[INFO] Ambari Client . SKIPPED
[INFO] Ambari Shell .. SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1:33.038s
[INFO] Finished at: Fri May 29 19:12:22 UTC 2015
[INFO] Final Memory: 46M/1962M
[INFO]
[ERROR] Failed to execute goal org.vafer:jdeb:1.0.1:jdeb (default-cli) on
project ambari-views-utils: Failed to create debian package
/grid/0/jenkins/workspace/Ambari-2.1.0-ubuntu12/hdp-BUILDS/ambari/contrib/views/utils/target/ambari-views-utils_0.0.1~SNAPSHOT_all.deb:
/grid/0/jenkins/workspace/Ambari-2.1.0-ubuntu12/hdp-BUILDS/ambari/contrib/views/utils/../../ambari-project/src/main/package/deb/control
is not a valid 'control' directory) - [Help 1]
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-11355) Modify default capacity scheduler config properties
[ https://issues.apache.org/jira/browse/AMBARI-11355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14556953#comment-14556953 ] Mahadev konar commented on AMBARI-11355: +1 Modify default capacity scheduler config properties --- Key: AMBARI-11355 URL: https://issues.apache.org/jira/browse/AMBARI-11355 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.1.0 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Priority: Critical Fix For: 2.1.0 Attachments: AMBARI-11355.patch Delete the following properties: * yarn.scheduler.capacity.root.accessible-node-labels.default.capacity * yarn.scheduler.capacity.root.accessible-node-labels.default.maximum-capacity * yarn.scheduler.capacity.root.default-node-label-expression -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-11281) Enable Phoenix UDFs by default
[
https://issues.apache.org/jira/browse/AMBARI-11281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14553293#comment-14553293
]
Mahadev konar commented on AMBARI-11281:
Getting issues with unit tests:
{code}
AIL: test_recommendHbaseSiteConfigurations
(test_stack_advisor.TestHDP22StackAdvisor)
--
Traceback (most recent call last):
File
/Users/mkonar/workspace/ambari-workspace/ambari-git/ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py,
line 1840, in test_recommendHbaseSiteConfigurations
self.assertEquals(configurations, expected)
AssertionError: {'hbase-site': {'properties': {'hbase.regionserver.wal.codec':
'org.apache.hadoo [truncated]... != {'hbase-site': {'properties':
{'hbase.regionserver.wal.codec': 'org.apache.hadoo [truncated]...
{'hbase-env': {'properties': {'hbase_master_heapsize': '8192',
'hbase_max_direct_memory_size': '',
'hbase_regionserver_heapsize': '8192'},
'property_attributes': {'hbase_master_heapsize': {'maximum':
'49152'}}},
'hbase-site': {'properties': {'hbase.bucketcache.ioengine': '',
'hbase.bucketcache.percentage.in.combinedcache': '',
'hbase.bucketcache.size': '',
'hbase.region.server.rpc.scheduler.factory.class':
'org.apache.hadoop.hbase.ipc.PhoenixRpcSchedulerFactory',
'hbase.regionserver.global.memstore.size':
'0.4',
'hbase.regionserver.wal.codec':
'org.apache.hadoop.hbase.regionserver.wal.WALCellCodec',
'hbase.rpc.controllerfactory.class':
'org.apache.hadoop.hbase.ipc.controller.ServerRpcControllerFactory',
'phoenix.functions.allowUserDefinedFunctions':
'true'},
'property_attributes':
{'hbase.coprocessor.regionserver.classes': {'delete': 'true'},
'hbase.region.server.rpc.scheduler.factory.class': {'delete': 'true'},
- 'hbase.rpc.controllerfactory.class':
{'delete': 'true'},
?
^
+ 'hbase.rpc.controllerfactory.class':
{'delete': 'true'
?
^^^
-
'phoenix.functions.allowUserDefinedFunctions': {'delete': 'true'
--
{code}
Enable Phoenix UDFs by default
--
Key: AMBARI-11281
URL: https://issues.apache.org/jira/browse/AMBARI-11281
Project: Ambari
Issue Type: Improvement
Reporter: Ted Yu
Assignee: Ted Yu
Attachments: ambari-11281-v1.patch, ambari-11281-v2.patch
The following config parameter should be added for Phoenix deployment:
property
namephoenix.functions.allowUserDefinedFunctions/name
valuetrue/value
/property
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-11281) Enable Phoenix UDFs by default
[ https://issues.apache.org/jira/browse/AMBARI-11281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14553254#comment-14553254 ] Mahadev konar commented on AMBARI-11281: +1 for the patch. Enable Phoenix UDFs by default -- Key: AMBARI-11281 URL: https://issues.apache.org/jira/browse/AMBARI-11281 Project: Ambari Issue Type: Improvement Reporter: Ted Yu Assignee: Ted Yu Attachments: ambari-11281-v1.patch, ambari-11281-v2.patch The following config parameter should be added for Phoenix deployment: property namephoenix.functions.allowUserDefinedFunctions/name valuetrue/value /property -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-11259) Slider view build break
[
https://issues.apache.org/jira/browse/AMBARI-11259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14551590#comment-14551590
]
Mahadev konar commented on AMBARI-11259:
+1 for the patch.
Slider view build break
---
Key: AMBARI-11259
URL: https://issues.apache.org/jira/browse/AMBARI-11259
Project: Ambari
Issue Type: Bug
Components: contrib
Affects Versions: 2.1.0
Reporter: Sumit Mohanty
Assignee: Sumit Mohanty
Priority: Critical
Fix For: 2.1.0
Attachments: AMBARI-11259.patch
{noformat}
[INFO] Slider FAILURE [25.689s]
[INFO] Capacity Scheduler SKIPPED
[INFO] Hive .. SKIPPED
[INFO] Tez ... SKIPPED
[INFO] Ambari Metrics Common . SKIPPED
[INFO] Ambari Server . SKIPPED
[INFO] Ambari Agent .. SKIPPED
[INFO] Ambari Client . SKIPPED
[INFO] Ambari Shell .. SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 3:57.156s
[INFO] Finished at: Tue May 19 19:17:02 EDT 2015
[INFO] Final Memory: 59M/1963M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile)
on project slider: Compilation failure: Compilation failure:
[ERROR]
/grid/0/jenkins/workspace/Ambari-2.1.0-centos6/hdp-BUILDS/ambari/contrib/views/slider/src/main/java/org/apache/ambari/view/slider/rest/client/SliderAppMasterClient.java:[274,35]
reference to readFrom is ambiguous, both method
readFrom(java.lang.String,java.lang.String,java.lang.String,java.util.Mapjava.lang.String,java.lang.String)
in org.apache.ambari.view.URLStreamProvider and method
readFrom(java.lang.String,java.lang.String,java.io.InputStream,java.util.Mapjava.lang.String,java.lang.String)
in org.apache.ambari.view.URLStreamProvider match
[ERROR]
/grid/0/jenkins/workspace/Ambari-2.1.0-centos6/hdp-BUILDS/ambari/contrib/views/slider/src/main/java/org/apache/ambari/view/slider/rest/client/SliderAppMetricsHelper.java:[70,34]
reference to readFrom is ambiguous, both method
readFrom(java.lang.String,java.lang.String,java.lang.String,java.util.Mapjava.lang.String,java.lang.String)
in org.apache.ambari.view.URLStreamProvider and method
readFrom(java.lang.String,java.lang.String,java.io.InputStream,java.util.Mapjava.lang.String,java.lang.String)
in org.apache.ambari.view.URLStreamProvider match
[ERROR
{noformat}
Ref: AMBARI-1170.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-11259) Several views encountering build break
[
https://issues.apache.org/jira/browse/AMBARI-11259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14551653#comment-14551653
]
Mahadev konar commented on AMBARI-11259:
+1 for the hive fix.
Several views encountering build break
--
Key: AMBARI-11259
URL: https://issues.apache.org/jira/browse/AMBARI-11259
Project: Ambari
Issue Type: Bug
Components: contrib
Affects Versions: 2.1.0
Reporter: Sumit Mohanty
Assignee: Sumit Mohanty
Priority: Critical
Fix For: 2.1.0
Attachments: AMBARI-11259.2.patch, AMBARI-11259.patch
{noformat}
[INFO] Slider FAILURE [25.689s]
[INFO] Capacity Scheduler SKIPPED
[INFO] Hive .. SKIPPED
[INFO] Tez ... SKIPPED
[INFO] Ambari Metrics Common . SKIPPED
[INFO] Ambari Server . SKIPPED
[INFO] Ambari Agent .. SKIPPED
[INFO] Ambari Client . SKIPPED
[INFO] Ambari Shell .. SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 3:57.156s
[INFO] Finished at: Tue May 19 19:17:02 EDT 2015
[INFO] Final Memory: 59M/1963M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile)
on project slider: Compilation failure: Compilation failure:
[ERROR]
/grid/0/jenkins/workspace/Ambari-2.1.0-centos6/hdp-BUILDS/ambari/contrib/views/slider/src/main/java/org/apache/ambari/view/slider/rest/client/SliderAppMasterClient.java:[274,35]
reference to readFrom is ambiguous, both method
readFrom(java.lang.String,java.lang.String,java.lang.String,java.util.Mapjava.lang.String,java.lang.String)
in org.apache.ambari.view.URLStreamProvider and method
readFrom(java.lang.String,java.lang.String,java.io.InputStream,java.util.Mapjava.lang.String,java.lang.String)
in org.apache.ambari.view.URLStreamProvider match
[ERROR]
/grid/0/jenkins/workspace/Ambari-2.1.0-centos6/hdp-BUILDS/ambari/contrib/views/slider/src/main/java/org/apache/ambari/view/slider/rest/client/SliderAppMetricsHelper.java:[70,34]
reference to readFrom is ambiguous, both method
readFrom(java.lang.String,java.lang.String,java.lang.String,java.util.Mapjava.lang.String,java.lang.String)
in org.apache.ambari.view.URLStreamProvider and method
readFrom(java.lang.String,java.lang.String,java.io.InputStream,java.util.Mapjava.lang.String,java.lang.String)
in org.apache.ambari.view.URLStreamProvider match
[ERROR
{noformat}
Ref: AMBARI-1170.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-11246) Release work for Apache Ambari Release 2.0.1 RC0
[ https://issues.apache.org/jira/browse/AMBARI-11246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550888#comment-14550888 ] Mahadev konar commented on AMBARI-11246: +1 for the patch. Release work for Apache Ambari Release 2.0.1 RC0 Key: AMBARI-11246 URL: https://issues.apache.org/jira/browse/AMBARI-11246 Project: Ambari Issue Type: Task Components: ambari-agent, ambari-server Affects Versions: 2.0.1 Reporter: Jayush Luniya Assignee: Jayush Luniya Priority: Critical Fix For: 2.0.1 Attachments: AMBARI-11246.patch Release work for Apache Ambari 2.0.1 RC0. - Commit updated pom.xml versions - Follow instructions on https://cwiki.apache.org/confluence/display/AMBARI/Releasing+Ambari to generate 2.0.1 RC0 artifacts -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-8788) Add HDFS NFS gateway management
[ https://issues.apache.org/jira/browse/AMBARI-8788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14547576#comment-14547576 ] Mahadev konar commented on AMBARI-8788: --- Fixed in 2.1.0. Add HDFS NFS gateway management --- Key: AMBARI-8788 URL: https://issues.apache.org/jira/browse/AMBARI-8788 Project: Ambari Issue Type: New Feature Affects Versions: 1.7.0 Environment: HDP 2.1 Reporter: Hari Sekhon Fix For: 2.1.0 Feature request to add management of the HDFS NFS gateway to Ambari. This will need to notify user to create new Kerberos principal if adding to an already kerberized cluster (relates to AMBARI-8610). Cloudera Manager already manages HDFS NFS gateway instance. Regards, Hari Sekhon (ex-Cloudera) http://www.linkedin.com/in/harisekhon -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-8788) Add HDFS NFS gateway management
[ https://issues.apache.org/jira/browse/AMBARI-8788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar resolved AMBARI-8788. --- Resolution: Fixed Fix Version/s: 2.1.0 Add HDFS NFS gateway management --- Key: AMBARI-8788 URL: https://issues.apache.org/jira/browse/AMBARI-8788 Project: Ambari Issue Type: New Feature Affects Versions: 1.7.0 Environment: HDP 2.1 Reporter: Hari Sekhon Fix For: 2.1.0 Feature request to add management of the HDFS NFS gateway to Ambari. This will need to notify user to create new Kerberos principal if adding to an already kerberized cluster (relates to AMBARI-8610). Cloudera Manager already manages HDFS NFS gateway instance. Regards, Hari Sekhon (ex-Cloudera) http://www.linkedin.com/in/harisekhon -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-4320) Add separate CONFIGURE command support to server
[ https://issues.apache.org/jira/browse/AMBARI-4320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated AMBARI-4320: -- Fix Version/s: (was: 2.1.0) 2.2.0 Add separate CONFIGURE command support to server Key: AMBARI-4320 URL: https://issues.apache.org/jira/browse/AMBARI-4320 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: 1.5.0 Reporter: Dmitry Lysnichenko Fix For: 2.2.0 CONFIGURE command is responsible for creating files/dirs, adjusting ownership, generating config files etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-7562) Provide ability to change hostname with Ambari
[ https://issues.apache.org/jira/browse/AMBARI-7562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated AMBARI-7562: -- Assignee: (was: Alejandro Fernandez) Provide ability to change hostname with Ambari -- Key: AMBARI-7562 URL: https://issues.apache.org/jira/browse/AMBARI-7562 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: 1.6.1 Reporter: Alejandro Fernandez There are several issues associated with hosts. - Uniquely identify a host. MAC address, IP are not sufficient. Perhaps store a file so that even if the hostname changes on the same physical machine, the rename can be auto-detected. - Ability to rename: requires using FK from an primary ID that is not the hostname, will require DB schema changes. When a host is readded, need to consider what happens if the OS or environment changes. - Properly delete a host (determine if we do hard-deletes that cascade across all of the log records, or soft-deletes so that the hosts persist but not in the cluster) Expose ability (capability, steps and/or utility) to change hostnames in Ambari, to avoid users having to: a) remove hosts and re-add, or b) having to dump the database and adjust directly Note: any utility cannot expect a SQL client. It needs to assume there is no database client available to the user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
