1.0.6 • Published 8 years ago

grapevine v1.0.6

Weekly downloads
50
License
-
Repository
github
Last release
8 years ago

Grapevine Build Status

A fork of the original node-gossip

grape·vine (grāp′vīn′) n. 1. A vine on which grapes grow. 2. a. The informal transmission of information, gossip, or rumor from person to person. b. A usually unrevealed source of confidential information.

Please note: Version 1.0.0+ has breaking changes and cannot transparently replace 0.*.* versions

New features:

  • default transport using nssocket
  • key/value pairs have optional expiry, which propagates to the other peers, it will cause keys to get deleted (although this is not an EXACT mechanism, so it shouldn't be used as such)
  • IPv6 support
  • various bug fixes

node-gossip implements a gossip protocol w/failure detection, allowing you to create a fault-tolerant, self-managing cluster of node.js processes. Each server in the cluster has it's own set of key-value pairs which are propogated to the others peers in the cluster. The API allows you to make changes to the local state, listen for changes in state, listen for new peers and be notified when a peer appears to be dead or appears to have come back to life.

Check out the the scripts in the simulations/ directory for some examples.

Usage

var Gossiper = require('grapevine').Gossiper;
// Create a seed peer.
var seed = new Gossiper({ port: 9000 });
seed.start();

// Create 20 new peers and point them at the seed (usually this would happen in 20 separate processes)
// To prevent having a single point of failure you would probably have multiple seeds
for(var i = 9001; i <= 9020;i++) {
  //For IPv6 peers use the format [ad:dre::ss]:port. e.g. [::1]:9000
  var g = new Gossiper({port: i, seeds:['127.0.0.1:9000'] });
  g.start();

  g.on('update', function(peer, k, v) {
    console.log("peer " + peer + " set " + k + " to " + v); // peer 127.0.0.1:9999 set somekey to somevalue
  });
}

// Add another peer which updates it's state after 15 seconds
var updater = new Gossiper({ port: 9999, seeds: ['127.0.0.1:9000'] });
updater.start();
setTimeout(function() {
  updater.setLocalState('somekey', 'somevalue');
  // with expiry
  updater.setLocalState('somekey', 'somevalue', Date.now() + 10000); // 10 seconds from now this key will start to expire in the gossip net
}, 15000);

API

Gossiper methods:

allPeers()
livePeers()
deadPeers()
peerValue(peer, key)
peerKeys(peer)
getLocalState(key)
setLocalSate(key, value)

Gossiper events:

on('update', function(peer_name, key, value) {})
on('new_peer', function(peer_name) {})
on('peer_alive', function(peer_name) {})
on('peer_failed', function(peer_name) {})

Tests

expresso -I lib test/*

TODO

  • major code refactoring, too many people wrote too much code without proper coordination
  • convert tests to mocha - partially completed
  • test edge cases
  • Cluster name -- dont allow peers to accidentally join the wrong cluster
  • The scuttlebutt paper mentions a couple things we don't current do:
    • congestion throttling
    • make digests only be random subsets

Acknowledgements

Both the gossip protocol and the failure detection algorithms are based off of academic papers and Cassandra's (http://www.cassandra.org/) implementation of those papers. This library is highly indebted to both.

1.0.6

8 years ago

1.0.5

9 years ago

1.0.4

9 years ago

1.0.3

9 years ago

1.0.2

9 years ago

1.0.1

9 years ago

1.0.0

9 years ago

0.2.2

10 years ago

0.2.1

10 years ago

0.2.0

10 years ago

0.1.46

10 years ago

0.1.45

10 years ago

0.1.44

10 years ago

0.1.43

10 years ago

0.1.42

10 years ago

0.1.41

10 years ago

0.1.4

10 years ago