[
https://issues.apache.org/jira/browse/OOZIE-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13996612#comment-13996612
]
Robert Kanter commented on OOZIE-1825:
--------------------------------------
{quote}One thing to note is that after running with this patch cannot rollback
to a older version. New workflows should be fine. But already running workflows
will fail or cannot rerun a succeeded workflow.{quote}
Do you mean that if you're using Oozie without OOZIE-1825, and you upgrade to
an Oozie with OOZIE-1825, existing jobs will be okay; but if you then decide to
downgrade to an Oozie without OOZIE-1825, existing jobs will fail?
> Optimize wf_jobs protoconf storage
> ----------------------------------
>
> Key: OOZIE-1825
> URL: https://issues.apache.org/jira/browse/OOZIE-1825
> Project: Oozie
> Issue Type: Bug
> Reporter: Purshotam Shah
> Assignee: Purshotam Shah
> Attachments: OOZIE-1825-V3.patch
>
>
> Currently protoconf stores all Hadoop configuration properties + libpath + ...
> Hadoop configuration properties are lot and take huge space, I don't think we
> need to store Hadoop configuration properties in protoconf.
> We can load it every time wf action runs.
> Some statistics on table storage.
> || Table || Size(gb) ||
> |WFJOBS_PROTO_ACTION_CONF|55.54|
> |WFJOBS_WF_INSTANCE|11.89|
> |WFJOBS_CONF|2.43|
> If we can remove Hadoop configuration form proto, size will be < 1gb.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
