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

ASF GitHub Bot commented on QUARKS-215:
---------------------------------------

GitHub user vdogaru opened a pull request:

    https://github.com/apache/incubator-quarks/pull/153

    [WIP] [QUARKS-215] Job control gets unregistered from ControlService after 
job gets closed

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/vdogaru/incubator-quarks QUARKS-215-vdogaru

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-quarks/pull/153.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #153
    
----
commit 02e1698e02da7ea5169295e5d4e3598836f1bc94
Author: Victor Dogaru <[email protected]>
Date:   2016-06-28T01:31:44Z

    Add ControlService.getControlId

commit 6a52ee86386a4b7e07c5993602a630169515d644
Author: Victor Dogaru <[email protected]>
Date:   2016-06-28T01:31:58Z

    EtiaoJobBean unregisters control from ControlService

commit 33be1b92d943b68b0b2be8b0e3719cfc6b4b0c9e
Author: Victor Dogaru <[email protected]>
Date:   2016-06-28T01:32:10Z

    JobMonitorApp closes unhealthy job before re-submitting

----


> Job control gets unregistered from ControlService after job gets closed
> -----------------------------------------------------------------------
>
>                 Key: QUARKS-215
>                 URL: https://issues.apache.org/jira/browse/QUARKS-215
>             Project: Quarks
>          Issue Type: Improvement
>          Components: Runtime
>            Reporter: Victor Dogaru
>            Assignee: Victor Dogaru
>
> When a job is being CLOSED using its control bean, a mechanism is needed to 
> unregister the associated JobMXBean control from the ControlService.



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

Reply via email to