[Spread-users] Slow receiver

[Ryan Caudy]

I whole-heartedly agree.  Maybe keep a commented explanation of that 
configuration in the sample.spread.conf, but certainly it seems like it 
shouldn't be the default anymore.  This might make a little more work 
for people wanting to use Spread "out of the box," but I feel like most 
people are willing to put in the work to get a correct configuration for 
their system before testing.

Cheers,
Ryan

John Schultz wrote:

> I propose that we remove the 127.0.0.1 address from the example config
> file for future _releases_ and add a entry to the FAQ about why it should
> rarely be used.
> 
> It seems that about half of the problems people have with Spread on this 
> list can be traced to incorrectly including a localhost entry or segment.
> 
> John
> 
> On Tue, 27 Jan 2004, Jonathan Stanton wrote:
> 
>>My first comment is I don't know if the spread.conf file you gave is 
>>exactly what you are using -- but if it is (and hte xxx.xxx addresses are 
>>real IP addresses) then one problem is that you should not mix the 
>>internal localhost addresses and external ones. It doesn't make sense from 
>>Spread's point of view. 
>>
>>I think your config may sort of work if you only connect from a client 
>>running on the same machine as the daemon, but the 'client' and 
>>'spread-daemon' machines will certainly not work.
>>
>>If you are just running on one machine, then I'd try the config
>>
>>Spread_Segment 127.0.0.255:4803 {
>>	localhost 127.0.0.1
>>}
>>
>>If you are connecting clients from other machines or using multiple 
>>daemons I'd do aconfig like:
>>
>>Spread_Segment xxx.yyy.zzz.255:4803 {
>>	client   xxx.yyy.zzz.1
>>	spread-daemon xxx.yyy.zzz.2
>>} 
>>
>>(Obviously with real addresses. The key change is you should not include 
>>localhost in the set of machines if you are not ONLY using localhost). 
>>
>>You are correct about what data_link is doing. It retries the sends on 
>>error to overcome transient errors. The question is why is the send 
>>failing in the first case. From the error I'm guessing it might be because 
>>of the config file having both localhost and remote addresses.
>>
>>The best thing to do is try with one of the config files listed above and 
>>if that doesn't fix it, then turn on the DATALINK debug flag by adding
>>
>>DebugFlags = { PRINT EXIT DATA_LINK } 
>>EventLogFile = bad_sendmsg.log
>>
>>Then run spread and your test program. This will generate a log file 
>>"bad_sendmsg.log" that has every send call logged and should report more 
>>information that might show me what the error is. 
>>
>>Cheers,
>>
>>Jonathan
> 
> 
> 
> 
> _______________________________________________
> Spread-users mailing list
> Spread-users at lists.spread.org
> http://lists.spread.org/mailman/listinfo/spread-users
> 

-- 
Ryan W. Caudy
Center for Networking and Distributed Systems
Department of Computer Science
Johns Hopkins University