[
https://issues.apache.org/jira/browse/OOZIE-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695537#comment-13695537
]
Rohini Palaniswamy commented on OOZIE-1398:
-------------------------------------------
Yes. We will be converting all CLOB columns to VARBINARY (can store up to 4MB)
in next release and compress and store data in there. postgres bytea is 2G.
VARBINARY in mysql has lesser limit though - max row size of 65K, but with
compression that should be good. For 4.0, we will revert back the sla_xml and
data columns back to CLOB due to openjpa issue with Oracle and ordering of
columns during insert (OOZIE-1436). We will only keep error message column as
varchar in 4.0.
> [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
