Skip to content

Sequential scripts executing on same inotify daemon blocking #27

@tjk584

Description

@tjk584

When executing several scripts in sequence on the same inotify daemon, later scripts cannot start until the first scripts finish executing. If later scripts are executing for a long time, they will prevent the first script from starting on time.

For example, on the site-linux computers, convert_and_restructure runs first, then rsync_to_campus runs. If rsync_to_campus has many files to transfer, it may take longer than 2 hours, and when the inotify daemon should be triggering again it can't because rsync_to_campus is still running. This blocks convert_and_restructure from executing until the next time inotify triggers (in 2 hours).

The main problem here is that having multiple dataflow scripts executing in succession within a single inotify script prevents them from executing in parallel. This isn't a problem for regular data flow, when all data is operated on in order and the amount of data is tolerable. For processing backlogs of data, where multiple dataflow scripts could be executing in parallel on different sets of data, this parallel computation is not possible.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions