Brad
Sent: Monday, November 23, 2015 12:26 PM
To: 'Reuti'
Cc: users@gridengine.org
Subject: RE: [gridengine users] Possible BDB corruption?
We had another qmaster crash over the weekend, and the jobseqnum again got
reset incorrectly to 9636419. I tried to delete the job with an ID
] Possible BDB corruption?
Hi,
> Am 17.11.2015 um 00:15 schrieb Dobbie, Brad :
>
> Our cluster is 6.2u5 and uses local BDB spooling. We recently suffered a
> qmaster crash and after reboot we noticed some strange behavior with the
> jobseqnum. When we restarted the qmaster, the JOBID
Hi,
> Am 17.11.2015 um 00:15 schrieb Dobbie, Brad :
>
> Our cluster is 6.2u5 and uses local BDB spooling. We recently suffered a
> qmaster crash and after reboot we noticed some strange behavior with the
> jobseqnum. When we restarted the qmaster, the JOBIDs skipped up to the high
> 9's (996
Our cluster is 6.2u5 and uses local BDB spooling. We recently suffered a
qmaster crash and after reboot we noticed some strange behavior with the
jobseqnum. When we restarted the qmaster, the JOBIDs skipped up to the high
9's (996 range).
>From the SGE source, it appears the qmaster tri
