<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Pavlos Parissis wrote:
<blockquote
cite="mid:AANLkTinDoZTh-QG-n+2OgqvZYzN2McEF3OjAPUy7-cXm@mail.gmail.com"
type="cite"><br>
<br>
<div class="gmail_quote">On 18 October 2010 10:52, Florian Haas <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:florian.haas@linbit.com">florian.haas@linbit.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">----- Original Message -----<br>
> From: "Andreas Vogelsang" <<a moz-do-not-send="true"
href="mailto:a.vogelsang@uni-muenster.de">a.vogelsang@uni-muenster.de</a>><br>
> To: <a moz-do-not-send="true"
href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a><br>
> Sent: Monday, October 18, 2010 9:46:12 AM<br>
> Subject: [Pacemaker] Question: How many nodes can join a cluster?<br>
> Hello,<br>
><br>
><br>
><br>
> I’m creating a presentation about a virtual Linux-HA Cluster. I
just<br>
> asked me how many nodes pacemaker can handle. Mr. Schwartzkopff
wrote<br>
> in his Book that Linux-HA version 2 can handle up to 16 Nodes. Is
this<br>
> also true for pacemaker?<br>
</div>
</blockquote>
</div>
<br>
I have been asked the same question and I said to them, let's say it is
126, what is the use of having 126 nodes in the cluster?<br>
Can someone imagine himself going through the logs to find why the
resource-XXX failed while there are 200 resources?!!<br>
<br>
The only use of having 126 nodes is if you want to have HPC, but HPC is
total different story than high available clusters.<br>
Even in N+N setup I would go with more than 4 or 6 nodes.<br>
<br>
<br>
My 2 cents,<br>
Pavlos<br>
<br>
<br>
</blockquote>
Actually, the syslog_facility in corosync.conf allows you to specify
either a log file for each node in the cluster (locally), or setting up
a remote syslog server. Either way, identifying the node by hostname or
some other identifier should point out what is going on where. Granted,
it's a large amount of data to process, therefore (such is the case
with any large deployment) SNMP is a much better alternative for
tracking issues, or (if you have _126_ times the same resource) adding
some notification options to the RA might be a choice, such as SNMP
trap, or even email.<br>
<br>
BTW, I'm also interested in this, I remember reading something about 64
nodes, but I'd appreciate an official response.<br>
<br>
Regards,<br>
<br>
Dan<br>
<blockquote
cite="mid:AANLkTinDoZTh-QG-n+2OgqvZYzN2McEF3OjAPUy7-cXm@mail.gmail.com"
type="cite">
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Pacemaker mailing list: <a class="moz-txt-link-abbreviated" href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a>
<a class="moz-txt-link-freetext" href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a>
Project Home: <a class="moz-txt-link-freetext" href="http://www.clusterlabs.org">http://www.clusterlabs.org</a>
Getting started: <a class="moz-txt-link-freetext" href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a>
Bugs: <a class="moz-txt-link-freetext" href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker">http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Dan FRINCU
Systems Engineer
CCNA, RHCE
Streamwide Romania
</pre>
</body>
</html>