jesus at omniti
May 28, 2002, 3:25 AM
Post #2 of 2
(816 views)
Permalink
|
On Sunday, May 26, 2002, at 03:09 PM, Stephen Wang wrote:
> I recently tried to add a new slave server to my existing, well-running
> two-tier solution but encountered some problems when trying to
> configure it
> to multicast it's stats.
>
> Here's the multicast config which I first attempted (the same config
> that
> runs on all of the succesfully running servers):
> MulticastStats X.X.X.255:4445
> AcceptStats X.X.X.0/24
>
> When running this config on the new server (X.X.X.26), I receive stats
> from
> ALL of the existing servers (X.X.X.17-25), but the existing servers
> don't
> receive stats from the new server (not traceable via tcpdump, either).
Sounds like the netmask and/or broadcast address is not set right on
that machine. That can really cause serious (and often confusing)
problems like the one you describe.
> On a separate topic, I was wondering if there might be any candidacy
> function that would randomly remove X number of servers from the
> candidacy
> list. byLogWindow removes such a large number of candidates from my list
> that it's not quite useful (when there are only less than 8 slaves); I'd
> much prefer to lop off 3 servers randomly so that I don't bombard any
> particular server. Thanks!
Nope. But writing your own as a loadable candidacy function should be
trivial.
--
Theo Schlossnagle
Principal Consultant
OmniTI Computer Consulting, Inc. -- http://www.omniti.com/
Phone: +1 301 776 6376 Fax: +1 410 880 4879
1024D/82844984/95FD 30F1 489E 4613 F22E 491A 7E88 364C 8284 4984
2047R/33131B65/71 F7 95 64 49 76 5D BA 3D 90 B9 9F BE 27 24 E7
|
