[SERVER-13089] setShardVersion failed host Created: 07/Mar/14  Updated: 11/Jul/16  Resolved: 22/Apr/14

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.2.2
Fix Version/s: 2.4.9

Type: Bug Priority: Major - P3
Reporter: liao Assignee: Randolph Tan
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File log.txt    
Issue Links:
Duplicate
duplicates SERVER-11697 Mongos crash when moveChunk Closed
Related
is related to SERVER-8255 backport sorted chunk cursor to 2.2 Closed
is related to SERVER-11697 Mongos crash when moveChunk Closed
Operating System: ALL
Participants:

 Description   

Help !!!
It happened for four times this month。
this error msg:
setShardVersion failed host: mongo4.mcloud.139.com:20004

{ oldVersion: Timestamp 0|0, oldVersionEpoch: ObjectId('000000000000000000000000'), ns: "mcloud.m_iosyncdetaillog", version: Timestamp 560000|381, versionEpoch: ObjectId('51d37afa0b8c2dd3569f5ed6'), globalVersion: Timestamp 561000|0, globalVersionEpoch: ObjectId('51d37afa0b8c2dd3569f5ed6'), reloadConfig: true, errmsg: "shard global version for collection is higher than trying to set to 'mcloud.m_iosyncdetaillog'", ok: 0.0 }

How to solve it?
thanks a lot。



 Comments   
Comment by liao [ 22/Apr/14 ]

HI,I upgrade to the newer version 2.4.9. After that It don't happen again. Thanks!

Comment by Randolph Tan [ 19/Mar/14 ]

Hi,

Based on the logs, it looks like mongos was not able to refresh the shard version metadata properly. I also noticed that you reported that the version you are running is in 2.2.2, which is a bit old, and would recommend upgrading to the the newer version - 2.2.7 (or better yet, to a newer major version - 2.4.9). The newer versions include several fixes, including SERVER-8255 where mongos can miss some metadata when doing a refresh.

Thanks!

Comment by liao [ 11/Mar/14 ]

My application can not read the records from m_iosyncdetaillog's collection.And mongodb report the errmsg: "shard global version for collection is higher than trying to set to 'mcloud.m_iosyncdetaillog'"。
it go normal until I steped down the primay node(mongo4.mcloud.139.com:20004) or rebooted it.
this issue happen again and again. I performed the above temporary solution again and again.
I am very upset this problem。Give me some advise ?
thank you !

Comment by Eliot Horowitz (Inactive) [ 10/Mar/14 ]

What happens after that? Does everything work?
It can sometimes happen if there are two things happening at the same time and is normal (though the log message is scary).

Generated at Thu Feb 08 03:30:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.