HackMD
  • Beta
    Beta  Get a sneak peek of HackMD’s new design
    Turn on the feature preview and give us feedback.
    Go → Got it
    • Beta  Get a sneak peek of HackMD’s new design
      Beta  Get a sneak peek of HackMD’s new design
      Turn on the feature preview and give us feedback.
      Go → Got it
      • Sharing Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Note Permission
      • Read
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • More (Comment, Invitee)
      • Publishing
        Please check the box to agree to the Community Guidelines.
        Everyone on the web can find and read all notes of this public team.
        After the note is published, everyone on the web can find and read this note.
        See all published notes on profile page.
      • Commenting Enable
        Disabled Forbidden Owners Signed-in users Everyone
      • Permission
        • Forbidden
        • Owners
        • Signed-in users
        • Everyone
      • Invitee
      • No invitee
      • Options
      • Versions and GitHub Sync
      • Transfer ownership
      • Delete this note
      • Template
      • Insert from template
      • Export
      • Dropbox
      • Google Drive Export to Google Drive
      • Gist
      • Import
      • Dropbox
      • Google Drive Import from Google Drive
      • Gist
      • Clipboard
      • Download
      • Markdown
      • HTML
      • Raw HTML
    Menu Sharing Help
    Menu
    Options
    Versions and GitHub Sync Transfer ownership Delete this note
    Export
    Dropbox Google Drive Export to Google Drive Gist
    Import
    Dropbox Google Drive Import from Google Drive Gist Clipboard
    Download
    Markdown HTML Raw HTML
    Back
    Sharing
    Sharing Link copied
    /edit
    View mode
    • Edit mode
    • View mode
    • Book mode
    • Slide mode
    Edit mode View mode Book mode Slide mode
    Note Permission
    Read
    Owners
    • Owners
    • Signed-in users
    • Everyone
    Owners Signed-in users Everyone
    Write
    Owners
    • Owners
    • Signed-in users
    • Everyone
    Owners Signed-in users Everyone
    More (Comment, Invitee)
    Publishing
    Please check the box to agree to the Community Guidelines.
    Everyone on the web can find and read all notes of this public team.
    After the note is published, everyone on the web can find and read this note.
    See all published notes on profile page.
    More (Comment, Invitee)
    Commenting Enable
    Disabled Forbidden Owners Signed-in users Everyone
    Permission
    Owners
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Invitee
    No invitee
       owned this note    owned this note      
    Published Linked with GitHub
    Like BookmarkBookmarked
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    # Tasking System Redesign POC: https://github.com/pulp/pulpcore/pull/1261 ## Locking Mechanism 1. Locks will be done using [Postgresql Advisory Locks](https://www.postgresql.org/docs/9.4/explicit-locking.html) 2. Strings will be deterministically converted to BigInt since Advisory Locks use integers * Collisions in that conversion might impact performance (thoughput), but not correctness (as long as the same task does not attempt to fetch the same lock twice) ## User Requirements 1. Tasks are processed such that tasks sharing a resource are handled First Come First Serve (FCFS) 2. Synchronous application code may attempt to aqcuire some locks (non-blocking) and simply fail if they are unavailable. It cannot however jump the resource queue (i.e. It must not use a resource that is already assigned to a queued task). 3. Worker can be reserved to short running tasks. 4. A high number of workers can be bad for database performance. Maybe workers can be grouped with one frontend to perform the distributed find-the-next-task algorithm. **Observation:** Given user requirement 1, a waiting task that is ready to be worked on will not loose that state again, because it will have shotgun for all its requested resources. ## Algorithm for each Worker 1. Finding the next task the worker can process * https://github.com/mdellweg/steakhouse/blob/master/steakhouse/grill.py#L38 * Find the oldest task in Waiting state that does not require a resource that is already locked (not sufficient to satisfy user requirement 1) ~~2. Locking the resources for that task Lock on resources one at a time, in a deterministic order such that all workers will attempt to lock in the same order~~ 2. Locking will be handled on the task level. Each process will only ever manipulate one task and therefore only ever hold one lock. The resources are protected transitively by requirement (1). **Note:** Maybe it is sufficient to lock on the task alone. Since the algorithm of finding the next workable task will ensure that no worker will even attempt to take a task if the resources are used by an earlier task. **Idea:** When looking at the running tasks anyway, we can attempt to clean up stale / abandoned tasks on the way. "A task in state RUNNING without a lock is considered invalid." This would move the task cleanup away from a worker_cleanup. ## Algorithm Example Tasks with Resources (Spices): T1 Pepper <-- user requested first T2 Salt T3 Salt, Pepper T4 Salt, Cumin T5 Cumin <-- use requested last ## Two worker example W1 - start T1; lock Pepper W2 - try to start T1 -> fail W2 - start T2; lock Salt W2 - finish T2; unlock Salt W2 - waiting W1 - finish T1; unlock pepper W1 - start T3; lock Salt, Pepper W2 - waiting W1 - finish T3; unlock Salt, Pepper W2 - start T4; lock Salt, Cumin W1 - waiting W2 - finish T4; unlock Salt, Cumin W1 - starting T5; lock Cumin W2 - nothing left -> hibernate W1 - finish T5; unlock Cumin W1 - nothing left -> hibernate ## Idea: Example with shared and exclusive locks T1 Pepper:exclusive T2 Salt:shared T3 Salt:shared, Pepper:shared T4 Salt:exclusive, Cumin:exclusive T5 Cumin:shared T6 Cumin:shared, Pepper:exclusive ## Two worker example W1 - start T1; lock Pepper:exclusive W2 - try to start T1 -> fail W2 - start T2; lock Salt:shared W2 - finish T2; unlock Salt W2 - waiting W1 - finish T1; unlock pepper W1 - start T3; lock Salt:shared, Pepper:shared W2 - waiting W1 - finish T3; unlock Salt, Pepper W2 - start T4; lock Salt:exclusive, Cumin:exclusive W1 - waiting W2 - finish T4; unlock Salt, Cumin W1 - starting T5; lock Cumin:shared W2 - starting T6; lock Cumin:shared, Pepper:exclusive W1 - finish T5; unlock Cumin W1 - waiting W2 - finish T6; unlock Cumin, Pepper W2 - waiting ## Human Work to Do 1. Extend the Task table to include: * Task args and kwargs * Resource Locks to be reserved 2. Write a new worker entry point based on click it needs to * heartbeat * Can advisory locks help here too? * record its worker entry in the db just like RQ did * watch other others if they disappear, e.g. due to OOM and cancel any unfinished tasks 3. Implement the identify_next_task() code 4. Implement the locking function ## Blog Post Outline ### Benefits Overview Queued tasks no longer cancel when worker stop/die Pulp is now fully highly available Simpler architecture with no resource manager Throughput scales with workers <------- show one graph Increased reliability * advisory locks auto-cleanup avoiding deadlock * resolves issues from data being synchronized between postgreSQL and Redis ### How to Use Disabled by default In 3.14 enable this setting, and start your workers this way... Can go back to the old style Switch with down time; drain tasks queues. TBD when the new-style will become the default, and it will become the default TBD when the old-style will be removed, but it will be removed ### Extra Info Identify that redis is no longer used for tasking but being kept in the architecture likely to speedup content serving caching ###### tags: `Tasking System`

    Import from clipboard

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lost their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template is not available.


    Upgrade

    All
    • All
    • Team
    No template found.

    Create custom template


    Upgrade

    Delete template

    Do you really want to delete this template?

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Tutorials

    Book Mode Tutorial

    Slide Mode Tutorial

    YAML Metadata

    Contacts

    Facebook

    Twitter

    Feedback

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions

    Versions and GitHub Sync

    Sign in to link this note to GitHub Learn more
    This note is not linked with GitHub Learn more
     
    Add badge Pull Push GitHub Link Settings
    Upgrade now

    Version named by    

    More Less
    • Edit
    • Delete

    Note content is identical to the latest version.
    Compare with
      Choose a version
      No search result
      Version not found

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub

        Please sign in to GitHub and install the HackMD app on your GitHub repo. Learn more

         Sign in to GitHub

        HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Available push count

        Upgrade

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Upgrade

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully