[SERVER-21991] Sharding not working on 3.2.0 Created: 22/Dec/15  Updated: 22/Dec/15  Resolved: 22/Dec/15

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

Type: Question Priority: Critical - P2
Reporter: saranjeet singh Assignee: Kelsey Schubert
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Os: amazon linux 2015.09. mongodb version 3.2.0


Participants:

 Description   

Hello,

I have below set up:
config server : 1
Query router : 1
shard node : 2

I have imported my database to shard-1 , then from query server enabled sharding on db and collections as well. But, data did not sharded to 2nd shard node.

I am getting below error :

I NETWORK  [initandlisten] connection accepted from 192.168.22.11:38942 #40 (5 connections now open)
2015-12-22T12:50:51.398+0000 W SHARDING [migrateThread] aborting migration, shard is missing 1 indexes and collection is not empty. Non-trivial index creation should be scheduled manually
2015-12-22T12:50:51.398+0000 I NETWORK  [migrateThread] scoped connection to test-shard-2:27020 not being returned to the pool
2015-12-22T12:50:51.400+0000 I SHARDING [migrateThread] about to log metadata event into changelog: { _id: "test-shard-1-2015-12-22T12:50:51.399+0000-5679472b07c7eb8ed8577b95", server: "test-sh
ard-1", clientAddr: "", time: new Date(1450788651399), what: "moveChunk.to", ns: "GithubMeta.repository", details: { min: { _id: MinKey }, max: { _id: 0 }, note: "aborted", errmsg: "aborting migration, shard is missing 1 indexes and collection is not empty. Non-trivial index creation should be scheduled manually" } }
2015-12-22T12:50:51.406+0000 W SHARDING [migrateThread] cannot remove pending chunk [{ _id: MinKey }, { _id: 0 }), this shard does not contain the chunk
2015-12-22T12:50:51.406+0000 W SHARDING [migrateThread] cannot remove pending chunk [{ _id: MinKey }, { _id: 0 }), this shard does not contain the chunk

Please help. I am new to mongo server administration.

Thanks and Regards,
Saranjeet Singh



 Comments   
Comment by Kelsey Schubert [ 22/Dec/15 ]

Hi saran,

Thank you for your report.

We have made a couple observations:

  1. The error message you are receiving only exists in 2.6 version of MongoDB. Running a mixed cluster with members of both 2.6 and 3.2 is not a valid configuration
  1. It appears that you have imported your data directly into the shard, bypassing the mongos. This does not work in a sharded closet and operations must be performed via the mongos.

Please note that SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-users group or Stack Overflow with the mongodb tag. Additionally, you may want to review our documentation on sharding here, as well as upgrade procedures here

Kind regards,
Thomas

Comment by saranjeet singh [ 22/Dec/15 ]

Hello,

This error I got from shard-1 node.

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