Made PoolDBOutputService compatible with threaded framework #3371
Conversation
Initial attempt at making PoolDBOutputService work with the threaded framework. The code now uses the new ActivityRegistry signals and has a recursive mutex around the function which change internal state. Several assumptions have been made 1) only one Run and Lumi are being processed in the job. This will be true for CMSSW_7_1_X but not in the future; 2) the calls to the DB are thread safe; 3) time based IOVs are only set during Event processing In addition, the session() method was not removed however I am fairly certain a caller could not use the return value in a thread safe manner.
|
A new Pull Request was created by @Dr15Jones (Chris Jones) for CMSSW_7_1_X. Made PoolDBOutputService compatible with threaded framework It involves the following packages: CondCore/DBOutputService @apfeiffer1, @diguida, @cmsbuild, @nclopezo, @rcastello, @ggovi, @Degano can you please review it and eventually sign? Thanks. |
|
+1 On Thu, Apr 17, 2014 at 12:50 PM, cmsbuild notifications@github.com wrote:
Thanks, |
|
@rcastello @diguida ping? |
|
+1 |
…ibleWithThreadedFramework Multithreading -- Made PoolDBOutputService compatible with threaded framework
Dr15Jones
deleted the
makePoolDBOutputServiceCompatibleWithThreadedFramework
branch
Initial attempt at making PoolDBOutputService work with the threaded
framework. The code now uses the new ActivityRegistry signals and
has a recursive mutex around the function which change internal state.
Several assumptions have been made
true for CMSSW_7_1_X but not in the future;
In addition, the session() method was not removed however I am
fairly certain a caller could not use the return value in a thread
safe manner.