npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

task-coordinator

v2.1.1

Published

Schedule a task to run at a fixed interval in at most one of your processes

Downloads

30

Readme

Task Coordinator

Build Status Inline docs Dependency Status

Schedule a task to run at a fixed interval in at most one of your processes

They will coordinate which one runs each time using a mongodb collection

Install

npm install task-coordinator --save

Usage

// Create the coordinator using the given mongodb connection
// (mongoose in not necessary, this lib talks directly with the mongodb driver)
var coordinator = require('task-coordinator')(mongoose.connection.db)

// Schedule a task to run every 5s
// Even if you deploy this to many machines/process, only one
// of them will execute the callback
var task = coordinator.schedule({
	name: 'task name',
	interval: '5s' // ms, s, min, h or d
}, function (done) {
	// Do something, them call done()
})

How it works

Each instance tries to insert a document in a collection in mongodb with a unique key in the task name. Only one call will succeed, that one will trigger the callback execution. When the task calls done(), that inserted document is removed.

The number of documents in that collection is bounded by the number of tasks scheduled, that is, they do not grow indefinitely.

Synchronization

A task scheduled to run every minute will run at 00:00:00Z, 00:01:00Z, 00:02:00Z and so on. That is, to ensure the execution interval, the tasks are run at whole intervals.

You can set how much each task will offset from whole intervals. A task with interval of 1 minute and offset of 5 seconds will run at 00:00:05Z, 00:01:05Z, 00:02:05Z and so on. By default, the offset is zero.

Timeout

If, for some reason, the task callback does not call done(), the locking mechanism would prevent the task from ever running again. To solve this problem, a lock may timeout after some time.

This approach also creates a problem: if the task is still running when the timeout expires, another task instance may start before the previous one completes. This would then break the assumption of at most one task running.

You can set the desired behaviour with the timeout option and monitor violations listening to events timeout, possibleOverrun.

Docs

See generated docs on github