[SERVER-33242] Erroneous Warning in Shell regarding replicaset protocol version Created: 09/Feb/18  Updated: 02/Apr/18  Resolved: 09/Mar/18

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

Type: Bug Priority: Major - P3
Reporter: Chad Kreimendahl Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-30345 Add startupWarning when running with pv0 Closed
Participants:

 Description   

Getting this warning:

2018-01-11T11:11:50.510-0600 I REPL     [replexec-0] ** WARNING: This replica set was configured with protocol version 0.
2018-01-11T11:11:50.511-0600 I REPL     [replexec-0] **          This protocol version is deprecated and subject to be removed
2018-01-11T11:11:50.512-0600 I REPL     [replexec-0] **          in a future version.

With this rs.config():

{
        "_id" : "domainDEV001",
        "version" : 13,
        "protocolVersion" : NumberLong(1),
        "members" : [
                {
                        "_id" : 0,
                        "host" : "dev-mongo001.dbx.domain.us:27017",
                        "arbiterOnly" : false,
                        "buildIndexes" : true,
                        "hidden" : false,
                        "priority" : 3,
                        "tags" : {
                                "dc" : "ev"
                        },
                        "slaveDelay" : NumberLong(0),
                        "votes" : 1
                },
                {
                        "_id" : 1,
                        "host" : "dev-mongo002.dbx.domain.us:27017",
                        "arbiterOnly" : false,
                        "buildIndexes" : true,
                        "hidden" : false,
                        "priority" : 4,
                        "tags" : {
                                "dc" : "ev"
                        },
                        "slaveDelay" : NumberLong(0),
                        "votes" : 1
                },
                {
                        "_id" : 2,
                        "host" : "dev-mongo003.dbx.domain.us:27017",
                        "arbiterOnly" : false,
                        "buildIndexes" : true,
                        "hidden" : false,
                        "priority" : 1,
                        "tags" : {
                                "dc" : "ev"
                        },
                        "slaveDelay" : NumberLong(0),
                        "votes" : 1
                }
        ],
        "settings" : {
                "chainingAllowed" : true,
                "heartbeatIntervalMillis" : 2000,
                "heartbeatTimeoutSecs" : 10,
                "electionTimeoutMillis" : 10000,
                "catchUpTimeoutMillis" : 60000,
                "catchUpTakeoverDelayMillis" : 30000,
                "getLastErrorModes" : {
 
                },
                "getLastErrorDefaults" : {
                        "w" : 1,
                        "wtimeout" : 0
                }
        }
}



 Comments   
Comment by Kelsey Schubert [ 09/Mar/18 ]

Hi sallgeud,

We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Regards,
Kelsey

Comment by Spencer Brody (Inactive) [ 09/Feb/18 ]

I suspect the issue is that we don't clear the warning out of the startupWarnings log when we reconfig from pv0 to pv1. So you'll see that warning if the node has been running pv0 at any point since the node was up. sallgeud, does the message go away if you restart the node you are connected to?

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