GitHub user HeartSaVioR opened a pull request: https://github.com/apache/storm/pull/2343
STORM-2083 Blacklist scheduler This is rebased version of #1674 with addressing latest review comments from me. Sure the credit for providing great stuff should go to @nilday. :) Since now I can't give +1 to my patch, it would be really appreciated if someone could review and do some manual tests. Thanks in advance. You can merge this pull request into a Git repository by running: $ git pull https://github.com/HeartSaVioR/storm STORM-2083 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/storm/pull/2343.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 #2343 ---- commit 9823af7b7ffa9d6552bbfc3a505a5f5245a74a30 Author: howard.li <howard...@vipshop.com> Date: 2016-07-07T10:32:30Z STORM-2083: Blacklist scheduler Resolved conflict via Jungtaek Lim <kabh...@gmail.com> This commit squashes the commits into one and commit messages were below: 1. add apache header 2. rename method 3. move config define to Config 4. code style fix 5. change debug log level to debug remove all blacklist enable config remove unused default value 1.storm blacklist code style, header and other bugs 2.wrap blacklist scheduler in nimbus and rebase to master change blacklist-scheduler schedule method log level. rename some variables and refactor badSlots args add blacklist.scheduler to default.yaml 1. removeLongTimeDisappearFromCache bug fix 2. add unit test for removeLongTimeDisappearFromCache 3. change blacklistScheduler fields to protected so it can be visited from sub-class and unit tests 1. remove CircularBuffer and replace it with guava EvictingQueue. 2. modify nimbus_test.clj to adapt blacklistScheduler 3. comments, Utils.getInt, DefaultBlacklistStrategy.prepare with conf commit 71fdbbc29670534dbb4e9d6ecfcecb8c2fd8e69d Author: Jungtaek Lim <kabh...@gmail.com> Date: 2017-09-25T13:16:48Z STORM-2083 Blacklist scheduler * address review comments from @HeartSaVioR and @revans2 ---- ---