[SERVER-4199] chunk boundaries are outdated (likely a split occurred) Created: 03/Nov/11  Updated: 30/Mar/12  Resolved: 14/Nov/11

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

Type: Bug Priority: Major - P3
Reporter: jie chen Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

I use mongodb(v2.0.1) in sharded environments.

10 threads insert to the Mongos

The command in shell to start the mongos is below:
./mongos --port 35000 --configdb "218.241.106.161:28002" --chunkSize 1024

Every few minutes,the mongos log print these message:errmsg: "chunk boundaries are outdated (likely a split occurred)", ok: 0.0

Is anyone tell me how to fill this problem?

thanks.



 Comments   
Comment by Eliot Horowitz (Inactive) [ 14/Nov/11 ]

Yeah - this is fine.

Comment by jie chen [ 14/Nov/11 ]

There are 2 shards and 1 mongos in my sharded environments.

Thank you, your reply set my mind at rest.

Fixed.

Comment by Eliot Horowitz (Inactive) [ 11/Nov/11 ]

These can be ignored.
Just to be sure, how many mongos do you have?

Comment by jie chen [ 04/Nov/11 ]

Hello,Eliot Horowitz,thank you for your attention.

This is a part of the mongos log.

Fri Nov 4 15:00:57 [conn52] warning: splitChunk failed - cmd: { splitChunk: "km_mongodb.snapshot_0", keyPattern:

{ _id: 1.0, executeTime: 1.0 }

, min:

{ _id: ObjectId('4eb27f11cb4a9fa4744c3449'), executeTime: new Date(1320320760890) }

, max:

{ _id: MaxKey, executeTime: MaxKey }

, from: "218.241.106.161:18002", splitKeys: [

{ _id: ObjectId('4eb38da8cb4adac9cf6bbafd'), executeTime: new Date(1320389914458) }

], shardId: "km_mongodb.snapshot_0-_id_ObjectId('4eb27f11cb4a9fa4744c3449')executeTime_new Date(1320320760890)", configdb: "218.241.106.161:28002" } result: { currMin:

{ _id: ObjectId('4eb27f11cb4a9fa4744c3449'), executeTime: new Date(1320320760890) }

, currMax:

{ _id: ObjectId('4eb38da2cb4adac9cf6af5b2'), executeTime: new Date(1320389908458) }

, requestedMin:

{ _id: ObjectId('4eb27f11cb4a9fa4744c3449'), executeTime: new Date(1320320760890) }

, requestedMax:

{ _id: MaxKey, executeTime: MaxKey }

, errmsg: "chunk boundaries are outdated (likely a split occurred)", ok: 0.0 }

When this log appeared, i ran the following command.
db.adminCommand("flushRouterConfig")

But a few minutes later, the warning log appeared again.

Is it a problem? Or it can be ignored?

Comment by Eliot Horowitz (Inactive) [ 03/Nov/11 ]

those message should be warnings, not errors.
can you send a log sample?

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