[SERVER-40050] Better error msg with transactions and enableMajorityReadConcern = false Created: 08/Mar/19 Updated: 29/Oct/23 Resolved: 16/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.11 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kay Kim (Inactive) | Assignee: | Tess Avitabile (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Repl 2019-04-22 |
| Participants: |
| Description |
|
So, when running transactions against a sharded clusters where enableMajorityReadConcern is turned off, I get the following error message pymongo.errors.OperationFailure: Encountered error from Kays-MacBook-Pro-2.local:27018 during a transaction :: caused by :: 'atClusterTime' is not supported when enableMajorityReadConcern=false Could we make it clearer that this means |
| Comments |
| Comment by Githook User [ 16/Apr/19 ] |
|
Author: {'email': 'tess.avitabile@mongodb.com', 'name': 'Tess Avitabile', 'username': 'tessavitabile'}Message: |
| Comment by Kay Kim (Inactive) [ 15/Apr/19 ] |
|
:thumbsup: |
| Comment by Tess Avitabile (Inactive) [ 15/Apr/19 ] |
|
Thank you! |
| Comment by Kay Kim (Inactive) [ 15/Apr/19 ] |
|
tess.avitabile – https://dochub.mongodb.org/core/disabled-read-concern-majority-snapshot-restrictions |
| Comment by Tess Avitabile (Inactive) [ 15/Apr/19 ] |
|
kay.kim, I'm going to change this error to state that "readConcern level 'snapshot' is not allowed in sharded clusters with enableMajorityReadConcern=false". Is there a good documentation link for this? |