Uploaded image for project: 'Apache Helix'
  1. Apache Helix
  2. HELIX-744

[TASK] Allow undefined workflow/job types to be assigned as DEFAULT type

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    Description

      Previously, we ignored undefined types, that is workflow/job types that are not defined in ClusterConfig. This is not backward-compatible because some users of Task Framework are setting types without any quota-related config set in ClusterConfig. The default behavior was changed so that each AssignableInstance will just treat these workflows/jobs as DEFAULT type, which will make quota-based scheduling backward-compatible. Changelist: 1. AssignableInstance treats undefined types as DEFAULT 2. Appropriate log messages and logic change was applied to restoreTaskAssignResult logic 3. A test case was added to TestQuotaBasedScheduling

      Attachments

        Activity

          People

            Unassigned Unassigned
            narendly Hunter L
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: