[SERVER-47918] Improve "replSet too much data to roll back" to include reason for "too much data" limit Created: 04/May/20  Updated: 06/Dec/22  Resolved: 11/May/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Eric Sommer Assignee: Backlog - Replication Team
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to DOCS-13626 [Server] 300MB rollback limit still e... Closed
is related to SERVER-23392 Increase Replication Rollback (Data) ... Closed
Assigned Teams:
Replication
Participants:

 Description   

There are two methods used for rollback:
1. "Rollback to Timestamp" (default)
2. "Rollback-via-Refetch" - used when "enableMajorityReadConcern=false"

Under condition #1 the 300MB rollback limit is no longer enforced post-4.0. But under condition #2, the limit is still enforced, and users can still get the following assertions:

2020-05-03T00:11:01.079Z F -        [rsBackgroundSync] Fatal Assertion 40507 at src/mongo/db/repl/rs_rollback.cpp 1515
2020-05-03T00:11:01.079Z F ROLLBACK [rsBackgroundSync] Unable to complete rollback. A full resync may be needed: UnrecoverableRollbackError: replSet too much data to roll back.

It would be helpful to include the information that the rollback limit was enforced because "enableMajorityReadConcern=false".


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