Details
Description
If you issue a query with a limit via the shell, the cursor created is left open on the server and is unable to be closed.
This is limited to the shell, as all drivers will issue a killCursors when the limit has been met.
t = db.cursor_test;
|
t.drop();
|
pre = db.serverStatus().cursors.totalOpen;
|
|
|
for ( i=1; i<=50; i++){
|
t.save( { a : i } );
|
}
|
t.find().limit(3);
|
|
|
assert.eq(pre,db.serverStatus().cursors.totalOpen)
|
Attachments
Issue Links
- has to be done before
-
SERVER-17767 Remove the code that ignores EBUSY returns from verify in the WT integration layer
-
- Closed
-
- related to
-
SERVER-16457 WT verify and salvage operations failing with EBUSY
-
- Closed
-