Uploaded image for project: 'Apache Storm'
  1. Apache Storm
  2. STORM-3588

RAS scheduler should not pre-empt and evict topologies due to generic resource

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

      Description

      Currently, when we enabled generic resource support in our cluster, RAS scheduler will evict scheduled topologies if new inappropriate asks for crazy amount of generic resources.

      We have identified the currently getScore() function in DefaultSchedulingPriorityStrategy does not consider the generic resource factor. Ideally, if user topology is asking way too much generic resources, it should be assigned lower priority in scheduling and won't affect other running topologies.

        Attachments

          Activity

            People

            • Assignee:
              li530 Rui Li
              Reporter:
              li530 Rui Li

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 13h
                13h

                  Issue deployment