[jira] [Commented] (AMBARI-18333) While checking for component dependency code looks for incorrect component name
[ https://issues.apache.org/jira/browse/AMBARI-18333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15475529#comment-15475529 ] Hudson commented on AMBARI-18333: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5641 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5641/]) AMBARI-18333. While checking for component dependency code looks for (rnettleton: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=146b2d72f28e1c9743bffba78e2b66ca4f08ccb5]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/BlueprintValidatorImpl.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/topology/BlueprintValidatorImplTest.java > While checking for component dependency code looks for incorrect component > name > --- > > Key: AMBARI-18333 > URL: https://issues.apache.org/jira/browse/AMBARI-18333 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-18333.patch > > > While validating host groups in blueprint for component dependency, code > should check if a dependency component is present in the host group component > list rather than the component on whose dependency list it is iterating. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18345) 'Stack advisor' validation code reports error while trying to access 'yarn.nodemanager.resource.memory-mb' config.
[ https://issues.apache.org/jira/browse/AMBARI-18345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15475527#comment-15475527 ] Hudson commented on AMBARI-18345: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5641 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5641/]) AMBARI-18345. 'Stack advisor' validation code reports error while trying (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7091fc2d1eb374d8897516cbdd45f918ae997057]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py > 'Stack advisor' validation code reports error while trying to access > 'yarn.nodemanager.resource.memory-mb' config. > -- > > Key: AMBARI-18345 > URL: https://issues.apache.org/jira/browse/AMBARI-18345 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.1 > > Attachments: AMBARI-18345.patch > > > 'Stack advisor' validation code reports error while trying to access > "yarn.nodemanager.resource.memory-mb" config. > *Reason:* > - Fn. 'validateHiveInteractiveSiteConfigurations' tried to query for config > 'yarn.nodemanager.resource.memory-mb'. The config may not be passed in > services[configurations], depending on which action triggered the validation. > - Fn. 'validateHiveInteractiveSiteConfigurations' was broken because it was > trying to query config 'yarn.nodemanager.resource.memory-mb', without > checking whether HSI is installed or not. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18343) Ambari server start fails after upgrade due to missing krb5JAASLogin.conf file on WireEncrypted cluster
[ https://issues.apache.org/jira/browse/AMBARI-18343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15475528#comment-15475528 ] Hudson commented on AMBARI-18343: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5641 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5641/]) AMBARI-18343. Ambari server start fails after upgrade due to missing (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0090e3ac41034fb1bbd90436c1a286e084c31469]) * (edit) ambari-server/src/main/package/rpm/preinstall.sh > Ambari server start fails after upgrade due to missing krb5JAASLogin.conf > file on WireEncrypted cluster > --- > > Key: AMBARI-18343 > URL: https://issues.apache.org/jira/browse/AMBARI-18343 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.1 > > Attachments: AMBARI-18343.patch > > > Ambari server host: 172.22.87.56 > ambari-server --hash > 6aa22480916d8497d6db077f1d8e744a9c8f73f8 > Build # ambari-server-2.4.1.0-10 > **Steps** > 1. Deploy HDP-242 cluster with Ambari 2.2.2.0 (secure, non-HA cluster, > Ambari server https enabled) > 2. Enable Wire Encryption on the cluster > 3. Upgrade Ambari to 2.4.1.0 and later start ambari-server > **Result** > Start failed with below error in logs: > > > > 07 Sep 2016 14:26:55,594 INFO [main] ActionDefinitionManager:130 - Added > custom action definition for ru_execute_tasks > 07 Sep 2016 14:26:55,619 INFO [main] CertificateManager:69 - > Initialization of root certificate > 07 Sep 2016 14:26:55,619 INFO [main] CertificateManager:71 - Certificate > exists:true > 07 Sep 2016 14:26:55,619 INFO [main] KerberosChecker:57 - Checking > Ambari Server Kerberos credentials. > 07 Sep 2016 14:26:55,625 ERROR [main] AmbariServer:927 - Failed to run > the Ambari Server > java.lang.SecurityException: /etc/ambari-server/conf/krb5JAASLogin.conf > (No such file or directory) > at > com.sun.security.auth.login.ConfigFile.(ConfigFile.java:110) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) > at java.lang.Class.newInstance(Class.java:374) > at > javax.security.auth.login.Configuration$2.run(Configuration.java:258) > at > javax.security.auth.login.Configuration$2.run(Configuration.java:250) > at java.security.AccessController.doPrivileged(Native Method) > at > javax.security.auth.login.Configuration.getConfiguration(Configuration.java:249) > at > org.apache.ambari.server.controller.utilities.KerberosChecker.checkJaasConfiguration(KerberosChecker.java:61) > at > org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:922) > Caused by: java.io.IOException: > /etc/ambari-server/conf/krb5JAASLogin.conf (No such file or directory) > at > com.sun.security.auth.login.ConfigFile.init(ConfigFile.java:212) > at > com.sun.security.auth.login.ConfigFile.(ConfigFile.java:108) > ... 11 more > 07 Sep 2016 14:26:55,900 INFO [Stack Version Loading Thread] > LatestRepoCallable:219 - Stack HDP-2.3 cannot resolve OS debian6 to the > supported ones: redhat6,redhat7,suse11,ubuntu14,debian7,ubuntu12. Family: null > 07 Sep 2016 14:26:56,120 INFO [Stack Version Loading Thread] > LatestRepoCallable:80 - Loading latest URL info for stack HDP-2.4 from > http://public-repo-1.hortonworks.com/HDP/hdp_urlinfo.json > > Checked in the directory and found the following > > > > nats11-36-juzs-dgm10toeriedwngdha-s11-5:/etc/ambari-server/conf # pwd > /etc/ambari-server/conf > nats11-36-juzs-dgm10toeriedwngdha-s11-5:/etc/ambari-server/conf # ls -lhrt > total 32K > -rw-r- 1 root root 13 Sep 7 10:20 password.dat > -rw-r--r-- 1 root root 300 Sep 7 11:25 krb5JAASLogin.conf.rpmsave > -rw-r--r-- 1 root root 5.0K Sep 7 12:13 > ambari.properties.rpmsave.20160907141713 > -rw-r--r-- 1 root root 4.9K Sep 7 14:17 log4j.properties > -rw-r--r-- 1 root root 7.5K Sep 7 17:53 ambari.properties > > Did not hit this issue in Ambari 2.4.0 timeframe, so possibly a regression -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18344) Metrics data is not available - AMS in distributed mode
[
https://issues.apache.org/jira/browse/AMBARI-18344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15475530#comment-15475530
]
Hudson commented on AMBARI-18344:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5641 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5641/])
AMBARI-18344 : Metrics data is not available - AMS in distributed mode
(avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4abe73766c9e26365268e0cb409860f3745fd89f])
* (edit)
ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/discovery/TestMetadataManager.java
* (edit)
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/PhoenixHBaseAccessor.java
> Metrics data is not available - AMS in distributed mode
> ---
>
> Key: AMBARI-18344
> URL: https://issues.apache.org/jira/browse/AMBARI-18344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.1
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18344.patch
>
>
> Data is unavailable for service, host and dashboard metrices.
> Seeing below error in metrics_collector log :
> {code}
> [org.mortbay.jetty.EofException]
> at
> com.sun.jersey.core.provider.jaxb.AbstractRootElementProvider.writeTo(AbstractRootElementProvider.java:159)
> at
> com.sun.jersey.spi.container.ContainerResponse.write(ContainerResponse.java:306)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1437)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:895)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:843)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:804)
> at
> com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)
> at
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
> at
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:118)
> at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:113)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.apache.hadoop.security.http.XFrameOptionsFilter.doFilter(XFrameOptionsFilter.java:57)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.apache.hadoop.http.lib.StaticUserWebFilter$StaticUserFilter.doFilter(StaticUserWebFilter.java:109)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.apache.hadoop.http.HttpServer2$QuotingInputFilter.doFilter(HttpServer2.java:1294)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at org.apache.hadoop.http.NoCacheFilter.doFilter(NoCacheFilter.java:45)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:767)
> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> at org.mortbay.jetty.Server.handle(Server.java:326)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:945)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
> at
[jira] [Commented] (AMBARI-18343) Ambari server start fails after upgrade due to missing krb5JAASLogin.conf file on WireEncrypted cluster
[ https://issues.apache.org/jira/browse/AMBARI-18343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15475424#comment-15475424 ] Hudson commented on AMBARI-18343: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #8 (See [https://builds.apache.org/job/Ambari-branch-2.5/8/]) AMBARI-18343. Ambari server start fails after upgrade due to missing (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=33931103464b3564652f0a8497557769e41b9eeb]) * (edit) ambari-server/src/main/package/rpm/preinstall.sh > Ambari server start fails after upgrade due to missing krb5JAASLogin.conf > file on WireEncrypted cluster > --- > > Key: AMBARI-18343 > URL: https://issues.apache.org/jira/browse/AMBARI-18343 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.1 > > Attachments: AMBARI-18343.patch > > > Ambari server host: 172.22.87.56 > ambari-server --hash > 6aa22480916d8497d6db077f1d8e744a9c8f73f8 > Build # ambari-server-2.4.1.0-10 > **Steps** > 1. Deploy HDP-242 cluster with Ambari 2.2.2.0 (secure, non-HA cluster, > Ambari server https enabled) > 2. Enable Wire Encryption on the cluster > 3. Upgrade Ambari to 2.4.1.0 and later start ambari-server > **Result** > Start failed with below error in logs: > > > > 07 Sep 2016 14:26:55,594 INFO [main] ActionDefinitionManager:130 - Added > custom action definition for ru_execute_tasks > 07 Sep 2016 14:26:55,619 INFO [main] CertificateManager:69 - > Initialization of root certificate > 07 Sep 2016 14:26:55,619 INFO [main] CertificateManager:71 - Certificate > exists:true > 07 Sep 2016 14:26:55,619 INFO [main] KerberosChecker:57 - Checking > Ambari Server Kerberos credentials. > 07 Sep 2016 14:26:55,625 ERROR [main] AmbariServer:927 - Failed to run > the Ambari Server > java.lang.SecurityException: /etc/ambari-server/conf/krb5JAASLogin.conf > (No such file or directory) > at > com.sun.security.auth.login.ConfigFile.(ConfigFile.java:110) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) > at java.lang.Class.newInstance(Class.java:374) > at > javax.security.auth.login.Configuration$2.run(Configuration.java:258) > at > javax.security.auth.login.Configuration$2.run(Configuration.java:250) > at java.security.AccessController.doPrivileged(Native Method) > at > javax.security.auth.login.Configuration.getConfiguration(Configuration.java:249) > at > org.apache.ambari.server.controller.utilities.KerberosChecker.checkJaasConfiguration(KerberosChecker.java:61) > at > org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:922) > Caused by: java.io.IOException: > /etc/ambari-server/conf/krb5JAASLogin.conf (No such file or directory) > at > com.sun.security.auth.login.ConfigFile.init(ConfigFile.java:212) > at > com.sun.security.auth.login.ConfigFile.(ConfigFile.java:108) > ... 11 more > 07 Sep 2016 14:26:55,900 INFO [Stack Version Loading Thread] > LatestRepoCallable:219 - Stack HDP-2.3 cannot resolve OS debian6 to the > supported ones: redhat6,redhat7,suse11,ubuntu14,debian7,ubuntu12. Family: null > 07 Sep 2016 14:26:56,120 INFO [Stack Version Loading Thread] > LatestRepoCallable:80 - Loading latest URL info for stack HDP-2.4 from > http://public-repo-1.hortonworks.com/HDP/hdp_urlinfo.json > > Checked in the directory and found the following > > > > nats11-36-juzs-dgm10toeriedwngdha-s11-5:/etc/ambari-server/conf # pwd > /etc/ambari-server/conf > nats11-36-juzs-dgm10toeriedwngdha-s11-5:/etc/ambari-server/conf # ls -lhrt > total 32K > -rw-r- 1 root root 13 Sep 7 10:20 password.dat > -rw-r--r-- 1 root root 300 Sep 7 11:25 krb5JAASLogin.conf.rpmsave > -rw-r--r-- 1 root root 5.0K Sep 7 12:13 > ambari.properties.rpmsave.20160907141713 > -rw-r--r-- 1 root root 4.9K Sep 7 14:17 log4j.properties > -rw-r--r-- 1 root root 7.5K Sep 7 17:53 ambari.properties > > Did not hit this issue in Ambari 2.4.0 timeframe, so possibly a regression -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18337) Syntax Error in Ambari HAWQ Unit test with Python 2.6
[
https://issues.apache.org/jira/browse/AMBARI-18337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15475395#comment-15475395
]
Hadoop QA commented on AMBARI-18337:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12827665/AMBARI-18337.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8623//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8623//console
This message is automatically generated.
> Syntax Error in Ambari HAWQ Unit test with Python 2.6
> -
>
> Key: AMBARI-18337
> URL: https://issues.apache.org/jira/browse/AMBARI-18337
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
> Environment: CentOS6, Python 2.6
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-18337.patch
>
>
> With Python 2.6, {code} {"A", "B"} {code} syntax isn't allowed.
> Ref. https://docs.python.org/2/library/stdtypes.html#set-types-set-frozenset
> {code}
> As of Python 2.7, non-empty sets (not frozensets) can be created by placing a
> comma-separated list of elements within braces, for example: {'jack',
> 'sjoerd'}, in addition to the set constructor.
> {code}
> Error
> {code}
> Traceback (most recent call last):
> File "unitTests.py", line 129, in stack_test_executor
> modules]
> File "/usr/lib64/python2.6/unittest.py", line 575, in loadTestsFromName
> module = __import__('.'.join(parts_copy))
> File
> "/tmp/ambari/ambari-server/src/test/python/common-services/HAWQ/test_service_advisor.py",
> li
> ne 646
> self.assertFalse({'HAWQMASTER', 'HAWQSTANDBY'}.issubset(hostComponents))
> ^
> SyntaxError: invalid syntax
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18348) Ranger audit log collection is not used in Log Search (managed by ambari)
[
https://issues.apache.org/jira/browse/AMBARI-18348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15475398#comment-15475398
]
Hadoop QA commented on AMBARI-18348:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12827664/AMBARI-18348.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/8624//console
This message is automatically generated.
> Ranger audit log collection is not used in Log Search (managed by ambari)
> -
>
> Key: AMBARI-18348
> URL: https://issues.apache.org/jira/browse/AMBARI-18348
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18348.patch
>
>
> Audit log collection and ranger audit log collection are 2 different
> collection with almost the same schema. With solr alias support, we can use
> both.
> Also use ambari audit logs inside audit collection, not in service log
> collection
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18347) Setting fetch_nonlocal_groups to false Can Prevent Services From Starting
[
https://issues.apache.org/jira/browse/AMBARI-18347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15475359#comment-15475359
]
Hadoop QA commented on AMBARI-18347:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12827649/AMBARI-18347.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 .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8622//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8622//console
This message is automatically generated.
> Setting fetch_nonlocal_groups to false Can Prevent Services From Starting
> -
>
> Key: AMBARI-18347
> URL: https://issues.apache.org/jira/browse/AMBARI-18347
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.2.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18347.patch
>
>
> When setting the {{cluster-env/fetch_nonlocal_groups}} value to {{false}}, if
> the {{/etc/group}} file has an unexpected format, services will fail to start:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py",
> line 35, in
> BeforeAnyHook().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 219, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py",
> line 29, in hook
> setup_users()
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py",
> line 44, in setup_users
> fetch_nonlocal_groups = params.fetch_nonlocal_groups
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 154, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/accounts.py",
> line 51, in action_create
> if getattr(self.resource, option_name) != None and getattr(self.resource,
> option_name) != attributes[0](self):
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/accounts.py",
> line 40, in
> groups=(lambda self: self.user_groups, "-G")
> File "/usr/lib/python2.6/site-packages/resource_management/core/utils.py",
> line 146, in decorated
> v = undecorated(self)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/accounts.py",
> line 109, in user_groups
> group_users = entries[3].split(',')
> IndexError: list index out of range
> Error: Error: Unable to run the custom hook script ['/usr/bin/python',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py',
> 'ANY', '/var/lib/ambari-agent/data/command-9429.json',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY',
> '/var/lib/ambari-agent/data/structured-out-9429.json', 'INFO',
> '/var/lib/ambari-agent/tmp']
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18342) Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain)
[
https://issues.apache.org/jira/browse/AMBARI-18342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15475336#comment-15475336
]
Hudson commented on AMBARI-18342:
-
ABORTED: Integrated in Jenkins build Ambari-trunk-Commit #5640 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5640/])
AMBARI-18342: Unit Tests failure: test_update_open_files_ulimit (nsomasundaram:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9a35900542fe88e764ecc5daf240d52c50f0b4b3])
* (edit) ambari-agent/src/test/python/ambari_agent/TestMain.py
> Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain)
> -
>
> Key: AMBARI-18342
> URL: https://issues.apache.org/jira/browse/AMBARI-18342
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 3.0.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: rb51733 (2).patch, rb51733.patch
>
>
> Unit test failure in ambari-agent because of AMBARI-18299:
> {code}
> FAIL: test_update_open_files_ulimit (TestMain.TestMain)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-agent/src/test/python/ambari_agent/TestMain.py",
> line 137, in test_update_open_files_ulimit
> self.assertEquals(hard_limit, open_files_ulimit)
> AssertionError: 6 != 10240
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18345) 'Stack advisor' validation code reports error while trying to access 'yarn.nodemanager.resource.memory-mb' config.
[
https://issues.apache.org/jira/browse/AMBARI-18345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15475333#comment-15475333
]
Hadoop QA commented on AMBARI-18345:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12827639/AMBARI-18345.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/8621//console
This message is automatically generated.
> 'Stack advisor' validation code reports error while trying to access
> 'yarn.nodemanager.resource.memory-mb' config.
> --
>
> Key: AMBARI-18345
> URL: https://issues.apache.org/jira/browse/AMBARI-18345
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.1
>
> Attachments: AMBARI-18345.patch
>
>
> 'Stack advisor' validation code reports error while trying to access
> "yarn.nodemanager.resource.memory-mb" config.
> *Reason:*
> - Fn. 'validateHiveInteractiveSiteConfigurations' tried to query for config
> 'yarn.nodemanager.resource.memory-mb'. The config may not be passed in
> services[configurations], depending on which action triggered the validation.
> - Fn. 'validateHiveInteractiveSiteConfigurations' was broken because it was
> trying to query config 'yarn.nodemanager.resource.memory-mb', without
> checking whether HSI is installed or not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18346) SmartSense Mandatory Install
[
https://issues.apache.org/jira/browse/AMBARI-18346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15475330#comment-15475330
]
Hadoop QA commented on AMBARI-18346:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12827642/AMBARI-18346.v0.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/8620//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8620//console
This message is automatically generated.
> SmartSense Mandatory Install
>
>
> Key: AMBARI-18346
> URL: https://issues.apache.org/jira/browse/AMBARI-18346
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-18346.v0.patch
>
>
> Perform a UI hack to force selection of SmartSense for HDP stacks (the user
> cannot deselect).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18341) Need to validate behaviour and show warn message for user after hcat user was removed
[
https://issues.apache.org/jira/browse/AMBARI-18341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15475288#comment-15475288
]
Hadoop QA commented on AMBARI-18341:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12827631/AMBARI-18341.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8618//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8618//console
This message is automatically generated.
> Need to validate behaviour and show warn message for user after hcat user was
> removed
> -
>
> Key: AMBARI-18341
> URL: https://issues.apache.org/jira/browse/AMBARI-18341
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-18341.patch
>
>
> We should validate behaviour for few basic scenarious and show warn message
> for user about potential problems.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18322) [Grafana] Add Apache NiFi - Hosts dashboard
[ https://issues.apache.org/jira/browse/AMBARI-18322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prajwal Rao updated AMBARI-18322: - Affects Version/s: 2.5.0 > [Grafana] Add Apache NiFi - Hosts dashboard > --- > > Key: AMBARI-18322 > URL: https://issues.apache.org/jira/browse/AMBARI-18322 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: trunk, 2.5.0 >Reporter: Prajwal Rao >Assignee: Prajwal Rao > Fix For: trunk > > Attachments: AMBARI-18322.patch > > > Added a Grafana dashboard for Apache NiFi that allows for visualization of > Apace NiFi metrics on a per host level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18322) [Grafana] Add Apache NiFi - Hosts dashboard
[ https://issues.apache.org/jira/browse/AMBARI-18322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prajwal Rao updated AMBARI-18322: - Fix Version/s: (was: 2.5.0) trunk > [Grafana] Add Apache NiFi - Hosts dashboard > --- > > Key: AMBARI-18322 > URL: https://issues.apache.org/jira/browse/AMBARI-18322 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: trunk >Reporter: Prajwal Rao >Assignee: Prajwal Rao > Fix For: trunk > > Attachments: AMBARI-18322.patch > > > Added a Grafana dashboard for Apache NiFi that allows for visualization of > Apace NiFi metrics on a per host level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18322) [Grafana] Add Apache NiFi - Hosts dashboard
[ https://issues.apache.org/jira/browse/AMBARI-18322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prajwal Rao updated AMBARI-18322: - Affects Version/s: (was: 2.5.0) trunk > [Grafana] Add Apache NiFi - Hosts dashboard > --- > > Key: AMBARI-18322 > URL: https://issues.apache.org/jira/browse/AMBARI-18322 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: trunk >Reporter: Prajwal Rao >Assignee: Prajwal Rao > Fix For: trunk > > Attachments: AMBARI-18322.patch > > > Added a Grafana dashboard for Apache NiFi that allows for visualization of > Apace NiFi metrics on a per host level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18343) Ambari server start fails after upgrade due to missing krb5JAASLogin.conf file on WireEncrypted cluster
[ https://issues.apache.org/jira/browse/AMBARI-18343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18343: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4 and branch-2.5 > Ambari server start fails after upgrade due to missing krb5JAASLogin.conf > file on WireEncrypted cluster > --- > > Key: AMBARI-18343 > URL: https://issues.apache.org/jira/browse/AMBARI-18343 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.1 > > Attachments: AMBARI-18343.patch > > > Ambari server host: 172.22.87.56 > ambari-server --hash > 6aa22480916d8497d6db077f1d8e744a9c8f73f8 > Build # ambari-server-2.4.1.0-10 > **Steps** > 1. Deploy HDP-242 cluster with Ambari 2.2.2.0 (secure, non-HA cluster, > Ambari server https enabled) > 2. Enable Wire Encryption on the cluster > 3. Upgrade Ambari to 2.4.1.0 and later start ambari-server > **Result** > Start failed with below error in logs: > > > > 07 Sep 2016 14:26:55,594 INFO [main] ActionDefinitionManager:130 - Added > custom action definition for ru_execute_tasks > 07 Sep 2016 14:26:55,619 INFO [main] CertificateManager:69 - > Initialization of root certificate > 07 Sep 2016 14:26:55,619 INFO [main] CertificateManager:71 - Certificate > exists:true > 07 Sep 2016 14:26:55,619 INFO [main] KerberosChecker:57 - Checking > Ambari Server Kerberos credentials. > 07 Sep 2016 14:26:55,625 ERROR [main] AmbariServer:927 - Failed to run > the Ambari Server > java.lang.SecurityException: /etc/ambari-server/conf/krb5JAASLogin.conf > (No such file or directory) > at > com.sun.security.auth.login.ConfigFile.(ConfigFile.java:110) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) > at java.lang.Class.newInstance(Class.java:374) > at > javax.security.auth.login.Configuration$2.run(Configuration.java:258) > at > javax.security.auth.login.Configuration$2.run(Configuration.java:250) > at java.security.AccessController.doPrivileged(Native Method) > at > javax.security.auth.login.Configuration.getConfiguration(Configuration.java:249) > at > org.apache.ambari.server.controller.utilities.KerberosChecker.checkJaasConfiguration(KerberosChecker.java:61) > at > org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:922) > Caused by: java.io.IOException: > /etc/ambari-server/conf/krb5JAASLogin.conf (No such file or directory) > at > com.sun.security.auth.login.ConfigFile.init(ConfigFile.java:212) > at > com.sun.security.auth.login.ConfigFile.(ConfigFile.java:108) > ... 11 more > 07 Sep 2016 14:26:55,900 INFO [Stack Version Loading Thread] > LatestRepoCallable:219 - Stack HDP-2.3 cannot resolve OS debian6 to the > supported ones: redhat6,redhat7,suse11,ubuntu14,debian7,ubuntu12. Family: null > 07 Sep 2016 14:26:56,120 INFO [Stack Version Loading Thread] > LatestRepoCallable:80 - Loading latest URL info for stack HDP-2.4 from > http://public-repo-1.hortonworks.com/HDP/hdp_urlinfo.json > > Checked in the directory and found the following > > > > nats11-36-juzs-dgm10toeriedwngdha-s11-5:/etc/ambari-server/conf # pwd > /etc/ambari-server/conf > nats11-36-juzs-dgm10toeriedwngdha-s11-5:/etc/ambari-server/conf # ls -lhrt > total 32K > -rw-r- 1 root root 13 Sep 7 10:20 password.dat > -rw-r--r-- 1 root root 300 Sep 7 11:25 krb5JAASLogin.conf.rpmsave > -rw-r--r-- 1 root root 5.0K Sep 7 12:13 > ambari.properties.rpmsave.20160907141713 > -rw-r--r-- 1 root root 4.9K Sep 7 14:17 log4j.properties > -rw-r--r-- 1 root root 7.5K Sep 7 17:53 ambari.properties > > Did not hit this issue in Ambari 2.4.0 timeframe, so possibly a regression -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18337) Syntax Error in Ambari HAWQ Unit test with Python 2.6
[
https://issues.apache.org/jira/browse/AMBARI-18337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-18337:
-
Status: Patch Available (was: Open)
> Syntax Error in Ambari HAWQ Unit test with Python 2.6
> -
>
> Key: AMBARI-18337
> URL: https://issues.apache.org/jira/browse/AMBARI-18337
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
> Environment: CentOS6, Python 2.6
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-18337.patch
>
>
> With Python 2.6, {code} {"A", "B"} {code} syntax isn't allowed.
> Ref. https://docs.python.org/2/library/stdtypes.html#set-types-set-frozenset
> {code}
> As of Python 2.7, non-empty sets (not frozensets) can be created by placing a
> comma-separated list of elements within braces, for example: {'jack',
> 'sjoerd'}, in addition to the set constructor.
> {code}
> Error
> {code}
> Traceback (most recent call last):
> File "unitTests.py", line 129, in stack_test_executor
> modules]
> File "/usr/lib64/python2.6/unittest.py", line 575, in loadTestsFromName
> module = __import__('.'.join(parts_copy))
> File
> "/tmp/ambari/ambari-server/src/test/python/common-services/HAWQ/test_service_advisor.py",
> li
> ne 646
> self.assertFalse({'HAWQMASTER', 'HAWQSTANDBY'}.issubset(hostComponents))
> ^
> SyntaxError: invalid syntax
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18337) Syntax Error in Ambari HAWQ Unit test with Python 2.6
[
https://issues.apache.org/jira/browse/AMBARI-18337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-18337:
-
Attachment: AMBARI-18337.patch
Attach a patch
> Syntax Error in Ambari HAWQ Unit test with Python 2.6
> -
>
> Key: AMBARI-18337
> URL: https://issues.apache.org/jira/browse/AMBARI-18337
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
> Environment: CentOS6, Python 2.6
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-18337.patch
>
>
> With Python 2.6, {code} {"A", "B"} {code} syntax isn't allowed.
> Ref. https://docs.python.org/2/library/stdtypes.html#set-types-set-frozenset
> {code}
> As of Python 2.7, non-empty sets (not frozensets) can be created by placing a
> comma-separated list of elements within braces, for example: {'jack',
> 'sjoerd'}, in addition to the set constructor.
> {code}
> Error
> {code}
> Traceback (most recent call last):
> File "unitTests.py", line 129, in stack_test_executor
> modules]
> File "/usr/lib64/python2.6/unittest.py", line 575, in loadTestsFromName
> module = __import__('.'.join(parts_copy))
> File
> "/tmp/ambari/ambari-server/src/test/python/common-services/HAWQ/test_service_advisor.py",
> li
> ne 646
> self.assertFalse({'HAWQMASTER', 'HAWQSTANDBY'}.issubset(hostComponents))
> ^
> SyntaxError: invalid syntax
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18348) Ranger audit log collection is not used in Log Search (managed by ambari)
[ https://issues.apache.org/jira/browse/AMBARI-18348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-18348: Status: Patch Available (was: In Progress) > Ranger audit log collection is not used in Log Search (managed by ambari) > - > > Key: AMBARI-18348 > URL: https://issues.apache.org/jira/browse/AMBARI-18348 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18348.patch > > > Audit log collection and ranger audit log collection are 2 different > collection with almost the same schema. With solr alias support, we can use > both. > Also use ambari audit logs inside audit collection, not in service log > collection -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18348) Ranger audit log collection is not used in Log Search (managed by ambari)
[ https://issues.apache.org/jira/browse/AMBARI-18348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-18348: Attachment: AMBARI-18348.patch > Ranger audit log collection is not used in Log Search (managed by ambari) > - > > Key: AMBARI-18348 > URL: https://issues.apache.org/jira/browse/AMBARI-18348 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18348.patch > > > Audit log collection and ranger audit log collection are 2 different > collection with almost the same schema. With solr alias support, we can use > both. > Also use ambari audit logs inside audit collection, not in service log > collection -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15538) Support service-specific repo for add-on services
[
https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15475155#comment-15475155
]
Tim Thorpe commented on AMBARI-15538:
-
Will the repos folder be linked to all services? I guess this is to reduce
duplication? Is this going to be specific to custom services? What about
extensions? Would I need to include the repos directory under all services in
the extension or I just include EXT/1.0/repos/repoinfo.xml and it would
automatically get associated with all services in that extension?
Couldn't the repos just be included directly under the service folder? Could I
have mpacks/custom-services/8.0.0/SERVICEA/repos/repoinfo.xml
If so will there be anything to prevent an mpack from doing both? Such that if
a service has its own repos folder that it would be an error to either have one
at the custom services level or potentially it just wouldn't link the other one.
Will services under the stack be allowed to specify their own repos? Either
those directly in any of the HDP stack versions, or in an mpack?
> Support service-specific repo for add-on services
> -
>
> Key: AMBARI-15538
> URL: https://issues.apache.org/jira/browse/AMBARI-15538
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.1.0, 2.2.0, 2.4.0
>Reporter: Jayush Luniya
>Assignee: Balázs Bence Sári
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-15538-trunk-v1.patch
>
>
> The approach for custom-services to specify their own repo location will be
> to provide a {{/repos/repoinfo.xml}} inside the stack-version they will be
> in. This repo file will be loaded by Ambari during startup into the
> {{/api/v1/stacks/HDP/versions/2.4/repository_versions}} repos. *Service repo
> files have a restriction that their (repo-name, base-url) locations should be
> unique and not conflict*. When conflicts do occur, they will not be loaded
> into the stacks model.
> Now the management-pack will provide such repos/ folder in
> {{mpacks/custom-services/8.0.0/repos}} which will be linked into the stacks/
> folder.
> {{ambari/ambari-server/src/main/resources/stacks/HDP/2.3/services/SERVICE_NAME/repos
> -> mpacks/custom-services/8.0.0/repos}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18348) Ranger audit log collection is not used in Log Search (managed by ambari)
Miklos Gergely created AMBARI-18348: --- Summary: Ranger audit log collection is not used in Log Search (managed by ambari) Key: AMBARI-18348 URL: https://issues.apache.org/jira/browse/AMBARI-18348 Project: Ambari Issue Type: Bug Affects Versions: 2.4.0 Reporter: Miklos Gergely Assignee: Miklos Gergely Priority: Critical Fix For: 2.5.0 Audit log collection and ranger audit log collection are 2 different collection with almost the same schema. With solr alias support, we can use both. Also use ambari audit logs inside audit collection, not in service log collection -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15538) Support service-specific repo for add-on services
[
https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-15538:
---
Fix Version/s: 2.4.2
> Support service-specific repo for add-on services
> -
>
> Key: AMBARI-15538
> URL: https://issues.apache.org/jira/browse/AMBARI-15538
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.1.0, 2.2.0, 2.4.0
>Reporter: Jayush Luniya
>Assignee: Balázs Bence Sári
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-15538-trunk-v1.patch
>
>
> The approach for custom-services to specify their own repo location will be
> to provide a {{/repos/repoinfo.xml}} inside the stack-version they will be
> in. This repo file will be loaded by Ambari during startup into the
> {{/api/v1/stacks/HDP/versions/2.4/repository_versions}} repos. *Service repo
> files have a restriction that their (repo-name, base-url) locations should be
> unique and not conflict*. When conflicts do occur, they will not be loaded
> into the stacks model.
> Now the management-pack will provide such repos/ folder in
> {{mpacks/custom-services/8.0.0/repos}} which will be linked into the stacks/
> folder.
> {{ambari/ambari-server/src/main/resources/stacks/HDP/2.3/services/SERVICE_NAME/repos
> -> mpacks/custom-services/8.0.0/repos}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18343) Ambari server start fails after upgrade due to missing krb5JAASLogin.conf file on WireEncrypted cluster
[
https://issues.apache.org/jira/browse/AMBARI-18343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15475025#comment-15475025
]
Hadoop QA commented on AMBARI-18343:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12827622/AMBARI-18343.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/8617//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8617//console
This message is automatically generated.
> Ambari server start fails after upgrade due to missing krb5JAASLogin.conf
> file on WireEncrypted cluster
> ---
>
> Key: AMBARI-18343
> URL: https://issues.apache.org/jira/browse/AMBARI-18343
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.1
>
> Attachments: AMBARI-18343.patch
>
>
> Ambari server host: 172.22.87.56
> ambari-server --hash
> 6aa22480916d8497d6db077f1d8e744a9c8f73f8
> Build # ambari-server-2.4.1.0-10
> **Steps**
> 1. Deploy HDP-242 cluster with Ambari 2.2.2.0 (secure, non-HA cluster,
> Ambari server https enabled)
> 2. Enable Wire Encryption on the cluster
> 3. Upgrade Ambari to 2.4.1.0 and later start ambari-server
> **Result**
> Start failed with below error in logs:
>
>
>
> 07 Sep 2016 14:26:55,594 INFO [main] ActionDefinitionManager:130 - Added
> custom action definition for ru_execute_tasks
> 07 Sep 2016 14:26:55,619 INFO [main] CertificateManager:69 -
> Initialization of root certificate
> 07 Sep 2016 14:26:55,619 INFO [main] CertificateManager:71 - Certificate
> exists:true
> 07 Sep 2016 14:26:55,619 INFO [main] KerberosChecker:57 - Checking
> Ambari Server Kerberos credentials.
> 07 Sep 2016 14:26:55,625 ERROR [main] AmbariServer:927 - Failed to run
> the Ambari Server
> java.lang.SecurityException: /etc/ambari-server/conf/krb5JAASLogin.conf
> (No such file or directory)
> at
> com.sun.security.auth.login.ConfigFile.(ConfigFile.java:110)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at java.lang.Class.newInstance(Class.java:374)
> at
> javax.security.auth.login.Configuration$2.run(Configuration.java:258)
> at
> javax.security.auth.login.Configuration$2.run(Configuration.java:250)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> javax.security.auth.login.Configuration.getConfiguration(Configuration.java:249)
> at
> org.apache.ambari.server.controller.utilities.KerberosChecker.checkJaasConfiguration(KerberosChecker.java:61)
> at
> org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:922)
> Caused by: java.io.IOException:
> /etc/ambari-server/conf/krb5JAASLogin.conf (No such file or directory)
> at
> com.sun.security.auth.login.ConfigFile.init(ConfigFile.java:212)
> at
> com.sun.security.auth.login.ConfigFile.(ConfigFile.java:108)
> ... 11 more
> 07 Sep 2016 14:26:55,900 INFO [Stack Version Loading Thread]
> LatestRepoCallable:219 - Stack HDP-2.3 cannot resolve OS debian6 to the
> supported ones: redhat6,redhat7,suse11,ubuntu14,debian7,ubuntu12. Family: null
> 07 Sep 2016 14:26:56,120 INFO [Stack Version Loading Thread]
> LatestRepoCallable:80 - Loading latest URL info for stack HDP-2.4 from
> http://public-repo-1.hortonworks.com/HDP/hdp_urlinfo.json
>
> Checked in the directory and found the following
>
>
>
> nats11-36-juzs-dgm10toeriedwngdha-s11-5:/etc/ambari-server/conf # pwd
>
[jira] [Updated] (AMBARI-18347) Setting fetch_nonlocal_groups to false Can Prevent Services From Starting
[
https://issues.apache.org/jira/browse/AMBARI-18347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-18347:
-
Attachment: AMBARI-18347.patch
> Setting fetch_nonlocal_groups to false Can Prevent Services From Starting
> -
>
> Key: AMBARI-18347
> URL: https://issues.apache.org/jira/browse/AMBARI-18347
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.2.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18347.patch
>
>
> When setting the {{cluster-env/fetch_nonlocal_groups}} value to {{false}}, if
> the {{/etc/group}} file has an unexpected format, services will fail to start:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py",
> line 35, in
> BeforeAnyHook().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 219, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py",
> line 29, in hook
> setup_users()
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py",
> line 44, in setup_users
> fetch_nonlocal_groups = params.fetch_nonlocal_groups
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 154, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/accounts.py",
> line 51, in action_create
> if getattr(self.resource, option_name) != None and getattr(self.resource,
> option_name) != attributes[0](self):
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/accounts.py",
> line 40, in
> groups=(lambda self: self.user_groups, "-G")
> File "/usr/lib/python2.6/site-packages/resource_management/core/utils.py",
> line 146, in decorated
> v = undecorated(self)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/accounts.py",
> line 109, in user_groups
> group_users = entries[3].split(',')
> IndexError: list index out of range
> Error: Error: Unable to run the custom hook script ['/usr/bin/python',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py',
> 'ANY', '/var/lib/ambari-agent/data/command-9429.json',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY',
> '/var/lib/ambari-agent/data/structured-out-9429.json', 'INFO',
> '/var/lib/ambari-agent/tmp']
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18347) Setting fetch_nonlocal_groups to false Can Prevent Services From Starting
[
https://issues.apache.org/jira/browse/AMBARI-18347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-18347:
-
Status: Patch Available (was: Open)
> Setting fetch_nonlocal_groups to false Can Prevent Services From Starting
> -
>
> Key: AMBARI-18347
> URL: https://issues.apache.org/jira/browse/AMBARI-18347
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.2.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18347.patch
>
>
> When setting the {{cluster-env/fetch_nonlocal_groups}} value to {{false}}, if
> the {{/etc/group}} file has an unexpected format, services will fail to start:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py",
> line 35, in
> BeforeAnyHook().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 219, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py",
> line 29, in hook
> setup_users()
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py",
> line 44, in setup_users
> fetch_nonlocal_groups = params.fetch_nonlocal_groups
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 154, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/accounts.py",
> line 51, in action_create
> if getattr(self.resource, option_name) != None and getattr(self.resource,
> option_name) != attributes[0](self):
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/accounts.py",
> line 40, in
> groups=(lambda self: self.user_groups, "-G")
> File "/usr/lib/python2.6/site-packages/resource_management/core/utils.py",
> line 146, in decorated
> v = undecorated(self)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/accounts.py",
> line 109, in user_groups
> group_users = entries[3].split(',')
> IndexError: list index out of range
> Error: Error: Unable to run the custom hook script ['/usr/bin/python',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py',
> 'ANY', '/var/lib/ambari-agent/data/command-9429.json',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY',
> '/var/lib/ambari-agent/data/structured-out-9429.json', 'INFO',
> '/var/lib/ambari-agent/tmp']
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18347) Setting fetch_nonlocal_groups to false Can Prevent Services From Starting
Jonathan Hurley created AMBARI-18347:
Summary: Setting fetch_nonlocal_groups to false Can Prevent
Services From Starting
Key: AMBARI-18347
URL: https://issues.apache.org/jira/browse/AMBARI-18347
Project: Ambari
Issue Type: Bug
Components: ambari-agent
Affects Versions: 2.2.2
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Critical
Fix For: trunk
When setting the {{cluster-env/fetch_nonlocal_groups}} value to {{false}}, if
the {{/etc/group}} file has an unexpected format, services will fail to start:
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py",
line 35, in
BeforeAnyHook().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 219, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py",
line 29, in hook
setup_users()
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py",
line 44, in setup_users
fetch_nonlocal_groups = params.fetch_nonlocal_groups
File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line
154, in __init__
self.env.run()
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/python2.6/site-packages/resource_management/core/providers/accounts.py",
line 51, in action_create
if getattr(self.resource, option_name) != None and getattr(self.resource,
option_name) != attributes[0](self):
File
"/usr/lib/python2.6/site-packages/resource_management/core/providers/accounts.py",
line 40, in
groups=(lambda self: self.user_groups, "-G")
File "/usr/lib/python2.6/site-packages/resource_management/core/utils.py", line
146, in decorated
v = undecorated(self)
File
"/usr/lib/python2.6/site-packages/resource_management/core/providers/accounts.py",
line 109, in user_groups
group_users = entries[3].split(',')
IndexError: list index out of range
Error: Error: Unable to run the custom hook script ['/usr/bin/python',
'/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py',
'ANY', '/var/lib/ambari-agent/data/command-9429.json',
'/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY',
'/var/lib/ambari-agent/data/structured-out-9429.json', 'INFO',
'/var/lib/ambari-agent/tmp']
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18344) Metrics data is not available - AMS in distributed mode
[
https://issues.apache.org/jira/browse/AMBARI-18344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-18344:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to trunk.
> Metrics data is not available - AMS in distributed mode
> ---
>
> Key: AMBARI-18344
> URL: https://issues.apache.org/jira/browse/AMBARI-18344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.1
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18344.patch
>
>
> Data is unavailable for service, host and dashboard metrices.
> Seeing below error in metrics_collector log :
> {code}
> [org.mortbay.jetty.EofException]
> at
> com.sun.jersey.core.provider.jaxb.AbstractRootElementProvider.writeTo(AbstractRootElementProvider.java:159)
> at
> com.sun.jersey.spi.container.ContainerResponse.write(ContainerResponse.java:306)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1437)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:895)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:843)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:804)
> at
> com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)
> at
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
> at
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:118)
> at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:113)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.apache.hadoop.security.http.XFrameOptionsFilter.doFilter(XFrameOptionsFilter.java:57)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.apache.hadoop.http.lib.StaticUserWebFilter$StaticUserFilter.doFilter(StaticUserWebFilter.java:109)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.apache.hadoop.http.HttpServer2$QuotingInputFilter.doFilter(HttpServer2.java:1294)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at org.apache.hadoop.http.NoCacheFilter.doFilter(NoCacheFilter.java:45)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:767)
> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> at org.mortbay.jetty.Server.handle(Server.java:326)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:945)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
> at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
> at
> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
> Caused by: javax.xml.bind.MarshalException
> - with linked exception:
> [org.mortbay.jetty.EofException]
> at
> com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:325)
> at
> com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:249)
> at
>
[jira] [Updated] (AMBARI-18345) 'Stack advisor' validation code reports error while trying to access 'yarn.nodemanager.resource.memory-mb' config.
[ https://issues.apache.org/jira/browse/AMBARI-18345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-18345: - Status: Patch Available (was: Open) > 'Stack advisor' validation code reports error while trying to access > 'yarn.nodemanager.resource.memory-mb' config. > -- > > Key: AMBARI-18345 > URL: https://issues.apache.org/jira/browse/AMBARI-18345 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Attachments: AMBARI-18345.patch > > > 'Stack advisor' validation code reports error while trying to access > "yarn.nodemanager.resource.memory-mb" config. > *Reason:* > - Fn. 'validateHiveInteractiveSiteConfigurations' tried to query for config > 'yarn.nodemanager.resource.memory-mb'. The config may not be passed in > services[configurations], depending on which action triggered the validation. > - Fn. 'validateHiveInteractiveSiteConfigurations' was broken because it was > trying to query config 'yarn.nodemanager.resource.memory-mb', without > checking whether HSI is installed or not. > *Fix:* > - Moved the ''yarn.nodemanager.resource.memory-mb'' config query code once we > have checked the presence of HSI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18346) SmartSense Mandatory Install
[ https://issues.apache.org/jira/browse/AMBARI-18346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18346: Attachment: AMBARI-18346.v0.patch > SmartSense Mandatory Install > > > Key: AMBARI-18346 > URL: https://issues.apache.org/jira/browse/AMBARI-18346 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18346.v0.patch > > > Perform a UI hack to force selection of SmartSense for HDP stacks (the user > cannot deselect). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18345) 'Stack advisor' validation code reports error while trying to access 'yarn.nodemanager.resource.memory-mb' config.
[ https://issues.apache.org/jira/browse/AMBARI-18345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-18345: - Description: 'Stack advisor' validation code reports error while trying to access "yarn.nodemanager.resource.memory-mb" config. *Reason:* - Fn. 'validateHiveInteractiveSiteConfigurations' tried to query for config 'yarn.nodemanager.resource.memory-mb'. The config may not be passed in services[configurations], depending on which action triggered the validation. - Fn. 'validateHiveInteractiveSiteConfigurations' was broken because it was trying to query config 'yarn.nodemanager.resource.memory-mb', without checking whether HSI is installed or not. was: 'Stack advisor' validation code reports error while trying to access "yarn.nodemanager.resource.memory-mb" config. *Reason:* - Fn. 'validateHiveInteractiveSiteConfigurations' tried to query for config 'yarn.nodemanager.resource.memory-mb'. The config may not be passed in services[configurations], depending on which action triggered the validation. - Fn. 'validateHiveInteractiveSiteConfigurations' was broken because it was trying to query config 'yarn.nodemanager.resource.memory-mb', without checking whether HSI is installed or not. *Fix:* - Moved the ''yarn.nodemanager.resource.memory-mb'' config query code once we have checked the presence of HSI. > 'Stack advisor' validation code reports error while trying to access > 'yarn.nodemanager.resource.memory-mb' config. > -- > > Key: AMBARI-18345 > URL: https://issues.apache.org/jira/browse/AMBARI-18345 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.1 > > Attachments: AMBARI-18345.patch > > > 'Stack advisor' validation code reports error while trying to access > "yarn.nodemanager.resource.memory-mb" config. > *Reason:* > - Fn. 'validateHiveInteractiveSiteConfigurations' tried to query for config > 'yarn.nodemanager.resource.memory-mb'. The config may not be passed in > services[configurations], depending on which action triggered the validation. > - Fn. 'validateHiveInteractiveSiteConfigurations' was broken because it was > trying to query config 'yarn.nodemanager.resource.memory-mb', without > checking whether HSI is installed or not. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18346) SmartSense Mandatory Install
[ https://issues.apache.org/jira/browse/AMBARI-18346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18346: Component/s: ambari-web > SmartSense Mandatory Install > > > Key: AMBARI-18346 > URL: https://issues.apache.org/jira/browse/AMBARI-18346 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18346.v0.patch > > > Perform a UI hack to force selection of SmartSense for HDP stacks (the user > cannot deselect). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18346) SmartSense Mandatory Install
[ https://issues.apache.org/jira/browse/AMBARI-18346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18346: Status: Patch Available (was: Open) > SmartSense Mandatory Install > > > Key: AMBARI-18346 > URL: https://issues.apache.org/jira/browse/AMBARI-18346 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18346.v0.patch > > > Perform a UI hack to force selection of SmartSense for HDP stacks (the user > cannot deselect). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18346) SmartSense Mandatory Install
[ https://issues.apache.org/jira/browse/AMBARI-18346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18346: Affects Version/s: 2.5.0 > SmartSense Mandatory Install > > > Key: AMBARI-18346 > URL: https://issues.apache.org/jira/browse/AMBARI-18346 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > > Perform a UI hack to force selection of SmartSense for HDP stacks (the user > cannot deselect). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18346) SmartSense Mandatory Install
Vivek Ratnavel Subramanian created AMBARI-18346: --- Summary: SmartSense Mandatory Install Key: AMBARI-18346 URL: https://issues.apache.org/jira/browse/AMBARI-18346 Project: Ambari Issue Type: Bug Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Fix For: 2.5.0 Perform a UI hack to force selection of SmartSense for HDP stacks (the user cannot deselect). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18345) 'Stack advisor' validation code reports error while trying to access 'yarn.nodemanager.resource.memory-mb' config.
[ https://issues.apache.org/jira/browse/AMBARI-18345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-18345: - Fix Version/s: 2.4.1 > 'Stack advisor' validation code reports error while trying to access > 'yarn.nodemanager.resource.memory-mb' config. > -- > > Key: AMBARI-18345 > URL: https://issues.apache.org/jira/browse/AMBARI-18345 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.1 > > Attachments: AMBARI-18345.patch > > > 'Stack advisor' validation code reports error while trying to access > "yarn.nodemanager.resource.memory-mb" config. > *Reason:* > - Fn. 'validateHiveInteractiveSiteConfigurations' tried to query for config > 'yarn.nodemanager.resource.memory-mb'. The config may not be passed in > services[configurations], depending on which action triggered the validation. > - Fn. 'validateHiveInteractiveSiteConfigurations' was broken because it was > trying to query config 'yarn.nodemanager.resource.memory-mb', without > checking whether HSI is installed or not. > *Fix:* > - Moved the ''yarn.nodemanager.resource.memory-mb'' config query code once we > have checked the presence of HSI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18345) 'Stack advisor' validation code reports error while trying to access 'yarn.nodemanager.resource.memory-mb' config.
[ https://issues.apache.org/jira/browse/AMBARI-18345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-18345: - Component/s: ambari-server > 'Stack advisor' validation code reports error while trying to access > 'yarn.nodemanager.resource.memory-mb' config. > -- > > Key: AMBARI-18345 > URL: https://issues.apache.org/jira/browse/AMBARI-18345 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.1 > > Attachments: AMBARI-18345.patch > > > 'Stack advisor' validation code reports error while trying to access > "yarn.nodemanager.resource.memory-mb" config. > *Reason:* > - Fn. 'validateHiveInteractiveSiteConfigurations' tried to query for config > 'yarn.nodemanager.resource.memory-mb'. The config may not be passed in > services[configurations], depending on which action triggered the validation. > - Fn. 'validateHiveInteractiveSiteConfigurations' was broken because it was > trying to query config 'yarn.nodemanager.resource.memory-mb', without > checking whether HSI is installed or not. > *Fix:* > - Moved the ''yarn.nodemanager.resource.memory-mb'' config query code once we > have checked the presence of HSI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18345) 'Stack advisor' validation code reports error while trying to access 'yarn.nodemanager.resource.memory-mb' config.
[ https://issues.apache.org/jira/browse/AMBARI-18345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15474864#comment-15474864 ] Swapan Shridhar commented on AMBARI-18345: -- *Fix:* - Moved the ''yarn.nodemanager.resource.memory-mb'' config query code once we have checked the presence of HSI. > 'Stack advisor' validation code reports error while trying to access > 'yarn.nodemanager.resource.memory-mb' config. > -- > > Key: AMBARI-18345 > URL: https://issues.apache.org/jira/browse/AMBARI-18345 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.1 > > Attachments: AMBARI-18345.patch > > > 'Stack advisor' validation code reports error while trying to access > "yarn.nodemanager.resource.memory-mb" config. > *Reason:* > - Fn. 'validateHiveInteractiveSiteConfigurations' tried to query for config > 'yarn.nodemanager.resource.memory-mb'. The config may not be passed in > services[configurations], depending on which action triggered the validation. > - Fn. 'validateHiveInteractiveSiteConfigurations' was broken because it was > trying to query config 'yarn.nodemanager.resource.memory-mb', without > checking whether HSI is installed or not. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18345) 'Stack advisor' validation code reports error while trying to access 'yarn.nodemanager.resource.memory-mb' config.
[ https://issues.apache.org/jira/browse/AMBARI-18345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-18345: - Status: Patch Available (was: Open) > 'Stack advisor' validation code reports error while trying to access > 'yarn.nodemanager.resource.memory-mb' config. > -- > > Key: AMBARI-18345 > URL: https://issues.apache.org/jira/browse/AMBARI-18345 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.1 > > Attachments: AMBARI-18345.patch > > > 'Stack advisor' validation code reports error while trying to access > "yarn.nodemanager.resource.memory-mb" config. > *Reason:* > - Fn. 'validateHiveInteractiveSiteConfigurations' tried to query for config > 'yarn.nodemanager.resource.memory-mb'. The config may not be passed in > services[configurations], depending on which action triggered the validation. > - Fn. 'validateHiveInteractiveSiteConfigurations' was broken because it was > trying to query config 'yarn.nodemanager.resource.memory-mb', without > checking whether HSI is installed or not. > *Fix:* > - Moved the ''yarn.nodemanager.resource.memory-mb'' config query code once we > have checked the presence of HSI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18345) 'Stack advisor' validation code reports error while trying to access 'yarn.nodemanager.resource.memory-mb' config.
[ https://issues.apache.org/jira/browse/AMBARI-18345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-18345: - Affects Version/s: 2.4.0 > 'Stack advisor' validation code reports error while trying to access > 'yarn.nodemanager.resource.memory-mb' config. > -- > > Key: AMBARI-18345 > URL: https://issues.apache.org/jira/browse/AMBARI-18345 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.1 > > Attachments: AMBARI-18345.patch > > > 'Stack advisor' validation code reports error while trying to access > "yarn.nodemanager.resource.memory-mb" config. > *Reason:* > - Fn. 'validateHiveInteractiveSiteConfigurations' tried to query for config > 'yarn.nodemanager.resource.memory-mb'. The config may not be passed in > services[configurations], depending on which action triggered the validation. > - Fn. 'validateHiveInteractiveSiteConfigurations' was broken because it was > trying to query config 'yarn.nodemanager.resource.memory-mb', without > checking whether HSI is installed or not. > *Fix:* > - Moved the ''yarn.nodemanager.resource.memory-mb'' config query code once we > have checked the presence of HSI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18345) 'Stack advisor' validation code reports error while trying to access 'yarn.nodemanager.resource.memory-mb' config.
[ https://issues.apache.org/jira/browse/AMBARI-18345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-18345: - Attachment: AMBARI-18345.patch > 'Stack advisor' validation code reports error while trying to access > 'yarn.nodemanager.resource.memory-mb' config. > -- > > Key: AMBARI-18345 > URL: https://issues.apache.org/jira/browse/AMBARI-18345 > Project: Ambari > Issue Type: Bug >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Attachments: AMBARI-18345.patch > > > 'Stack advisor' validation code reports error while trying to access > "yarn.nodemanager.resource.memory-mb" config. > *Reason:* > - Fn. 'validateHiveInteractiveSiteConfigurations' tried to query for config > 'yarn.nodemanager.resource.memory-mb'. The config may not be passed in > services[configurations], depending on which action triggered the validation. > - Fn. 'validateHiveInteractiveSiteConfigurations' was broken because it was > trying to query config 'yarn.nodemanager.resource.memory-mb', without > checking whether HSI is installed or not. > *Fix:* > - Moved the ''yarn.nodemanager.resource.memory-mb'' config query code once we > have checked the presence of HSI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18345) 'Stack advisor' validation code reports error while trying to access 'yarn.nodemanager.resource.memory-mb' config.
[ https://issues.apache.org/jira/browse/AMBARI-18345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-18345: - Summary: 'Stack advisor' validation code reports error while trying to access 'yarn.nodemanager.resource.memory-mb' config. (was: 'Stack advisor' validation code reports error while trying to access "yarn.nodemanager.resource.memory-mb" config.) > 'Stack advisor' validation code reports error while trying to access > 'yarn.nodemanager.resource.memory-mb' config. > -- > > Key: AMBARI-18345 > URL: https://issues.apache.org/jira/browse/AMBARI-18345 > Project: Ambari > Issue Type: Bug >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > > 'Stack advisor' validation code reports error while trying to access > "yarn.nodemanager.resource.memory-mb" config. > Reason: > - Fn. 'validateHiveInteractiveSiteConfigurations' tried to query for config > 'yarn.nodemanager.resource.memory-mb'. The config may not be passed in > services[configurations], depending on which action triggered the validation. > - Fn. 'validateHiveInteractiveSiteConfigurations' was broken because it was > trying to query config 'yarn.nodemanager.resource.memory-mb', without > checking whether HSI is installed or not. > Fix: Moved the ''yarn.nodemanager.resource.memory-mb'' config query code once > we have checked the presence of HSI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18345) 'Stack advisor' validation code reports error while trying to access "yarn.nodemanager.resource.memory-mb" config.
Swapan Shridhar created AMBARI-18345: Summary: 'Stack advisor' validation code reports error while trying to access "yarn.nodemanager.resource.memory-mb" config. Key: AMBARI-18345 URL: https://issues.apache.org/jira/browse/AMBARI-18345 Project: Ambari Issue Type: Bug Reporter: Swapan Shridhar Assignee: Swapan Shridhar 'Stack advisor' validation code reports error while trying to access "yarn.nodemanager.resource.memory-mb" config. Reason: - Fn. 'validateHiveInteractiveSiteConfigurations' tried to query for config 'yarn.nodemanager.resource.memory-mb'. The config may not be passed in services[configurations], depending on which action triggered the validation. - Fn. 'validateHiveInteractiveSiteConfigurations' was broken because it was trying to query config 'yarn.nodemanager.resource.memory-mb', without checking whether HSI is installed or not. Fix: Moved the ''yarn.nodemanager.resource.memory-mb'' config query code once we have checked the presence of HSI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18345) 'Stack advisor' validation code reports error while trying to access 'yarn.nodemanager.resource.memory-mb' config.
[ https://issues.apache.org/jira/browse/AMBARI-18345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-18345: - Description: 'Stack advisor' validation code reports error while trying to access "yarn.nodemanager.resource.memory-mb" config. *Reason:* - Fn. 'validateHiveInteractiveSiteConfigurations' tried to query for config 'yarn.nodemanager.resource.memory-mb'. The config may not be passed in services[configurations], depending on which action triggered the validation. - Fn. 'validateHiveInteractiveSiteConfigurations' was broken because it was trying to query config 'yarn.nodemanager.resource.memory-mb', without checking whether HSI is installed or not. *Fix:* - Moved the ''yarn.nodemanager.resource.memory-mb'' config query code once we have checked the presence of HSI. was: 'Stack advisor' validation code reports error while trying to access "yarn.nodemanager.resource.memory-mb" config. Reason: - Fn. 'validateHiveInteractiveSiteConfigurations' tried to query for config 'yarn.nodemanager.resource.memory-mb'. The config may not be passed in services[configurations], depending on which action triggered the validation. - Fn. 'validateHiveInteractiveSiteConfigurations' was broken because it was trying to query config 'yarn.nodemanager.resource.memory-mb', without checking whether HSI is installed or not. Fix: Moved the ''yarn.nodemanager.resource.memory-mb'' config query code once we have checked the presence of HSI. > 'Stack advisor' validation code reports error while trying to access > 'yarn.nodemanager.resource.memory-mb' config. > -- > > Key: AMBARI-18345 > URL: https://issues.apache.org/jira/browse/AMBARI-18345 > Project: Ambari > Issue Type: Bug >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > > 'Stack advisor' validation code reports error while trying to access > "yarn.nodemanager.resource.memory-mb" config. > *Reason:* > - Fn. 'validateHiveInteractiveSiteConfigurations' tried to query for config > 'yarn.nodemanager.resource.memory-mb'. The config may not be passed in > services[configurations], depending on which action triggered the validation. > - Fn. 'validateHiveInteractiveSiteConfigurations' was broken because it was > trying to query config 'yarn.nodemanager.resource.memory-mb', without > checking whether HSI is installed or not. > *Fix:* > - Moved the ''yarn.nodemanager.resource.memory-mb'' config query code once we > have checked the presence of HSI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18333) While checking for component dependency code looks for incorrect component name
[ https://issues.apache.org/jira/browse/AMBARI-18333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-18333: --- Resolution: Fixed Status: Resolved (was: Patch Available) > While checking for component dependency code looks for incorrect component > name > --- > > Key: AMBARI-18333 > URL: https://issues.apache.org/jira/browse/AMBARI-18333 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-18333.patch > > > While validating host groups in blueprint for component dependency, code > should check if a dependency component is present in the host group component > list rather than the component on whose dependency list it is iterating. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18344) Metrics data is not available - AMS in distributed mode
[
https://issues.apache.org/jira/browse/AMBARI-18344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15474830#comment-15474830
]
Siddharth Wagle commented on AMBARI-18344:
--
+1 LGTM
> Metrics data is not available - AMS in distributed mode
> ---
>
> Key: AMBARI-18344
> URL: https://issues.apache.org/jira/browse/AMBARI-18344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.1
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18344.patch
>
>
> Data is unavailable for service, host and dashboard metrices.
> Seeing below error in metrics_collector log :
> {code}
> [org.mortbay.jetty.EofException]
> at
> com.sun.jersey.core.provider.jaxb.AbstractRootElementProvider.writeTo(AbstractRootElementProvider.java:159)
> at
> com.sun.jersey.spi.container.ContainerResponse.write(ContainerResponse.java:306)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1437)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:895)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:843)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:804)
> at
> com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)
> at
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
> at
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:118)
> at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:113)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.apache.hadoop.security.http.XFrameOptionsFilter.doFilter(XFrameOptionsFilter.java:57)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.apache.hadoop.http.lib.StaticUserWebFilter$StaticUserFilter.doFilter(StaticUserWebFilter.java:109)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.apache.hadoop.http.HttpServer2$QuotingInputFilter.doFilter(HttpServer2.java:1294)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at org.apache.hadoop.http.NoCacheFilter.doFilter(NoCacheFilter.java:45)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:767)
> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> at org.mortbay.jetty.Server.handle(Server.java:326)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:945)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
> at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
> at
> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
> Caused by: javax.xml.bind.MarshalException
> - with linked exception:
> [org.mortbay.jetty.EofException]
> at
> com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:325)
> at
> com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:249)
> at
> javax.xml.bind.helpers.AbstractMarshallerImpl.marshal(AbstractMarshallerImpl.java:95)
> at
>
[jira] [Commented] (AMBARI-18290) Ambari does not support HBase on HTTPS mode
[ https://issues.apache.org/jira/browse/AMBARI-18290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15474764#comment-15474764 ] Hudson commented on AMBARI-18290: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5639 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5639/]) AMBARI-18290. Ambari does not support HBase on HTTPS mode. (swagle: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f0e022d27d09fdcb5b7e513a42f08b3617bd6a53]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractProviderModule.java > Ambari does not support HBase on HTTPS mode > --- > > Key: AMBARI-18290 > URL: https://issues.apache.org/jira/browse/AMBARI-18290 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0, 2.2.2 > Environment: all >Reporter: amarnathreddy >Assignee: amarnathreddy >Priority: Critical > Attachments: 18290.txt > > > Ambari tries to talk to Hbase URL on HTTP mode even after SSL is enabled for > HBase master. There is an issue when Ambari trying to retrive HBase JMX > parameters. Because of this Ambari shows incorrect information about > Active/Standby -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18325) Ambari cannot install HDP from mirror list
[ https://issues.apache.org/jira/browse/AMBARI-18325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15474765#comment-15474765 ] Hudson commented on AMBARI-18325: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5639 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5639/]) AMBARI-18325. Ambari cannot install HDP from mirror list (dlysnichenko) (dlysnichenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=26b4299e7105c540fa2ab3dcf34e5abdc76025c6]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/RepositoryEntity.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/StackModule.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog200Test.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/RepositoryInfo.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/AmbariMetaInfo.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/RepositoryRequest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/stack/LatestRepoCallable.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/RepositoryVersionHelper.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/StackContext.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/StackUpgradeUtilTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/StackUpgradeHelper.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryResourceProvider.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/StackUpgradeUtil.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog200.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/api/services/AmbariMetaInfoTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProvider.java > Ambari cannot install HDP from mirror list > -- > > Key: AMBARI-18325 > URL: https://issues.apache.org/jira/browse/AMBARI-18325 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Fix For: trunk > > Attachments: AMBARI-18325.patch > > > Ambari should update the code and be able to use a mirror list instead of a > single url. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18341) Need to validate behaviour and show warn message for user after hcat user was removed
[ https://issues.apache.org/jira/browse/AMBARI-18341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18341: --- Attachment: (was: AMBARI-18341.patch) > Need to validate behaviour and show warn message for user after hcat user was > removed > - > > Key: AMBARI-18341 > URL: https://issues.apache.org/jira/browse/AMBARI-18341 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18341.patch > > > We should validate behaviour for few basic scenarious and show warn message > for user about potential problems. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18341) Need to validate behaviour and show warn message for user after hcat user was removed
[ https://issues.apache.org/jira/browse/AMBARI-18341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18341: --- Attachment: AMBARI-18341.patch > Need to validate behaviour and show warn message for user after hcat user was > removed > - > > Key: AMBARI-18341 > URL: https://issues.apache.org/jira/browse/AMBARI-18341 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18341.patch > > > We should validate behaviour for few basic scenarious and show warn message > for user about potential problems. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18344) Metrics data is not available - AMS in distributed mode
[
https://issues.apache.org/jira/browse/AMBARI-18344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-18344:
---
Status: Patch Available (was: Open)
> Metrics data is not available - AMS in distributed mode
> ---
>
> Key: AMBARI-18344
> URL: https://issues.apache.org/jira/browse/AMBARI-18344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.1
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18344.patch
>
>
> Data is unavailable for service, host and dashboard metrices.
> Seeing below error in metrics_collector log :
> {code}
> [org.mortbay.jetty.EofException]
> at
> com.sun.jersey.core.provider.jaxb.AbstractRootElementProvider.writeTo(AbstractRootElementProvider.java:159)
> at
> com.sun.jersey.spi.container.ContainerResponse.write(ContainerResponse.java:306)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1437)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:895)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:843)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:804)
> at
> com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)
> at
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
> at
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:118)
> at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:113)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.apache.hadoop.security.http.XFrameOptionsFilter.doFilter(XFrameOptionsFilter.java:57)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.apache.hadoop.http.lib.StaticUserWebFilter$StaticUserFilter.doFilter(StaticUserWebFilter.java:109)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.apache.hadoop.http.HttpServer2$QuotingInputFilter.doFilter(HttpServer2.java:1294)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at org.apache.hadoop.http.NoCacheFilter.doFilter(NoCacheFilter.java:45)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:767)
> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> at org.mortbay.jetty.Server.handle(Server.java:326)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:945)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
> at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
> at
> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
> Caused by: javax.xml.bind.MarshalException
> - with linked exception:
> [org.mortbay.jetty.EofException]
> at
> com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:325)
> at
> com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:249)
> at
> javax.xml.bind.helpers.AbstractMarshallerImpl.marshal(AbstractMarshallerImpl.java:95)
> at
>
[jira] [Updated] (AMBARI-18344) Metrics data is not available - AMS in distributed mode
[
https://issues.apache.org/jira/browse/AMBARI-18344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-18344:
---
Attachment: AMBARI-18344.patch
> Metrics data is not available - AMS in distributed mode
> ---
>
> Key: AMBARI-18344
> URL: https://issues.apache.org/jira/browse/AMBARI-18344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.1
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18344.patch
>
>
> Data is unavailable for service, host and dashboard metrices.
> Seeing below error in metrics_collector log :
> {code}
> [org.mortbay.jetty.EofException]
> at
> com.sun.jersey.core.provider.jaxb.AbstractRootElementProvider.writeTo(AbstractRootElementProvider.java:159)
> at
> com.sun.jersey.spi.container.ContainerResponse.write(ContainerResponse.java:306)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1437)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:895)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:843)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:804)
> at
> com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)
> at
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
> at
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:118)
> at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:113)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.apache.hadoop.security.http.XFrameOptionsFilter.doFilter(XFrameOptionsFilter.java:57)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.apache.hadoop.http.lib.StaticUserWebFilter$StaticUserFilter.doFilter(StaticUserWebFilter.java:109)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.apache.hadoop.http.HttpServer2$QuotingInputFilter.doFilter(HttpServer2.java:1294)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at org.apache.hadoop.http.NoCacheFilter.doFilter(NoCacheFilter.java:45)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:767)
> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> at org.mortbay.jetty.Server.handle(Server.java:326)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:945)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
> at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
> at
> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
> Caused by: javax.xml.bind.MarshalException
> - with linked exception:
> [org.mortbay.jetty.EofException]
> at
> com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:325)
> at
> com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:249)
> at
> javax.xml.bind.helpers.AbstractMarshallerImpl.marshal(AbstractMarshallerImpl.java:95)
> at
>
[jira] [Commented] (AMBARI-18261) CapSched View: Showing warning icons to refresh or restart capsched once after configs are saved
[ https://issues.apache.org/jira/browse/AMBARI-18261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15474746#comment-15474746 ] Hudson commented on AMBARI-18261: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #7 (See [https://builds.apache.org/job/Ambari-branch-2.5/7/]) AMBARI-18261. CapSched View: Showing warning icons to refresh or restart (pallav.kul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=df5fdb33e01a2cd8a21c1383818a395ac02673a9]) * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/components/queueSummary.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/capsched/partials/queueResources.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/controllers/scheduler.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/components/capacityInput.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/styles/application.less * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/adapters.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/components/editQueueCapacity.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/controllers/editqueue.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/capsched/advanced.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/components/queueMapping.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/controllers/queuesconf.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/capsched/scheduler.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/capsched/partials/preemption.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/components/queueMapping.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/models/queue.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/components/editQueueCapacity.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/components/queueSummary.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/capsched/partials/queueCapacity.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/controllers/advanced.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/components/labelCapacityBar.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/router.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/store.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/capsched/queuesconf.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/components/saveConfigDialog.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/capsched/partials/labelCapacity.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/capsched/partials/accessControlList.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/components/editLabelCapacity.js > CapSched View: Showing warning icons to refresh or restart capsched once > after configs are saved > > > Key: AMBARI-18261 > URL: https://issues.apache.org/jira/browse/AMBARI-18261 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Akhil PB >Assignee: Akhil PB > Fix For: 2.5.0 > > Attachments: AMBARI-18261.1.patch, AMBARI-18261.2.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17602) Capacity Scheduler View - Fetching current RM configuration of queues and preemption implementation
[ https://issues.apache.org/jira/browse/AMBARI-17602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15474745#comment-15474745 ] Hudson commented on AMBARI-17602: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #7 (See [https://builds.apache.org/job/Ambari-branch-2.5/7/]) AMBARI-17602. Capacity Scheduler View - Fetching current RM (pallav.kul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6a89de639bb071b987997ebc315bf2aedd703558]) * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/serializers.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/components/displayNodeLabels.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/components/labelCapacityBar.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/models/queue.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/components/capacityInput.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/store.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/capsched/queuesconf.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/components/queueMapping.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/controllers/queuesconf.js * (edit) contrib/views/capacity-scheduler/src/main/java/org/apache/ambari/view/capacityscheduler/ConfigurationService.java * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/capsched/queuesconf/editqueue.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/controllers/capsched.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/components/queueSummary.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/capsched.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/adapters.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/capsched/partials/queueResources.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/capsched/partials/labelCapacity.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/components/editLabelCapacity.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/router.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/capsched/partials/queueCapacity.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/views/editqueue.js * (add) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/capsched/partials/preemption.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/controllers/editqueue.js * (add) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/capsched/trace.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/components/editLabelCapacity.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/components/editQueueCapacity.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/components/queueSummary.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/styles/application.less > Capacity Scheduler View - Fetching current RM configuration of queues and > preemption implementation > --- > > Key: AMBARI-17602 > URL: https://issues.apache.org/jira/browse/AMBARI-17602 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Akhil PB >Assignee: Akhil PB > Fix For: trunk > > Attachments: AMBARI-17602.1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18344) Metrics data is not available - AMS in distributed mode
Aravindan Vijayan created AMBARI-18344:
--
Summary: Metrics data is not available - AMS in distributed mode
Key: AMBARI-18344
URL: https://issues.apache.org/jira/browse/AMBARI-18344
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: 2.4.1
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
Priority: Critical
Fix For: 2.4.2
Data is unavailable for service, host and dashboard metrices.
Seeing below error in metrics_collector log :
{code}
[org.mortbay.jetty.EofException]
at
com.sun.jersey.core.provider.jaxb.AbstractRootElementProvider.writeTo(AbstractRootElementProvider.java:159)
at
com.sun.jersey.spi.container.ContainerResponse.write(ContainerResponse.java:306)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1437)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)
at
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
at
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537)
at
com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:895)
at
com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:843)
at
com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:804)
at
com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)
at
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
at
com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:118)
at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:113)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
at
org.apache.hadoop.security.http.XFrameOptionsFilter.doFilter(XFrameOptionsFilter.java:57)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
at
org.apache.hadoop.http.lib.StaticUserWebFilter$StaticUserFilter.doFilter(StaticUserWebFilter.java:109)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
at
org.apache.hadoop.http.HttpServer2$QuotingInputFilter.doFilter(HttpServer2.java:1294)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
at org.apache.hadoop.http.NoCacheFilter.doFilter(NoCacheFilter.java:45)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:767)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at
org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:945)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
Caused by: javax.xml.bind.MarshalException
- with linked exception:
[org.mortbay.jetty.EofException]
at
com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:325)
at
com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:249)
at
javax.xml.bind.helpers.AbstractMarshallerImpl.marshal(AbstractMarshallerImpl.java:95)
at
com.sun.jersey.core.provider.jaxb.AbstractRootElementProvider.writeTo(AbstractRootElementProvider.java:179)
at
com.sun.jersey.core.provider.jaxb.AbstractRootElementProvider.writeTo(AbstractRootElementProvider.java:157)
... 37 more
Caused by: org.mortbay.jetty.EofException
at
[jira] [Commented] (AMBARI-18335) After upgrading cluster from HDP-2.4.x to HDP-2.5.x and added atlas service - missing kafka security properties
[
https://issues.apache.org/jira/browse/AMBARI-18335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15474718#comment-15474718
]
Hadoop QA commented on AMBARI-18335:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12827604/AMBARI-18335_trunk_02.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 9 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/8614//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8614//console
This message is automatically generated.
> After upgrading cluster from HDP-2.4.x to HDP-2.5.x and added atlas service -
> missing kafka security properties
> ---
>
> Key: AMBARI-18335
> URL: https://issues.apache.org/jira/browse/AMBARI-18335
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Blocker
> Labels: kerberos_descriptor, upgrade
> Fix For: 2.4.1
>
> Attachments: AMBARI-18335_branch-2.4_01.patch,
> AMBARI-18335_branch-2.4_02.patch, AMBARI-18335_trunk_01.patch,
> AMBARI-18335_trunk_02.patch
>
>
> Steps to repro:
> * Install Ambari 2.2.2
> * Install HDP-2.4.x cluster with Atlas
> * Stop Atlas
> * Upgrade Ambari to 2.4
> * Delete Atlas service
> * Upgrade the cluster to HDP-2.5.x cluster
> * Add Atlas service.
> *Below config properties are missing from atlas-applicataion.properties file
> for Atlas, Storm, Falcon, Hive services.*
> #atlas.jaas.KafkaClient.option.keyTab =
> /etc/security/keytabs/atlas.service.keytab
> #atlas.jaas.KafkaClient.option.principal = atlas/_h...@example.com
> From HDP 2.4 to 2.5, the kerberos.json file for Atlas changed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18335) After upgrading cluster from HDP-2.4.x to HDP-2.5.x and added atlas service - missing kafka security properties
[ https://issues.apache.org/jira/browse/AMBARI-18335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18335: --- Priority: Blocker (was: Major) > After upgrading cluster from HDP-2.4.x to HDP-2.5.x and added atlas service - > missing kafka security properties > --- > > Key: AMBARI-18335 > URL: https://issues.apache.org/jira/browse/AMBARI-18335 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Blocker > Labels: kerberos_descriptor, upgrade > Fix For: 2.4.1 > > Attachments: AMBARI-18335_branch-2.4_01.patch, > AMBARI-18335_branch-2.4_02.patch, AMBARI-18335_trunk_01.patch, > AMBARI-18335_trunk_02.patch > > > Steps to repro: > * Install Ambari 2.2.2 > * Install HDP-2.4.x cluster with Atlas > * Stop Atlas > * Upgrade Ambari to 2.4 > * Delete Atlas service > * Upgrade the cluster to HDP-2.5.x cluster > * Add Atlas service. > *Below config properties are missing from atlas-applicataion.properties file > for Atlas, Storm, Falcon, Hive services.* > #atlas.jaas.KafkaClient.option.keyTab = > /etc/security/keytabs/atlas.service.keytab > #atlas.jaas.KafkaClient.option.principal = atlas/_h...@example.com > From HDP 2.4 to 2.5, the kerberos.json file for Atlas changed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18342) Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain)
[
https://issues.apache.org/jira/browse/AMBARI-18342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-18342:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain)
> -
>
> Key: AMBARI-18342
> URL: https://issues.apache.org/jira/browse/AMBARI-18342
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 3.0.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: rb51733 (2).patch, rb51733.patch
>
>
> Unit test failure in ambari-agent because of AMBARI-18299:
> {code}
> FAIL: test_update_open_files_ulimit (TestMain.TestMain)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-agent/src/test/python/ambari_agent/TestMain.py",
> line 137, in test_update_open_files_ulimit
> self.assertEquals(hard_limit, open_files_ulimit)
> AssertionError: 6 != 10240
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18342) Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain)
[
https://issues.apache.org/jira/browse/AMBARI-18342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-18342:
---
Attachment: rb51733 (2).patch
> Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain)
> -
>
> Key: AMBARI-18342
> URL: https://issues.apache.org/jira/browse/AMBARI-18342
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 3.0.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: rb51733 (2).patch, rb51733.patch
>
>
> Unit test failure in ambari-agent because of AMBARI-18299:
> {code}
> FAIL: test_update_open_files_ulimit (TestMain.TestMain)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-agent/src/test/python/ambari_agent/TestMain.py",
> line 137, in test_update_open_files_ulimit
> self.assertEquals(hard_limit, open_files_ulimit)
> AssertionError: 6 != 10240
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18342) Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain)
[
https://issues.apache.org/jira/browse/AMBARI-18342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-18342:
---
Status: Open (was: Patch Available)
> Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain)
> -
>
> Key: AMBARI-18342
> URL: https://issues.apache.org/jira/browse/AMBARI-18342
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 3.0.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: rb51733 (2).patch, rb51733.patch
>
>
> Unit test failure in ambari-agent because of AMBARI-18299:
> {code}
> FAIL: test_update_open_files_ulimit (TestMain.TestMain)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-agent/src/test/python/ambari_agent/TestMain.py",
> line 137, in test_update_open_files_ulimit
> self.assertEquals(hard_limit, open_files_ulimit)
> AssertionError: 6 != 10240
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18342) Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain)
[
https://issues.apache.org/jira/browse/AMBARI-18342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-18342:
---
Status: Patch Available (was: Open)
> Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain)
> -
>
> Key: AMBARI-18342
> URL: https://issues.apache.org/jira/browse/AMBARI-18342
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 3.0.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: rb51733 (2).patch, rb51733.patch
>
>
> Unit test failure in ambari-agent because of AMBARI-18299:
> {code}
> FAIL: test_update_open_files_ulimit (TestMain.TestMain)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-agent/src/test/python/ambari_agent/TestMain.py",
> line 137, in test_update_open_files_ulimit
> self.assertEquals(hard_limit, open_files_ulimit)
> AssertionError: 6 != 10240
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18335) After upgrading cluster from HDP-2.4.x to HDP-2.5.x and added atlas service - missing kafka security properties
[ https://issues.apache.org/jira/browse/AMBARI-18335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18335: --- Fix Version/s: (was: 2.4.2) 2.4.1 > After upgrading cluster from HDP-2.4.x to HDP-2.5.x and added atlas service - > missing kafka security properties > --- > > Key: AMBARI-18335 > URL: https://issues.apache.org/jira/browse/AMBARI-18335 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Robert Levas >Assignee: Robert Levas > Labels: kerberos_descriptor, upgrade > Fix For: 2.4.1 > > Attachments: AMBARI-18335_branch-2.4_01.patch, > AMBARI-18335_branch-2.4_02.patch, AMBARI-18335_trunk_01.patch, > AMBARI-18335_trunk_02.patch > > > Steps to repro: > * Install Ambari 2.2.2 > * Install HDP-2.4.x cluster with Atlas > * Stop Atlas > * Upgrade Ambari to 2.4 > * Delete Atlas service > * Upgrade the cluster to HDP-2.5.x cluster > * Add Atlas service. > *Below config properties are missing from atlas-applicataion.properties file > for Atlas, Storm, Falcon, Hive services.* > #atlas.jaas.KafkaClient.option.keyTab = > /etc/security/keytabs/atlas.service.keytab > #atlas.jaas.KafkaClient.option.principal = atlas/_h...@example.com > From HDP 2.4 to 2.5, the kerberos.json file for Atlas changed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18271) Multiple Aggregate Alerts For JournalNode Exist With Some Being Incorrect
[ https://issues.apache.org/jira/browse/AMBARI-18271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Sposetti updated AMBARI-18271: --- Fix Version/s: 2.4.1 > Multiple Aggregate Alerts For JournalNode Exist With Some Being Incorrect > - > > Key: AMBARI-18271 > URL: https://issues.apache.org/jira/browse/AMBARI-18271 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.0.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Critical > Fix For: trunk, 2.4.1 > > Attachments: AMBARI-18271.patch > > > When a cluster is being created initially, there are many new alert instances > being generated concurrently. This can lead to a race condition where certain > alert types, such as aggregate alerts, fire several events and end up > creating duplicate alert instances. > Although aggregate alerts are the most common, the flaw is in the alert > listener since it never guarantees uniqueness even though it supports > concurrent events. > This problem is mainly encountered when the cluster is initially created, and > therefore a solution shouldn't impact the rest of the cluster's lifetime. In > other words, we shouldn't cause a degradation the other 99.9% of the time in > order to fix this problem. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18321) atlas hook for hive and storm fail to push metadeta
[
https://issues.apache.org/jira/browse/AMBARI-18321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Sposetti updated AMBARI-18321:
---
Fix Version/s: 2.4.1
> atlas hook for hive and storm fail to push metadeta
> ---
>
> Key: AMBARI-18321
> URL: https://issues.apache.org/jira/browse/AMBARI-18321
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Dmytro Grinenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Fix For: trunk, 2.4.1
>
> Attachments: AMBARI-18321-rat-fix.patch, AMBARI-18321.patch,
> AMBARI-18321.patch.1
>
>
> 1] On the upgraded cluster we added Atlas service
> 2] On submitting the storm topology,atlas hook fails to send metadata.
> Attached logs [ storm_atlas.log] where connect to kafka is failing.
> 3] Hive hook is also failing with the same error as below
> {code}
> Caused by: javax.security.auth.login.LoginException: Could not login: the
> client is being asked for a password, but the Kafka client code does not
> currently support obtaining a password from the user. not available to garner
> authentication information from the user
> at
> com.sun.security.auth.module.Krb5LoginModule.promptForPass(Krb5LoginModule.java:940)
> at
> com.sun.security.auth.module.Krb5LoginModule.attemptAuthentication(Krb5LoginModule.java:760)
> at
> com.sun.security.auth.module.Krb5LoginModule.login(Krb5LoginModule.java:617)
> at sun.reflect.GeneratedMethodAccessor54.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> javax.security.auth.login.LoginContext.invoke(LoginContext.java:755)
> at
> javax.security.auth.login.LoginContext.access$000(LoginContext.java:195)
> at javax.security.auth.login.LoginContext$4.run(LoginContext.java:682)
> at javax.security.auth.login.LoginContext$4.run(LoginContext.java:680)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
> at javax.security.auth.login.LoginContext.login(LoginContext.java:587)
> at
> org.apache.kafka.common.security.authenticator.AbstractLogin.login(AbstractLogin.java:69)
> at
> org.apache.kafka.common.security.kerberos.KerberosLogin.login(KerberosLogin.java:110)
> at
> org.apache.kafka.common.security.authenticator.LoginManager.(LoginManager.java:46)
> at
> org.apache.kafka.common.security.authenticator.LoginManager.acquireLoginManager(LoginManager.java:68)
> at
> org.apache.kafka.common.network.SaslChannelBuilder.configure(SaslChannelBuilder.java:78)
> ... 18 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18191) "Restart all required" services operation failed at Metrics Collector since HDFS was not yet up
[
https://issues.apache.org/jira/browse/AMBARI-18191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Sposetti updated AMBARI-18191:
---
Fix Version/s: 2.4.1
> "Restart all required" services operation failed at Metrics Collector since
> HDFS was not yet up
> ---
>
> Key: AMBARI-18191
> URL: https://issues.apache.org/jira/browse/AMBARI-18191
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Sunitha
>Assignee: Siddharth Wagle
>Priority: Blocker
> Fix For: trunk, 2.4.1
>
> Attachments: AMBARI-18191.patch
>
>
> ambari-server --hash
> 4017036da951a10f519a578de934308cf866ba50
> *Steps*
> # Deploy HDP-2.3.6 cluster with Ambari 2.2.2.0 (AMS is configured in
> distributed mode)
> # Upgrade Ambari to 2.4.0.0 and let it complete
> # Open Ambari web UI and hit "Restart all required" under Actions menu
> *Result*
> The operation fails while trying to restart Metrics Collector as it tried to
> make a WebHDFS call while HDFS was not started:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
> line 148, in
> AmsCollector().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 725, in restart
> self.start(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
> line 46, in start
> self.configure(env, action = 'start') # for security
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
> line 41, in configure
> hbase('master', action)
> 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/hbase.py",
> line 213, in hbase
> dfs_type=params.dfs_type
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 459, in action_create_on_execute
> self.action_delayed("create")
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 456, in action_delayed
> self.get_hdfs_resource_executor().action_delayed(action_name, self)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 256, in action_delayed
> self._set_mode(self.target_status)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 363, in _set_mode
> self.util.run_command(self.main_resource.resource.target,
> 'SETPERMISSION', method='PUT', permission=self.mode, assertable_result=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 179, in run_command
> _, out, err = get_user_call_output(cmd, user=self.run_user,
> logoutput=self.logoutput, quiet=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_user_call_output.py",
> line 61, in get_user_call_output
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'curl -sS -L -w
> '%{http_code}' -X PUT --negotiate -u :
> 'http://vsharma-eu-mt-5.openstacklocal:50070/webhdfs/v1/user/ams/hbase?op=SETPERMISSION=hdfs=775'
> 1>/tmp/tmp8twcZt 2>/tmp/tmpLPih9a' returned 7. curl: (7) couldn't connect to
> host
> 401
> {code}
> Afterwards, restarted HDFS individually first and then hit "Restart all
> Required" - the operation was successful
> Looks like the issue is because the order of restart is incorrect across the
> hosts, hence the dependent services don't come up upfront
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18343) Ambari server start fails after upgrade due to missing krb5JAASLogin.conf file on WireEncrypted cluster
Andrew Onischuk created AMBARI-18343: Summary: Ambari server start fails after upgrade due to missing krb5JAASLogin.conf file on WireEncrypted cluster Key: AMBARI-18343 URL: https://issues.apache.org/jira/browse/AMBARI-18343 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.4.1 Attachments: AMBARI-18343.patch Ambari server host: 172.22.87.56 ambari-server --hash 6aa22480916d8497d6db077f1d8e744a9c8f73f8 Build # ambari-server-2.4.1.0-10 **Steps** 1. Deploy HDP-242 cluster with Ambari 2.2.2.0 (secure, non-HA cluster, Ambari server https enabled) 2. Enable Wire Encryption on the cluster 3. Upgrade Ambari to 2.4.1.0 and later start ambari-server **Result** Start failed with below error in logs: 07 Sep 2016 14:26:55,594 INFO [main] ActionDefinitionManager:130 - Added custom action definition for ru_execute_tasks 07 Sep 2016 14:26:55,619 INFO [main] CertificateManager:69 - Initialization of root certificate 07 Sep 2016 14:26:55,619 INFO [main] CertificateManager:71 - Certificate exists:true 07 Sep 2016 14:26:55,619 INFO [main] KerberosChecker:57 - Checking Ambari Server Kerberos credentials. 07 Sep 2016 14:26:55,625 ERROR [main] AmbariServer:927 - Failed to run the Ambari Server java.lang.SecurityException: /etc/ambari-server/conf/krb5JAASLogin.conf (No such file or directory) at com.sun.security.auth.login.ConfigFile.(ConfigFile.java:110) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at java.lang.Class.newInstance(Class.java:374) at javax.security.auth.login.Configuration$2.run(Configuration.java:258) at javax.security.auth.login.Configuration$2.run(Configuration.java:250) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.login.Configuration.getConfiguration(Configuration.java:249) at org.apache.ambari.server.controller.utilities.KerberosChecker.checkJaasConfiguration(KerberosChecker.java:61) at org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:922) Caused by: java.io.IOException: /etc/ambari-server/conf/krb5JAASLogin.conf (No such file or directory) at com.sun.security.auth.login.ConfigFile.init(ConfigFile.java:212) at com.sun.security.auth.login.ConfigFile.(ConfigFile.java:108) ... 11 more 07 Sep 2016 14:26:55,900 INFO [Stack Version Loading Thread] LatestRepoCallable:219 - Stack HDP-2.3 cannot resolve OS debian6 to the supported ones: redhat6,redhat7,suse11,ubuntu14,debian7,ubuntu12. Family: null 07 Sep 2016 14:26:56,120 INFO [Stack Version Loading Thread] LatestRepoCallable:80 - Loading latest URL info for stack HDP-2.4 from http://public-repo-1.hortonworks.com/HDP/hdp_urlinfo.json Checked in the directory and found the following nats11-36-juzs-dgm10toeriedwngdha-s11-5:/etc/ambari-server/conf # pwd /etc/ambari-server/conf nats11-36-juzs-dgm10toeriedwngdha-s11-5:/etc/ambari-server/conf # ls -lhrt total 32K -rw-r- 1 root root 13 Sep 7 10:20 password.dat -rw-r--r-- 1 root root 300 Sep 7 11:25 krb5JAASLogin.conf.rpmsave -rw-r--r-- 1 root root 5.0K Sep 7 12:13 ambari.properties.rpmsave.20160907141713 -rw-r--r-- 1 root root 4.9K Sep 7 14:17 log4j.properties -rw-r--r-- 1 root root 7.5K Sep 7 17:53 ambari.properties Did not hit this issue in Ambari 2.4.0 timeframe, so possibly a regression -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18343) Ambari server start fails after upgrade due to missing krb5JAASLogin.conf file on WireEncrypted cluster
[ https://issues.apache.org/jira/browse/AMBARI-18343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18343: - Status: Patch Available (was: Open) > Ambari server start fails after upgrade due to missing krb5JAASLogin.conf > file on WireEncrypted cluster > --- > > Key: AMBARI-18343 > URL: https://issues.apache.org/jira/browse/AMBARI-18343 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.1 > > Attachments: AMBARI-18343.patch > > > Ambari server host: 172.22.87.56 > ambari-server --hash > 6aa22480916d8497d6db077f1d8e744a9c8f73f8 > Build # ambari-server-2.4.1.0-10 > **Steps** > 1. Deploy HDP-242 cluster with Ambari 2.2.2.0 (secure, non-HA cluster, > Ambari server https enabled) > 2. Enable Wire Encryption on the cluster > 3. Upgrade Ambari to 2.4.1.0 and later start ambari-server > **Result** > Start failed with below error in logs: > > > > 07 Sep 2016 14:26:55,594 INFO [main] ActionDefinitionManager:130 - Added > custom action definition for ru_execute_tasks > 07 Sep 2016 14:26:55,619 INFO [main] CertificateManager:69 - > Initialization of root certificate > 07 Sep 2016 14:26:55,619 INFO [main] CertificateManager:71 - Certificate > exists:true > 07 Sep 2016 14:26:55,619 INFO [main] KerberosChecker:57 - Checking > Ambari Server Kerberos credentials. > 07 Sep 2016 14:26:55,625 ERROR [main] AmbariServer:927 - Failed to run > the Ambari Server > java.lang.SecurityException: /etc/ambari-server/conf/krb5JAASLogin.conf > (No such file or directory) > at > com.sun.security.auth.login.ConfigFile.(ConfigFile.java:110) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) > at java.lang.Class.newInstance(Class.java:374) > at > javax.security.auth.login.Configuration$2.run(Configuration.java:258) > at > javax.security.auth.login.Configuration$2.run(Configuration.java:250) > at java.security.AccessController.doPrivileged(Native Method) > at > javax.security.auth.login.Configuration.getConfiguration(Configuration.java:249) > at > org.apache.ambari.server.controller.utilities.KerberosChecker.checkJaasConfiguration(KerberosChecker.java:61) > at > org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:922) > Caused by: java.io.IOException: > /etc/ambari-server/conf/krb5JAASLogin.conf (No such file or directory) > at > com.sun.security.auth.login.ConfigFile.init(ConfigFile.java:212) > at > com.sun.security.auth.login.ConfigFile.(ConfigFile.java:108) > ... 11 more > 07 Sep 2016 14:26:55,900 INFO [Stack Version Loading Thread] > LatestRepoCallable:219 - Stack HDP-2.3 cannot resolve OS debian6 to the > supported ones: redhat6,redhat7,suse11,ubuntu14,debian7,ubuntu12. Family: null > 07 Sep 2016 14:26:56,120 INFO [Stack Version Loading Thread] > LatestRepoCallable:80 - Loading latest URL info for stack HDP-2.4 from > http://public-repo-1.hortonworks.com/HDP/hdp_urlinfo.json > > Checked in the directory and found the following > > > > nats11-36-juzs-dgm10toeriedwngdha-s11-5:/etc/ambari-server/conf # pwd > /etc/ambari-server/conf > nats11-36-juzs-dgm10toeriedwngdha-s11-5:/etc/ambari-server/conf # ls -lhrt > total 32K > -rw-r- 1 root root 13 Sep 7 10:20 password.dat > -rw-r--r-- 1 root root 300 Sep 7 11:25 krb5JAASLogin.conf.rpmsave > -rw-r--r-- 1 root root 5.0K Sep 7 12:13 > ambari.properties.rpmsave.20160907141713 > -rw-r--r-- 1 root root 4.9K Sep 7 14:17 log4j.properties > -rw-r--r-- 1 root root 7.5K Sep 7 17:53 ambari.properties > > Did not hit this issue in Ambari 2.4.0 timeframe, so possibly a regression -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18343) Ambari server start fails after upgrade due to missing krb5JAASLogin.conf file on WireEncrypted cluster
[ https://issues.apache.org/jira/browse/AMBARI-18343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18343: - Attachment: AMBARI-18343.patch > Ambari server start fails after upgrade due to missing krb5JAASLogin.conf > file on WireEncrypted cluster > --- > > Key: AMBARI-18343 > URL: https://issues.apache.org/jira/browse/AMBARI-18343 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.1 > > Attachments: AMBARI-18343.patch > > > Ambari server host: 172.22.87.56 > ambari-server --hash > 6aa22480916d8497d6db077f1d8e744a9c8f73f8 > Build # ambari-server-2.4.1.0-10 > **Steps** > 1. Deploy HDP-242 cluster with Ambari 2.2.2.0 (secure, non-HA cluster, > Ambari server https enabled) > 2. Enable Wire Encryption on the cluster > 3. Upgrade Ambari to 2.4.1.0 and later start ambari-server > **Result** > Start failed with below error in logs: > > > > 07 Sep 2016 14:26:55,594 INFO [main] ActionDefinitionManager:130 - Added > custom action definition for ru_execute_tasks > 07 Sep 2016 14:26:55,619 INFO [main] CertificateManager:69 - > Initialization of root certificate > 07 Sep 2016 14:26:55,619 INFO [main] CertificateManager:71 - Certificate > exists:true > 07 Sep 2016 14:26:55,619 INFO [main] KerberosChecker:57 - Checking > Ambari Server Kerberos credentials. > 07 Sep 2016 14:26:55,625 ERROR [main] AmbariServer:927 - Failed to run > the Ambari Server > java.lang.SecurityException: /etc/ambari-server/conf/krb5JAASLogin.conf > (No such file or directory) > at > com.sun.security.auth.login.ConfigFile.(ConfigFile.java:110) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) > at java.lang.Class.newInstance(Class.java:374) > at > javax.security.auth.login.Configuration$2.run(Configuration.java:258) > at > javax.security.auth.login.Configuration$2.run(Configuration.java:250) > at java.security.AccessController.doPrivileged(Native Method) > at > javax.security.auth.login.Configuration.getConfiguration(Configuration.java:249) > at > org.apache.ambari.server.controller.utilities.KerberosChecker.checkJaasConfiguration(KerberosChecker.java:61) > at > org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:922) > Caused by: java.io.IOException: > /etc/ambari-server/conf/krb5JAASLogin.conf (No such file or directory) > at > com.sun.security.auth.login.ConfigFile.init(ConfigFile.java:212) > at > com.sun.security.auth.login.ConfigFile.(ConfigFile.java:108) > ... 11 more > 07 Sep 2016 14:26:55,900 INFO [Stack Version Loading Thread] > LatestRepoCallable:219 - Stack HDP-2.3 cannot resolve OS debian6 to the > supported ones: redhat6,redhat7,suse11,ubuntu14,debian7,ubuntu12. Family: null > 07 Sep 2016 14:26:56,120 INFO [Stack Version Loading Thread] > LatestRepoCallable:80 - Loading latest URL info for stack HDP-2.4 from > http://public-repo-1.hortonworks.com/HDP/hdp_urlinfo.json > > Checked in the directory and found the following > > > > nats11-36-juzs-dgm10toeriedwngdha-s11-5:/etc/ambari-server/conf # pwd > /etc/ambari-server/conf > nats11-36-juzs-dgm10toeriedwngdha-s11-5:/etc/ambari-server/conf # ls -lhrt > total 32K > -rw-r- 1 root root 13 Sep 7 10:20 password.dat > -rw-r--r-- 1 root root 300 Sep 7 11:25 krb5JAASLogin.conf.rpmsave > -rw-r--r-- 1 root root 5.0K Sep 7 12:13 > ambari.properties.rpmsave.20160907141713 > -rw-r--r-- 1 root root 4.9K Sep 7 14:17 log4j.properties > -rw-r--r-- 1 root root 7.5K Sep 7 17:53 ambari.properties > > Did not hit this issue in Ambari 2.4.0 timeframe, so possibly a regression -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18339) Persist UI console errors from Admin View
[
https://issues.apache.org/jira/browse/AMBARI-18339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15474486#comment-15474486
]
Hudson commented on AMBARI-18339:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5638 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5638/])
AMBARI-18339. Persist UI console errors from Admin View. (alexantonenko)
(hiveww:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4e4f67ae87778ab487c766be9476e7a4445276ff])
* (add)
ambari-admin/src/main/resources/ui/admin-web/test/unit/services/Utility_test.js
* (edit)
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/mainCtrl.js
* (edit)
ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Utility.js
* (edit)
ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/PermissionLoader.js
* (edit) ambari-web/app/controllers/global/errors_handler_controller.js
* (edit)
ambari-admin/src/main/resources/ui/admin-web/test/unit/controllers/mainCtrl_test.js
* (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/app.js
> Persist UI console errors from Admin View
> -
>
> Key: AMBARI-18339
> URL: https://issues.apache.org/jira/browse/AMBARI-18339
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-18339.patch
>
>
> Errors thrown to browser console in {{ambari-admin}} should be persisted like
> it's implemented for {{ambari-web}}. That should be an improvement for
> investigation of UI issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18331) JMX metric retrieval method may unnecessarily refresh metrics at a high rate
[ https://issues.apache.org/jira/browse/AMBARI-18331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15474488#comment-15474488 ] Hudson commented on AMBARI-18331: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5638 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5638/]) AMBARI-18331 - JMX metric retrieval method may unnecessarily refresh (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8efbde8fd13be4278017345a4077bebb6f4f366e]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/RestMetricsPropertyProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/jmx/JMXPropertyProvider.java * (edit) ambari-server/docs/configuration/index.md * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/RestMetricsPropertyProvider.java * (add) ambari-server/src/test/java/org/apache/ambari/server/state/services/MetricsRetrievalServiceTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/JMXPropertyProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/services/MetricsRetrievalService.java > JMX metric retrieval method may unnecessarily refresh metrics at a high rate > > > Key: AMBARI-18331 > URL: https://issues.apache.org/jira/browse/AMBARI-18331 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley > Fix For: trunk > > Attachments: AMBARI-18331.patch > > > In AMBARI-16913 we revised the JMX retrieval method to maintain an internal > state of JMX metrics, with the retrieval taking place out of band of the > actual jetty query requiring the metric. However, each query will still > generate a refresh request to the metric, regardless of it's current state. > Recommend setting a TTL on a given metric such as 5 seconds, and only > generate a new request for the metric if a TTL has expired, to avoid large > amounts of repeat metrics collections in short windows. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18325) Ambari cannot install HDP from mirror list
[ https://issues.apache.org/jira/browse/AMBARI-18325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-18325: Resolution: Fixed Status: Resolved (was: Patch Available) Committed To https://git-wip-us.apache.org/repos/asf/ambari.git f0e022d..26b4299 trunk -> trunk > Ambari cannot install HDP from mirror list > -- > > Key: AMBARI-18325 > URL: https://issues.apache.org/jira/browse/AMBARI-18325 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko > Fix For: trunk > > Attachments: AMBARI-18325.patch > > > Ambari should update the code and be able to use a mirror list instead of a > single url. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18290) Ambari does not support HBase on HTTPS mode
[ https://issues.apache.org/jira/browse/AMBARI-18290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-18290: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk. > Ambari does not support HBase on HTTPS mode > --- > > Key: AMBARI-18290 > URL: https://issues.apache.org/jira/browse/AMBARI-18290 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0, 2.2.2 > Environment: all >Reporter: amarnathreddy >Assignee: amarnathreddy >Priority: Critical > Attachments: 18290.txt > > > Ambari tries to talk to Hbase URL on HTTP mode even after SSL is enabled for > HBase master. There is an issue when Ambari trying to retrive HBase JMX > parameters. Because of this Ambari shows incorrect information about > Active/Standby -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18341) Need to validate behaviour and show warn message for user after hcat user was removed
[
https://issues.apache.org/jira/browse/AMBARI-18341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15474446#comment-15474446
]
Hadoop QA commented on AMBARI-18341:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12827569/AMBARI-18341.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8613//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8613//console
This message is automatically generated.
> Need to validate behaviour and show warn message for user after hcat user was
> removed
> -
>
> Key: AMBARI-18341
> URL: https://issues.apache.org/jira/browse/AMBARI-18341
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-18341.patch
>
>
> We should validate behaviour for few basic scenarious and show warn message
> for user about potential problems.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18342) Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain)
[
https://issues.apache.org/jira/browse/AMBARI-18342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-18342:
---
Attachment: rb51733.patch
> Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain)
> -
>
> Key: AMBARI-18342
> URL: https://issues.apache.org/jira/browse/AMBARI-18342
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 3.0.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: rb51733.patch
>
>
> Unit test failure in ambari-agent because of AMBARI-18299:
> {code}
> FAIL: test_update_open_files_ulimit (TestMain.TestMain)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-agent/src/test/python/ambari_agent/TestMain.py",
> line 137, in test_update_open_files_ulimit
> self.assertEquals(hard_limit, open_files_ulimit)
> AssertionError: 6 != 10240
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-18291) Ambari tempory path configuration
[ https://issues.apache.org/jira/browse/AMBARI-18291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] amarnathreddy resolved AMBARI-18291. Resolution: Fixed Fix Version/s: 2.4.0 This is already available in 2.4.0 , hence marking it as fixed > Ambari tempory path configuration > - > > Key: AMBARI-18291 > URL: https://issues.apache.org/jira/browse/AMBARI-18291 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 > Environment: all >Reporter: amarnathreddy >Assignee: amarnathreddy >Priority: Trivial > Fix For: 2.4.0 > > > By default Ambari uses "/tmp" as temporary path, > 1. while using Ambari-server it creates so many temporary files under /tmp > path. > 2. While doing the file upload in the File View, Ambari uses /tmp path during > the file upload and if there is no enough space left then file upload would > fail. > Proposing solution: > path should be configurable in ambari.properties -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18291) Ambari tempory path configuration
[ https://issues.apache.org/jira/browse/AMBARI-18291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15474425#comment-15474425 ] amarnathreddy commented on AMBARI-18291: This bug is already fixed in Ambari2.4.0 , hence closing this. > Ambari tempory path configuration > - > > Key: AMBARI-18291 > URL: https://issues.apache.org/jira/browse/AMBARI-18291 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 > Environment: all >Reporter: amarnathreddy >Assignee: amarnathreddy >Priority: Trivial > > By default Ambari uses "/tmp" as temporary path, > 1. while using Ambari-server it creates so many temporary files under /tmp > path. > 2. While doing the file upload in the File View, Ambari uses /tmp path during > the file upload and if there is no enough space left then file upload would > fail. > Proposing solution: > path should be configurable in ambari.properties -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18291) Ambari tempory path configuration
[ https://issues.apache.org/jira/browse/AMBARI-18291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] amarnathreddy updated AMBARI-18291: --- Affects Version/s: (was: 2.4.0) > Ambari tempory path configuration > - > > Key: AMBARI-18291 > URL: https://issues.apache.org/jira/browse/AMBARI-18291 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 > Environment: all >Reporter: amarnathreddy >Assignee: amarnathreddy >Priority: Trivial > > By default Ambari uses "/tmp" as temporary path, > 1. while using Ambari-server it creates so many temporary files under /tmp > path. > 2. While doing the file upload in the File View, Ambari uses /tmp path during > the file upload and if there is no enough space left then file upload would > fail. > Proposing solution: > path should be configurable in ambari.properties -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18324) Externalize skip repo url check to ambari.properties instead of hardcoding it in Ambari Java code
[ https://issues.apache.org/jira/browse/AMBARI-18324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-18324: --- Status: Open (was: Patch Available) > Externalize skip repo url check to ambari.properties instead of hardcoding it > in Ambari Java code > - > > Key: AMBARI-18324 > URL: https://issues.apache.org/jira/browse/AMBARI-18324 > Project: Ambari > Issue Type: Bug > Components: ambari-trunk >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-18324.patch, AMBARI-18324_rebase.patch > > > Externalize skip repo url check to ambari.properties instead of hardcoding it > in Ambari Java code, so that users can define what repo ids to skip repo urls > validation when adding repos for the given stack -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18324) Externalize skip repo url check to ambari.properties instead of hardcoding it in Ambari Java code
[ https://issues.apache.org/jira/browse/AMBARI-18324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-18324: --- Attachment: AMBARI-18324_rebase.patch > Externalize skip repo url check to ambari.properties instead of hardcoding it > in Ambari Java code > - > > Key: AMBARI-18324 > URL: https://issues.apache.org/jira/browse/AMBARI-18324 > Project: Ambari > Issue Type: Bug > Components: ambari-trunk >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-18324.patch, AMBARI-18324_rebase.patch > > > Externalize skip repo url check to ambari.properties instead of hardcoding it > in Ambari Java code, so that users can define what repo ids to skip repo urls > validation when adding repos for the given stack -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18324) Externalize skip repo url check to ambari.properties instead of hardcoding it in Ambari Java code
[ https://issues.apache.org/jira/browse/AMBARI-18324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-18324: --- Status: Patch Available (was: Open) > Externalize skip repo url check to ambari.properties instead of hardcoding it > in Ambari Java code > - > > Key: AMBARI-18324 > URL: https://issues.apache.org/jira/browse/AMBARI-18324 > Project: Ambari > Issue Type: Bug > Components: ambari-trunk >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-18324.patch, AMBARI-18324_rebase.patch > > > Externalize skip repo url check to ambari.properties instead of hardcoding it > in Ambari Java code, so that users can define what repo ids to skip repo urls > validation when adding repos for the given stack -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16219) Agent computes the DAG due to RCO and executes
[ https://issues.apache.org/jira/browse/AMBARI-16219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-16219: -- Fix Version/s: (was: 2.4.2) 3.0.0 > Agent computes the DAG due to RCO and executes > -- > > Key: AMBARI-16219 > URL: https://issues.apache.org/jira/browse/AMBARI-16219 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sebastian Toader > Fix For: 3.0.0 > > > Make agents independent of servers where server can send all the details of > all the commands one-shot and the agents compute the DAG and execute the > command without any further coordination from the server. At least for > initial start, this can reduce the time taken significantly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16221) AMS/LogSearch service should be outside the cluster and shared across clusters
[ https://issues.apache.org/jira/browse/AMBARI-16221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-16221: -- Fix Version/s: (was: 2.4.2) 3.0.0 > AMS/LogSearch service should be outside the cluster and shared across clusters > -- > > Key: AMBARI-16221 > URL: https://issues.apache.org/jira/browse/AMBARI-16221 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sebastian Toader > Fix For: 3.0.0 > > > AMS and LogSearch can be shared services that is shared across clusters. > Cluster deployments can simply deploy the agents (AMS Monitor, Sinks, and Log > Feeders) that can communicate with shared services. In some ways, logs are > already being collected by log4j sinks and syslog handlers. Metrics should > also be collected in the same way by a shared service and made accessible to > the user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16213) Initial Start All should be similar to a later Start All
[ https://issues.apache.org/jira/browse/AMBARI-16213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-16213: -- Fix Version/s: (was: 2.4.2) 3.0.0 > Initial Start All should be similar to a later Start All > > > Key: AMBARI-16213 > URL: https://issues.apache.org/jira/browse/AMBARI-16213 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sebastian Toader > Fix For: 3.0.0 > > > Starting a cluster in a pre-provisioned environment should need minimal setup > activities. So first start should not be different than any start from a > full-stop. Of course, it is not. Typical differences are: > * Files and folders do not exist and are created (config files, log folders, > etc.) > * Several services perform initialization - AMS/HDFS/OOZIE > Investigate what operations from the initial Start-All that can be moved to > sys-provisioning step and what can be optimized in general. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18342) Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain)
[
https://issues.apache.org/jira/browse/AMBARI-18342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-18342:
---
Status: Patch Available (was: Open)
> Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain)
> -
>
> Key: AMBARI-18342
> URL: https://issues.apache.org/jira/browse/AMBARI-18342
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 3.0.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: rb51733.patch
>
>
> Unit test failure in ambari-agent because of AMBARI-18299:
> {code}
> FAIL: test_update_open_files_ulimit (TestMain.TestMain)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-agent/src/test/python/ambari_agent/TestMain.py",
> line 137, in test_update_open_files_ulimit
> self.assertEquals(hard_limit, open_files_ulimit)
> AssertionError: 6 != 10240
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16218) Identify Starts (e.g. NN/Oozie) that are the longest and optimize work done during start
[ https://issues.apache.org/jira/browse/AMBARI-16218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-16218: -- Fix Version/s: (was: 2.4.2) 2.5.0 > Identify Starts (e.g. NN/Oozie) that are the longest and optimize work done > during start > > > Key: AMBARI-16218 > URL: https://issues.apache.org/jira/browse/AMBARI-16218 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sebastian Toader > Fix For: 2.5.0 > > > There are some components that take longer to start than the other. Identify > the long-poles and optimize the start. Candidates are NameNode and Oozie. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16215) Ambari starts the right component when multi instances are deployed (e.g. AMS)
[ https://issues.apache.org/jira/browse/AMBARI-16215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-16215: -- Fix Version/s: (was: 2.4.2) 3.0.0 > Ambari starts the right component when multi instances are deployed (e.g. AMS) > -- > > Key: AMBARI-16215 > URL: https://issues.apache.org/jira/browse/AMBARI-16215 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sebastian Toader > Fix For: 3.0.0 > > > Currently, components that are HA through externally managed failover are > deployed with the desired state INSTALLED - AMS Collector and JHS/ATS. Ambari > can auto-start them on a specific host during the deployment if it is > possible to guarantee that for the duration of initial cluster deployment the > host is always available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16226) Execute topology tasks in parallel by hosts.
[ https://issues.apache.org/jira/browse/AMBARI-16226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-16226: -- Fix Version/s: (was: 2.4.2) 3.0.0 > Execute topology tasks in parallel by hosts. > > > Key: AMBARI-16226 > URL: https://issues.apache.org/jira/browse/AMBARI-16226 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sebastian Toader > Fix For: 3.0.0 > > > Currently a when a cluster is created using Blueprints > PersistHostResourcesTask, RegisterWithConfigGroupTask, InstallHostTask and > StartHostTask topology tasks are created for each host in this order. These > tasks than are executed by a single threaded executor > TopologyManager.executor as hosts are being assigned to the cluster. > Since TopologyManager is singleton this will leads to sequential execution of > topology tasks on a single thread. The execution of the each individual > topology tasks involves db operations under the hood. If for any reason there > is some latency introduced by the db operations (e.g. the db server is not > local but a remote one is used) than this latency builds up a considerable > delay if there are many hosts to execute topology tasks for. > Executing the topology tasks in parallel will reduce the delay in this case. > Since topology tasks for a host must be executed in order only tasks that > belong to different hosts. E.g. the PersistHostResourcesTask, > RegisterWithConfigGroupTask, InstallHostTask and StartHostTask topology tasks > would be executed sequentially by one thread for host1 and by another thread > for host2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18342) Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain)
Nahappan Somasundaram created AMBARI-18342:
--
Summary: Unit Tests failure: test_update_open_files_ulimit
(TestMain.TestMain)
Key: AMBARI-18342
URL: https://issues.apache.org/jira/browse/AMBARI-18342
Project: Ambari
Issue Type: Bug
Components: ambari-agent
Affects Versions: 3.0.0
Reporter: Nahappan Somasundaram
Assignee: Nahappan Somasundaram
Priority: Critical
Fix For: 3.0.0
Unit test failure in ambari-agent because of AMBARI-18299:
{code}
FAIL: test_update_open_files_ulimit (TestMain.TestMain)
--
Traceback (most recent call last):
File
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-agent/src/test/python/ambari_agent/TestMain.py",
line 137, in test_update_open_files_ulimit
self.assertEquals(hard_limit, open_files_ulimit)
AssertionError: 6 != 10240
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18323) Cluster creation complete is missing from ambari-server log
[ https://issues.apache.org/jira/browse/AMBARI-18323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-18323: -- Fix Version/s: (was: 2.5.0) trunk > Cluster creation complete is missing from ambari-server log > --- > > Key: AMBARI-18323 > URL: https://issues.apache.org/jira/browse/AMBARI-18323 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: trunk > > > In case provision_action is set to INSTALL_ONLY on a given hostgroup compoent > in Blueprint, cluster completion message is not logged. Normally during > Blueprint deployments Ambari creates LogicalTasks bounded later to INSTALL > tasks (HostRoleCommand), however in this case there are no INSTALL task > bounded to LogicalTasks, so they will never complete. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18285) Ambari upgrade from 2.4.0.x version fails.
[ https://issues.apache.org/jira/browse/AMBARI-18285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18285: --- Priority: Blocker (was: Major) > Ambari upgrade from 2.4.0.x version fails. > --- > > Key: AMBARI-18285 > URL: https://issues.apache.org/jira/browse/AMBARI-18285 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.1 >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Blocker > Fix For: 2.4.1 > > Attachments: AMBARI-18285.patch > > > > nat-s11-4-aiws-1226-5:~ # ambari-server upgrade -v > Using python /usr/bin/python > Upgrading ambari-server > Updating properties in ambari.properties ... > WARNING: Can not find ambari.properties.rpmsave file from previous > version, skipping import of settings > INFO: Can not find ambari-env.sh.rpmsave file from previous version, > skipping restore of environment settings. ambari-env.sh may not include any > user customization. > INFO: Loading properties from /etc/ambari-server/conf/ambari.properties > INFO: Loading properties from /etc/ambari-server/conf/ambari.properties > INFO: No mpack replay logs found. Skipping replaying mpack commands > INFO: Loading properties from /etc/ambari-server/conf/ambari.properties > INFO: Loading properties from /etc/ambari-server/conf/ambari.properties > Fixing database objects owner > INFO: Loading properties from /etc/ambari-server/conf/ambari.properties > INFO: about to run command: ['ambari-sudo.sh', 'su', 'postgres', '-', > '--command=/var/lib/ambari-server/resources/scripts/change_owner.sh -d ambari > -s ambari -o \'"ambari"\''] > INFO: Fixed database objects owner > INFO: Loading properties from /etc/ambari-server/conf/ambari.properties > Traceback (most recent call last): > File "/usr/sbin/ambari-server.py", line 754, in > mainBody() > File "/usr/sbin/ambari-server.py", line 725, in mainBody > main(options, args, parser) > File "/usr/sbin/ambari-server.py", line 678, in main > action_obj.execute() > File "/usr/sbin/ambari-server.py", line 69, in execute > self.fn(*self.args, **self.kwargs) > File "/usr/lib/python2.6/site-packages/ambari_server/serverUpgrade.py", > line 370, in upgrade > retcode = run_schema_upgrade(args) > File "/usr/lib/python2.6/site-packages/ambari_server/serverUpgrade.py", > line 249, in run_schema_upgrade > db_title = get_db_type(get_ambari_properties()).title > AttributeError: 'NoneType' object has no attribute 'title' > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18316) Ambari upgrade to Ambari 2.4.0 failed during DB upgrade due to incorrect TEZ view regex
[
https://issues.apache.org/jira/browse/AMBARI-18316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-18316:
---
Priority: Blocker (was: Major)
> Ambari upgrade to Ambari 2.4.0 failed during DB upgrade due to incorrect TEZ
> view regex
> ---
>
> Key: AMBARI-18316
> URL: https://issues.apache.org/jira/browse/AMBARI-18316
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
>Priority: Blocker
> Fix For: 2.4.1
>
> Attachments: AMBARI-18316.branch-2.4.patch
>
>
> Ambari upgrade to Ambari 2.4.0 failed during DB upgrade due to incorrect TEZ
> view regular expression.
> *Steps to Reproduce*
> # Install Ambari 2.2.0
> # Install cluster with TEZ
> # Change {{tez-site/tez.tez-ui.history-url.base}} from something like
> {{http://c6501.ambari.apache.org:8080/#/main/views/TEZ/0.7.0.2.3.4.0-460/TEZ_CLUSTER_INSTANCE}}
> to
> {{http://c6501.ambari.apache.org:8080/#/main/views/TEZ/0.7.0.2.3.4.0-460/tezv1}}
>
> ** Notice "TEZ_CLUSTER_INSTANCE" was changed to "tezv1"
> # Upgrade Ambari to 2.4.0.1
> # Execute {{ambari-server upgrade}}
> # See error
> {noformat}
> Using python /usr/bin/python
> Upgrading ambari-server
> Updating properties in ambari.properties ...
> WARNING: Original file ambari-env.sh kept
> Fixing database objects owner
> Ambari Server configured for Embedded Postgres. Confirm you have made a
> backup of the Ambari Server database [y/n] (y)? y
> Upgrading database schema
> Error output from schema upgrade command:
> Exception in thread "main" org.apache.ambari.server.AmbariException: Cannot
> prepare the new value for property: 'tez.tez-ui.history-url.base' using the
> old value:
> 'https://c6501.ambari.apache.org:8080/#/main/views/TEZ/0.7.0.2.3.4.0-460/tezv1;
>
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
>
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:353)
>
> Caused by: org.apache.ambari.server.AmbariException: Cannot prepare the new
> value for property: 'tez.tez-ui.history-url.base' using the old value:
> 'https://c6501.ambari.apache.org:8080/#/main/views/TEZ/0.7.0.2.3.4.0-460/tezv1;
>
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.getUpdatedTezHistoryUrlBase(AbstractUpgradeCatalog.java:951)
>
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.updateTezHistoryUrlBase(AbstractUpgradeCatalog.java:923)
>
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:900)
>
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:234)
>
> ... 1 more
> {noformat}
> *Cause*
> The cause for this error is in the regular expression below:
> {code:title=At or around
> org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java:986}
> String pattern = "(.*\\/TEZ\\/)(.*)(\\/TEZ_CLUSTER_INSTANCE)";
> {code}
> This pattern assumes the URL will end with "TEZ_CLUSTER_INSTANCE", however
> this may be changed by the user causing a failure when matching and yielding
> an exception being thrown.
> *Workaround*
> If the Ambari server package has not yet been upgraded
> # Edit the {{tez-site/tez.tez-ui.history-url.base}} config to match the
> pattern
> # Perform the upgrade
> # Edit the {{tez-site/tez.tez-ui.history-url.base}} config to fix the URL as
> needed
> If the Ambari server package has been upgraded
> # If {{ambari-server upgrade}} has been executed and failed, restore the
> database
> # Using some database access utility (example, Toad), edit the
> {{config_data}} column of the {{clusterconfig}} table for the record that
> represents the _desired_ version of the {{tez-site}} config to match the
> pattern
> # Perform the upgrade
> # Edit the {{tez-site/tez.tez-ui.history-url.base}} config to fix the URL as
> needed
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18294) Ambari Server Start/Stop fails on Centos 7.1+
[ https://issues.apache.org/jira/browse/AMBARI-18294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18294: --- Priority: Blocker (was: Major) > Ambari Server Start/Stop fails on Centos 7.1+ > - > > Key: AMBARI-18294 > URL: https://issues.apache.org/jira/browse/AMBARI-18294 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Blocker > Fix For: 2.4.1 > > Attachments: AMBARI-18294.patch > > > Brand new install on Centos 7.2 > Ambari Server 'setup' completed successfully. > [root@c7001 ~]# ambari-server start > Using python /usr/bin/python > Starting ambari-server > Ambari Server running with administrator privileges. > Organizing resource files at /var/lib/ambari-server/resources... > Ambari database consistency check started... > No errors were found. > Ambari database consistency check finished > Server PID at: /var/run/ambari-server/ambari-server.pid > Server out at: /var/log/ambari-server/ambari-server.out > Server log at: /var/log/ambari-server/ambari-server.log > Waiting for server start > Ambari Server 'start' completed successfully. > [root@c7001 ~]# cat /var/run/ambari-server/ambari-server.pid > 12302 > 12303 > [root@c7001 ~]# ps aux | grep AmbariServer > root 12302 0.0 0.0 113116 644 pts/0S20:42 0:00 /bin/sh -c > ulimit -n 1 ; /usr/jdk64/jdk1.8.0_77/bin/java -server -XX:NewRatio=3 > -XX:+UseConcMarkSweepGC -XX:-UseGCOverheadLimit > -XX:CMSInitiatingOccupancyFraction=60 -XX:+CMSClassUnloadingEnabled > -Dsun.zip.disableMemoryMapping=true -Xms512m -Xmx2048m -XX:MaxPermSize=128m > -Djava.security.auth.login.config=$ROOT/etc/ambari-server/conf/krb5JAASLogin.conf > -Djava.security.krb5.conf=/etc/krb5.conf > -Djavax.security.auth.useSubjectCredsOnly=false -cp > '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/postgresql-jdbc.jar' > org.apache.ambari.server.controller.AmbariServer > > /var/log/ambari-server/ambari-server.out 2>&1 || echo $? > > /var/run/ambari-server/ambari-server.exitcode & > root 12303 87.7 14.8 4377224 431856 pts/0 Sl 20:42 0:29 > /usr/jdk64/jdk1.8.0_77/bin/java -server -XX:NewRatio=3 > -XX:+UseConcMarkSweepGC -XX:-UseGCOverheadLimit > -XX:CMSInitiatingOccupancyFraction=60 -XX:+CMSClassUnloadingEnabled > -Dsun.zip.disableMemoryMapping=true -Xms512m -Xmx2048m -XX:MaxPermSize=128m > -Djava.security.auth.login.config=/etc/ambari-server/conf/krb5JAASLogin.conf > -Djava.security.krb5.conf=/etc/krb5.conf > -Djavax.security.auth.useSubjectCredsOnly=false -cp > /etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/postgresql-jdbc.jar > org.apache.ambari.server.controller.AmbariServer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18335) After upgrading cluster from HDP-2.4.x to HDP-2.5.x and added atlas service - missing kafka security properties
[ https://issues.apache.org/jira/browse/AMBARI-18335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18335: --- Fix Version/s: (was: 2.4.1) 2.4.2 > After upgrading cluster from HDP-2.4.x to HDP-2.5.x and added atlas service - > missing kafka security properties > --- > > Key: AMBARI-18335 > URL: https://issues.apache.org/jira/browse/AMBARI-18335 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Robert Levas >Assignee: Robert Levas > Labels: kerberos_descriptor, upgrade > Fix For: 2.4.2 > > Attachments: AMBARI-18335_branch-2.4_01.patch, > AMBARI-18335_branch-2.4_02.patch, AMBARI-18335_trunk_01.patch, > AMBARI-18335_trunk_02.patch > > > Steps to repro: > * Install Ambari 2.2.2 > * Install HDP-2.4.x cluster with Atlas > * Stop Atlas > * Upgrade Ambari to 2.4 > * Delete Atlas service > * Upgrade the cluster to HDP-2.5.x cluster > * Add Atlas service. > *Below config properties are missing from atlas-applicataion.properties file > for Atlas, Storm, Falcon, Hive services.* > #atlas.jaas.KafkaClient.option.keyTab = > /etc/security/keytabs/atlas.service.keytab > #atlas.jaas.KafkaClient.option.principal = atlas/_h...@example.com > From HDP 2.4 to 2.5, the kerberos.json file for Atlas changed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16226) Execute topology tasks in parallel by hosts.
[ https://issues.apache.org/jira/browse/AMBARI-16226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-16226: --- Fix Version/s: (was: 2.4.1) 2.4.2 > Execute topology tasks in parallel by hosts. > > > Key: AMBARI-16226 > URL: https://issues.apache.org/jira/browse/AMBARI-16226 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sebastian Toader > Fix For: 2.4.2 > > > Currently a when a cluster is created using Blueprints > PersistHostResourcesTask, RegisterWithConfigGroupTask, InstallHostTask and > StartHostTask topology tasks are created for each host in this order. These > tasks than are executed by a single threaded executor > TopologyManager.executor as hosts are being assigned to the cluster. > Since TopologyManager is singleton this will leads to sequential execution of > topology tasks on a single thread. The execution of the each individual > topology tasks involves db operations under the hood. If for any reason there > is some latency introduced by the db operations (e.g. the db server is not > local but a remote one is used) than this latency builds up a considerable > delay if there are many hosts to execute topology tasks for. > Executing the topology tasks in parallel will reduce the delay in this case. > Since topology tasks for a host must be executed in order only tasks that > belong to different hosts. E.g. the PersistHostResourcesTask, > RegisterWithConfigGroupTask, InstallHostTask and StartHostTask topology tasks > would be executed sequentially by one thread for host1 and by another thread > for host2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16218) Identify Starts (e.g. NN/Oozie) that are the longest and optimize work done during start
[ https://issues.apache.org/jira/browse/AMBARI-16218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-16218: --- Fix Version/s: (was: 2.4.1) 2.4.2 > Identify Starts (e.g. NN/Oozie) that are the longest and optimize work done > during start > > > Key: AMBARI-16218 > URL: https://issues.apache.org/jira/browse/AMBARI-16218 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sebastian Toader > Fix For: 2.4.2 > > > There are some components that take longer to start than the other. Identify > the long-poles and optimize the start. Candidates are NameNode and Oozie. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16219) Agent computes the DAG due to RCO and executes
[ https://issues.apache.org/jira/browse/AMBARI-16219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-16219: --- Fix Version/s: (was: 2.4.1) 2.4.2 > Agent computes the DAG due to RCO and executes > -- > > Key: AMBARI-16219 > URL: https://issues.apache.org/jira/browse/AMBARI-16219 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sebastian Toader > Fix For: 2.4.2 > > > Make agents independent of servers where server can send all the details of > all the commands one-shot and the agents compute the DAG and execute the > command without any further coordination from the server. At least for > initial start, this can reduce the time taken significantly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18314) Users page after LDAP sync shows blank
[ https://issues.apache.org/jira/browse/AMBARI-18314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18314: --- Fix Version/s: (was: 2.4.1) 2.4.2 > Users page after LDAP sync shows blank > -- > > Key: AMBARI-18314 > URL: https://issues.apache.org/jira/browse/AMBARI-18314 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Shreya Bhat > Fix For: 2.4.2 > > > The network shows 500 Server error -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16221) AMS/LogSearch service should be outside the cluster and shared across clusters
[ https://issues.apache.org/jira/browse/AMBARI-16221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-16221: --- Fix Version/s: (was: 2.4.1) 2.4.2 > AMS/LogSearch service should be outside the cluster and shared across clusters > -- > > Key: AMBARI-16221 > URL: https://issues.apache.org/jira/browse/AMBARI-16221 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sebastian Toader > Fix For: 2.4.2 > > > AMS and LogSearch can be shared services that is shared across clusters. > Cluster deployments can simply deploy the agents (AMS Monitor, Sinks, and Log > Feeders) that can communicate with shared services. In some ways, logs are > already being collected by log4j sinks and syslog handlers. Metrics should > also be collected in the same way by a shared service and made accessible to > the user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16215) Ambari starts the right component when multi instances are deployed (e.g. AMS)
[ https://issues.apache.org/jira/browse/AMBARI-16215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-16215: --- Fix Version/s: (was: 2.4.1) 2.4.2 > Ambari starts the right component when multi instances are deployed (e.g. AMS) > -- > > Key: AMBARI-16215 > URL: https://issues.apache.org/jira/browse/AMBARI-16215 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sebastian Toader > Fix For: 2.4.2 > > > Currently, components that are HA through externally managed failover are > deployed with the desired state INSTALLED - AMS Collector and JHS/ATS. Ambari > can auto-start them on a specific host during the deployment if it is > possible to guarantee that for the duration of initial cluster deployment the > host is always available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17285) Custom service repos in repoinfo.xml got overwritten by public VDFs
[ https://issues.apache.org/jira/browse/AMBARI-17285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-17285: --- Fix Version/s: (was: 2.4.1) 2.4.2 > Custom service repos in repoinfo.xml got overwritten by public VDFs > --- > > Key: AMBARI-17285 > URL: https://issues.apache.org/jira/browse/AMBARI-17285 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Alexander Denissov >Assignee: Nate Cole >Priority: Critical > Fix For: 2.4.2 > > > Ambari 2.4 introduced Version Definition Files that break the functionality > of adding a custom service repo, since custom services do not have an entry > in the public VDF. > In the case of HAWQ, the plugin is installed on Ambari host and it adds the > new repo information to the repoinfo.xml of all available stacks on the file > system. Once Ambari cluster creation wizard queries the latest repo info from > the public URLs, it will get the info for all stack repos, but not the custom > ones. > So, the logic should be: > 1. Use default repoinfo (from file system) as the base > 2. Query public VDF, if available > 3. For each entry in public VDF overwrite values in the default repoinfo > 4. Entries in default repoinfo that do not have corresponding entries in VDF > should stay intact > This way custom services can be added via file edit and the latest > information can still be retrieved and applied for the standard stack. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
