[SERVER-18835] change shard collection's 'expireAfterSeconds' cause moveChunk fail Created: 05/Jun/15 Updated: 28/Oct/15 Resolved: 28/Oct/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance, Sharding |
| Affects Version/s: | 2.6.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | cswuyg | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | In shard cluster |
| Participants: |
| Description |
|
mongod version: 2.6.5 , name: "__-1", ns: "xx.xx", expireAfterSeconds: 5227200 } error: IndexOptionsConflict Index with name: __-1 already exists with different options After I restart all shards the moveChunk works fine, Is it a 'cached' bug? |
| Comments |
| Comment by Sam Kleinman (Inactive) [ 30/Jun/15 ] |
|
Sorry for not getting back to you sooner. We're still investigating this behavior, but I wanted ask you to clarify the method that you used to rebuild the index with the expire seconds option. Can you provide the sequence of operations in Python using PyMongo, or JavaScript and the mongo shell, as well as how you created the MongoDB connection, when you modifed the index? Regards, |