Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid interrupting jetty threads #10987

Merged
merged 1 commit into from
Feb 11, 2022

Commits on Feb 9, 2022

  1. Do not interrupt threads other than TaskRunner on Driver#close

    Driver methods such as Driver#updateSplitAssignment can be ran from a
    thread other than a thread created by TaskExecutor. Interrupting a
    thread that is not managed by the engine is potentially unsafe.
    
    For example the Jetty server may preserve the "interrupted" flag in between
    requests, potentially impacting a different task or a query:
    jetty/jetty.project#7548
    
    While the issue in Jetty is likely a bug that will be fixed there is no
    real reason why to interrupt a method other than Driver#process (which
    is only invoked by the TaskExecutor).
    
    Other driver methods (such as Driver#updateSplitAssignment) are
    lightweight and shouldn't take any significant time to finish while the
    interrupt mechanism is rather intended to terminate a processing
    that could potentially take a significant amount of time.
    arhimondr committed Feb 9, 2022
    Configuration menu
    Copy the full SHA
    5ded6b1 View commit details
    Browse the repository at this point in the history