[
https://issues.apache.org/jira/browse/OOZIE-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Purshotam Shah updated OOZIE-2280:
----------------------------------
Description:
@NamedQuery(name = "GET_COORD_ACTIONS_WAITING_SUBMITTED_OLDER_THAN", query =
"select a.id, a.jobId, a.statusStr, a.externalId, a.pushMissingDependencies
from CoordinatorActionBean a where (a.statusStr = 'WAITING' OR a.statusStr =
'SUBMITTED') AND a.lastModifiedTimestamp <= :lastModifiedTime"),
1. Recovery service also queues CoordPushDependencyCheckXCommand, which doesn't
have nominal time check.
2. CoordMaterializeTransitionXCommand will queue CoordActionInputCheckXCommand,
so re-queuing by RecoveryService will not cause any issue. But it will get
queued in other host.
was:
@NamedQuery(name = "GET_COORD_ACTIONS_WAITING_SUBMITTED_OLDER_THAN", query =
"select a.id, a.jobId, a.statusStr, a.externalId, a.pushMissingDependencies
from CoordinatorActionBean a where (a.statusStr = 'WAITING' OR a.statusStr =
'SUBMITTED') AND a.lastModifiedTimestamp <= :lastModifiedTime"),
1. Recovery service also queues CoordPushDependencyCheckXCommand, which doesn't
have nominal time check.
2. CoordMaterializeTransitionXCommand will queue CoordActionInputCheckXCommand,
so re-queuing by check will not work in HA. It will get queued in other host.
> RecoveryService keeps on recovering coord action whose nominal time is not
> reached
> ----------------------------------------------------------------------------------
>
> Key: OOZIE-2280
> URL: https://issues.apache.org/jira/browse/OOZIE-2280
> Project: Oozie
> Issue Type: Bug
> Reporter: Purshotam Shah
>
> @NamedQuery(name = "GET_COORD_ACTIONS_WAITING_SUBMITTED_OLDER_THAN", query =
> "select a.id, a.jobId, a.statusStr, a.externalId, a.pushMissingDependencies
> from CoordinatorActionBean a where (a.statusStr = 'WAITING' OR a.statusStr =
> 'SUBMITTED') AND a.lastModifiedTimestamp <= :lastModifiedTime"),
> 1. Recovery service also queues CoordPushDependencyCheckXCommand, which
> doesn't have nominal time check.
> 2. CoordMaterializeTransitionXCommand will queue
> CoordActionInputCheckXCommand, so re-queuing by RecoveryService will not
> cause any issue. But it will get queued in other host.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
