Github user jerrypeng commented on the pull request:
https://github.com/apache/storm/pull/921#issuecomment-165702815
If there no slots left on a node, the DefaultResourceAwareStrategy will not
schedule on that node. The number of slots should not effect the default
eviction/priority strategy currently implemented. We could implement strategies
that takes into account slots but I don't think that is necessary. In the
future, perhaps the concept of a worker slot will disappear. Workers can be
scheduled on nodes as long as there is free resources. The size of a worker
could be limited. However, we should be careful and not spawn too many jvm
process thus perhaps there should be an upper limit to the amount of jvm
process a node can have
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
