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

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

GitHub user kishorvpatil opened a pull request:

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

    [STORM-479] (security) Multi-tenant scheduler handles already used slot not 
reported by supervisor

    When there is mismatch between supervisor heartbeats reported number for 
slots and actual slots used by the worker on the node, this change in 
multi-tenant scheduler assumes that slot (exists /must have existed on the 
supervisor before) and accommodates this discrepancy in the state (reported by 
supervisor vs worker heartbeats).

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

    $ git pull https://github.com/kishorvpatil/incubator-storm 
mt-scheduler-used-node-check

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

    https://github.com/apache/incubator-storm/pull/244.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 #244
    
----
commit 6e3c77a69c48c11ce9564b5098953ff7a722e95a
Author: Kishor Patil <[email protected]>
Date:   2014-08-28T14:39:36Z

    Scheduler handles already used slot not reported by supervisor

----


> (Security) Multi-tenant scheduler needs extra check for used slots
> ------------------------------------------------------------------
>
>                 Key: STORM-479
>                 URL: https://issues.apache.org/jira/browse/STORM-479
>             Project: Apache Storm (Incubating)
>          Issue Type: Bug
>    Affects Versions: feature-security
>            Reporter: Kishor Patil
>
> When there is mismatch between supervisor heartbeats reported number for 
> slots and actual slots used by the worker on the node, scheduler fails with 
> IllegalArgumentException - causing failure to schedule. 



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

Reply via email to