[jira] [Commented] (AMBARI-19119) Fix hive-site.xml and hive-env.sh permissions for /etc/hive/conf (client) folder from 600 to 644.
[ https://issues.apache.org/jira/browse/AMBARI-19119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15728039#comment-15728039 ] Swapan Shridhar commented on AMBARI-19119: -- CC [~sumitmohanty] > Fix hive-site.xml and hive-env.sh permissions for /etc/hive/conf (client) > folder from 600 to 644. > - > > Key: AMBARI-19119 > URL: https://issues.apache.org/jira/browse/AMBARI-19119 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0 > > Attachments: AMBARI-19119.patch > > > - As part of change for AMBARI-19005, permissions for hive-site.xml and > hive-env.sh files in conf folder were also getting set as 600, whereas they > are expected to stay 644 (earlier it was 644). > - Adding fix for that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19119) Fix hive-site.xml and hive-env.sh permissions for /etc/hive/conf (client) folder from 600 to 644.
[ https://issues.apache.org/jira/browse/AMBARI-19119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19119: - Description: - As part of change for AMBARI-19005, permissions for hive-site.xml and hive-env.sh files in conf folder were also getting set as 600, whereas they are expected to stay 644 (earlier it was 644). - Adding fix for that. was: - As part of change for AMBARI-19005, permissions for hive-site.xml and hive-env.sh files in conf folder were also getting set as 600, whereas they are expected to stay 644 (earlier also). - Adding fix for that. > Fix hive-site.xml and hive-env.sh permissions for /etc/hive/conf (client) > folder from 600 to 644. > - > > Key: AMBARI-19119 > URL: https://issues.apache.org/jira/browse/AMBARI-19119 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0 > > Attachments: AMBARI-19119.patch > > > - As part of change for AMBARI-19005, permissions for hive-site.xml and > hive-env.sh files in conf folder were also getting set as 600, whereas they > are expected to stay 644 (earlier it was 644). > - Adding fix for that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19119) Fix hive-site.xml and hive-env.sh permissions for /etc/hive/conf (client) folder from 600 to 644.
[ https://issues.apache.org/jira/browse/AMBARI-19119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15728035#comment-15728035 ] Dmytro Grinenko commented on AMBARI-19119: -- LGTM, +1 [~swapanshridhar] FYI > Fix hive-site.xml and hive-env.sh permissions for /etc/hive/conf (client) > folder from 600 to 644. > - > > Key: AMBARI-19119 > URL: https://issues.apache.org/jira/browse/AMBARI-19119 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0 > > Attachments: AMBARI-19119.patch > > > - As part of change for AMBARI-19005, permissions for hive-site.xml and > hive-env.sh files in conf folder were also getting set as 600, whereas they > are expected to stay 644 (earlier it was 644). > - Adding fix for that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19119) Fix hive-site.xml and hive-env.sh permissions for /etc/hive/conf (client) folder from 600 to 644.
[ https://issues.apache.org/jira/browse/AMBARI-19119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19119: - Status: Patch Available (was: Open) > Fix hive-site.xml and hive-env.sh permissions for /etc/hive/conf (client) > folder from 600 to 644. > - > > Key: AMBARI-19119 > URL: https://issues.apache.org/jira/browse/AMBARI-19119 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0 > > Attachments: AMBARI-19119.patch > > > - As part of change for AMBARI-19005, permissions for hive-site.xml and > hive-env.sh files in conf folder were also getting set as 600, whereas they > are expected to stay 644 (earlier it was 644). > - Adding fix for that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19119) Fix hive-site.xml and hive-env.sh permissions for /etc/hive/conf (client) folder from 600 to 644.
[ https://issues.apache.org/jira/browse/AMBARI-19119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19119: - Attachment: AMBARI-19119.patch > Fix hive-site.xml and hive-env.sh permissions for /etc/hive/conf (client) > folder from 600 to 644. > - > > Key: AMBARI-19119 > URL: https://issues.apache.org/jira/browse/AMBARI-19119 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0 > > Attachments: AMBARI-19119.patch > > > - As part of change for AMBARI-19005, permissions for hive-site.xml and > hive-env.sh files in conf folder were also getting set as 600, whereas they > are expected to stay 644 (earlier also). > - Adding fix for that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19119) Fix hive-site.xml and hive-env.sh permissions for /etc/hive/conf (client) folder from 600 to 644.
Swapan Shridhar created AMBARI-19119: Summary: Fix hive-site.xml and hive-env.sh permissions for /etc/hive/conf (client) folder from 600 to 644. Key: AMBARI-19119 URL: https://issues.apache.org/jira/browse/AMBARI-19119 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.1 Reporter: Swapan Shridhar Assignee: Swapan Shridhar Fix For: 2.5.0 - As part of change for AMBARI-19005, permissions for hive-site.xml and hive-env.sh files in conf folder were also getting set as 600, whereas they are expected to stay 644 (earlier also). - Adding fix for that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-10500) Error installing ambari-metrics-assembly during cluster setup wizard
[
https://issues.apache.org/jira/browse/AMBARI-10500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15727939#comment-15727939
]
santhoshi commented on AMBARI-10500:
I'm getting this issue in ambari 2.4.2 while installing ambari metrics service
> Error installing ambari-metrics-assembly during cluster setup wizard
>
>
> Key: AMBARI-10500
> URL: https://issues.apache.org/jira/browse/AMBARI-10500
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.0.0
> Environment: Ubuntu 12.04 fresh installation on ProfitBricks.
>Reporter: Zoltán Marić
> Labels: ambari-server
>
> I have a small cluster on Profitbricks. It consists of 4 machines:
> the ambari server
> * a node running the name node, s name node, history server, app timeline
> server, hbase master, zookeeper server
> * a node running resource manager, metrics collector, zookeeper server
> * a node running a data node, client and the zookeeper server
> On step 9 of the installation wizard, the 1st and 3rd nodes finish installing
> with warnings, while the second fails with the following output:
> {quote}
> stderr: /var/lib/ambari-agent/data/errors-113.txt
> 2015-04-15 12:37:28,467 - Error while executing command 'install':
> 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/AMBARI_METRICS/0.1.0/package/scripts/metrics_monitor.py",
> line 28, in install
> self.install_packages(env, exclude_packages =
> ['ambari-metrics-collector'])
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 289, in install_packages
> Package(name)
> 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/package/__init__.py",
> line 43, in action_install
> self.install_package(package_name, self.resource.use_repos)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/package/apt.py",
> line 55, in wrapper
> return function_to_decorate(self, name, *args[2:])
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/package/apt.py",
> line 95, in install_package
> shell.checked_call(cmd, sudo=True, logoutput=self.get_logoutput())
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 70, in inner
> return function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 82, in checked_call
> return _call(command, logoutput, True, cwd, env, preexec_fn, user,
> wait_for_finish, timeout, path, sudo, on_new_line)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 199, in _call
> raise Fail(err_msg)
> Fail: Execution of '/usr/bin/apt-get -q -o Dpkg::Options::=--force-confdef
> --allow-unauthenticated --assume-yes install ambari-metrics-assembly'
> returned 100. Reading package lists...
> Building dependency tree...
> Reading state information...
> E: Unable to locate package ambari-metrics-assembly
> stdout: /var/lib/ambari-agent/data/output-113.txt
> 2015-04-15 12:37:13,647 -
> u"Directory['/var/lib/ambari-agent/data/tmp/AMBARI-artifacts/']"
> {'recursive': True}
> 2015-04-15 12:37:13,828 -
> u"File['/var/lib/ambari-agent/data/tmp/AMBARI-artifacts//UnlimitedJCEPolicyJDK7.zip']"
> {'content':
> DownloadSource('http://10.0.10.13:8080/resources//UnlimitedJCEPolicyJDK7.zip')}
> 2015-04-15 12:37:13,924 - Not downloading the file from
> http://10.0.10.13:8080/resources//UnlimitedJCEPolicyJDK7.zip, because
> /var/lib/ambari-agent/data/tmp/UnlimitedJCEPolicyJDK7.zip already exists
> 2015-04-15 12:37:14,106 - u"Group['hadoop']" {'ignore_failures': False}
> 2015-04-15 12:37:14,107 - Modifying group hadoop
> 2015-04-15 12:37:14,160 - u"Group['users']" {'ignore_failures': False}
> 2015-04-15 12:37:14,161 - Modifying group users
> 2015-04-15 12:37:14,211 - u"User['mapred']" {'gid': 'hadoop',
> 'ignore_failures': False, 'groups': [u'hadoop']}
> 2015-04-15 12:37:14,212 - Modifying user mapred
> 2015-04-15 12:37:14,264 - u"User['hbase']" {'gid': 'hadoop',
> 'ignore_failures': False, 'groups': [u'hadoop']}
> 2015-04-15 12:37:14,264 - Modifying user hbase
> 2015-04-15
[jira] [Updated] (AMBARI-19025) Add livy.spark.master to livy.conf and update spark-blacklist.conf
[ https://issues.apache.org/jira/browse/AMBARI-19025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated AMBARI-19025: Summary: Add livy.spark.master to livy.conf and update spark-blacklist.conf (was: Livy Configuration Change for HDP 2.6) > Add livy.spark.master to livy.conf and update spark-blacklist.conf > -- > > Key: AMBARI-19025 > URL: https://issues.apache.org/jira/browse/AMBARI-19025 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Jeff Zhang >Assignee: Jeff Zhang > > We would use livy 0.3 in HDP 2.6. and need to add livy.spark.master to > livy.conf and also update spark-blacklist.conf -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19118) Ranger Admin Start failed while enabling NameNode HA
[ https://issues.apache.org/jira/browse/AMBARI-19118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19118: -- Status: Patch Available (was: Open) > Ranger Admin Start failed while enabling NameNode HA > > > Key: AMBARI-19118 > URL: https://issues.apache.org/jira/browse/AMBARI-19118 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-19118.patch > > > Ranger Admin Start failed while enabling NameNode HA. ZooKeeper needs to be > started before Ranger. Ambari infra also needs to be started before Ranger. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19118) Ranger Admin Start failed while enabling NameNode HA
[ https://issues.apache.org/jira/browse/AMBARI-19118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19118: -- Attachment: AMBARI-19118.patch > Ranger Admin Start failed while enabling NameNode HA > > > Key: AMBARI-19118 > URL: https://issues.apache.org/jira/browse/AMBARI-19118 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-19118.patch > > > Ranger Admin Start failed while enabling NameNode HA. ZooKeeper needs to be > started before Ranger. Ambari infra also needs to be started before Ranger. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19118) Ranger Admin Start failed while enabling NameNode HA
Richard Zang created AMBARI-19118: - Summary: Ranger Admin Start failed while enabling NameNode HA Key: AMBARI-19118 URL: https://issues.apache.org/jira/browse/AMBARI-19118 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Richard Zang Assignee: Richard Zang Priority: Blocker Fix For: 2.5.0 Ranger Admin Start failed while enabling NameNode HA. ZooKeeper needs to be started before Ranger. Ambari infra also needs to be started before Ranger. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-11001) Ambari uses users' interactive ticket cache
[ https://issues.apache.org/jira/browse/AMBARI-11001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15727419#comment-15727419 ] Eric Yang edited comment on AMBARI-11001 at 12/7/16 2:16 AM: - Hi Robert, Krb5LoginModule will not have a thread to renew expired ticket, if "renewTGT=false". I concur this code change is incorrect. The file browser or Ambari functions should use doAs impersonation to interact with Hadoop services. If ticket is not renewed, file browser function would stop working. When end user present end user credential via SPNEGO ticket. Ambari suppose have a list of acl to the credential. However, receiving end user credential and sending service credential to other services are two different things. We like to understand the reason to disable service from renewing it ticket. It seems like the wrong thing to do. was (Author: eyang): Hi Robert, Krb5LoginModule will not have a thread to renew expired ticket, if "renewTGT=false". I concur this code change is incorrect. The file browser or Ambari functions should use doAs impersonation to interact with Hadoop services. If ticket is not renewed, file browser function would stop working. When end user present end user credential via SPNEGO ticket. Ambari suppose have a list of acl list to the credential. However, receiving end user credential and sending service credential to other services are two different things. We like to understand the reason to disable service from renewing it ticket. It seems like the wrong thing to do. > Ambari uses users' interactive ticket cache > --- > > Key: AMBARI-11001 > URL: https://issues.apache.org/jira/browse/AMBARI-11001 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.0 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Critical > Labels: JAAS > Fix For: 2.1.0 > > Attachments: AMBARI-11001_01.patch > > > It appears that it is necessary to kinit prior to starting ambari-server, > even after ambari-server setup-security (#3). It seems that this should be > automatically handled by Ambari. > Ambari-server should NOT use the same ticket cache as the interactive user. > STR: > 1. kinit > 2. ambari-server start > 3. verify that ambari-server can authenticate with ticket specified in #1 > 4. kdestroy > 5. try to authenticate through Ambari again (it will not work) > *Solution* > Ensure JAAS Login works properly such that the Kerberos tickets for the > account that executes Ambari is not relevant. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-11001) Ambari uses users' interactive ticket cache
[ https://issues.apache.org/jira/browse/AMBARI-11001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15727419#comment-15727419 ] Eric Yang commented on AMBARI-11001: Hi Robert, Krb5LoginModule will not have a thread to renew expired ticket, if "renewTGT=false". I concur this code change is incorrect. The file browser or Ambari functions should use doAs impersonation to interact with Hadoop services. If ticket is not renewed, file browser function would stop working. When end user present end user credential via SPNEGO ticket. Ambari suppose have a list of acl list to the credential. However, receiving end user credential and sending service credential to other services are two different things. We like to understand the reason to disable service from renewing it ticket. It seems like the wrong thing to do. > Ambari uses users' interactive ticket cache > --- > > Key: AMBARI-11001 > URL: https://issues.apache.org/jira/browse/AMBARI-11001 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.0 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Critical > Labels: JAAS > Fix For: 2.1.0 > > Attachments: AMBARI-11001_01.patch > > > It appears that it is necessary to kinit prior to starting ambari-server, > even after ambari-server setup-security (#3). It seems that this should be > automatically handled by Ambari. > Ambari-server should NOT use the same ticket cache as the interactive user. > STR: > 1. kinit > 2. ambari-server start > 3. verify that ambari-server can authenticate with ticket specified in #1 > 4. kdestroy > 5. try to authenticate through Ambari again (it will not work) > *Solution* > Ensure JAAS Login works properly such that the Kerberos tickets for the > account that executes Ambari is not relevant. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19099) Improve and Fix "Wizard pages" after new guidelines
[ https://issues.apache.org/jira/browse/AMBARI-19099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15727410#comment-15727410 ] Hudson commented on AMBARI-19099: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6171 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6171/]) AMBARI-19099. Improve and Fix 'Wizard pages' after new guidelines. (xiwang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1e261db06128143a4e631aff899704cf12709413]) * (edit) ambari-web/app/styles/wizard.less * (edit) ambari-web/app/templates/wizard/step8.hbs * (edit) ambari-web/app/styles/theme/bootstrap-ambari.css > Improve and Fix "Wizard pages" after new guidelines > --- > > Key: AMBARI-19099 > URL: https://issues.apache.org/jira/browse/AMBARI-19099 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > > In all wizard steps: > 1. should always show completed step markers in green, not grey. Even if > those steps were disabled. > 2. Summary and review page text line height. > 3. In "Assign Master" step, the green labels of components need more padding > 4. Wizard menu and content should be divided with a clean line, the line in > the red circle is not clean. This is because the background. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16914) Ambari uses too small a window for region server shutdown
[
https://issues.apache.org/jira/browse/AMBARI-16914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-16914:
---
Fix Version/s: 2.4.0
> Ambari uses too small a window for region server shutdown
> -
>
> Key: AMBARI-16914
> URL: https://issues.apache.org/jira/browse/AMBARI-16914
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web, stacks
>Affects Versions: 2.2.1
>Reporter: Shankar Venkataraman
> Fix For: 2.4.0
>
> Attachments: AMBARI-16914.patch
>
>
> Ambari seems to issue a formal shutdown to a Region server but quickly (30
> seconds) follows it up with SIGKILL. On a full loaded HBase system with
> about 200 regions per region server and active transaction flow, there is no
> way a RS can stop in 30 seconds. This has caused many issues in production
> including a memstore corruption. Why not use the shutdown script that comes
> with HBase?
> 2016-05-24 15:36:19,191 -
> Execute['/usr/hdp/current/hbase-regionserver/bin/hbase-daemon.sh --config
> /usr/hdp/current/hbase-regionserver/conf stop regionserver'] {'only_if':
> 'ambari-sudo.sh -H -E test -f /var/run/hbase/hbase-hbase-regionserver.pid &&
> ps -p `ambari-sudo.sh -H -E cat /var/run/hbase/hbase-hbase-regionserver.pid`
> >/dev/null 2>&1', 'on_timeout': '! ( ambari-sudo.sh -H -E test -f
> /var/run/hbase/hbase-hbase-regionserver.pid && ps -p `ambari-sudo.sh -H -E
> cat /var/run/hbase/hbase-hbase-regionserver.pid` >/dev/null 2>&1 ) ||
> ambari-sudo.sh -H -E kill -9 `ambari-sudo.sh -H -E cat
> /var/run/hbase/hbase-hbase-regionserver.pid`', 'timeout': 30, 'user': 'hbase'}
> 2016-05-24 15:36:50,982 - Executing '! ( ambari-sudo.sh -H -E test -f
> /var/run/hbase/hbase-hbase-regionserver.pid && ps -p `ambari-sudo.sh -H -E
> cat /var/run/hbase/hbase-hbase-regionserver.pid` >/dev/null 2>&1 ) ||
> ambari-sudo.sh -H -E kill -9 `ambari-sudo.sh -H -E cat
> /var/run/hbase/hbase-hbase-regionserver.pid`'. Reason: Execution of
> 'ambari-sudo.sh su hbase -l -s /bin/bash -c 'export
> PATH='"'"'/usr/sbin:/sbin:/usr/lib/ambari-server/*:/sbin:/usr/sbin:/bin:/usr/bin:/var/lib/ambari-agent'"'"'
> ; /usr/hdp/current/hbase-regionserver/bin/hbase-daemon.sh --config
> /usr/hdp/current/hbase-regionserver/conf stop regionserver'' was killed due
> timeout after 30 seconds
> 2016-05-24 15:36:51,053 - File['/var/run/hbase/hbase-hbase-regionserver.pid']
> {'action': ['delete']}
> 2016-05-24 15:36:51,054 - Deleting
> File['/var/run/hbase/hbase-hbase-regionserver.pid'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16914) Ambari uses too small a window for region server shutdown
[
https://issues.apache.org/jira/browse/AMBARI-16914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-16914:
---
Assignee: Andrew Onischuk
> Ambari uses too small a window for region server shutdown
> -
>
> Key: AMBARI-16914
> URL: https://issues.apache.org/jira/browse/AMBARI-16914
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web, stacks
>Affects Versions: 2.2.1
>Reporter: Shankar Venkataraman
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-16914.patch
>
>
> Ambari seems to issue a formal shutdown to a Region server but quickly (30
> seconds) follows it up with SIGKILL. On a full loaded HBase system with
> about 200 regions per region server and active transaction flow, there is no
> way a RS can stop in 30 seconds. This has caused many issues in production
> including a memstore corruption. Why not use the shutdown script that comes
> with HBase?
> 2016-05-24 15:36:19,191 -
> Execute['/usr/hdp/current/hbase-regionserver/bin/hbase-daemon.sh --config
> /usr/hdp/current/hbase-regionserver/conf stop regionserver'] {'only_if':
> 'ambari-sudo.sh -H -E test -f /var/run/hbase/hbase-hbase-regionserver.pid &&
> ps -p `ambari-sudo.sh -H -E cat /var/run/hbase/hbase-hbase-regionserver.pid`
> >/dev/null 2>&1', 'on_timeout': '! ( ambari-sudo.sh -H -E test -f
> /var/run/hbase/hbase-hbase-regionserver.pid && ps -p `ambari-sudo.sh -H -E
> cat /var/run/hbase/hbase-hbase-regionserver.pid` >/dev/null 2>&1 ) ||
> ambari-sudo.sh -H -E kill -9 `ambari-sudo.sh -H -E cat
> /var/run/hbase/hbase-hbase-regionserver.pid`', 'timeout': 30, 'user': 'hbase'}
> 2016-05-24 15:36:50,982 - Executing '! ( ambari-sudo.sh -H -E test -f
> /var/run/hbase/hbase-hbase-regionserver.pid && ps -p `ambari-sudo.sh -H -E
> cat /var/run/hbase/hbase-hbase-regionserver.pid` >/dev/null 2>&1 ) ||
> ambari-sudo.sh -H -E kill -9 `ambari-sudo.sh -H -E cat
> /var/run/hbase/hbase-hbase-regionserver.pid`'. Reason: Execution of
> 'ambari-sudo.sh su hbase -l -s /bin/bash -c 'export
> PATH='"'"'/usr/sbin:/sbin:/usr/lib/ambari-server/*:/sbin:/usr/sbin:/bin:/usr/bin:/var/lib/ambari-agent'"'"'
> ; /usr/hdp/current/hbase-regionserver/bin/hbase-daemon.sh --config
> /usr/hdp/current/hbase-regionserver/conf stop regionserver'' was killed due
> timeout after 30 seconds
> 2016-05-24 15:36:51,053 - File['/var/run/hbase/hbase-hbase-regionserver.pid']
> {'action': ['delete']}
> 2016-05-24 15:36:51,054 - Deleting
> File['/var/run/hbase/hbase-hbase-regionserver.pid'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16914) Ambari uses too small a window for region server shutdown
[
https://issues.apache.org/jira/browse/AMBARI-16914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-16914:
---
Component/s: stacks
> Ambari uses too small a window for region server shutdown
> -
>
> Key: AMBARI-16914
> URL: https://issues.apache.org/jira/browse/AMBARI-16914
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web, stacks
>Affects Versions: 2.2.1
>Reporter: Shankar Venkataraman
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-16914.patch
>
>
> Ambari seems to issue a formal shutdown to a Region server but quickly (30
> seconds) follows it up with SIGKILL. On a full loaded HBase system with
> about 200 regions per region server and active transaction flow, there is no
> way a RS can stop in 30 seconds. This has caused many issues in production
> including a memstore corruption. Why not use the shutdown script that comes
> with HBase?
> 2016-05-24 15:36:19,191 -
> Execute['/usr/hdp/current/hbase-regionserver/bin/hbase-daemon.sh --config
> /usr/hdp/current/hbase-regionserver/conf stop regionserver'] {'only_if':
> 'ambari-sudo.sh -H -E test -f /var/run/hbase/hbase-hbase-regionserver.pid &&
> ps -p `ambari-sudo.sh -H -E cat /var/run/hbase/hbase-hbase-regionserver.pid`
> >/dev/null 2>&1', 'on_timeout': '! ( ambari-sudo.sh -H -E test -f
> /var/run/hbase/hbase-hbase-regionserver.pid && ps -p `ambari-sudo.sh -H -E
> cat /var/run/hbase/hbase-hbase-regionserver.pid` >/dev/null 2>&1 ) ||
> ambari-sudo.sh -H -E kill -9 `ambari-sudo.sh -H -E cat
> /var/run/hbase/hbase-hbase-regionserver.pid`', 'timeout': 30, 'user': 'hbase'}
> 2016-05-24 15:36:50,982 - Executing '! ( ambari-sudo.sh -H -E test -f
> /var/run/hbase/hbase-hbase-regionserver.pid && ps -p `ambari-sudo.sh -H -E
> cat /var/run/hbase/hbase-hbase-regionserver.pid` >/dev/null 2>&1 ) ||
> ambari-sudo.sh -H -E kill -9 `ambari-sudo.sh -H -E cat
> /var/run/hbase/hbase-hbase-regionserver.pid`'. Reason: Execution of
> 'ambari-sudo.sh su hbase -l -s /bin/bash -c 'export
> PATH='"'"'/usr/sbin:/sbin:/usr/lib/ambari-server/*:/sbin:/usr/sbin:/bin:/usr/bin:/var/lib/ambari-agent'"'"'
> ; /usr/hdp/current/hbase-regionserver/bin/hbase-daemon.sh --config
> /usr/hdp/current/hbase-regionserver/conf stop regionserver'' was killed due
> timeout after 30 seconds
> 2016-05-24 15:36:51,053 - File['/var/run/hbase/hbase-hbase-regionserver.pid']
> {'action': ['delete']}
> 2016-05-24 15:36:51,054 - Deleting
> File['/var/run/hbase/hbase-hbase-regionserver.pid'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19089) Manage Journalnode Wizard is stuck at Add/Remove JournalNodes in Kerberized Cluster
[
https://issues.apache.org/jira/browse/AMBARI-19089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15727384#comment-15727384
]
Hadoop QA commented on AMBARI-19089:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842045/AMBARI-19089.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9557//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9557//console
This message is automatically generated.
> Manage Journalnode Wizard is stuck at Add/Remove JournalNodes in Kerberized
> Cluster
> ---
>
> Key: AMBARI-19089
> URL: https://issues.apache.org/jira/browse/AMBARI-19089
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
>Assignee: Richard Zang
> Fix For: 2.5.0
>
> Attachments: AMBARI-19089.patch, Screen Shot 2016-12-05 at 1.47.33
> PM.png
>
>
> Manage Journalnode Wizard is stuck at Add/Remove JournalNodes.
> This occured while running the test on firefox (version 29.0)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19093) HDP 3.0 support for HDFS with configs, kerberos, widgets, metrics, quicklinks, and themes
[ https://issues.apache.org/jira/browse/AMBARI-19093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15727342#comment-15727342 ] Hudson commented on AMBARI-19093: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6170 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6170/]) AMBARI-19093. HDP 3.0 support for HDFS with configs, kerberos, widgets, (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2a710b3587965c09e7b034ea79a7eca31fc35c25]) * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/configuration/ranger-hdfs-plugin-properties.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/configuration/hdfs-site.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/configuration/ranger-hdfs-policymgr-ssl.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/configuration/ranger-hdfs-security.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/configuration/core-site.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/configuration/hadoop-env.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/themes/theme.json * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/configuration/hdfs-log4j.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/configuration/widgets.json * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/metainfo.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/quicklinks/quicklinks.json * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/configuration/ranger-hdfs-audit.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/kerberos.json > HDP 3.0 support for HDFS with configs, kerberos, widgets, metrics, > quicklinks, and themes > - > > Key: AMBARI-19093 > URL: https://issues.apache.org/jira/browse/AMBARI-19093 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19093.patch > > > New service definition for HDFS in HDP 3.0 TP > * Flatten configs, metrics, widgets, kerberos -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19094) HDP 3.0 support for YARN/MR with configs, kerberos, widgets, metrics, quicklinks, and themes
[ https://issues.apache.org/jira/browse/AMBARI-19094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15727344#comment-15727344 ] Hudson commented on AMBARI-19094: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6170 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6170/]) AMBARI-19094. HDP 3.0 support for YARN/MR with configs, kerberos, (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a62119ab9f1abc355bc99ee0fc71afac6723d827]) * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration/yarn-log4j.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration/ranger-yarn-security.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration/yarn-env.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration-mapred/mapred-site.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/quicklinks/quicklinks.json * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/themes-mapred/theme.json * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/themes/theme.json * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/kerberos.json * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/YARN_widgets.json * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration/ranger-yarn-policymgr-ssl.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration/yarn-site.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration/ranger-yarn-audit.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration/ranger-yarn-plugin-properties.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration/capacity-scheduler.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/metainfo.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration-mapred/mapred-env.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/quicklinks-mapred/quicklinks.json > HDP 3.0 support for YARN/MR with configs, kerberos, widgets, metrics, > quicklinks, and themes > > > Key: AMBARI-19094 > URL: https://issues.apache.org/jira/browse/AMBARI-19094 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19094.patch > > > New service definition for YARN/MR in HDP 3.0 TP > * Flatten configs, metrics, widgets, kerberos -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19091) HDP 3.0 TP - bootstrap the stack with metainfo, cluster-env, repos, and hooks
[ https://issues.apache.org/jira/browse/AMBARI-19091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15727343#comment-15727343 ] Hudson commented on AMBARI-19091: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6170 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6170/]) AMBARI-19091. HDP 3.0 TP - bootstrap the stack with metainfo, (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=757267fc6c62dff71aeb162976de39278d40aa04]) * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-ANY/files/changeToSecureUid.sh * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/templates/health_check.j2 * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-INSTALL/scripts/params.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-ANY/scripts/hook.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/after-INSTALL/scripts/shared_initialization.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-INSTALL/scripts/hook.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-INSTALL/scripts/repo_initialization.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/scripts/hook.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/scripts/params.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/templates/exclude_hosts_list.j2 * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/after-INSTALL/scripts/hook.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/widgets.json * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/files/checkForFormat.sh * (add) ambari-server/src/main/resources/stacks/HDP/3.0/repos/repoinfo.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/templates/include_hosts_list.j2 * (add) ambari-server/src/main/resources/stacks/HDP/3.0/configuration/cluster-env.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/files/task-log4j.properties * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/files/topology_script.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/scripts/rack_awareness.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/templates/commons-logging.properties.j2 * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/scripts/shared_initialization.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/metainfo.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-ANY/scripts/params.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-INSTALL/scripts/shared_initialization.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/templates/hadoop-metrics2.properties.j2 * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-ANY/scripts/shared_initialization.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/properties/stack_tools.json * (add) ambari-server/src/main/resources/stacks/HDP/3.0/kerberos.json * (add) ambari-server/src/main/resources/stacks/HDP/3.0/properties/stack_features.json * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/templates/topology_mappings.data.j2 * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/files/fast-hdfs-resource.jar * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-RESTART/scripts/hook.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/after-INSTALL/scripts/params.py > HDP 3.0 TP - bootstrap the stack with metainfo, cluster-env, repos, and hooks > - > > Key: AMBARI-19091 > URL: https://issues.apache.org/jira/browse/AMBARI-19091 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19091.patch > > > Bootstrap the HDP 3.0 Tech Preview stack with the following > * metainfo > * configs in cluster-env > * repositories > * hooks -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19092) HDP 3.0 support for ZK with metainfo
[ https://issues.apache.org/jira/browse/AMBARI-19092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15727341#comment-15727341 ] Hudson commented on AMBARI-19092: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6170 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6170/]) AMBARI-19092. HDP 3.0 support for ZK with metainfo (alejandro) (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=aed983973034114931aca387f92bae5ca0d4e169]) * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/ZOOKEEPER/metainfo.xml > HDP 3.0 support for ZK with metainfo > > > Key: AMBARI-19092 > URL: https://issues.apache.org/jira/browse/AMBARI-19092 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19092.patch > > > New service definition for ZK in HDP 3.0 TP -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19116) Hive2/HiveServer2 (HSI) heap size calculation to be based on LLAP concurrency.
[
https://issues.apache.org/jira/browse/AMBARI-19116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15727338#comment-15727338
]
Hadoop QA commented on AMBARI-19116:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842062/AMBARI-19116.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9556//console
This message is automatically generated.
> Hive2/HiveServer2 (HSI) heap size calculation to be based on LLAP concurrency.
> --
>
> Key: AMBARI-19116
> URL: https://issues.apache.org/jira/browse/AMBARI-19116
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19116.patch
>
>
> - Currently, hive2/HiveServer2 (HSI) heap size is ket same as that of
> hive/HiveServer2.
> Required:
> - Hive2/HiveServer2 (HSI) heap size calculations to be based on LLAP
> concurrency.
> {code}
> = min(max(2GB, 400*LLAP concurrency (Tez sessions)), 3/8 * RAM>)
> {code}
> *Side fix:* Also, updated "hive.llap.daemon.queue.name" and
> "hive.server2.tez.default.queues" config values to one of the existing leaf
> queues, in case of HSI being turned on and config values have queue names
> which no more exist. The scenario can happen when, say :
> - HSI was ON and the above 2 configs has queue name 'XYZ'.
> - HSI was then turned off.
> - Capacity Scheduler queues were changed and 'XYZ' queue was deleted.
> - The above configs without this fix will otherwise show stale/non-existing
> queue name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19117) Implement Create Alerts: PORT alert configs page (step 2)
[ https://issues.apache.org/jira/browse/AMBARI-19117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-19117: - Status: Patch Available (was: Open) > Implement Create Alerts: PORT alert configs page (step 2) > - > > Key: AMBARI-19117 > URL: https://issues.apache.org/jira/browse/AMBARI-19117 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19117.patch, Step2-PORT-40% done.png > > > This is a FE task to implement the "Create Alerts Wizard " based on the > design attached. > This task is to create Step 2 of PORT alert. see the design for details. > Pay attention to the dependencies on selecting different options. The further > fields will determined by the current selection. > eg. Selecting HDP service (such as HDFS, YARN) or Custom service will display > totally different UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19117) Implement Create Alerts: PORT alert configs page (step 2)
[ https://issues.apache.org/jira/browse/AMBARI-19117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-19117: - Attachment: Step2-PORT-40% done.png > Implement Create Alerts: PORT alert configs page (step 2) > - > > Key: AMBARI-19117 > URL: https://issues.apache.org/jira/browse/AMBARI-19117 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19117.patch, Step2-PORT-40% done.png > > > This is a FE task to implement the "Create Alerts Wizard " based on the > design attached. > This task is to create Step 2 of PORT alert. see the design for details. > Pay attention to the dependencies on selecting different options. The further > fields will determined by the current selection. > eg. Selecting HDP service (such as HDFS, YARN) or Custom service will display > totally different UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19117) Implement Create Alerts: PORT alert configs page (step 2)
[ https://issues.apache.org/jira/browse/AMBARI-19117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-19117: - Attachment: AMBARI-19117.patch > Implement Create Alerts: PORT alert configs page (step 2) > - > > Key: AMBARI-19117 > URL: https://issues.apache.org/jira/browse/AMBARI-19117 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19117.patch, Step2-PORT-40% done.png > > > This is a FE task to implement the "Create Alerts Wizard " based on the > design attached. > This task is to create Step 2 of PORT alert. see the design for details. > Pay attention to the dependencies on selecting different options. The further > fields will determined by the current selection. > eg. Selecting HDP service (such as HDFS, YARN) or Custom service will display > totally different UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19093) HDP 3.0 support for HDFS with configs, kerberos, widgets, metrics, quicklinks, and themes
[ https://issues.apache.org/jira/browse/AMBARI-19093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15727326#comment-15727326 ] Hudson commented on AMBARI-19093: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #467 (See [https://builds.apache.org/job/Ambari-branch-2.5/467/]) AMBARI-19093. HDP 3.0 support for HDFS with configs, kerberos, widgets, (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0a171c0608787a8a9dd524132a85e0e46e89552c]) * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/quicklinks/quicklinks.json * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/configuration/hdfs-log4j.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/configuration/ranger-hdfs-policymgr-ssl.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/configuration/ranger-hdfs-security.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/configuration/core-site.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/configuration/ranger-hdfs-audit.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/themes/theme.json * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/kerberos.json * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/configuration/widgets.json * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/configuration/hadoop-env.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/metainfo.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/configuration/ranger-hdfs-plugin-properties.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/configuration/hdfs-site.xml > HDP 3.0 support for HDFS with configs, kerberos, widgets, metrics, > quicklinks, and themes > - > > Key: AMBARI-19093 > URL: https://issues.apache.org/jira/browse/AMBARI-19093 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19093.patch > > > New service definition for HDFS in HDP 3.0 TP > * Flatten configs, metrics, widgets, kerberos -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19092) HDP 3.0 support for ZK with metainfo
[ https://issues.apache.org/jira/browse/AMBARI-19092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15727325#comment-15727325 ] Hudson commented on AMBARI-19092: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #467 (See [https://builds.apache.org/job/Ambari-branch-2.5/467/]) AMBARI-19092. HDP 3.0 support for ZK with metainfo (alejandro) (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0d653289bbce0418929a3a698792fca133dea784]) * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/ZOOKEEPER/metainfo.xml > HDP 3.0 support for ZK with metainfo > > > Key: AMBARI-19092 > URL: https://issues.apache.org/jira/browse/AMBARI-19092 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19092.patch > > > New service definition for ZK in HDP 3.0 TP -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19091) HDP 3.0 TP - bootstrap the stack with metainfo, cluster-env, repos, and hooks
[ https://issues.apache.org/jira/browse/AMBARI-19091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15727327#comment-15727327 ] Hudson commented on AMBARI-19091: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #467 (See [https://builds.apache.org/job/Ambari-branch-2.5/467/]) AMBARI-19091. HDP 3.0 TP - bootstrap the stack with metainfo, (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=957316927f234b1b944cd0c5cab99707055ee374]) * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/after-INSTALL/scripts/shared_initialization.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/repos/repoinfo.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/files/topology_script.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-INSTALL/scripts/shared_initialization.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-ANY/scripts/hook.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-INSTALL/scripts/repo_initialization.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/widgets.json * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/files/task-log4j.properties * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-ANY/scripts/shared_initialization.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-INSTALL/scripts/params.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-ANY/files/changeToSecureUid.sh * (add) ambari-server/src/main/resources/stacks/HDP/3.0/kerberos.json * (add) ambari-server/src/main/resources/stacks/HDP/3.0/properties/stack_features.json * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/scripts/rack_awareness.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/after-INSTALL/scripts/hook.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/scripts/hook.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/templates/commons-logging.properties.j2 * (add) ambari-server/src/main/resources/stacks/HDP/3.0/metainfo.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/configuration/cluster-env.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-RESTART/scripts/hook.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/templates/hadoop-metrics2.properties.j2 * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/scripts/params.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-ANY/scripts/params.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/templates/topology_mappings.data.j2 * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/after-INSTALL/scripts/params.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-INSTALL/scripts/hook.py * (add) ambari-server/src/main/resources/stacks/HDP/3.0/properties/stack_tools.json * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/files/checkForFormat.sh * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/templates/exclude_hosts_list.j2 * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/templates/health_check.j2 * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/templates/include_hosts_list.j2 * (add) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/scripts/shared_initialization.py > HDP 3.0 TP - bootstrap the stack with metainfo, cluster-env, repos, and hooks > - > > Key: AMBARI-19091 > URL: https://issues.apache.org/jira/browse/AMBARI-19091 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19091.patch > > > Bootstrap the HDP 3.0 Tech Preview stack with the following > * metainfo > * configs in cluster-env > * repositories > * hooks -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19094) HDP 3.0 support for YARN/MR with configs, kerberos, widgets, metrics, quicklinks, and themes
[ https://issues.apache.org/jira/browse/AMBARI-19094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15727328#comment-15727328 ] Hudson commented on AMBARI-19094: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #467 (See [https://builds.apache.org/job/Ambari-branch-2.5/467/]) AMBARI-19094. HDP 3.0 support for YARN/MR with configs, kerberos, (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5309703b071f2656729fa9b7cb575f15a6520ca5]) * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/themes-mapred/theme.json * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/metainfo.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration/ranger-yarn-plugin-properties.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration/ranger-yarn-policymgr-ssl.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration/yarn-log4j.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/kerberos.json * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/quicklinks-mapred/quicklinks.json * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/themes/theme.json * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration-mapred/mapred-site.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration/yarn-env.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration/capacity-scheduler.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration/ranger-yarn-audit.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration-mapred/mapred-env.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/quicklinks/quicklinks.json * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration/yarn-site.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/YARN_widgets.json * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration/ranger-yarn-security.xml > HDP 3.0 support for YARN/MR with configs, kerberos, widgets, metrics, > quicklinks, and themes > > > Key: AMBARI-19094 > URL: https://issues.apache.org/jira/browse/AMBARI-19094 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19094.patch > > > New service definition for YARN/MR in HDP 3.0 TP > * Flatten configs, metrics, widgets, kerberos -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-19099) Improve and Fix "Wizard pages" after new guidelines
[ https://issues.apache.org/jira/browse/AMBARI-19099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang resolved AMBARI-19099. -- Resolution: Fixed > Improve and Fix "Wizard pages" after new guidelines > --- > > Key: AMBARI-19099 > URL: https://issues.apache.org/jira/browse/AMBARI-19099 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > > In all wizard steps: > 1. should always show completed step markers in green, not grey. Even if > those steps were disabled. > 2. Summary and review page text line height. > 3. In "Assign Master" step, the green labels of components need more padding > 4. Wizard menu and content should be divided with a clean line, the line in > the red circle is not clean. This is because the background. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19117) Implement Create Alerts: PORT alert configs page (step 2)
Xi Wang created AMBARI-19117: Summary: Implement Create Alerts: PORT alert configs page (step 2) Key: AMBARI-19117 URL: https://issues.apache.org/jira/browse/AMBARI-19117 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Xi Wang Assignee: Xi Wang Fix For: 3.0.0 This is a FE task to implement the "Create Alerts Wizard " based on the design attached. This task is to create Step 2 of PORT alert. see the design for details. Pay attention to the dependencies on selecting different options. The further fields will determined by the current selection. eg. Selecting HDP service (such as HDFS, YARN) or Custom service will display totally different UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19116) Hive2/HiveServer2 (HSI) heap size calculation to be based on LLAP concurrency.
[
https://issues.apache.org/jira/browse/AMBARI-19116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19116:
-
Status: Patch Available (was: Open)
> Hive2/HiveServer2 (HSI) heap size calculation to be based on LLAP concurrency.
> --
>
> Key: AMBARI-19116
> URL: https://issues.apache.org/jira/browse/AMBARI-19116
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19116.patch
>
>
> - Currently, hive2/HiveServer2 (HSI) heap size is ket same as that of
> hive/HiveServer2.
> Required:
> - Hive2/HiveServer2 (HSI) heap size calculations to be based on LLAP
> concurrency.
> {code}
> = min(max(2GB, 400*LLAP concurrency (Tez sessions)), 3/8 * RAM>)
> {code}
> *Side fix:* Also, updated "hive.llap.daemon.queue.name" and
> "hive.server2.tez.default.queues" config values to one of the existing leaf
> queues, in case of HSI being turned on and config values have queue names
> which no more exist. The scenario can happen when, say :
> - HSI was ON and the above 2 configs has queue name 'XYZ'.
> - HSI was then turned off.
> - Capacity Scheduler queues were changed and 'XYZ' queue was deleted.
> - The above configs without this fix will otherwise show stale/non-existing
> queue name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19116) Hive2/HiveServer2 (HSI) heap size calculation to be based on LLAP concurrency.
[
https://issues.apache.org/jira/browse/AMBARI-19116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19116:
-
Attachment: AMBARI-19116.patch
> Hive2/HiveServer2 (HSI) heap size calculation to be based on LLAP concurrency.
> --
>
> Key: AMBARI-19116
> URL: https://issues.apache.org/jira/browse/AMBARI-19116
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19116.patch
>
>
> - Currently, hive2/HiveServer2 (HSI) heap size is ket same as that of
> hive/HiveServer2.
> Required:
> - Hive2/HiveServer2 (HSI) heap size calculations to be based on LLAP
> concurrency.
> {code}
> = min(max(2GB, 400*LLAP concurrency (Tez sessions)), 3/8 * RAM>)
> {code}
> *Side fix:* Also, updated "hive.llap.daemon.queue.name" and
> "hive.server2.tez.default.queues" config values to one of the existing leaf
> queues, in case of HSI being turned on and config values have queue names
> which no more exist. The scenario can happen when, say :
> - HSI was ON and the above 2 configs has queue name 'XYZ'.
> - HSI was then turned off.
> - Capacity Scheduler queues were changed and 'XYZ' queue was deleted.
> - The above configs without this fix will otherwise show stale/non-existing
> queue name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19116) Hive2/HiveServer2 (HSI) heap size calculation to be based on LLAP concurrency.
[
https://issues.apache.org/jira/browse/AMBARI-19116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19116:
-
Description:
- Currently, hive2/HiveServer2 (HSI) heap size is ket same as that of
hive/HiveServer2.
Required:
- Hive2/HiveServer2 (HSI) heap size calculations to be based on LLAP
concurrency.
{code}
= min(max(2GB, 400*LLAP concurrency (Tez sessions)), 3/8 * )
{code}
Side fix: Also, updated "hive.llap.daemon.queue.name" and
"hive.server2.tez.default.queues" config values to one of the existing leaf
queues, in case of HSI being turned on and config values have queue names which
no more exist. The scenario can happen when, say :
- HSI was ON and the above 2 configs has queue name 'XYZ'.
- HSI was then turned off.
- Capacity Scheduler queues were changed and 'XYZ' queue was deleted.
- The above configs without this fix will otherwise show stale/non-existing
queue name.
was:
- Currently, hive2/HiveServer2 (HSI) heap size is ket same as that of
hive/HiveServer2.
Required:
- Hive2/HiveServer2 (HSI) heap size calculations to be based on LLAP
concurrency.
{code}
= min(max(2GB, 400*LLAP concurrency (Tez sessions)), 3/8 * )
{code}
Also, updated "hive.llap.daemon.queue.name" and
"hive.server2.tez.default.queues" config values to one of the existing leaf
queues, in case of HSI being turned on and config values have queue names which
no more exist. The scenario can happen when, say :
- HSI was ON and the above 2 configs has queue name 'XYZ'.
- HSI was then turned off.
- Capacity Scheduler queues were changed and 'XYZ' queue was deleted.
- The above configs without this fix will otherwise show stale/non-existing
queue name.
> Hive2/HiveServer2 (HSI) heap size calculation to be based on LLAP concurrency.
> --
>
> Key: AMBARI-19116
> URL: https://issues.apache.org/jira/browse/AMBARI-19116
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
>
> - Currently, hive2/HiveServer2 (HSI) heap size is ket same as that of
> hive/HiveServer2.
> Required:
> - Hive2/HiveServer2 (HSI) heap size calculations to be based on LLAP
> concurrency.
> {code}
> = min(max(2GB, 400*LLAP concurrency (Tez sessions)), 3/8 * RAM>)
> {code}
> Side fix: Also, updated "hive.llap.daemon.queue.name" and
> "hive.server2.tez.default.queues" config values to one of the existing leaf
> queues, in case of HSI being turned on and config values have queue names
> which no more exist. The scenario can happen when, say :
> - HSI was ON and the above 2 configs has queue name 'XYZ'.
> - HSI was then turned off.
> - Capacity Scheduler queues were changed and 'XYZ' queue was deleted.
> - The above configs without this fix will otherwise show stale/non-existing
> queue name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19116) Hive2/HiveServer2 (HSI) heap size calculation to be based on LLAP concurrency.
[
https://issues.apache.org/jira/browse/AMBARI-19116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19116:
-
Description:
- Currently, hive2/HiveServer2 (HSI) heap size is ket same as that of
hive/HiveServer2.
Required:
- Hive2/HiveServer2 (HSI) heap size calculations to be based on LLAP
concurrency.
{code}
= min(max(2GB, 400*LLAP concurrency (Tez sessions)), 3/8 * )
{code}
*Side fix:* Also, updated "hive.llap.daemon.queue.name" and
"hive.server2.tez.default.queues" config values to one of the existing leaf
queues, in case of HSI being turned on and config values have queue names which
no more exist. The scenario can happen when, say :
- HSI was ON and the above 2 configs has queue name 'XYZ'.
- HSI was then turned off.
- Capacity Scheduler queues were changed and 'XYZ' queue was deleted.
- The above configs without this fix will otherwise show stale/non-existing
queue name.
was:
- Currently, hive2/HiveServer2 (HSI) heap size is ket same as that of
hive/HiveServer2.
Required:
- Hive2/HiveServer2 (HSI) heap size calculations to be based on LLAP
concurrency.
{code}
= min(max(2GB, 400*LLAP concurrency (Tez sessions)), 3/8 * )
{code}
Side fix: Also, updated "hive.llap.daemon.queue.name" and
"hive.server2.tez.default.queues" config values to one of the existing leaf
queues, in case of HSI being turned on and config values have queue names which
no more exist. The scenario can happen when, say :
- HSI was ON and the above 2 configs has queue name 'XYZ'.
- HSI was then turned off.
- Capacity Scheduler queues were changed and 'XYZ' queue was deleted.
- The above configs without this fix will otherwise show stale/non-existing
queue name.
> Hive2/HiveServer2 (HSI) heap size calculation to be based on LLAP concurrency.
> --
>
> Key: AMBARI-19116
> URL: https://issues.apache.org/jira/browse/AMBARI-19116
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
>
> - Currently, hive2/HiveServer2 (HSI) heap size is ket same as that of
> hive/HiveServer2.
> Required:
> - Hive2/HiveServer2 (HSI) heap size calculations to be based on LLAP
> concurrency.
> {code}
> = min(max(2GB, 400*LLAP concurrency (Tez sessions)), 3/8 * RAM>)
> {code}
> *Side fix:* Also, updated "hive.llap.daemon.queue.name" and
> "hive.server2.tez.default.queues" config values to one of the existing leaf
> queues, in case of HSI being turned on and config values have queue names
> which no more exist. The scenario can happen when, say :
> - HSI was ON and the above 2 configs has queue name 'XYZ'.
> - HSI was then turned off.
> - Capacity Scheduler queues were changed and 'XYZ' queue was deleted.
> - The above configs without this fix will otherwise show stale/non-existing
> queue name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19116) Hive2/HiveServer2 (HSI) heap size calculation to be based on LLAP concurrency.
[
https://issues.apache.org/jira/browse/AMBARI-19116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19116:
-
Description:
- Currently, hive2/HiveServer2 (HSI) heap size is ket same as that of
hive/HiveServer2.
Required:
- Hive2/HiveServer2 (HSI) heap size calculations to be based on LLAP
concurrency.
{code}
= min(max(2GB, 400*LLAP concurrency (Tez sessions)), 3/8 * )
{code}
Also, updated "hive.llap.daemon.queue.name" and
"hive.server2.tez.default.queues" config values to one of the existing leaf
queues, in case of HSI being turned on and config values have queue names which
no more exist. The scenario can happen when, say :
- HSI was ON and the above 2 configs has queue name 'XYZ'.
- HSI was then turned off.
- Capacity Scheduler queues were changed and 'XYZ' queue was deleted.
- The above configs without this fix will otherwise show stale/non-existing
queue name.
was:
- Currently, hive2/HiveServer2 (HSI) heap size is ket same as that of
hive/HiveServer2.
Required:
- Hive2/HiveServer2 (HSI) heap size calculations to be based on LLAP
concurrency.
{code}
= min(max(2GB, 400*LLAP concurrency (Tez sessions)), 3/8 * )
{code}
> Hive2/HiveServer2 (HSI) heap size calculation to be based on LLAP concurrency.
> --
>
> Key: AMBARI-19116
> URL: https://issues.apache.org/jira/browse/AMBARI-19116
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
>
> - Currently, hive2/HiveServer2 (HSI) heap size is ket same as that of
> hive/HiveServer2.
> Required:
> - Hive2/HiveServer2 (HSI) heap size calculations to be based on LLAP
> concurrency.
> {code}
> = min(max(2GB, 400*LLAP concurrency (Tez sessions)), 3/8 * RAM>)
> {code}
> Also, updated "hive.llap.daemon.queue.name" and
> "hive.server2.tez.default.queues" config values to one of the existing leaf
> queues, in case of HSI being turned on and config values have queue names
> which no more exist. The scenario can happen when, say :
> - HSI was ON and the above 2 configs has queue name 'XYZ'.
> - HSI was then turned off.
> - Capacity Scheduler queues were changed and 'XYZ' queue was deleted.
> - The above configs without this fix will otherwise show stale/non-existing
> queue name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19093) HDP 3.0 support for HDFS with configs, kerberos, widgets, metrics, quicklinks, and themes
[ https://issues.apache.org/jira/browse/AMBARI-19093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19093: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk, commit 2a710b3587965c09e7b034ea79a7eca31fc35c25 branch-2.5, commit 0a171c0608787a8a9dd524132a85e0e46e89552c > HDP 3.0 support for HDFS with configs, kerberos, widgets, metrics, > quicklinks, and themes > - > > Key: AMBARI-19093 > URL: https://issues.apache.org/jira/browse/AMBARI-19093 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19093.patch > > > New service definition for HDFS in HDP 3.0 TP > * Flatten configs, metrics, widgets, kerberos -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19091) HDP 3.0 TP - bootstrap the stack with metainfo, cluster-env, repos, and hooks
[ https://issues.apache.org/jira/browse/AMBARI-19091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19091: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk, commit 757267fc6c62dff71aeb162976de39278d40aa04 branch-2.5, commit 957316927f234b1b944cd0c5cab99707055ee374 > HDP 3.0 TP - bootstrap the stack with metainfo, cluster-env, repos, and hooks > - > > Key: AMBARI-19091 > URL: https://issues.apache.org/jira/browse/AMBARI-19091 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19091.patch > > > Bootstrap the HDP 3.0 Tech Preview stack with the following > * metainfo > * configs in cluster-env > * repositories > * hooks -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19092) HDP 3.0 support for ZK with metainfo
[ https://issues.apache.org/jira/browse/AMBARI-19092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19092: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk, commit aed983973034114931aca387f92bae5ca0d4e169 branch-2.5, commit 0d653289bbce0418929a3a698792fca133dea784 > HDP 3.0 support for ZK with metainfo > > > Key: AMBARI-19092 > URL: https://issues.apache.org/jira/browse/AMBARI-19092 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19092.patch > > > New service definition for ZK in HDP 3.0 TP -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19094) HDP 3.0 support for YARN/MR with configs, kerberos, widgets, metrics, quicklinks, and themes
[ https://issues.apache.org/jira/browse/AMBARI-19094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19094: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk, commit a62119ab9f1abc355bc99ee0fc71afac6723d827 branch-2.5, commit 5309703b071f2656729fa9b7cb575f15a6520ca5 > HDP 3.0 support for YARN/MR with configs, kerberos, widgets, metrics, > quicklinks, and themes > > > Key: AMBARI-19094 > URL: https://issues.apache.org/jira/browse/AMBARI-19094 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19094.patch > > > New service definition for YARN/MR in HDP 3.0 TP > * Flatten configs, metrics, widgets, kerberos -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19116) Hive2/HiveServer2 (HSI) heap size calculation to be based on LLAP concurrency.
[
https://issues.apache.org/jira/browse/AMBARI-19116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19116:
-
Summary: Hive2/HiveServer2 (HSI) heap size calculation to be based on LLAP
concurrency. (was: Hive2/HiveServer2 (HSI) heap size calculations to be based
on LLAP concurrency.)
> Hive2/HiveServer2 (HSI) heap size calculation to be based on LLAP concurrency.
> --
>
> Key: AMBARI-19116
> URL: https://issues.apache.org/jira/browse/AMBARI-19116
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
>
> - Currently, hive2/HiveServer2 (HSI) heap size is ket same as that of
> hive/HiveServer2.
> Required:
> - Hive2/HiveServer2 (HSI) heap size calculations to be based on LLAP
> concurrency.
> {code}
> = min(max(2GB, 400*LLAP concurrency (Tez sessions)), 3/8 * RAM>)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19116) Hive2/HiveServer2 (HSI) heap size calculations to be based on LLAP concurrency.
Swapan Shridhar created AMBARI-19116:
Summary: Hive2/HiveServer2 (HSI) heap size calculations to be
based on LLAP concurrency.
Key: AMBARI-19116
URL: https://issues.apache.org/jira/browse/AMBARI-19116
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.1
Reporter: Swapan Shridhar
Assignee: Swapan Shridhar
Priority: Critical
Fix For: 2.5.0
- Currently, hive2/HiveServer2 (HSI) heap size is ket same as that of
hive/HiveServer2.
Required:
- Hive2/HiveServer2 (HSI) heap size calculations to be based on LLAP
concurrency.
{code}
= min(max(2GB, 400*LLAP concurrency (Tez sessions)), 3/8 * )
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19107) False warning about NTP not running on SUSE12
[
https://issues.apache.org/jira/browse/AMBARI-19107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15727241#comment-15727241
]
Hudson commented on AMBARI-19107:
-
ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #466 (See
[https://builds.apache.org/job/Ambari-branch-2.5/466/])
AMBARI-19107. False warning about NTP not running on SUSE12. (Attila (swagle:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4eaa1b320983f808b1e15ebc28a13cdca4188221])
* (edit) ambari-agent/src/main/python/ambari_agent/HostInfo.py
> False warning about NTP not running on SUSE12
> -
>
> Key: AMBARI-19107
> URL: https://issues.apache.org/jira/browse/AMBARI-19107
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
> Environment: SUSE12
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19107.patch
>
>
> When installing cluster via wizard on SUSE12, the host checks generate a
> warning that NTP is no running even if it is. The problem is that on SUSE12
> the service is called {{ntpd}}, not {{ntp}} (although the package is {{ntp}}):
> {noformat}
> zypper install ntp
> service ntpd start
> {noformat}
> On a related note: Ambari supports {{chrony}} as an alternative to NTP only
> on RedHat7+, but it is also available on RedHat6 and Ubuntu.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19101) Merge AMS service check support for HA from trunk
[ https://issues.apache.org/jira/browse/AMBARI-19101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15727247#comment-15727247 ] Hudson commented on AMBARI-19101: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6169 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6169/]) AMBARI-19101 : Merge AMS service check support for HA from trunk. (dsen, (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9a938e6cc27811057895d495f700a8e874c69a10]) * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/service_check.py * (edit) ambari-common/src/main/python/ambari_commons/ambari_metrics_helper.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py * (edit) ambari-server/src/main/resources/stacks/HDPWIN/2.1/hooks/before-START/scripts/params.py > Merge AMS service check support for HA from trunk > - > > Key: AMBARI-19101 > URL: https://issues.apache.org/jira/browse/AMBARI-19101 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19101-2.5.patch, AMBARI-19101-trunk.patch > > > AMBARI-17457 was missed while backporting AMS HA commits into branch-2.5. > Hence, service_check.py for AMS in branch-2.5 and trunk are different, no AMS > HA support in branch-2.5. > Applied AMBARI-17457 patch, and made changes to so that the service check and > Grafana datasource creation is compatible with changes introduced through > AMBARI-19032. > Part of these changes may be checked into trunk as well, to maintain parity. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19107) False warning about NTP not running on SUSE12
[
https://issues.apache.org/jira/browse/AMBARI-19107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15727246#comment-15727246
]
Hudson commented on AMBARI-19107:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6169 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6169/])
AMBARI-19107. False warning about NTP not running on SUSE12. (Attila (swagle:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=641886160877e4bc4c38e9d461967285d77bd0c3])
* (edit) ambari-agent/src/main/python/ambari_agent/HostInfo.py
> False warning about NTP not running on SUSE12
> -
>
> Key: AMBARI-19107
> URL: https://issues.apache.org/jira/browse/AMBARI-19107
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
> Environment: SUSE12
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19107.patch
>
>
> When installing cluster via wizard on SUSE12, the host checks generate a
> warning that NTP is no running even if it is. The problem is that on SUSE12
> the service is called {{ntpd}}, not {{ntp}} (although the package is {{ntp}}):
> {noformat}
> zypper install ntp
> service ntpd start
> {noformat}
> On a related note: Ambari supports {{chrony}} as an alternative to NTP only
> on RedHat7+, but it is also available on RedHat6 and Ubuntu.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19101) Merge AMS service check support for HA from trunk
[ https://issues.apache.org/jira/browse/AMBARI-19101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15727242#comment-15727242 ] Hudson commented on AMBARI-19101: - ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #466 (See [https://builds.apache.org/job/Ambari-branch-2.5/466/]) AMBARI-19101 : Merge AMS service check support for HA from trunk. (dsen, (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ee5651dcfbba9be46b58b06dd44c667da29255fe]) * (edit) ambari-common/src/main/python/ambari_commons/ambari_metrics_helper.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/service_check.py * (edit) ambari-server/src/main/resources/stacks/HDPWIN/2.1/hooks/before-START/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/templates/metrics_grafana_datasource.json.j2 * (add) ambari-common/src/main/python/ambari_commons/parallel_processing.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py > Merge AMS service check support for HA from trunk > - > > Key: AMBARI-19101 > URL: https://issues.apache.org/jira/browse/AMBARI-19101 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19101-2.5.patch, AMBARI-19101-trunk.patch > > > AMBARI-17457 was missed while backporting AMS HA commits into branch-2.5. > Hence, service_check.py for AMS in branch-2.5 and trunk are different, no AMS > HA support in branch-2.5. > Applied AMBARI-17457 patch, and made changes to so that the service check and > Grafana datasource creation is compatible with changes introduced through > AMBARI-19032. > Part of these changes may be checked into trunk as well, to maintain parity. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19099) Improve and Fix "Wizard pages" after new guidelines
[ https://issues.apache.org/jira/browse/AMBARI-19099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15727214#comment-15727214 ] Xi Wang commented on AMBARI-19099: -- 19926 tests complete (47 seconds) 155 tests pending > Improve and Fix "Wizard pages" after new guidelines > --- > > Key: AMBARI-19099 > URL: https://issues.apache.org/jira/browse/AMBARI-19099 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > > In all wizard steps: > 1. should always show completed step markers in green, not grey. Even if > those steps were disabled. > 2. Summary and review page text line height. > 3. In "Assign Master" step, the green labels of components need more padding > 4. Wizard menu and content should be divided with a clean line, the line in > the red circle is not clean. This is because the background. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19099) Improve and Fix "Wizard pages" after new guidelines
[ https://issues.apache.org/jira/browse/AMBARI-19099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15727216#comment-15727216 ] Xi Wang commented on AMBARI-19099: -- Got +1 from review board > Improve and Fix "Wizard pages" after new guidelines > --- > > Key: AMBARI-19099 > URL: https://issues.apache.org/jira/browse/AMBARI-19099 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > > In all wizard steps: > 1. should always show completed step markers in green, not grey. Even if > those steps were disabled. > 2. Summary and review page text line height. > 3. In "Assign Master" step, the green labels of components need more padding > 4. Wizard menu and content should be divided with a clean line, the line in > the red circle is not clean. This is because the background. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19112) Grafana start failing at create datasource step
[
https://issues.apache.org/jira/browse/AMBARI-19112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15727173#comment-15727173
]
Hudson commented on AMBARI-19112:
-
ABORTED: Integrated in Jenkins build Ambari-trunk-Commit #6168 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6168/])
AMBARI-19112 : Grafana start failing at create datasource step (and a
(avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=502d4447fa7f78421e606cff83661b41c4923a61])
* (edit)
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java
> Grafana start failing at create datasource step
> ---
>
> Key: AMBARI-19112
> URL: https://issues.apache.org/jira/browse/AMBARI-19112
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19112.patch
>
>
> grafana failed to start due to following error
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 77, in
> AmsGrafana().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 282, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 58, in start
> create_ams_datasource()
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py",
> line 205, in create_ams_datasource
> response = perform_grafana_get_call(GRAFANA_DATASOURCE_URL, server)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py",
> line 67, in perform_grafana_get_call
> raise Fail("Ambari Metrics Grafana update failed due to: %s" % str(ex))
> resource_management.core.exceptions.Fail: Ambari Metrics Grafana update
> failed due to: [Errno 111] Connection refused
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19094) HDP 3.0 support for YARN/MR with configs, kerberos, widgets, metrics, quicklinks, and themes
[ https://issues.apache.org/jira/browse/AMBARI-19094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19094: - Description: New service definition for YARN/MR in HDP 3.0 TP * Flatten configs, metrics, widgets, kerberos was: New service definition for YARN/MR in HDP 3.0 TP * Flatten configs, metrics, widgets, kerberos * Break up Stack Advisor into Service Advisor > HDP 3.0 support for YARN/MR with configs, kerberos, widgets, metrics, > quicklinks, and themes > > > Key: AMBARI-19094 > URL: https://issues.apache.org/jira/browse/AMBARI-19094 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19094.patch > > > New service definition for YARN/MR in HDP 3.0 TP > * Flatten configs, metrics, widgets, kerberos -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19094) HDP 3.0 support for YARN/MR with configs, kerberos, widgets, metrics, quicklinks, and themes
[ https://issues.apache.org/jira/browse/AMBARI-19094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19094: - Attachment: AMBARI-19094.patch > HDP 3.0 support for YARN/MR with configs, kerberos, widgets, metrics, > quicklinks, and themes > > > Key: AMBARI-19094 > URL: https://issues.apache.org/jira/browse/AMBARI-19094 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-19094.patch > > > New service definition for YARN/MR in HDP 3.0 TP > * Flatten configs, metrics, widgets, kerberos > * Break up Stack Advisor into Service Advisor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19089) Manage Journalnode Wizard is stuck at Add/Remove JournalNodes in Kerberized Cluster
[ https://issues.apache.org/jira/browse/AMBARI-19089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19089: -- Status: Patch Available (was: Open) > Manage Journalnode Wizard is stuck at Add/Remove JournalNodes in Kerberized > Cluster > --- > > Key: AMBARI-19089 > URL: https://issues.apache.org/jira/browse/AMBARI-19089 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Rathod >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-19089.patch, Screen Shot 2016-12-05 at 1.47.33 > PM.png > > > Manage Journalnode Wizard is stuck at Add/Remove JournalNodes. > This occured while running the test on firefox (version 29.0) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19089) Manage Journalnode Wizard is stuck at Add/Remove JournalNodes in Kerberized Cluster
[ https://issues.apache.org/jira/browse/AMBARI-19089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19089: -- Summary: Manage Journalnode Wizard is stuck at Add/Remove JournalNodes in Kerberized Cluster (was: Manage Journalnode Wizard is stuck at Add/Remove JournalNodes2 of 310 Return to search) > Manage Journalnode Wizard is stuck at Add/Remove JournalNodes in Kerberized > Cluster > --- > > Key: AMBARI-19089 > URL: https://issues.apache.org/jira/browse/AMBARI-19089 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Rathod >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-19089.patch, Screen Shot 2016-12-05 at 1.47.33 > PM.png > > > Manage Journalnode Wizard is stuck at Add/Remove JournalNodes. > This occured while running the test on firefox (version 29.0) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19089) Manage Journalnode Wizard is stuck at Add/Remove JournalNodes 2 of 310 Return to search
[ https://issues.apache.org/jira/browse/AMBARI-19089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19089: -- Attachment: AMBARI-19089.patch > Manage Journalnode Wizard is stuck at Add/Remove JournalNodes 2 of 310 > Return to search > > > Key: AMBARI-19089 > URL: https://issues.apache.org/jira/browse/AMBARI-19089 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Rathod >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-19089.patch, Screen Shot 2016-12-05 at 1.47.33 > PM.png > > > Manage Journalnode Wizard is stuck at Add/Remove JournalNodes. > This occured while running the test on firefox (version 29.0) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-19089) Manage Journalnode Wizard is stuck at Add/Remove JournalNodes 2 of 310 Return to search
[ https://issues.apache.org/jira/browse/AMBARI-19089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang reassigned AMBARI-19089: - Assignee: Richard Zang > Manage Journalnode Wizard is stuck at Add/Remove JournalNodes 2 of 310 > Return to search > > > Key: AMBARI-19089 > URL: https://issues.apache.org/jira/browse/AMBARI-19089 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Rathod >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: Screen Shot 2016-12-05 at 1.47.33 PM.png > > > Manage Journalnode Wizard is stuck at Add/Remove JournalNodes. > This occured while running the test on firefox (version 29.0) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19113) Add timeout for LogSearch and Infra Solr metainfo.xml
[
https://issues.apache.org/jira/browse/AMBARI-19113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15726953#comment-15726953
]
Hadoop QA commented on AMBARI-19113:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842027/AMBARI-19113.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9555//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9555//console
This message is automatically generated.
> Add timeout for LogSearch and Infra Solr metainfo.xml
> -
>
> Key: AMBARI-19113
> URL: https://issues.apache.org/jira/browse/AMBARI-19113
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch, ambari-server
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19113.patch
>
>
> Add more timeout as a workaround for slow env startup (e.g. wait too much
> time for multiple zookeepers to start).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19115) Metrics Monitor start failed: ERROR: Cannot write pid /grid/0/pid/metric_monitor/ambari-metrics-monitor.pid
Vivek Rathod created AMBARI-19115:
-
Summary: Metrics Monitor start failed: ERROR: Cannot write pid
/grid/0/pid/metric_monitor/ambari-metrics-monitor.pid
Key: AMBARI-19115
URL: https://issues.apache.org/jira/browse/AMBARI-19115
Project: Ambari
Issue Type: Bug
Affects Versions: 2.5.0
Reporter: Vivek Rathod
Fix For: 2.5.0
STR: Install cluster with 4 services: HDFS, Flume, AMS and Smartsense, with
custom PID's
Metrics Monitor start fails while starting services
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_monitor.py",
line 68, in
AmsMonitor().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 282, in execute
method(env)
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_monitor.py",
line 42, in start
action = 'start'
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/AMBARI_METRICS/0.1.0/package/scripts/ams_service.py",
line 103, in ams_service
user=params.ams_user
File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
line 155, in __init__
self.env.run()
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
line 262, 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 72, in inner
result = function(command, **kwargs)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 102, in checked_call
tries=tries, try_sleep=try_sleep,
timeout_kill_strategy=timeout_kill_strategy)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 150, in _call_wrapper
result = _call(command, **kwargs_copy)
File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
line 303, in _call
raise ExecutionFailed(err_msg, code, out, err)
resource_management.core.exceptions.ExecutionFailed: Execution of
'/usr/sbin/ambari-metrics-monitor --config /etc/ambari-metrics-monitor/conf
start' returned 1. Hortonworks #
This is MOTD message, added for testing in qe infra
Building psutil...
running build
running build_py
creating build/lib.linux-x86_64-2.6
creating build/lib.linux-x86_64-2.6/psutil
copying psutil/__init__.py -> build/lib.linux-x86_64-2.6/psutil
copying psutil/_common.py -> build/lib.linux-x86_64-2.6/psutil
copying psutil/_compat.py -> build/lib.linux-x86_64-2.6/psutil
copying psutil/_psbsd.py -> build/lib.linux-x86_64-2.6/psutil
copying psutil/_pslinux.py -> build/lib.linux-x86_64-2.6/psutil
copying psutil/_psosx.py -> build/lib.linux-x86_64-2.6/psutil
copying psutil/_psposix.py -> build/lib.linux-x86_64-2.6/psutil
copying psutil/_pssunos.py -> build/lib.linux-x86_64-2.6/psutil
copying psutil/_pswindows.py -> build/lib.linux-x86_64-2.6/psutil
running build_ext
building '_psutil_linux' extension
creating build/temp.linux-x86_64-2.6
creating build/temp.linux-x86_64-2.6/psutil
gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic
-D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic
-D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/usr/include/python2.6 -c
psutil/_psutil_linux.c -o build/temp.linux-x86_64-2.6/psutil/_psutil_linux.o
psutil/_psutil_linux.c: In function ‘psutil_proc_cpu_affinity_set’:
psutil/_psutil_linux.c:327: warning: suggest explicit braces to avoid ambiguous
‘else’
gcc -pthread -shared build/temp.linux-x86_64-2.6/psutil/_psutil_linux.o
-L/usr/lib64 -lpython2.6 -o build/lib.linux-x86_64-2.6/_psutil_linux.so
building '_psutil_posix' extension
gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic
-D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic
-D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/usr/include/python2.6 -c
psutil/_psutil_posix.c -o build/temp.linux-x86_64-2.6/psutil/_psutil_posix.o
gcc -pthread -shared build/temp.linux-x86_64-2.6/psutil/_psutil_posix.o
-L/usr/lib64 -lpython2.6 -o
[jira] [Commented] (AMBARI-19114) Update hardcoded stack version warning to be more general than saying hdp
[
https://issues.apache.org/jira/browse/AMBARI-19114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15726895#comment-15726895
]
Hadoop QA commented on AMBARI-19114:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842029/AMBARI-19114.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9554//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9554//console
This message is automatically generated.
> Update hardcoded stack version warning to be more general than saying hdp
> -
>
> Key: AMBARI-19114
> URL: https://issues.apache.org/jira/browse/AMBARI-19114
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Di Li
>Assignee: Di Li
>Priority: Minor
> Attachments: AMBARI-19114.patch
>
>
> Update hardcoded stack version warning to be more general than saying hdp
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19114) Update hardcoded stack version warning to be more general than saying hdp
Di Li created AMBARI-19114: -- Summary: Update hardcoded stack version warning to be more general than saying hdp Key: AMBARI-19114 URL: https://issues.apache.org/jira/browse/AMBARI-19114 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk, 2.5.0 Reporter: Di Li Assignee: Di Li Priority: Minor Update hardcoded stack version warning to be more general than saying hdp -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19107) False warning about NTP not running on SUSE12
[
https://issues.apache.org/jira/browse/AMBARI-19107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15726732#comment-15726732
]
Doroszlai, Attila commented on AMBARI-19107:
Thanks.
> False warning about NTP not running on SUSE12
> -
>
> Key: AMBARI-19107
> URL: https://issues.apache.org/jira/browse/AMBARI-19107
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
> Environment: SUSE12
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19107.patch
>
>
> When installing cluster via wizard on SUSE12, the host checks generate a
> warning that NTP is no running even if it is. The problem is that on SUSE12
> the service is called {{ntpd}}, not {{ntp}} (although the package is {{ntp}}):
> {noformat}
> zypper install ntp
> service ntpd start
> {noformat}
> On a related note: Ambari supports {{chrony}} as an alternative to NTP only
> on RedHat7+, but it is also available on RedHat6 and Ubuntu.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19114) Update hardcoded stack version warning to be more general than saying hdp
[ https://issues.apache.org/jira/browse/AMBARI-19114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19114: --- Status: Patch Available (was: Open) > Update hardcoded stack version warning to be more general than saying hdp > - > > Key: AMBARI-19114 > URL: https://issues.apache.org/jira/browse/AMBARI-19114 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Di Li >Assignee: Di Li >Priority: Minor > Attachments: AMBARI-19114.patch > > > Update hardcoded stack version warning to be more general than saying hdp -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19114) Update hardcoded stack version warning to be more general than saying hdp
[ https://issues.apache.org/jira/browse/AMBARI-19114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19114: --- Attachment: AMBARI-19114.patch > Update hardcoded stack version warning to be more general than saying hdp > - > > Key: AMBARI-19114 > URL: https://issues.apache.org/jira/browse/AMBARI-19114 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Di Li >Assignee: Di Li >Priority: Minor > Attachments: AMBARI-19114.patch > > > Update hardcoded stack version warning to be more general than saying hdp -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19113) Add timeout for LogSearch and Infra Solr metainfo.xml
[ https://issues.apache.org/jira/browse/AMBARI-19113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-19113: -- Attachment: AMBARI-19113.patch > Add timeout for LogSearch and Infra Solr metainfo.xml > - > > Key: AMBARI-19113 > URL: https://issues.apache.org/jira/browse/AMBARI-19113 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-19113.patch > > > Add more timeout as a workaround for slow env startup (e.g. wait too much > time for multiple zookeepers to start). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19108) Perf: Web UI can't load json with host check info
[
https://issues.apache.org/jira/browse/AMBARI-19108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15726674#comment-15726674
]
Hadoop QA commented on AMBARI-19108:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842005/AMBARI-19108.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9553//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9553//console
This message is automatically generated.
> Perf: Web UI can't load json with host check info
> -
>
> Key: AMBARI-19108
> URL: https://issues.apache.org/jira/browse/AMBARI-19108
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.5.0
>
> Attachments: AMBARI-19108.patch
>
>
> When i'm trying to deploy cluster with 1200 nodes, host check get stuck.
> Looks like json with host check info is too big and UI can't parse it in 3
> minutes, as the result fails with timeout.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19101) Merge AMS service check support for HA from trunk
[ https://issues.apache.org/jira/browse/AMBARI-19101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-19101: --- Attachment: AMBARI-19101-trunk.patch > Merge AMS service check support for HA from trunk > - > > Key: AMBARI-19101 > URL: https://issues.apache.org/jira/browse/AMBARI-19101 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19101-2.5.patch, AMBARI-19101-trunk.patch > > > AMBARI-17457 was missed while backporting AMS HA commits into branch-2.5. > Hence, service_check.py for AMS in branch-2.5 and trunk are different, no AMS > HA support in branch-2.5. > Applied AMBARI-17457 patch, and made changes to so that the service check and > Grafana datasource creation is compatible with changes introduced through > AMBARI-19032. > Part of these changes may be checked into trunk as well, to maintain parity. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19101) Merge AMS service check support for HA from trunk
[ https://issues.apache.org/jira/browse/AMBARI-19101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-19101: --- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to branch-2.5 and trunk. > Merge AMS service check support for HA from trunk > - > > Key: AMBARI-19101 > URL: https://issues.apache.org/jira/browse/AMBARI-19101 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19101-2.5.patch, AMBARI-19101-trunk.patch > > > AMBARI-17457 was missed while backporting AMS HA commits into branch-2.5. > Hence, service_check.py for AMS in branch-2.5 and trunk are different, no AMS > HA support in branch-2.5. > Applied AMBARI-17457 patch, and made changes to so that the service check and > Grafana datasource creation is compatible with changes introduced through > AMBARI-19032. > Part of these changes may be checked into trunk as well, to maintain parity. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19112) Grafana start failing at create datasource step
[
https://issues.apache.org/jira/browse/AMBARI-19112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1572#comment-1572
]
Hudson commented on AMBARI-19112:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #465 (See
[https://builds.apache.org/job/Ambari-branch-2.5/465/])
AMBARI-19112 : Grafana start failing at create datasource step (and a
(avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9d4a91a6b6b6e89f48fd81b06117336418cd2b12])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java
* (edit)
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py
> Grafana start failing at create datasource step
> ---
>
> Key: AMBARI-19112
> URL: https://issues.apache.org/jira/browse/AMBARI-19112
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19112.patch
>
>
> grafana failed to start due to following error
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 77, in
> AmsGrafana().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 282, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 58, in start
> create_ams_datasource()
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py",
> line 205, in create_ams_datasource
> response = perform_grafana_get_call(GRAFANA_DATASOURCE_URL, server)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py",
> line 67, in perform_grafana_get_call
> raise Fail("Ambari Metrics Grafana update failed due to: %s" % str(ex))
> resource_management.core.exceptions.Fail: Ambari Metrics Grafana update
> failed due to: [Errno 111] Connection refused
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19107) False warning about NTP not running on SUSE12
[
https://issues.apache.org/jira/browse/AMBARI-19107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle updated AMBARI-19107:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to branch-2.5 ans trunk. Please close the review board.
> False warning about NTP not running on SUSE12
> -
>
> Key: AMBARI-19107
> URL: https://issues.apache.org/jira/browse/AMBARI-19107
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
> Environment: SUSE12
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19107.patch
>
>
> When installing cluster via wizard on SUSE12, the host checks generate a
> warning that NTP is no running even if it is. The problem is that on SUSE12
> the service is called {{ntpd}}, not {{ntp}} (although the package is {{ntp}}):
> {noformat}
> zypper install ntp
> service ntpd start
> {noformat}
> On a related note: Ambari supports {{chrony}} as an alternative to NTP only
> on RedHat7+, but it is also available on RedHat6 and Ubuntu.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19101) Merge AMS service check support for HA from trunk
[ https://issues.apache.org/jira/browse/AMBARI-19101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15726574#comment-15726574 ] Siddharth Wagle commented on AMBARI-19101: -- +1 LGTM > Merge AMS service check support for HA from trunk > - > > Key: AMBARI-19101 > URL: https://issues.apache.org/jira/browse/AMBARI-19101 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19101-2.5.patch > > > AMBARI-17457 was missed while backporting AMS HA commits into branch-2.5. > Hence, service_check.py for AMS in branch-2.5 and trunk are different, no AMS > HA support in branch-2.5. > Applied AMBARI-17457 patch, and made changes to so that the service check and > Grafana datasource creation is compatible with changes introduced through > AMBARI-19032. > Part of these changes may be checked into trunk as well, to maintain parity. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19112) Grafana start failing at create datasource step
[
https://issues.apache.org/jira/browse/AMBARI-19112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-19112:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to branch-2.5 and trunk.
> Grafana start failing at create datasource step
> ---
>
> Key: AMBARI-19112
> URL: https://issues.apache.org/jira/browse/AMBARI-19112
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19112.patch
>
>
> grafana failed to start due to following error
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 77, in
> AmsGrafana().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 282, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 58, in start
> create_ams_datasource()
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py",
> line 205, in create_ams_datasource
> response = perform_grafana_get_call(GRAFANA_DATASOURCE_URL, server)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py",
> line 67, in perform_grafana_get_call
> raise Fail("Ambari Metrics Grafana update failed due to: %s" % str(ex))
> resource_management.core.exceptions.Fail: Ambari Metrics Grafana update
> failed due to: [Errno 111] Connection refused
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19112) Grafana start failing at create datasource step
[
https://issues.apache.org/jira/browse/AMBARI-19112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15726544#comment-15726544
]
Siddharth Wagle commented on AMBARI-19112:
--
+1
> Grafana start failing at create datasource step
> ---
>
> Key: AMBARI-19112
> URL: https://issues.apache.org/jira/browse/AMBARI-19112
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19112.patch
>
>
> grafana failed to start due to following error
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 77, in
> AmsGrafana().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 282, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 58, in start
> create_ams_datasource()
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py",
> line 205, in create_ams_datasource
> response = perform_grafana_get_call(GRAFANA_DATASOURCE_URL, server)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py",
> line 67, in perform_grafana_get_call
> raise Fail("Ambari Metrics Grafana update failed due to: %s" % str(ex))
> resource_management.core.exceptions.Fail: Ambari Metrics Grafana update
> failed due to: [Errno 111] Connection refused
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19112) Grafana start failing at create datasource step
[
https://issues.apache.org/jira/browse/AMBARI-19112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-19112:
---
Status: Patch Available (was: Open)
> Grafana start failing at create datasource step
> ---
>
> Key: AMBARI-19112
> URL: https://issues.apache.org/jira/browse/AMBARI-19112
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19112.patch
>
>
> grafana failed to start due to following error
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 77, in
> AmsGrafana().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 282, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 58, in start
> create_ams_datasource()
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py",
> line 205, in create_ams_datasource
> response = perform_grafana_get_call(GRAFANA_DATASOURCE_URL, server)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py",
> line 67, in perform_grafana_get_call
> raise Fail("Ambari Metrics Grafana update failed due to: %s" % str(ex))
> resource_management.core.exceptions.Fail: Ambari Metrics Grafana update
> failed due to: [Errno 111] Connection refused
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19112) Grafana start failing at create datasource step
[
https://issues.apache.org/jira/browse/AMBARI-19112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-19112:
---
Attachment: AMBARI-19112.patch
> Grafana start failing at create datasource step
> ---
>
> Key: AMBARI-19112
> URL: https://issues.apache.org/jira/browse/AMBARI-19112
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19112.patch
>
>
> grafana failed to start due to following error
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 77, in
> AmsGrafana().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 282, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 58, in start
> create_ams_datasource()
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py",
> line 205, in create_ams_datasource
> response = perform_grafana_get_call(GRAFANA_DATASOURCE_URL, server)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py",
> line 67, in perform_grafana_get_call
> raise Fail("Ambari Metrics Grafana update failed due to: %s" % str(ex))
> resource_management.core.exceptions.Fail: Ambari Metrics Grafana update
> failed due to: [Errno 111] Connection refused
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19112) Grafana start failing at create datasource step
[
https://issues.apache.org/jira/browse/AMBARI-19112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15726539#comment-15726539
]
Aravindan Vijayan commented on AMBARI-19112:
Tested manually.
> Grafana start failing at create datasource step
> ---
>
> Key: AMBARI-19112
> URL: https://issues.apache.org/jira/browse/AMBARI-19112
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19112.patch
>
>
> grafana failed to start due to following error
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 77, in
> AmsGrafana().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 282, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 58, in start
> create_ams_datasource()
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py",
> line 205, in create_ams_datasource
> response = perform_grafana_get_call(GRAFANA_DATASOURCE_URL, server)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py",
> line 67, in perform_grafana_get_call
> raise Fail("Ambari Metrics Grafana update failed due to: %s" % str(ex))
> resource_management.core.exceptions.Fail: Ambari Metrics Grafana update
> failed due to: [Errno 111] Connection refused
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19112) Grafana start failing at create datasource step
[
https://issues.apache.org/jira/browse/AMBARI-19112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15726448#comment-15726448
]
Aravindan Vijayan commented on AMBARI-19112:
*Analysis*
Grafana failed to Start during a 'Start All' command. This was done after an
initial deployment & a 'Stop All' command. The reason Grafana start failed was
because the script was not able to reach Grafana API to check for datasource
>From the grafana logs, I see that during the time the API call was made,
>Grafana server was not fully initialized and started.
> Grafana start failing at create datasource step
> ---
>
> Key: AMBARI-19112
> URL: https://issues.apache.org/jira/browse/AMBARI-19112
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
>
> grafana failed to start due to following error
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 77, in
> AmsGrafana().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 282, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 58, in start
> create_ams_datasource()
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py",
> line 205, in create_ams_datasource
> response = perform_grafana_get_call(GRAFANA_DATASOURCE_URL, server)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py",
> line 67, in perform_grafana_get_call
> raise Fail("Ambari Metrics Grafana update failed due to: %s" % str(ex))
> resource_management.core.exceptions.Fail: Ambari Metrics Grafana update
> failed due to: [Errno 111] Connection refused
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19112) Grafana start failing at create datasource step
Aravindan Vijayan created AMBARI-19112:
--
Summary: Grafana start failing at create datasource step
Key: AMBARI-19112
URL: https://issues.apache.org/jira/browse/AMBARI-19112
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: 2.5.0
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
Priority: Blocker
Fix For: 2.5.0
grafana failed to start due to following error
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
line 77, in
AmsGrafana().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 282, in execute
method(env)
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
line 58, in start
create_ams_datasource()
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py",
line 205, in create_ams_datasource
response = perform_grafana_get_call(GRAFANA_DATASOURCE_URL, server)
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py",
line 67, in perform_grafana_get_call
raise Fail("Ambari Metrics Grafana update failed due to: %s" % str(ex))
resource_management.core.exceptions.Fail: Ambari Metrics Grafana update failed
due to: [Errno 111] Connection refused
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19107) False warning about NTP not running on SUSE12
[
https://issues.apache.org/jira/browse/AMBARI-19107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15726387#comment-15726387
]
Hadoop QA commented on AMBARI-19107:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841967/AMBARI-19107.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9552//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9552//console
This message is automatically generated.
> False warning about NTP not running on SUSE12
> -
>
> Key: AMBARI-19107
> URL: https://issues.apache.org/jira/browse/AMBARI-19107
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
> Environment: SUSE12
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19107.patch
>
>
> When installing cluster via wizard on SUSE12, the host checks generate a
> warning that NTP is no running even if it is. The problem is that on SUSE12
> the service is called {{ntpd}}, not {{ntp}} (although the package is {{ntp}}):
> {noformat}
> zypper install ntp
> service ntpd start
> {noformat}
> On a related note: Ambari supports {{chrony}} as an alternative to NTP only
> on RedHat7+, but it is also available on RedHat6 and Ubuntu.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18874) Provide SSL related configurations for Ranger-Tagsync.
[
https://issues.apache.org/jira/browse/AMBARI-18874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15726337#comment-15726337
]
Hadoop QA commented on AMBARI-18874:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841979/AMBARI-18874.3.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9551//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9551//console
This message is automatically generated.
> Provide SSL related configurations for Ranger-Tagsync.
> --
>
> Key: AMBARI-18874
> URL: https://issues.apache.org/jira/browse/AMBARI-18874
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: 2.5.0
> Environment: Need to provide ssl related configurations for
> Ranger-Tagsync service.
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-18874.1.patch, AMBARI-18874.2.patch,
> AMBARI-18874.3.patch, AMBARI-18874.patch
>
>
> Need to provide ssl related configurations for Ranger-Tagsync service.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19108) Perf: Web UI can't load json with host check info
[ https://issues.apache.org/jira/browse/AMBARI-19108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19108: -- Status: Patch Available (was: Open) > Perf: Web UI can't load json with host check info > - > > Key: AMBARI-19108 > URL: https://issues.apache.org/jira/browse/AMBARI-19108 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.5.0 > > Attachments: AMBARI-19108.patch > > > When i'm trying to deploy cluster with 1200 nodes, host check get stuck. > Looks like json with host check info is too big and UI can't parse it in 3 > minutes, as the result fails with timeout. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19108) Perf: Web UI can't load json with host check info
[
https://issues.apache.org/jira/browse/AMBARI-19108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15726268#comment-15726268
]
Hadoop QA commented on AMBARI-19108:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841975/AMBARI-19108.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9550//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9550//console
This message is automatically generated.
> Perf: Web UI can't load json with host check info
> -
>
> Key: AMBARI-19108
> URL: https://issues.apache.org/jira/browse/AMBARI-19108
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.5.0
>
> Attachments: AMBARI-19108.patch
>
>
> When i'm trying to deploy cluster with 1200 nodes, host check get stuck.
> Looks like json with host check info is too big and UI can't parse it in 3
> minutes, as the result fails with timeout.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19108) Perf: Web UI can't load json with host check info
[ https://issues.apache.org/jira/browse/AMBARI-19108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19108: -- Attachment: AMBARI-19108.patch > Perf: Web UI can't load json with host check info > - > > Key: AMBARI-19108 > URL: https://issues.apache.org/jira/browse/AMBARI-19108 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.5.0 > > Attachments: AMBARI-19108.patch > > > When i'm trying to deploy cluster with 1200 nodes, host check get stuck. > Looks like json with host check info is too big and UI can't parse it in 3 > minutes, as the result fails with timeout. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19108) Perf: Web UI can't load json with host check info
[ https://issues.apache.org/jira/browse/AMBARI-19108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19108: -- Attachment: (was: AMBARI-19108.patch) > Perf: Web UI can't load json with host check info > - > > Key: AMBARI-19108 > URL: https://issues.apache.org/jira/browse/AMBARI-19108 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.5.0 > > > When i'm trying to deploy cluster with 1200 nodes, host check get stuck. > Looks like json with host check info is too big and UI can't parse it in 3 > minutes, as the result fails with timeout. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19111) Ambari server upgrade log printout refactoring
[
https://issues.apache.org/jira/browse/AMBARI-19111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15726222#comment-15726222
]
Hadoop QA commented on AMBARI-19111:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841992/AMBARI-19111.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9549//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9549//console
This message is automatically generated.
> Ambari server upgrade log printout refactoring
> --
>
> Key: AMBARI-19111
> URL: https://issues.apache.org/jira/browse/AMBARI-19111
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Di Li
>Assignee: Di Li
>Priority: Minor
> Attachments: AMBARI-19111.patch
>
>
> Ambari server upgrade log printout refactoring with the INFO header for info
> level logs and print INFO log that should be there regardless whether verbose
> is set.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19110) "Cluster Load" widget in ambari-dashboard, download as CSV is not working
[ https://issues.apache.org/jira/browse/AMBARI-19110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15726196#comment-15726196 ] Hudson commented on AMBARI-19110: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6166 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6166/]) AMBARI-19110. "Cluster Load" widget in ambari-dashboard, download as CSV (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0f297510640f24db5c11bfbabaa390bb29e619a6]) * (edit) ambari-web/app/mixins/common/widgets/export_metrics_mixin.js > "Cluster Load" widget in ambari-dashboard, download as CSV is not working > - > > Key: AMBARI-19110 > URL: https://issues.apache.org/jira/browse/AMBARI-19110 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19110.patch > > > *Steps to Reporduce:-* > 1. Log In to Ambari > 2. Open DashBoard. > 3. Download CSV file by clicking on Save icon in extreme right corner. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18662) Check that Stack Version and repo URLs match up when registering repo
[ https://issues.apache.org/jira/browse/AMBARI-18662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15726195#comment-15726195 ] Hudson commented on AMBARI-18662: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6166 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6166/]) Revert "AMBARI-18662. Check that Stack Version and repo URLs match up (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2cd12ce4cebcf0a3a6fa58ff6f79a79b0a92f631]) * (edit) ambari-web/test/controllers/installer_test.js * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/controllers/installer.js * (edit) ambari-web/app/controllers/wizard/step1_controller.js > Check that Stack Version and repo URLs match up when registering repo > -- > > Key: AMBARI-18662 > URL: https://issues.apache.org/jira/browse/AMBARI-18662 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-18662.patch > > > Right now there's no validation when registering a repo to catch these type > of user errors, which caused a lot of problems down the road. We should have > very basic validation using JS so that if we detect a number like "2.5.0.0" > we ensure that the selected stack is also HDP 2.5. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19110) "Cluster Load" widget in ambari-dashboard, download as CSV is not working
[ https://issues.apache.org/jira/browse/AMBARI-19110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15726190#comment-15726190 ] Hudson commented on AMBARI-19110: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #464 (See [https://builds.apache.org/job/Ambari-branch-2.5/464/]) AMBARI-19110. "Cluster Load" widget in ambari-dashboard, download as CSV (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2b0cf6dd9b637999ec13e0af989577e9f27bc634]) * (edit) ambari-web/app/mixins/common/widgets/export_metrics_mixin.js > "Cluster Load" widget in ambari-dashboard, download as CSV is not working > - > > Key: AMBARI-19110 > URL: https://issues.apache.org/jira/browse/AMBARI-19110 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19110.patch > > > *Steps to Reporduce:-* > 1. Log In to Ambari > 2. Open DashBoard. > 3. Download CSV file by clicking on Save icon in extreme right corner. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19106) Kerberos wizard is broken if stacks doesn't contain Ranger
[
https://issues.apache.org/jira/browse/AMBARI-19106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonenko Alexander updated AMBARI-19106:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed to trunk
> Kerberos wizard is broken if stacks doesn't contain Ranger
> --
>
> Key: AMBARI-19106
> URL: https://issues.apache.org/jira/browse/AMBARI-19106
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Denys Buzhor
>Assignee: Denys Buzhor
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-19106.patch
>
>
> {code}
> Stacktrace :
> Uncaught TypeError: Cannot read property 'split' of null
> at Class.compareCurrentVersion (app.js:79641)
> at Class. (app.js:191470)
> at ComputedPropertyPrototype.get (vendor.js:14954)
> at get (vendor.js:13360)
> {code}
> Looks like it fails here :
> App.StackService.find('RANGER').compareCurrentVersion('0.5')
> Patch with this issue was committed only in trunk
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19106) Kerberos wizard is broken if stacks doesn't contain Ranger
[
https://issues.apache.org/jira/browse/AMBARI-19106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15726100#comment-15726100
]
Hadoop QA commented on AMBARI-19106:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841965/AMBARI-19106.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9548//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9548//console
This message is automatically generated.
> Kerberos wizard is broken if stacks doesn't contain Ranger
> --
>
> Key: AMBARI-19106
> URL: https://issues.apache.org/jira/browse/AMBARI-19106
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Denys Buzhor
>Assignee: Denys Buzhor
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-19106.patch
>
>
> {code}
> Stacktrace :
> Uncaught TypeError: Cannot read property 'split' of null
> at Class.compareCurrentVersion (app.js:79641)
> at Class. (app.js:191470)
> at ComputedPropertyPrototype.get (vendor.js:14954)
> at get (vendor.js:13360)
> {code}
> Looks like it fails here :
> App.StackService.find('RANGER').compareCurrentVersion('0.5')
> Patch with this issue was committed only in trunk
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19110) "Cluster Load" widget in ambari-dashboard, download as CSV is not working
[ https://issues.apache.org/jira/browse/AMBARI-19110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-19110: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to 2.5 and trunk > "Cluster Load" widget in ambari-dashboard, download as CSV is not working > - > > Key: AMBARI-19110 > URL: https://issues.apache.org/jira/browse/AMBARI-19110 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19110.patch > > > *Steps to Reporduce:-* > 1. Log In to Ambari > 2. Open DashBoard. > 3. Download CSV file by clicking on Save icon in extreme right corner. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19111) Ambari server upgrade log printout refactoring
[ https://issues.apache.org/jira/browse/AMBARI-19111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19111: --- Attachment: AMBARI-19111.patch > Ambari server upgrade log printout refactoring > -- > > Key: AMBARI-19111 > URL: https://issues.apache.org/jira/browse/AMBARI-19111 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Di Li >Assignee: Di Li >Priority: Minor > Attachments: AMBARI-19111.patch > > > Ambari server upgrade log printout refactoring with the INFO header for info > level logs and print INFO log that should be there regardless whether verbose > is set. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19111) Ambari server upgrade log printout refactoring
[ https://issues.apache.org/jira/browse/AMBARI-19111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19111: --- Status: Patch Available (was: Open) > Ambari server upgrade log printout refactoring > -- > > Key: AMBARI-19111 > URL: https://issues.apache.org/jira/browse/AMBARI-19111 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Di Li >Assignee: Di Li >Priority: Minor > Attachments: AMBARI-19111.patch > > > Ambari server upgrade log printout refactoring with the INFO header for info > level logs and print INFO log that should be there regardless whether verbose > is set. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19111) Ambari server upgrade log printout refactoring
Di Li created AMBARI-19111: -- Summary: Ambari server upgrade log printout refactoring Key: AMBARI-19111 URL: https://issues.apache.org/jira/browse/AMBARI-19111 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk, 2.5.0 Reporter: Di Li Assignee: Di Li Priority: Minor Ambari server upgrade log printout refactoring with the INFO header for info level logs and print INFO log that should be there regardless whether verbose is set. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19110) "Cluster Load" widget in ambari-dashboard, download as CSV is not working
[
https://issues.apache.org/jira/browse/AMBARI-19110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15726037#comment-15726037
]
Hadoop QA commented on AMBARI-19110:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841987/AMBARI-19110.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9547//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9547//console
This message is automatically generated.
> "Cluster Load" widget in ambari-dashboard, download as CSV is not working
> -
>
> Key: AMBARI-19110
> URL: https://issues.apache.org/jira/browse/AMBARI-19110
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19110.patch
>
>
> *Steps to Reporduce:-*
> 1. Log In to Ambari
> 2. Open DashBoard.
> 3. Download CSV file by clicking on Save icon in extreme right corner.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19109) Ambari-server: Encrypt clear text passwords and store in DB and command files
[ https://issues.apache.org/jira/browse/AMBARI-19109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19109: --- Issue Type: Improvement (was: Bug) > Ambari-server: Encrypt clear text passwords and store in DB and command files > - > > Key: AMBARI-19109 > URL: https://issues.apache.org/jira/browse/AMBARI-19109 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 3.0.0 > > > * Properties that are passwords should be encrypted and base64 encoded and > stored in the database. > * Ambari agent should decrypt encrypted passwords coming from the server and > store it in the service's command file and configuration's JCEKS provider. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19110) "Cluster Load" widget in ambari-dashboard, download as CSV is not working
[ https://issues.apache.org/jira/browse/AMBARI-19110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15725986#comment-15725986 ] Aleksandr Kovalenko commented on AMBARI-19110: -- +1 for the patch > "Cluster Load" widget in ambari-dashboard, download as CSV is not working > - > > Key: AMBARI-19110 > URL: https://issues.apache.org/jira/browse/AMBARI-19110 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19110.patch > > > *Steps to Reporduce:-* > 1. Log In to Ambari > 2. Open DashBoard. > 3. Download CSV file by clicking on Save icon in extreme right corner. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19110) "Cluster Load" widget in ambari-dashboard, download as CSV is not working
[ https://issues.apache.org/jira/browse/AMBARI-19110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-19110: - Status: Patch Available (was: Open) > "Cluster Load" widget in ambari-dashboard, download as CSV is not working > - > > Key: AMBARI-19110 > URL: https://issues.apache.org/jira/browse/AMBARI-19110 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19110.patch > > > *Steps to Reporduce:-* > 1. Log In to Ambari > 2. Open DashBoard. > 3. Download CSV file by clicking on Save icon in extreme right corner. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19110) "Cluster Load" widget in ambari-dashboard, download as CSV is not working
[ https://issues.apache.org/jira/browse/AMBARI-19110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-19110: - Attachment: AMBARI-19110.patch > "Cluster Load" widget in ambari-dashboard, download as CSV is not working > - > > Key: AMBARI-19110 > URL: https://issues.apache.org/jira/browse/AMBARI-19110 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19110.patch > > > *Steps to Reporduce:-* > 1. Log In to Ambari > 2. Open DashBoard. > 3. Download CSV file by clicking on Save icon in extreme right corner. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19110) "Cluster Load" widget in ambari-dashboard, download as CSV is not working
Antonenko Alexander created AMBARI-19110: Summary: "Cluster Load" widget in ambari-dashboard, download as CSV is not working Key: AMBARI-19110 URL: https://issues.apache.org/jira/browse/AMBARI-19110 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Priority: Critical Fix For: 2.5.0 *Steps to Reporduce:-* 1. Log In to Ambari 2. Open DashBoard. 3. Download CSV file by clicking on Save icon in extreme right corner. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19109) Ambari-server: Encrypt clear text passwords and store in DB and command files
Nahappan Somasundaram created AMBARI-19109: -- Summary: Ambari-server: Encrypt clear text passwords and store in DB and command files Key: AMBARI-19109 URL: https://issues.apache.org/jira/browse/AMBARI-19109 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Nahappan Somasundaram Assignee: Nahappan Somasundaram Fix For: 3.0.0 * Properties that are passwords should be encrypted and base64 encoded and stored in the database. * Ambari agent should decrypt encrypted passwords coming from the server and store it in the service's command file and configuration's JCEKS provider. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
