[Swift-devel] problem at end of workflow

Glen Hocky hockyg at uchicago.edu
Fri Apr 24 01:17:54 CDT 2009


I upgraded to newest cog and swift (Swift svn swift-r2880 cog-r2391)
I got new behavior this time. instead of just 16 jobs to the queue, i 
got up to 50 before I killed. So that's probably a good thing.

The bad thing is that a job became active before any of the jobs in the 
queue started and i started getting error messages (error transfer log 
messages)

Everything is in
/home/hockyg/oops/swift/output/rangeroutdir.3000

and as promised, new ranger coaster logs in
> /home/hockyg/oops/swift/coaster_logs/ranger/coasters

sorry i don't have more time to stress test this tonight

Glen

Mihael Hategan wrote:
> On Thu, 2009-04-23 at 20:55 -0500, Mihael Hategan wrote:
>   
>> On Thu, 2009-04-23 at 20:42 -0500, Glen Hocky wrote:
>>     
>>> from now on, if i have a question about a site, i'll sync my 
>>> remote:~/.globus/coasters folder to 
>>> /home/hockyg/oops/swift/coaster_logs/SITE
>>>
>>> i just did that for ranger
>>> /home/hockyg/oops/swift/coaster_logs/ranger/coasters
>>>       
>> What I see in the logs is a bunch of starting workers, none running and
>> a bunch of queued jobs.
>>
>> I'm not sure what went wrong and where. I'll continue looking.
>>     
>
> I committed a patch (cog r2391) that tries to avoid the problem seen
> there (that of improper count of active workers which keeps growing to
> the maximum allowed and prevents other workers from being created).
>
>   




More information about the Swift-devel mailing list