[SERVER-8156] Poor handling of long-running operations in mongo client shell Created: 11/Jan/13  Updated: 29/Jan/18  Resolved: 13/Jul/17

Status: Closed
Project: Core Server
Component/s: Admin, JavaScript
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: eHarmony Matching Assignee: Alyson Cabral (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Participants:

 Description   

When driving configuration from script files, there are a few places – such as when a cluster is starting up, or when an election is taking place – when the cluster passes through a series of relatively long-running state changes, and the script cannot continue until those changes have completed. The scripting interface provided is JavaScript; unfortunately, it is not practical to block in JavaScript, nor are any callbacks provided. We have only a few fallbacks, none of them great:

  • Break the JavaScript into several pieces, invoke them separately from shell scripts, and wait in the shell scripts. Requires polling.
  • Aggressively busy wait in the JavaScript.
  • Write all of this simple setup code in Java or another more-powerful programming language.

It would be more convenient if we could either (1) choose to have mongo itself block until the full state change is complete, or (2) receive a callback when the operation is finished.



 Comments   
Comment by Ian Whalen (Inactive) [ 13/Jul/17 ]

Resolving this ticket as we believe this has gone away with the release of Cloud Manager/Ops Manager.

Comment by Eliot Horowitz (Inactive) [ 22/Jan/13 ]

likely solved by SERVER-8267

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