You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Shadi A. Noghabi (JIRA)" <ji...@apache.org> on 2015/08/08 20:19:45 UTC

[jira] [Commented] (SAMZA-724) Create a tool to read configuration changes after the the bootstrap of the job, and react to them accordingly

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

Shadi A. Noghabi commented on SAMZA-724:
----------------------------------------

Patch updated with the reviews applied

> Create a tool to read configuration changes after the the bootstrap of the job, and react to them accordingly
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: SAMZA-724
>                 URL: https://issues.apache.org/jira/browse/SAMZA-724
>             Project: Samza
>          Issue Type: Sub-task
>            Reporter: Shadi A. Noghabi
>            Assignee: Shadi A. Noghabi
>         Attachments: config-manager-separate-module-v2.patch, config-manager-separate-module-v3.patch
>
>
> After a job is submitted, it might need some configuration change, specifically it might need more containers. In SAMZA-704 a tool is being added to write to the coordinator stream.  This tool can be used to write new configurations to the coordinator stream. However, another tool (ConfigManager) is needed to read the config changes and react to them, which is the goal of this task. This tool should be brought up after the job is submitted and read any config changes added to the coordinator stream, and react to each accordingly. 
> Each configuration will need a different action, and the should be added one-by one. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)