Details
-
Bug
-
Resolution: Works as Designed
-
Major - P3
-
None
-
None
-
None
-
Sharding
-
Service Arch 2019-02-25
-
(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:
> mongo --eval 'db.shutdownServer()' admin
|
MongoDB shell version v3.4.17
|
connecting to: mongodb://127.0.0.1:27017/admin
|
MongoDB server version: 3.4.17
|
server should be down...
|
3.6:
> mongo --eval 'db.shutdownServer()' admin
|
MongoDB shell version v3.6.8
|
connecting to: mongodb://127.0.0.1:27017/admin
|
MongoDB server version: 3.6.8
|
server should be down...
|
4.0:
> mongo --eval 'db.shutdownServer()' admin
|
MongoDB shell version v4.0.5
|
connecting to: mongodb://127.0.0.1:27017/admin?authSource=admin&gssapiServiceName=mongodb
|
Implicit session: session { "id" : UUID("676a6332-127a-4caa-85a8-51ea5fd88069") }
|
MongoDB server version: 4.0.5
|
server should be down...
|
2019-02-06T12:54:59.356+0000 I NETWORK [js] trying reconnect to 127.0.0.1:27017 failed
|
2019-02-06T12:54:59.356+0000 I NETWORK [js] reconnect 127.0.0.1:27017 failed failed
|
2019-02-06T12:54:59.356+0000 I QUERY [js] Failed to end session { id: UUID("676a6332-127a-4caa-85a8-51ea5fd88069") } due to SocketException: socket exception [CONNECT_ERROR] server [couldn't connect to server 127.0.0.1:27017, connection attempt failed: SocketException: Error connecting to 127.0.0.1:27017 :: caused by :: Connection refused]
|
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.