ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-19929) TopologyRequest/TopologyLogicalRequest/TopologyHostRequest database inconsistency
Date Sat, 25 Feb 2017 11:12:44 GMT


Hadoop QA commented on AMBARI-19929:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  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
                        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:
Console output:

This message is automatically generated.

> TopologyRequest/TopologyLogicalRequest/TopologyHostRequest database inconsistency
> ---------------------------------------------------------------------------------
>                 Key: AMBARI-19929
>                 URL:
>             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/
> java.lang.NullPointerException
> some of the entries for topology_request does not have reference entry in topology_logical_request
> 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(
>         at org.apache.ambari.server.topology.TopologyManager.ensureInitialized(
>         at org.apache.ambari.server.topology.TopologyManager.onHostRegistered(
>         at$HostRegistrationReceived.transition(
>         at$HostRegistrationReceived.transition(
>         at org.apache.ambari.server.state.fsm.StateMachineFactory$SingleInternalArc.doTransition(
>         at org.apache.ambari.server.state.fsm.StateMachineFactory.doTransition(
>         at org.apache.ambari.server.state.fsm.StateMachineFactory.access$300(
>         at org.apache.ambari.server.state.fsm.StateMachineFactory$InternalStateMachine.doTransition(
>         at
>         at org.apache.ambari.server.agent.HeartBeatHandler.handleRegistration(
>         at
>         at sun.reflect.GeneratedMethodAccessor161.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(
>         at java.lang.reflect.Method.invoke(
>         at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(
>         at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(
>         at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(
>         at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(
>         at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(
>         at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(
>         at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(
>         at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(
>         at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(
>         at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(
>         at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(
>         at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(
> BUSINESS IMPACT: Production cluster cannot be managed through Ambari

This message was sent by Atlassian JIRA

View raw message