[SERVER-1117] don't use DBDirectClient in findAndModify Created: 13/May/10  Updated: 27/Feb/15  Resolved: 27/Feb/15

Status: Closed
Project: Core Server
Component/s: Write Ops
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Eliot Horowitz (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 15
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-2626 Excluding _id field doesn't work with... Closed
Duplicate
duplicates SERVER-15715 find_and_modify appears to be taking ... Closed
Related
Participants:

 Comments   
Comment by J Rassi [ 27/Feb/15 ]

Resolving as dup of SERVER-15715.

Comment by auto [ 11/May/12 ]

Author:

{u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: working on SERVER-1117, don't use DBDirectClient in findAndModify
Branch: master
https://github.com/mongodb/mongo/commit/499678422da4f7ee822d6cfb88f5a149f0c2cfb0

Comment by Eliot Horowitz (Inactive) [ 15/Sep/11 ]

@paolo - I doubt the recursive lock is cause the issue. Usually that means the query part isn't optimized.
CAn you follow up on http://groups.google.com/group/mongodb-user/

Comment by Paolo de Dios [ 15/Sep/11 ]

Is there a patch available that I can apply on my own? The recursive locking issue is causing some major performance degradation in my application.

Comment by Eliot Horowitz (Inactive) [ 21/Jan/11 ]

There are some other reasons, notable recursive locking, so we should do this.

Comment by Mathias Stearn [ 28/Oct/10 ]

My testing shows findAndModify has the same Ops/sec as update+getLastError so there isn't much room for improvement.

Comment by Mathias Stearn [ 01/Jul/10 ]

Down-prioritizing since the feature currently works

Comment by Mathias Stearn [ 16/Jun/10 ]

Mostly done, but still need to get sorting working.

Generated at Thu Feb 08 02:56:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.