[Spread-users] Spread daemon -8 and -11 errors

[Chetan Gadgil]

Ideally, the flow control should be done by the spread library itself.
If the messages are pushed at a much higher rate than they are pulled,
the "push" operation (SP_multicast) can become progressively more and
more expensive in terms of time. i.e. it will take progressively more
time to return from the call. (This can be made "intelligent" and
configurable - per group, type of message etc.)

In any case, killing the receiver seems un-intuitive. If at all, you
should kill the sender.


Regards
Chetan



HISTORY, n. 
  An account mostly false, of events mostly unimportant, which are
brought about by rulers mostly knaves, and soldiers mostly fools. 
    - Ambrose Bierce, The Devil's Dictionary


> -----Original Message-----
> From: Jacob Green [mailto:jgreen at spreadconcepts.com] 
> Sent: Wednesday, December 24, 2003 3:17 AM
> To: spread-users at lists.spread.org
> Cc: cgadgil_list at cxoindia.dnsalias.com; 'Bill Montgomery'
> Subject: RE: [Spread-users] Spread daemon -8 and -11 errors
> 
> 
> CONNECTION_CLOSED is often due to joined spread clients not 
> receiving messages fast enough.  Spread daemons will do 
> _some_ buffering of messages (up to 10,000 by default), but 
> ultimately if your senders far outpace your receiver's 
> capacity, you will need to implement some sort of flow control. 
> 
> Discussions and suds code for possible flow control methods 
> can be found on the list at: 
> http://lists.spread.org/pipermail/spread-users/2003-June/001483.html
> 
> and a detailed analysis at the bottom of: 
> http://lists.spread.org/pipermail/spread-users/2002-May/000767.html
> 
> Jacob
> 
> > -----Original Message-----
> > From: spread-users-admin at lists.spread.org [mailto:spread-users- 
> > admin at lists.spread.org] On Behalf Of Chetan Gadgil
> > Sent: Monday, December 22, 2003 10:52 PM
> > To: 'Bill Montgomery'
> > Cc: spread-users at lists.spread.org
> > Subject: RE: [Spread-users] Spread daemon -8 and -11 errors
> > 
> > I have the same situation - I get arbitrary disconnects:
> > 
> > (The SP_receive call returns CONNECTION_CLOSED)
> > 
> > 
> > I am using spread under Windows XP Professional, with all 
> the patches 
> > (service packs) and spread compiled with MS-VS.NET 2003.
> > 
> > This tends to happen under heavy load situations. (Large number of
> > messages)
> > 
> > Chetan
> > 
> > 
> > Bucy's Law:
> >         Nothing is ever accomplished by a reasonable man.
> > 
> > 
> > 
> > > -----Original Message-----
> > > From: spread-users-admin at lists.spread.org
> > > [mailto:spread-users-admin at lists.spread.org] On Behalf Of Bill 
> > > Montgomery
> > > Sent: Tuesday, December 23, 2003 3:01 AM
> > > To: mls-users at lists.backhand.org
> > > Cc: spread-users at lists.spread.org
> > > Subject: [Spread-users] Spread daemon -8 and -11 errors
> > >
> > >
> > > Hi,
> > > I'm running mod_log_spread with apache 2.0.47, using the prefork 
> > > MPM, and spread 3.17.1. There is a spread daemon running 
> locally on 
> > > each web server, specified with the following line in httpd.conf:
> > >
> > > SpreadDaemon 3333
> > >
> > > Most (75%?) of the apache log messages are being sent over the 
> > > spread ring and are recorded by spreadlogd on my logging host. 
> > > However, portion of the log messages cause an error, and are not 
> > > succesfully sent to the
> > > spread daemon. The errors look like this in the apache error log:
> > >
> > > [Mon Dec 22 14:24:42 2003] [crit] [client 66.193.5.50] 
> Spread Daemon 
> > > returned an error. -11 This Request could not be logged 
> > > /author/upload/upload_progress.cgi
> > >
> > > There are also occasional -8 spread errors. Looking at 
> sp.h in the 
> > > spread source tells me that these errors are 
> CONNECTION_CLOSED (-8) 
> > > and ILLEGAL_SESSION (-11). These errors are returned a dozen 
> > > different places in the spread daemon code, and I wasn't able to 
> > > tell why in most
> > > cases.
> > >
> > > READMEs, Google, and mailing list archives have not turned up 
> > > anything useful. I tried linking mod_log_spread.so against 
> > > libtspread, thinking
> > > it might be a problem with thread safety (don't think it
> > > should be, with
> > > the apache prefork MPM), but the same symptoms are present.
> > > Could this
> > > be a message length problem? I don't have any absurdly 
> long URL's I'm
> > > servering up, and I'm using the standard "combined" log
> > > format. Probably
> > > no measureable percentage of log messages longer than 300 
> characters,
> > > except that I'm losing a large fraction of the log messages.
> > >
> > > Also, I see the same symptoms on a web server that is 
> under a heavy 
> > > load (~10 log messages/sec) and another that has no load (just me
> > > testing). I
> > > see no pattern to the failures on the server under heavy
> > > load, but I can
> > > hit certain pages that will always generate a spread error on
> > > the test
> > > server.
> > >
> > > Anyone ever seen something like this? TIA for your help.
> > >
> > > Best Regards,
> > > Bill Montgomery
> > >
> > >
> > > _______________________________________________
> > > Spread-users mailing list
> > > Spread-users at lists.spread.org 
> > > http://lists.spread.org/mailman/listinfo/sprea> d-users
> > >
> > 
> > 
> > _______________________________________________
> > Spread-users mailing list
> > Spread-users at lists.spread.org 
> > http://lists.spread.org/mailman/listinfo/spread-users
>