[SERVER-17012] Server Terminates Javascript Execution for GroupStage Setup with a Timeout Created: 22/Jan/15 Updated: 18/Sep/15 Resolved: 26/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | MapReduce |
| Affects Version/s: | None |
| Fix Version/s: | 3.0.0-rc7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jonathan Balsano | Assignee: | Jonathan Balsano |
| Resolution: | Done | Votes: | 0 |
| Labels: | 28qa, pull-request | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
Build failures were observed in the concurrency workloads that result in the following error:
Builds that encountered this error include:
These seem to be caused by a javascript timeout that we've placed in multiple locations on our own code execution in db/exec/group.cpp:
Other calls to both exec() and invoke() do not seem to use this timeout. For example, in db/commands/mr.cpp
Note that in both examples we're not executing client code, we're executing our own server code. It would appear that it is likely that a garbage collection could cause the execution to take more than 100ms but there seems to be no reason to keep the timeout here. |
| Comments |
| Comment by Githook User [ 26/Jan/15 ] |
|
Author: {u'username': u'jrbalsano', u'name': u'Jonathan Balsano', u'email': u'jonathan.balsano@10gen.com'}Message: Closes #915 Signed-off-by: Benety Goh <benety@mongodb.com> |
| Comment by Githook User [ 26/Jan/15 ] |
|
Author: {u'username': u'jrbalsano', u'name': u'Jonathan Balsano', u'email': u'jonathan.balsano@10gen.com'}Message: Closes #915 Signed-off-by: Benety Goh <benety@mongodb.com> |