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

ASF GitHub Bot commented on STORM-358:
--------------------------------------

GitHub user kishorvpatil opened a pull request:

    https://github.com/apache/incubator-storm/pull/145

    STORM-358 - Multitenant scheduler fix to free a slot in bad-state

    Force free the slot that's in bad state during reassignments in multi 
tenant scheduler.
    Includes are unit test to validate the fix works for a slot in bad state.


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

    $ git pull https://github.com/kishorvpatil/incubator-storm slot-free-fix

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

    https://github.com/apache/incubator-storm/pull/145.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 #145
    
----
commit ab7784e49d251ca4da967c6ec6bc340cc7f940aa
Author: Kishor Patil <[email protected]>
Date:   2014-06-17T15:19:00Z

    Force free a slot in bad-state

----


> Multitenant scheduler fails to free a slot in bad-state
> -------------------------------------------------------
>
>                 Key: STORM-358
>                 URL: https://issues.apache.org/jira/browse/STORM-358
>             Project: Apache Storm (Incubating)
>          Issue Type: Bug
>            Reporter: Kishor Patil
>              Labels: security
>
> Nimbus crashes, as it fails to free  up the slot in bad state. 
>  b.s.d.nimbus [ERROR] Error when processing event
> java.lang.IllegalArgumentException: Tried to free a slot that was not part of 
> this node 2a697d77-e16d-4586-a460-f7630244b68f
>         at backtype.storm.scheduler.multitenant.Node.free(Node.java:160) 
> ~[storm-core-0.9.0-wip21.jar:na]
>         at 
> backtype.storm.scheduler.multitenant.Node.getAllNodesFrom(Node.java:286) 
> ~[storm-core-0.9.0-wip21.jar:na]



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to