Nsq helper to poll a nsqlookupd service for all it's nodes and mirror it locally.
INFO: all examples are written in coffee-script
npm install nsq-nodes
new NsqNodes( config );Example:
var NsqNodes = require( "nsq-nodes" )
var nodes = new NsqNodes({
// Listen to two local nsq lookupservers
"lookupdHTTPAddresses": [ "127.0.0.1:4161", "127.0.0.1:4163" ]
});
// get the current list of nodes
nodes.list( function( err, nodes ){
if( err ){
// handle the error
}
console.log( nodes ) // -> an array of nodes. E.g.: ( )`users`, `logins`, ... )
// listen for new nodes
nodes.on( "add", function( node ){
// called until a new node arrived
});
// listen for removed nodes
nodes.on( "remove", function( node ){
// called until a node was removed
});
// listen for node list changes
nodes.on( "change", function( nodeList ){
// beside the `add` and `remove` events a single "change" event will be emitted
});
// listen for errors
nodes.on( "error", function( err ){
// E.g. called if a invalid filter was used or no lookup server is available
});
});Config
- lookupdHTTPAddresses : (
String|String[]required ) A single or multiple nsqlookupd hosts. This is also a configuration of 'nsqjs' - lookupdPollInterval : (
Numberoptional: default =60) Time in seconds to poll the nsqlookupd servers to sync the available nodes. This is also a configuration of 'nsqjs' - active : (
Booleanoptional: default =true) Configuration to (de)activate the nsq nodes on startup
Activate the module
Return
( Boolean ): true if it is now activated. false if it was already active
Deactivate the module
Return
( Boolean ): true if it is now deactivated. false if it was already inactive
Test if the module is currently active
Return
( Boolean ): Is active?
Get a list of the current nodes
cb: (Functionoptional ): Callback to get the list of nodes
Return
( Self ): The instance itself for chaining.
Example:
nodes.list( function( err, nodes ){
if( err ){
// handle the error
}
console.log( nodes ) // -> an array of nodes. E.g.: ( )`users`, `logins`, ... )
});A new node was added
Arguments
- node : (
String) The new node
Example:
nodes.on( "add", function( node ){
// called until a new node arrived
});A existing node was removed
Arguments
- node : (
String) The removed node
Example:
nodes.on( "remove", function( node ){
// called until a node was removed
});The list of nodes changed
Arguments
- nodes : (
String[]) A list of current nodes
Example:
nodes.on( "change", function( nodeList ){
// beside the `add` and `remove` events a single "change" event will be emitted
});An error occurred. E.g. called if a invalid filter was used or no lookup server is available
Arguments
- err : (
Error) The error object.
Example:
nodes.on( "error", function( err ){
// handle the error
});Emitted once the list of nodes where received the first time.
This is just an internal helper. The Method list will also wait for the first response. The events add, remove and change are active after this first response.
Example:
nodes.on( "ready", function( err ){
// handle the error
});| Version | Date | Description |
|---|---|---|
| 1.1.0 | 2019-01-25 | now able to handle the formats of nsq < and > 1.x |
| 1.0.0 | 2019-01-25 | updated nodes response handler to match nsq >= 1.x format |
| 0.0.3 | 2016-05-04 | Another configuration bugfix |
| 0.0.2 | 2016-05-04 | Bugfix configuration and update to lodash |
| 0.0.1 | 2015-11-27 | Initial commit |
Initially Generated with generator-mpnodemodule
| Name | Description |
|---|---|
| nsq-logger | Nsq service to read messages from all topics listed within a list of nsqlookupd services. |
| nsq-topics | Nsq helper to poll a nsqlookupd service for all it's topics and mirror it locally. |
| nsq-watch | Watch one or many topics for unprocessed messages. |
| node-cache | Simple and fast NodeJS internal caching. Node internal in memory cache like memcached. |
| rsmq | A really simple message queue based on redis |
| redis-heartbeat | Pulse a heartbeat to redis. This can be used to detach or attach servers to nginx or similar problems. |
| systemhealth | Node module to run simple custom checks for your machine or it's connections. It will use redis-heartbeat to send the current state to redis. |
| rsmq-cli | a terminal client for rsmq |
| rest-rsmq | REST interface for. |
| redis-sessions | An advanced session store for NodeJS and Redis |
| connect-redis-sessions | A connect or express middleware to simply use the redis sessions. With redis sessions you can handle multiple sessions per user_id. |
| redis-notifications | A redis based notification engine. It implements the rsmq-worker to safely create notifications and recurring reports. |
| hyperrequest | A wrapper around hyperquest to handle the results |
| task-queue-worker | A powerful tool for background processing of tasks that are run by making standard http requests |
| soyer | Soyer is small lib for server side use of Google Closure Templates with node.js. |
| grunt-soy-compile | Compile Goggle Closure Templates ( SOY ) templates including the handling of XLIFF language files. |
| backlunr | A solution to bring Backbone Collections together with the browser fulltext search engine Lunr.js |
| domel | A simple dom helper if you want to get rid of jQuery |
| obj-schema | Simple module to validate an object by a predefined schema |
Copyright © 2015 M. Peter, http://www.tcs.de
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.