ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Wagle (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-4291) To handle misfired trigger, the scheduler should start after a fixed delay
Date Tue, 14 Jan 2014 20:51:22 GMT
Siddharth Wagle created AMBARI-4291:
---------------------------------------

             Summary: To handle misfired trigger, the scheduler should start after a fixed
delay
                 Key: AMBARI-4291
                 URL: https://issues.apache.org/jira/browse/AMBARI-4291
             Project: Ambari
          Issue Type: Task
          Components: controller
    Affects Versions: 1.5.0
            Reporter: Siddharth Wagle
            Assignee: Siddharth Wagle
             Fix For: 1.5.0


*Scenario*: Schedule restart in the future and stop ambari server before schedule time and
start ambari server after scheduled time

*Stack trace*:

{code}
01:24:57,640  INFO [main] JobStoreTX:861 - Freed 0 triggers from 'acquired' / 'blocked' state.
01:24:57,647  INFO [main] JobStoreTX:968 - Handling 1 trigger(s) that missed their scheduled
fire-time.
01:24:57,684  INFO [main] JobStoreTX:871 - Recovering 0 jobs that were in-progress at the
time of the last shut-down.
01:24:57,684  INFO [main] JobStoreTX:884 - Recovery complete.
01:24:57,685  INFO [main] JobStoreTX:891 - Removed 0 'complete' triggers.
01:24:57,685  INFO [main] JobStoreTX:896 - Removed 0 stale fired job entries.
01:24:57,699  INFO [main] QuartzScheduler:575 - Scheduler ExecutionScheduler_$_NON_CLUSTERED
started.
01:24:57,699  INFO [main] AmbariServer:388 - ********* Started Scheduled Request Manager **********
01:24:58,121  INFO [qtp1845176179-23] AmbariCustomCommandExecutionHelper:166 - Received a
command execution request, clusterName=c1, serviceName=NAGIOS, request=isCommand :true, action
:null, command :RESTART, inputs :{}, targetService :NAGIOS, targetComponent :NAGIOS_SERVER,
targetHosts :[c6401.ambari.apache.org], clusterName :c1
01:24:58,139  INFO [qtp1845176179-23] RoleCommandOrder:211 - Role command order info was loaded
from classpath: jar:file:/usr/lib/ambari-server/ambari-server-1.3.0-SNAPSHOT.jar!/role_command_order.json
01:24:58,328 ERROR [Thread-21] ServiceComponentHostImpl:722 - Can't handle ServiceComponentHostEvent
event at current state, serviceComponentName=NAGIOS_SERVER, hostName=c6401.ambari.apache.org,
currentState=UNKNOWN, eventType=HOST_SVCCOMP_OP_IN_PROGRESS, event=EventType: HOST_SVCCOMP_OP_IN_PROGRESS
01:24:58,329  INFO [Thread-21] ActionScheduler:436 - Transition failed for host: c6401.ambari.apache.org,
role: NAGIOS_SERVER
org.apache.ambari.server.state.fsm.InvalidStateTransitionException: Invalid event: HOST_SVCCOMP_OP_IN_PROGRESS
at UNKNOWN
        at org.apache.ambari.server.state.fsm.StateMachineFactory.doTransition(StateMachineFactory.java:297)
        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.svccomphost.ServiceComponentHostImpl.handleEvent(ServiceComponentHostImpl.java:717)
        at com.google.inject.persist.jpa.JpaLocalTxnInterceptor.invoke(JpaLocalTxnInterceptor.java:66)
        at org.apache.ambari.server.actionmanager.ActionScheduler.scheduleHostRole(ActionScheduler.java:432)
        at org.apache.ambari.server.actionmanager.ActionScheduler.doWork(ActionScheduler.java:215)
        at org.apache.ambari.server.actionmanager.ActionScheduler.run(ActionScheduler.java:137)
        at java.lang.Thread.run(Thread.java:744)
{code}

*Reason*: Agent heartbeats have not updated the host component statuses.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message