01-18-2016
NX 3 had a dump round-robin dispatcher. If one of the NX nodes was rebooted, it was less loaded than the other nodes, and never caught up.
The nxpub simply adds a more sophisticated dispatcher, and is transparent i.e. there is no administrative change and no extra dependency.
If you are using another load balancer, then likely this one won't add any value.
5 More Discussions You Might Find Interesting
1. Programming
Halo mates,
I m going to write a load balancer with C. Does anybody know some good reference on this?
Cheers,
Elton (5 Replies)
Discussion started by: EltonSky
5 Replies
2. AIX
Hi All,
How do I failover on the ip load balancer (back and forth)? It involves first to load a new config on the passive ip. If success, load the new config on the ip active (which is now passive).
Any idea, please.
Thanks in advance. (0 Replies)
Discussion started by: itik
0 Replies
3. Red Hat
Hi,
What's the best load balancer for Linux (CentOS, SuSE) according to your personal experience?
Linux Virtual Server (LVS) is a famous one, but their download site has not been updated since 2007. Their web and mailing list are so quiet. Is the Ultra Monkey project including LVS... (1 Reply)
Discussion started by: aixlover
1 Replies
4. UNIX for Advanced & Expert Users
we use piranha load balancer with two nodes
even the primary node is running fine and up failover happend to secondary node
this happend quite few times ehy node2 cannot talk to node1
what logs are to be checked and investigate why failover occured
pulse: partner dead: activating... (0 Replies)
Discussion started by: robo
0 Replies
5. Linux
Hello Guys,
Hope you all doing well . :)
I was checking load balance command (uptime)on VM server and got below output.
# uptime
07:08:40 up 52 min, 2 users,a load average: 0.45, 0.11, 0.03
A :How we can calculate load average?
Thank you in advance !!
Cheers:)
Dont forget... (1 Reply)
Discussion started by: Nats
1 Replies
LEARN ABOUT CENTOS
crm_node
PACEMAKER(8) System Administration Utilities PACEMAKER(8)
NAME
Pacemaker - Part of the Pacemaker cluster resource manager
SYNOPSIS
crm_node command [options]
DESCRIPTION
crm_node - Tool for displaying low-level node information
OPTIONS
-?, --help
This text
-$, --version
Version information
-V, --verbose
Increase debug output
-Q, --quiet
Essential output only
Stack:
-A, --openais
Only try connecting to an OpenAIS-based cluster
-H, --heartbeat
Only try connecting to a Heartbeat-based cluster
Commands:
-n, --name
Display the name used by the cluster for this node
-N, --name-for-id=value
Display the name used by the cluster for the node with the specified id
-e, --epoch
Display the epoch during which this node joined the cluster
-q, --quorum
Display a 1 if our partition has quorum, 0 if not
-l, --list
Display all known members (past and present) of this cluster (Not available for heartbeat clusters)
-p, --partition
Display the members of this partition
-i, --cluster-id
Display this node's cluster id
-R, --remove=value
(Advanced) Remove the (stopped) node with the specified name from Pacemaker's configuration and caches
In the case of Heartbeat, CMAN and Corosync 2.0, requires that the node has already been removed from the underlying cluster
Additional Options:
-f, --force
AUTHOR
Written by Andrew Beekhof
REPORTING BUGS
Report bugs to pacemaker@oss.clusterlabs.org
Pacemaker 1.1.10-29.el7 June 2014 PACEMAKER(8)