[
https://issues.apache.org/jira/browse/AMBARI-19929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15884195#comment-15884195
]
Hadoop QA commented on AMBARI-19929:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12854655/AMBARI-19929.trunk.v3.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/10754//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10754//console
This message is automatically generated.
> TopologyRequest/TopologyLogicalRequest/TopologyHostRequest database
> inconsistency
> ---------------------------------------------------------------------------------
>
> Key: AMBARI-19929
> URL: https://issues.apache.org/jira/browse/AMBARI-19929
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.1
> Reporter: amarnathreddy
> Assignee: Sebastian Toader
> Priority: Critical
> Attachments: AMBARI-19929.trunk.v3.patch
>
>
> If there is any inconsistency with topology_logical_request, topology_request
> tables then all heart beat request fails with below exception
> 10 Jan 2017 10:43:12,004 WARN [qtp-ambari-agent-137] ServletHandler:563 -
> /agent/v1/register/agent540.xxxx.com
> java.lang.NullPointerException
> some of the entries for topology_request does not have reference entry in
> topology_logical_request table.
> because of that all healthy agents are marked as heart beat lost.
> This should not happen, rather it should print the exception and process the
> heart beats.
> full stack trace:
> java.lang.NullPointerException
> at
> org.apache.ambari.server.topology.PersistedStateImpl.getAllRequests(PersistedStateImpl.java:157)
> at
> org.apache.ambari.server.topology.TopologyManager.ensureInitialized(TopologyManager.java:131)
> at
> org.apache.ambari.server.topology.TopologyManager.onHostRegistered(TopologyManager.java:315)
> at
> org.apache.ambari.server.state.host.HostImpl$HostRegistrationReceived.transition(HostImpl.java:301)
> at
> org.apache.ambari.server.state.host.HostImpl$HostRegistrationReceived.transition(HostImpl.java:266)
> at
> org.apache.ambari.server.state.fsm.StateMachineFactory$SingleInternalArc.doTransition(StateMachineFactory.java:354)
> at
> org.apache.ambari.server.state.fsm.StateMachineFactory.doTransition(StateMachineFactory.java:294)
> at
> org.apache.ambari.server.state.fsm.StateMachineFactory.access$300(StateMachineFactory.java:39)
> at
> org.apache.ambari.server.state.fsm.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:440)
> at
> org.apache.ambari.server.state.host.HostImpl.handleEvent(HostImpl.java:570)
> at
> org.apache.ambari.server.agent.HeartBeatHandler.handleRegistration(HeartBeatHandler.java:966)
> at
> org.apache.ambari.server.agent.rest.AgentResource.register(AgentResource.java:95)
> at sun.reflect.GeneratedMethodAccessor161.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> BUSINESS IMPACT: Production cluster cannot be managed through Ambari
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
