[
https://issues.apache.org/jira/browse/OOZIE-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673468#comment-13673468
]
Rohini Palaniswamy commented on OOZIE-1398:
-------------------------------------------
Since there is a DB upgrade involved with HCat and SLA changes, trying to get
this also into this release.
These are the easy ones. Changing CONF columns might involve compressing and
storing them. Not looking at those right now.
Candidates for conversion to varachar2:
COORD_JOBS.SLA_XML
COORD_ACTIONS.SLA_XML
WF_JOBS.SLA_XML
WF_ACTIONS.SLA_XML
WF_ACTIONS.ERROR_MESSAGE (Can add logic to truncate and store)
WF_ACTIONS.DATA (Max length for storing to this column is set to 2K in code in
places where it is populated with action data)
Candidates for removal:
BUNDLE_JOBS.AUTH_TOKEN
COORD_JOBS.AUTH_TOKEN
WORKFLOW_JOBS.AUTH_TOKEN
[~tucu00],
Not sure why we need to store AUTH_TOKEN column in database. Doesn't seem
to be used anywhere. I only see ? (undef) stored as value. Can we remove this
column?
> [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: 3.3.2
> Reporter: Rohini Palaniswamy
> Fix For: trunk
>
>
> 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
