You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Mahadev konar (JIRA)" <ji...@apache.org> on 2013/10/18 00:17:43 UTC
[jira] [Updated] (AMBARI-3136) Reduce the size of ExecutionCommand
entity
[ https://issues.apache.org/jira/browse/AMBARI-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mahadev konar updated AMBARI-3136:
----------------------------------
Fix Version/s: (was: 1.4.1)
> 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
> 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 was sent by Atlassian JIRA
(v6.1#6144)