[SERVER-57380] Improve "InvalidOptions: read concern level snapshot is only valid in a transaction" message during cluster incompatibility Created: 03/Jun/21  Updated: 29/Oct/23  Resolved: 01/Jul/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 5.0.0-rc0
Fix Version/s: 5.0.2, 5.1.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Dmitry Agranat Assignee: Allison Easton
Resolution: Fixed Votes: 0
Labels: 5.0-dogfooding, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
is related to SERVER-57381 Make the wrong upgrade/downgrade orde... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.0
Sprint: Sharding EMEA 2021-06-28
Participants:

 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 22/Jul/21 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com'}

Message: SERVER-57380 Improve "InvalidOptions: read concern level snapshot is only valid in a transaction" message during cluster incompatibility
Branch: v5.0
https://github.com/mongodb/mongo/commit/5d01916fbbc698a6029a3e9f0e1f97d32c3a3762

Comment by Githook User [ 01/Jul/21 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com'}

Message: SERVER-57380 Improve "InvalidOptions: read concern level snapshot is only valid in a transaction" message during cluster incompatibility
Branch: master
https://github.com/mongodb/mongo/commit/337fd98d07c74634c50839c9326521a0bc8a5a6e

Comment by Kaloian Manassiev [ 04/Jun/21 ]

Proposing to make this ticket neweng and just enhance the error message from the CatalogCache to catch InvalidOptions and append "This error could be due to the fact that the config server is running an older version". Alternatively, we can even check the wire version of the response (if available) at the level of when we send requests to the config server.

Comment by Kaloian Manassiev [ 03/Jun/21 ]

I would like to add here that this is just one of many possible errors that could potentially happen during upgrade order swap. Even if we improve it, there could be numerous other that we don't know of. As a general rule, during development we don't invest too much time to make the wrong upgrade order user-friendly (as long as it doesn't lose data).

Generated at Thu Feb 08 05:41:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.