Hi Junko-san,

On Fri, Sep 05, 2008 at 05:53:53PM +0900, Junko IKEDA wrote:
> Hi,
> 
> I encountered the following error.
> There are 9 nodes ( 8 actives + 1 standby) and each active node has 16
> resources.
> 
> heartbeat[23545]: 2008/09/02_17:12:10 ERROR: glib: Unable to send bcast [-1]
> packet(len=71866): Message too long
> 
> It seems that heartbeat can compress a message, so the size of final message
> would be less than 256 Kbyte.

Yes, that was fixed about last November, I can very well recall
that.

> /* MAXMSG is the maximum final message size on the wire. */
> #define MAXMSG          (256*1024)
> 
> /* MAXUNCOMPRESSED is the maximum, raw data size prior to compression. */
> /* 1:8 compression ratio is to be expected on data such as xml */
> 
> But the error I found came here;
> 
> lib/plugins/HBcomm/bcast.c
> bcast_write(struct hb_media* mp, void *pkt, int len){
> 
> if ((rc=sendto(ei->wsocket, pkt, len, 0
> 
> }
> 
> The maximum size for sendto() is about 64Kbyte.

> Is there any limitation for the message size which bcast_write() can handle?
> Will it send MAXMSG ( + header )?

Hmm. Perhaps this (the maximum packet size) has been checked by
somebody before, then forgotten and it never got into discussion
about the message compression. When I started working on the
compression, the MAXMSG was already temporarily set to 2MB.

Also, I can distinctly recall that Lars was setting the MAXMSG
size to 2MB (before the compression has been fixed) to support
his 9-node cluster (or thereabouts). I don't know what kind of hb
media he used.

Cheers,

Dejan

> 
> Best Regards,
> Junko Ikeda
> 
> NTT DATA INTELLILINK CORPORATION
> 
> 
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to