Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-10352

Bind Task's URLClassLoader to TaskExecutor's slot

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 1.5.3, 1.6.0, 1.7.0
    • Fix Version/s: None
    • Component/s: Runtime / Coordination
    • Labels:
      None

      Description

      The Task's URLClassLoader is used to dynamically load user code classes. The lifetime of this class loader is bound to the Task and, thus, it can happen that we generate multiple class loader for the same job if multiple Tasks are deployed to the same slot successively.

      We could avoid this situation by binding the lifetime of the URLClassLoader to the slot instead of the Task. The slot will only be released if the JobMaster no longer needs it. That way we won't potentially recreate the URLClassLoader for every submitted Task.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                trohrmann Till Rohrmann
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: