[SERVER-5268] Show JavaScript lock information in currentOp results Created: 09/Mar/12  Updated: 03/Jan/18  Resolved: 02/Apr/13

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

Type: Improvement Priority: Major - P3
Reporter: Jared D. Cottrell Assignee: Unassigned
Resolution: Done Votes: 0
Labels: admin, currentOp, javascript
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Case:

 Description   

Some operations require a JavaScript lock. It would be useful to be able to see the information about that lock in the results of currentOp(), including:

  • Which ops need the lock
  • Which are waiting for it, which have it

Not sure if a parallel for "numYields" is appropriate for the JS lock.



 Comments   
Comment by Eliot Horowitz (Inactive) [ 02/Apr/13 ]

2.4 and v8 no longer have a javascript lock

Comment by Scott Hernandez (Inactive) [ 10/Mar/12 ]

It seems like with any resource we will want to set some limitation, even if it is on the high side at 1K; generally unlimited resource allocation is problematic.

I expect we will want to limit the number of js engined to some memory footprint or number of js pools.

Comment by Eliot Horowitz (Inactive) [ 10/Mar/12 ]

If the js engine is thread safe then we probably won't limit at all.

Comment by Scott Hernandez (Inactive) [ 10/Mar/12 ]

Even with multiple js engines we probably still want to limit concurrency and the number of engines.

Comment by Eliot Horowitz (Inactive) [ 10/Mar/12 ]

this probably goes away in 2.4

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