[SERVER-14143] Reenable JS interruption Created: 03/Jun/14  Updated: 04/Dec/14  Resolved: 01/Dec/14

Status: Closed
Project: Core Server
Component/s: JavaScript
Affects Version/s: 2.7.2
Fix Version/s: 2.8.0-rc2

Type: Task Priority: Major - P3
Reporter: Mathias Stearn Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-15129 Count does not honor maxTimeMS Closed
Related
related to SERVER-14069 Move killCurrentOp out of threadlocal Closed
Tested
Backwards Compatibility: Fully Compatible
Participants:

 Description   

When fixing, need to consider cases that are broken today, which at least include

  • multiple V8Scopes within a single operation
  • operation changing due to getMore


 Comments   
Comment by Githook User [ 01/Dec/14 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-14143 Re-enable javascript interruption.

This restores the behavior from 2.6 to interrupt server-side javascript contexts, but doesn't fix
the existing bugs with it due to multiple javascript scopes being associated with a single opId and
opIds changing between getMore calls.
Branch: master
https://github.com/mongodb/mongo/commit/06928da7d219ac9085d666274af4a82d81e99d4c

Comment by Githook User [ 21/Aug/14 ]

Author:

{u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}

Message: SERVER-14371 SERVER-14143 killOp notification callback
Branch: master
https://github.com/mongodb/mongo/commit/11abe6693bf9cd070ae8ac050396212f73397956

Comment by Githook User [ 03/Jun/14 ]

Author:

{u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}

Message: SERVER-14069 Temporarily disable interrupting JS code

SERVER-14143 Will reenable it
Branch: master
https://github.com/mongodb/mongo/commit/4857b8701526b07b1dedd508e768a980bf21c1dd

Generated at Thu Feb 08 03:33:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.