[SERVER-39390] --eval 'db.shutdownServer()' on 4.0 show warnings not present in previous versions Created: 06/Feb/19 Updated: 08/Jan/24 Resolved: 15/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Shell |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Miguel Angel Nieto | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Sprint: | Service Arch 2019-02-25 |
| Participants: | |
| Case: | (copied to CRM) |
| Description |
|
Hello, The output of the command mongo --eval 'db.shutdownServer()' admin has changed in the latest 4.0 version. 3.4:
3.6:
4.0:
This is confusing, because there are three error messages and the "server should be down" is there in the middle. Those warning messages shouldn't be there to make the message clear and not confuse the users. |
| Comments |
| Comment by Kaloian Manassiev [ 15/Mar/19 ] |
|
The message is telling you that there are some sessions opened by the shell, which could not be closed, because the server is shut down. Given that this happens on server shut down and that the alternative is to entirely mask warnings for inability to close sessions (which sometimes is useful since it indicates the shell possibly left an orphaned session), I am closing this as Works as Designed. |