You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Fady K Sedrak (JIRA)" <ji...@apache.org> on 2016/08/05 16:10:20 UTC
[jira] [Commented] (OOZIE-2626) Oozie workflow processing becomes
slow after the increase of rows in COORD_ACTIONS and WF_ACTIONS tables when
the metastore is running on SQL Server
[ https://issues.apache.org/jira/browse/OOZIE-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15409634#comment-15409634 ]
Fady K Sedrak commented on OOZIE-2626:
--------------------------------------
Working on a patch
> Oozie workflow processing becomes slow after the increase of rows in COORD_ACTIONS 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 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)