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

Posted to dev@ambari.apache.org by "Siddharth Wagle (JIRA)" <ji...@apache.org> on 2013/09/07 00:08:52 UTC

[jira] [Commented] (AMBARI-3136) Reduce the size of ExecutionCommand entity

    [ https://issues.apache.org/jira/browse/AMBARI-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13760689#comment-13760689 ] 

Siddharth Wagle commented on AMBARI-3136:
-----------------------------------------

+1 LGTM
                
> Reduce the size of ExecutionCommand entity
> ------------------------------------------
>
>                 Key: AMBARI-3136
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3136
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 1.4.0
>            Reporter: Myroslav Papirkovskyy
>            Assignee: Myroslav Papirkovskyy
>             Fix For: 1.4.1
>
>         Attachments: AMBARI-3136.patch
>
>
> Currently, each ExecutionCommandEntity stores the whole config blob. This is a severe duplication of data as tagged configuration information is already available as immutable entry.
> We need to reduce the footprint of ExecutionCommandEntity by storing only configuration tags. The tags can be replaced with actual configuration value when the command is handed off to the agent.
> We need to ensure that when Ambari is upgraded and there is a mix of ExecutionCommandEntity instances with and without embedded config - it works.

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