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

volatile-redis-cluster

v3.0.0

Published

Volatile redis clustering implementation

Downloads

14

Readme

Volatile Redis Cluster

This is a software implementation of a redis cluster where the data on the slave nodes does not need to be persistent. The architecture requires a single master redis node (which is used to track and coordinate the slaves) and any number of slave nodes which actually store the data. By default, no sharded data is stored on the master; it serves only to track the current list of slaves.

Running the Server(s)

Start the master (coordinator) redis server via the OS's normal means. Then run node ./lib/coordinator.js on localhost (you can also run the coordinator process on a separate server, and supply '-h HOST -p PORT' to point it to the actual master redis instance). The coordinator process connects to the master redis server and uses it for temporary data storage.

After the master is running, start the slave servers. Each slave server also has both a redis instance, and a node process the coordinates it. To run a slave, start the slave server, then run node ./lib/slave.js . You may need to supply options to the slave node process:

-h <SlaveRedisHost>
-p <SlaveRedisPort>
-w <SlaveWeight>
-H <MasterRedisHost>
-P <MasterRedisPort>

There are also some bash scripts provided to help:

./scripts/run-coordinator.sh

This will start the coordinator node process and connect to an already-running redis instance on localhost with the default port. It will run in the background.

./scripts/stop-coordinator.sh

Does what it says on the tin.

./scripts/run-slaves.sh

This will start BOTH the redis processes AND the node processes for the slaves. By default, it will start as many processes are there are cores on the machine. It instantiates the redis instances using custom configs in the current working directory.

This reads configuration in ./scripts/slave-config.sh and ./scripts/slave-redis.conf-template .

./scripts/stop-slaves.sh

Does what it says on the tin.

Using the Client

var ClusterClient = require('volatilerediscluster');
var clusterClient = new ClusterClient({
	host: /* Master Redis Host */,
	port: /* Master Redis Port */
});
clusterClient.getShardClient('my:redis:key', function(err, redis) {
		if (err) ...
		redis.get('my:redis:key', ...)
});