 |
 |
Hi Matevz, The only way to find out is to turn on redirect debugging in the cmsd for a while and see what the decisions were. We can go from there once we have a timeline. Andy On Wed, 26 Feb 2014, Matevz Tadel wrote: > On 02/26/14 09:22, Matevz Tadel wrote: >> Hi, >> >> We have ~20 of xrootd servers at UCSD, all of them do something else, too, >> and >> are thus under different load. This led to practically all requests going >> to a >> few servers only so I set cms.sched to do round-robin. But this does't help >> much, the open requests are still mostly sent to the same few servers. >> >> Could it be that "cms.dfs lookup distrib" causes the redirector to send the >> client to the "fastest to respond" server instead of decoupling verify and >> redirect steps? > > OK, that wasn't it ... I got hdfs configured on our redirector and tried > lookup central but it didn't change anything. > > What could cause the redirector to only redirect to a few servers? I have > this now ... so it should be pure round-robin, right? > cms.sched cpu 0 io 0 mem 0 pag 0 runq 0 space 0 fuzz 100 refreset 3600 > > > Matevz > > ######################################################################## > Use REPLY-ALL to reply to list > > To unsubscribe from the XROOTD-DEV list, click the following link: > https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1 > ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1