[SERVER-22292] Use more reliable mechanism in the mongo shell to wait for process to terminate on windows Created: 25/Jan/16  Updated: 23/Nov/16  Resolved: 29/Jan/16

Status: Closed
Project: Core Server
Component/s: Shell, Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.0.10, 3.2.4, 3.3.2

Type: Bug Priority: Major - P3
Reporter: Sam Kleinman (Inactive) Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 1
Labels: code-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Backport Completed:
Sprint: Build F (01/29/16)
Participants:
Linked BF Score: 0

 Description   

The current mechanism used to wait for processes is not reliable on windows, and leads to situations where we attempt to reset the dbPath before the process is fully terminated and the file handles appear to be open from the perspective of the os.



 Comments   
Comment by Githook User [ 24/Feb/16 ]

Author:

{u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}

Message: SERVER-22292: make wait-for-pid operation more robust on windows

(cherry picked from commit bc065bab600d637b42c78f0622994fbd060aea01)
Branch: v3.2
https://github.com/mongodb/mongo/commit/c7144dab233baf267956e5a074fc5771f6cc1496

Comment by Githook User [ 29/Jan/16 ]

Author:

{u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}

Message: SERVER-22292: make wait-for-pid operation more robust on windows

(cherry picked from commit bc065bab600d637b42c78f0622994fbd060aea01)
Branch: v3.0
https://github.com/mongodb/mongo/commit/187432388ef06de4c02ad5cd70b59c4634abf7a4

Comment by Githook User [ 29/Jan/16 ]

Author:

{u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}

Message: SERVER-22292: make wait-for-pid operation more robust on windows
Branch: master
https://github.com/mongodb/mongo/commit/bc065bab600d637b42c78f0622994fbd060aea01

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