wiredtiger/wiredtiger.github.com — Issue #83: threads using the default connection session
Author: wiredtiger
Created: 2012-01-31 16:46:29+00:00
State: open

1. The eviction thread & read thread both use the default connection session, which isn't safe, there's no locking or other method of stopping them from colliding (for example, if they both allocated scratch buffers at the same time). The work threads should all have their own session handles. (I'm not sure about the workQ thread -- currently, it doesn't use a session for anything.) The default connection session can only be used in single-threaded code paths.
2. We need to "close" the default connection session like any other session, it may have attached scratch buffers, for example.