[SERVER-14995] OperationContext should have a constant id for whole lifetime Created: 21/Aug/14 Updated: 25/Jan/17 Resolved: 04/Jun/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code, Usability |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.4 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Andy Schwerin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Currently it uses CurOp's id, but CurOps can be nested and the nested CurOps each have their own id. Instead, the OperationContext should get an ID at construction time and use the same ID until it is over. |
| Comments |
| Comment by Githook User [ 05/Jun/15 ] |
|
Author: {u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}Message: |
| Comment by Githook User [ 02/Jun/15 ] |
|
Author: {u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}Message: |
| Comment by Githook User [ 02/Jun/15 ] |
|
Author: {u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}Message: Also, limit the lifetime of OperationContext in MongoD so that it goes out of |
| Comment by Githook User [ 02/Jun/15 ] |
|
Author: {u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}Message: Reapply " This reverts commit e181ea38af737ef7aaf5f8228f870d8c7149b2bb. |
| Comment by Githook User [ 29/May/15 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: Revert " This reverts commit 4ea38c308da292f43e29d32b1b53b7324db0bafe. |
| Comment by Githook User [ 29/May/15 ] |
|
Author: {u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}Message: They have been moved from OperationContextImpl. Furthermore, the CurOp stack is With this change, an operation's lifetime is governed by the lifetime of an A future change will adjust operation lifetime timing to time the lifetime of |