Problem in 1.4.1 / Local repository ?

Start two parallel ganga sessions and try to commit the same job:

Session 1
for i in range(100): jobs[1].name = 'bbbb'

Session 2

for i in range(100): jobs[1].name = 'cccc'

This should give warning: CANNOT COMMIT!

Then quit session 1 and then session 2.

Mutexes in repository

We may use the states like 'submitting' or 'gettingoutput' in order to mutually exclude monitoring threads in parallel ganga sessions. So probably we do not need mutexes at all

What is the current behaviour of two parallel ganga sessions which create jobs?

Given experience with DIANE submitters, sometimes the job disappear. To be checked.

Alexander: this may happen if the timestamp of both sessions is the same. In python 2.4 this is a problem (changed time.time()) -> replaced with clock().

Why cannot we use GUIDS?

-- JakubMoscicki - 22 Jun 2006

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2006-06-22 - JakubMoscicki
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    ArdaGrid All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback