You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@oozie.apache.org by "Purshotam Shah (JIRA)" <ji...@apache.org> on 2014/05/07 00:38:20 UTC

[jira] [Assigned] (OOZIE-1825) Optimize wf_jobs protoconf storage

     [ https://issues.apache.org/jira/browse/OOZIE-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Purshotam Shah reassigned OOZIE-1825:
-------------------------------------

    Assignee: Purshotam Shah

> 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
>
> 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)