How can we stop a running map/reduce?

My understanding is that you cannot. It should timeout after 60 minutes as long as that was left as the default.

Thanks

unfortunately it doesn't necessarily time out after 60 minutes either. 😞

@stalbert Do you have to get NetSuite support involved at that point? What has been your experience?

you can delete and re-create/deploy, taht usually kills it i beleive

I've tried deleting - NS will not allow deleting the deployment or record in my case since it was already executing.

Remove everything from the map/ reduce end points in script and undeploy. It will complete soon then

This is sort of thing is part of why I still like scheduled scripts 🙂

"runaway MRs" are the worst.

undeploy I think results in similar stopping behavior (once it decides to restart/check)

i never tried that one so ill have to take your word on it. Sounds reasonable.

From experience I have found that if you exceed 40k - 50k search results, the getInputData time starts to increase disproportionately. 60k results might take twice as long as 40k, for example. I try to limit mine to around 25-30k max per execution, and just run the M/R multiple times if needed

getInputData is single threaded so that makes sense. You don't get the real benefits until it starts processing in parallel

what I think is strange is it seems like getInputData() must pull ALL the search results before it sends ANY to map(). I presume that's a limitation of the underlying technology?

I think it does get all the data at once, and that’s probably why the performance falls off sharply when the resultset gets too large. It’s also capped at 200MB in terms of size, too.

Yes, it gets all the data then moves on to map/reduce