[SERVER-84628] Startup warning in mongos for Read/Write Concern Created: 08/Jan/24 Updated: 01/Feb/24 Resolved: 01/Feb/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 7.0.4 |
| Fix Version/s: | 8.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Wernfried Domscheit | Assignee: | Ali Mir |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | startup_warning | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Requested: |
v7.3, v7.0
|
||||
| Sprint: | Repl 2024-02-05 | ||||
| Participants: | |||||
| Description |
|
I upgraded my Sharded cluster to MongoDB version 7.0.4. When I open a `mongosh`
It is running as a config server, not a shard server as pointed out in the warning message.
|
| Comments |
| Comment by Githook User [ 01/Feb/24 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Author: {'name': 'Ali Mir', 'email': 'ali.mir@mongodb.com', 'username': 'ali-mir'}Message: GitOrigin-RevId: 58d45fe39687e4b8a82c6b7d6abe1c3da17d1f3c | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Noopur Gupta [ 11/Jan/24 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Thanks wernfried.domscheit@sunrise.net , I understand this warning is misleading here. I am going to pass this ticket to Service Architecture team. To Service Architecture Team,
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Wernfried Domscheit [ 11/Jan/24 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Yes, deleting the ReadWriteConcernDefaults (and restart the server) as advised in support article, removes the warning. However, I am running PSA (Primary-Secondary-Arbiter) shards and setting DefaultRWConcern is recommended according to Performance Issues with PSA replica sets
I agree, it is just a warning and does not have any impact. But it is a bit misleading, it triggers the feeling, that you have done something "not optimal". At least in a PSA configuration, it is indeed the recommended setting. I see this warning as really useless. But as said, it is a minor issue, you hardly connect to a config-server directly. Kind Regards
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Noopur Gupta [ 10/Jan/24 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi wernfried.domscheit@sunrise.net for sharing the details. This warning looks like a change made as a part of SERVER-46025. Please let me know if there are probable server issues that you are experiencing apart from this warning. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Wernfried Domscheit [ 09/Jan/24 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi I followed the upgrade instruction and it worked well. I connected directly to the config-server mongod, because I wanted to check whether mongod is properly running after upgrade/restart:
Log is also found in logfile:
The message is also shown when I connect to the replica set:
Logfile is attached. When I connect to a shard server or mongos router then this warning message is not shown.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Noopur Gupta [ 08/Jan/24 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi wernfried.domscheit@sunrise.net, It looks like the above warning is coming from server, but I am a bit unclear about the server it is coming from. In order to understand the problem, can you share more details on cluster: Also, please make sure that you have followed the upgrade instructions in https://www.mongodb.com/docs/manual/release-notes/7.0-upgrade-sharded-cluster/ , to avoid issues related to an upgrade itself. |