[SERVER-3900] Should indexes automatically upgrade to "v1" on a replication initial sync / resync? Created: 19/Sep/11  Updated: 11/Jul/16  Resolved: 30/Sep/11

Status: Closed
Project: Core Server
Component/s: Index Maintenance, Replication
Affects Version/s: 2.0.0
Fix Version/s: 2.0.1, 2.1.0

Type: Bug Priority: Major - P3
Reporter: Mathias Stearn Assignee: Kristina Chodorow (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Operating System: ALL
Participants:

 Description   

If index is explicitly v:0 it will be created as that rather than v:1 on the new slave.



 Comments   
Comment by auto [ 30/Sep/11 ]

Author:

{u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}

Message: upgrade indexes on resync SERVER-3900
Branch: v2.0
https://github.com/mongodb/mongo/commit/fec06cfe915a53e5e53cd2b8e114c99814fbe436

Comment by Kristina Chodorow (Inactive) [ 29/Sep/11 ]

It is in master but hasn't been backported to 2.0. Let me know if you'd like me to do that backport.

Comment by Eliot Horowitz (Inactive) [ 29/Sep/11 ]

Ok - lets go with auto upgrading on sync.
Is that what is not in master and v2.0?
If so - can just resolve.

Comment by Kristina Chodorow (Inactive) [ 20/Sep/11 ]

It looks like compact upgrades the indexes.

Comment by Dwight Merriman [ 20/Sep/11 ]

wonder if one couldn't just reindex each collection. that might even be faster.

by the way - what does compact() do?

Comment by Kristina Chodorow (Inactive) [ 19/Sep/11 ]

Then you probably want to wait for the official backport. And yes, 2.0.1 is just a bugfix release with backports like this.

Comment by Volodymyr Gren [ 19/Sep/11 ]

don't know i'd like smth that can be 100% be deployed on prod

btw - according to https://jira.mongodb.org/browse/SERVER#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel

2.0.1 will be in 10 days?

Comment by Kristina Chodorow (Inactive) [ 19/Sep/11 ]

It hasn't been backported yet, are you interested in a custom build, waiting for the official backport, or the development branch build?

Comment by Volodymyr Gren [ 19/Sep/11 ]

can we have a binary build with that fix for linux x64 ?

Comment by Kristina Chodorow (Inactive) [ 19/Sep/11 ]

@Vladimir: the most up-to-date information on release dates is at https://jira.mongodb.org/browse/SERVER#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel

Comment by auto [ 19/Sep/11 ]

Author:

{u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}

Message: upgrade indexes on resync SERVER-3900
Branch: master
https://github.com/mongodb/mongo/commit/40ca7c408d3560a4909627fda6b51b3ee334e667

Comment by Volodymyr Gren [ 19/Sep/11 ]

when 2.0.1 is expected to be a production release?

Comment by Mathias Stearn [ 19/Sep/11 ]

I think this will also make repair upgrade indexes, which is probably a good thing.

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