[SERVER-32565] Stepdown suites should tolerate js engine errors Created: 05/Jan/18  Updated: 11/Sep/20  Resolved: 09/Oct/18

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

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Mira Carey
Resolution: Duplicate Votes: 0
Labels: former-quick-wins, todo_in_code
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates SERVER-37126 Invoke runSafely for all external imp... Closed
Related
related to SERVER-34770 Retry on JavaScript execution interru... Closed
related to SERVER-43503 Complete TODO listed in SERVER-32565 Closed
is related to SERVER-35082 group_killop.js should accept "Intern... Closed
is related to SERVER-37126 Invoke runSafely for all external imp... Closed
Operating System: ALL
Sprint: Platforms 2018-05-07, Service Arch 2018-10-08, Service Arch 2018-10-22
Participants:
Linked BF Score: 18

 Description   

From one of the test failures, the where command threw this error when step down happened while it was running:

  "ok" : 0,
  "errmsg" : "Failed to call method",
  "code" : 1,
  "codeName" : "InternalError"

This error comes from ObjectWrapper::callMethod inside the js engine.



 Comments   
Comment by Githook User [ 11/Sep/20 ]

Author:

{'name': 'Ruoxin Xu', 'email': 'ruoxin.xu@mongodb.com', 'username': 'RuoxinXu'}

Message: SERVER-43503 Complete TODO listed in SERVER-32565
Branch: master
https://github.com/mongodb/mongo/commit/1373280c254a39d2ca7d85563718a6f74c927216

Comment by Mira Carey [ 09/Oct/18 ]

After SERVER-37126, I believe that I've clamped down on all cases where internal errors leaked where other better errors could have been returned instead.

Comment by Spencer Jackson [ 24/Aug/18 ]

I took a look at this, and it seems the work in SERVER-35061 which made some JS components more aggressively return Interrupted did not happen to alleviate this.

Comment by Jonathan Reams [ 14/May/18 ]

We're going to bump this out to 4.1.

Comment by Randolph Tan [ 23/Jan/18 ]

Assigning to platforms team to investigate the cause of the internalError.

Comment by Kaloian Manassiev [ 18/Jan/18 ]

renctan, assigning this ticket to you to either close or pass on to the platforms team. I don't believe there is anything that the sharding team needs to do here.

Comment by Kaloian Manassiev [ 09/Jan/18 ]

If the method call failed due to internal error in the JS engine, I don't think the tests should be resilient to that. This likely a bug in the JS engine, which shouldn't happen.

Should this go to the platforms team instead?

Generated at Thu Feb 08 04:30:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.