[SERVER-29363] Improve the error message on 3.4 for catchUpTimeoutMillis:-1 Created: 24/May/17  Updated: 27/Oct/23  Resolved: 16/Jun/17

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

Type: Task Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Siyuan Zhou
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

When mongod 3.4 attempts to join a replica set with catchUpTimeoutMillis:-1, it fails to join the replica set and logs the error message "BadValue: Invalid value in field "catchUpTimeoutMillis": -1: catch-up timeout must be greater than or equal to 0". -1 is the default value for catchUpTimeoutMillis on 3.6, so this is likely to occur when adding a 3.4 mongod to 3.6 replica set. The error message should explain that in order to add a 3.4 mongod to a 3.6 replica set, the catchUpTimeoutMillis value for the replica set must be changed.



 Comments   
Comment by Tess Avitabile (Inactive) [ 16/Jun/17 ]

Sounds good! I will close this ticket.

Comment by Siyuan Zhou [ 16/Jun/17 ]

tess.avitabile, thanks for filing the ticket! This behavior is actually desired. When we backport the catchup improvements to 3.4 in BACKPORT-134, -1 will be accepted by later versions of 3.4. Downgrading from 3.6 to early versions of 3.4 will run into this issue so I added a note in Documentation Changes Summary of SERVER-26848.

Generated at Thu Feb 08 04:20:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.