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

redis-clustering-client

v0.1.0

Published

A client for communicating with a Redis Cluster via the cluster's Sentinel applications.

Downloads

2

Readme

redis-clustering-client

A client for communicating with a Redis Cluster via the cluster's Sentinel applications.

This module abstracts away the concept of a cluster to allow users to connect to the cluster master regardless of any failovers that have occurred since the last connection.
You also have the option of connecting to a random slave of the cluster as well.

Usage:

A simple example:

  var Sentinel = require('./redis-sentinel.js');

  // Initialize to use all known Sentinels
  Sentinel.init('mymaster', 
  [
    { host:'localhost', port:26379},
    { host:'192.168.1.1', port:26379},
    { host:'anotherHost', port:26380}
  ], ready);


  function ready(err) {
    if (err) {
      console.log('ERROR: ' + err);
      return;
    }

    // Connect to the cluster master and set a value
    Sentinel.command('set', ['clustering', 'is cool!']);

    // Connect to a random slave and get a hash value
    Sentinel.command('hget', ['fuster', 'cluck'], function(err, resp) {
      if (err) {
        console.log('ERROR: ' + err);
        return;
      }
      console.log(resp);
    }, true);
  }

API:

###cluster.init(cluster, sentinelArray, [callback]) Provide an ordered array of sentinels to use for connections. A connection to the reported Master Redis server is also established as a check.

  • cluster: the name of the Redis Cluster in sentinel.conf (default: mymaster)
  • sentinelArray: an array of objects describing each Redis Sentinel to attempt a connection with.
    Example (default):
    [{host:"localhost", port:26379}]
  • callback([err]): called when test connection to master is completed or an error occurs

###cluster.command(cmd, args, [callback, slave]) Send a Redis command to the cluster master (or slave if slave == true) and receive the response.

  • cmd: redis command to execute
  • args: array of arguments to the command
  • callback(err, [res]): response from the redis server
  • slave: boolean - if true send command to a random slave

Defaults:

  • cluster: mymaster
  • sentinels:
    [{host:"localhost", port:26389}]