[SERVER-2555] Allow custom server-side timeout for map-reduce requests Created: 15/Feb/11  Updated: 17/Mar/11  Resolved: 16/Feb/11

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

Type: New Feature Priority: Minor - P4
Reporter: Jonathan Chambers Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

I'm building a web application that will allow users to generate ad hoc map reduce requests of arbitrary complexity and I'm worried that a poorly constructed request could lock up the whole database. I'm using the ruby driver (via MongoMapper) and I noticed that cursors already have a server-side timeout of ten minutes (I presume this applies to map reduce jobs?), and so I was wondering whether it would be possible to have the option to override this value on a per request basis instead?



 Comments   
Comment by Jonathan Chambers [ 16/Feb/11 ]

Thanks for the cron tip, I'll do it that way.

Comment by Eliot Horowitz (Inactive) [ 16/Feb/11 ]

The client cursor timeout does not impact map/reduce at al.
That's only for inactive cursors.

If you want to timeout map/reduce jobs, the best way to do that is a cron that looks at the current operations, and kills any map/reduce longer than a threshold

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