[
https://issues.apache.org/jira/browse/OOZIE-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13694576#comment-13694576
]
Ryota Egashira commented on OOZIE-1398:
---------------------------------------
thanks for pointing this out. we need code change to parametrize "2000" part,
which supposed to use max of oozie.action.max.output.data, and 2K, created
OOZIE-1437
also about this limit, some users at Y! asking for more than 2K for
oozie.action.max.output.data. their use case is to identify list of input files
to process in one action, and pass the list to next action(like pig) which
actually consume these input files, when so many files to process, it easily
exceeds 2K. so I strongly agree with Virag's idea to introduce compression on
this.
> [Scale] Reduce the number of CLOB columns used
> ----------------------------------------------
>
> Key: OOZIE-1398
> URL: https://issues.apache.org/jira/browse/OOZIE-1398
> Project: Oozie
> Issue Type: Improvement
> Affects Versions: trunk, 3.3.2
> Reporter: Rohini Palaniswamy
> Assignee: Ryota Egashira
> Fix For: trunk
>
> Attachments: OOZIE-1398-v4.patch, OOZIE-1398-v5.patch,
> OOZIE-1398-v7.patch, OOZIE-1398-v8.patch, OOZIE-1398-v8.patch
>
>
> When the number of concurrent submissions on Oozie increased to 100-200 per
> minute, it was not able to scale and we hit Oracle issues as there were lot
> of CLOB columns and DB became a bottle neck.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
