[Spread-users] Bug in spread - message counter

Nico Meyer nmeyer at virtualminds.de
Mon Apr 7 05:10:18 EDT 2008

Hello Witold,

I think a few people would be interested in this fix, since this affects other 
people too. I first reported this problem 3 months ago, but I fell through 
the cracks. Last month I tried it again, and John told me they would look 
into it. There haven't been any news since, which is a little disturbing 
given how bad this problem is when it bites you.

But just changing the counters might not work, because the sequence number is 
also transmitted to other deamons, so you would probably also need to change 
the message format also.


On Monday 07 April 2008 10:39:06 Witold Kręcicki wrote:
> I have 4 spread daemons running high (~10000mps) traffic, and I have been
> encountering 'full lockups' of the whole system (no new connections
> accepted, no messages passed). After testing, it came up that this lockup
> happens when 'highest seq' (and all other similiar counters) value in
> spread monitor comes close to signed 32bit int limit (2**31). As a
> temporary workaround, I'm planning to change these counters to 64bit - do I
> have to change it in spread daemon only, or also in client library? Which
> ones do I have to change?

More information about the Spread-users mailing list