Jayv,
One additional thing to check is if there is clock skew between the 3
machines involved.
The window for rebroadcast of a dropped message is 20 seconds, so a
clock skew of
15 seconds or more coupled with the small UDP buffer could be causing
the messages
that are coming up too frequently.
-Joe
On 5/19/11 5:50 AM, forums_at_java.net wrote:
> Hi Joe,
>
> I've implemented the logging tweaks, however it only stopped after I
> restarted both clusters and the DAS, but this is probably a known issue.
>
> I'd like to send you some log files but the question is will it be
> helpfull
> as I can't seem to find the logfile containing the start of the problem,
> we've been deleting them from time to time... so only got about 2GB of
> logs
> of the past 2 days. I could re-enable logging but if this requires me to
> bring down the cluster it will take some time as we're not fond of
> bringing
> down a live system during business hours.
>
> Regarding your other suggestions, yes we are on Linux (ubuntu), but
> we're on
> beefy machines with 8 CPUs and a 24GB RAM, so the machines are hardly
> used
> for the moment, 0.40 loadavg.
>
> # cat /proc/sys/net/core/rmem_max
>
> 131071
>
> # cat /proc/sys/net/core/rmem_default
>
> 124928
>
> Our UDP buffers might need tuning for heavyer loads, which I expect in
> the
> future with other apps deployed, but I would not expect the current
> load to
> require larger buffersizes, but I'm no expert in this area so I could be
> wrong here.
>
> Thanks for your assistance.
>
>
> --
>
> [Message sent by forum member 'jayv']
>
> View Post: http://forums.java.net/node/803337
>
>