Nicklas Nordborg writes:
> > I'll post back here again if we see duplication again and can recreate the
> > conditions. In the meantime, all seems OK again.
> >
>
> I think this is a problem with the how the job queue start jobs. We'll
> check if we can reproduce it here as well. Having
> > one thing that comes to my mind and that could explain both the 'table
> > exists' error and the duplication issue is that each job is for some
> > reason executed twice (and at the same time). It shouldn't happen, but I
> > remember that we had some problems when running test programs
Hi Nicklas,
Nicklas Nordborg writes:
> I think the 'table exists' problem can happen in rare cases if two jobs
> are executed at the same time, the time window between checking if a
> table exists and creating it if it doesn't is small but not zero. This
> means that two different jobs may
I think the 'table exists' problem can happen in rare cases if two jobs
are executed at the same time, the time window between checking if a
table exists and creating it if it doesn't is small but not zero. This
means that two different jobs may not see the table and both will try to
create it.
Dear BASE team,
I just got the following error while creating a root bioassayset for a small
test experiment. My hunch is that it's something bad like a corrupted db...
I plan to get 2.5 installed ASAP, but was hoping to do a demo with 2.4.5 to
my colleagues later this week.
Well I am in luck