Bugzilla – Bug 5511
Review synchronization in MJFS.createManagedJob()
Last modified: 2007-11-30 22:55:11
You need to
before you can comment on or make changes to this bug.
The creation of a job resource is synchronized. There had been
some very rare issues where a service thread creating a managed
job resource kept stuck and blocked subsequent threads an caused
all available service threads to be consumed. This finally caused
the container to keep stuck.
This synchronization seems to be unnecessary. However, if we
remove the synchronization here we must take care that access to
the idempotence id map managed in MEJHome is synchronized properly.
Access to the idempotence id map is properly synchronized.
I ran about 4-5 condor-g tests each with 1000 concurrent
jobs with removed synchronization without problems and
committed the change to the 4.0 branch.