[
https://issues.apache.org/jira/browse/OOZIE-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fady K Sedrak updated OOZIE-2626:
---------------------------------
Description: Oozie workflow processing becomes slow after the increase of
rows in WF_JOBS and WF_ACTIONS tables when running against SQL Server. A
secondary index need to be created against WF_JOBS (created_time), WF_ACTIONS
(last_check_time & pending) to avoid going for a full table scan when querying
against these fields. (was: Oozie workflow processing becomes slow after the
increase of rows in COORD_ACTIONS and WF_ACTIONS tables when running against
SQL Server. A secondary index need to be created against COORD_ACTIONS
(last_modified_time & status), WF_ACTIONS (last_modified_time & status) to
avoid going for a full table scan when querying against these fields.)
> Oozie workflow processing becomes slow after the increase of rows in WF_JOBS
> and WF_ACTIONS tables when the metastore is running on SQL Server
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: OOZIE-2626
> URL: https://issues.apache.org/jira/browse/OOZIE-2626
> Project: Oozie
> Issue Type: Bug
> Components: coordinator, workflow
> Reporter: Fady K Sedrak
>
> Oozie workflow processing becomes slow after the increase of rows in WF_JOBS
> and WF_ACTIONS tables when running against SQL Server. A secondary index need
> to be created against WF_JOBS (created_time), WF_ACTIONS (last_check_time &
> pending) to avoid going for a full table scan when querying against these
> fields.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
