Github user jerrypeng commented on the pull request:
https://github.com/apache/storm/pull/921#issuecomment-162585896
@hustfxj thanks for your comment. Topology priorities are relative to the
user. The main metric to compare uses is how much of their resource guarantee
is satisfied. Given the example your provide, the only reason why a topology
from user A is going to be killed due to User B submitted a topology is because
user A is above his or her resource guarantee given user B is below his or her
resource guarantee. To prevent this happening, User A must have a higher
resource guarantee or at least higher than user C if you want topologies from
user C to be killed. However, in my implementation the eviction strategy to
use is a pluggable interface so you can easily add addition logic or create a
whole entire eviction strategy to fit your needs
---
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.
---
