[SERVER-16984] UpdateLifecycleImpl can return empty collectionMetadata even if ns is sharded Created: 21/Jan/15  Updated: 18/Sep/15  Resolved: 27/Jan/15

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.8.0-rc5
Fix Version/s: 2.6.8, 3.0.0-rc7

Type: Bug Priority: Major - P3
Reporter: Matt Dannenberg Assignee: Randolph Tan
Resolution: Done Votes: 0
Labels: 28qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-16978 sharding/SERVER-7379.js fails with a ... Closed
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Participants:

 Description   

Original description:
sharding/array_shard_key.js fails with a mixed version cluster

If you run the set with a config as follows:

var config = {                                              
        mongos: 2,                                          
        shards: 2,                                          
        other: {                                            
            rs: true,                                      
            mongosOptions: { binVersion: "2.8"},       
            configOptions: { binVersion: oldVersion},       
            rsOptions: {binVersion: ["2.6"], nodes:3}
        }                                                                       
    };                                                      

The test will fail on the line that reads:

assert.writeError(coll.update( value, Object.merge( value, { i : [ 3 ] } ) ));



 Comments   
Comment by Githook User [ 09/Feb/15 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-16984 Do not rely on ShardedConnectionInfo::get() if not doing normal query

(cherry picked from commit d0e977f7310a1befaa48ffb9edee71e9fc004421)

Conflicts:
src/mongo/db/commands/find_cmd.cpp
src/mongo/db/dbcommands.cpp
Branch: v2.6
https://github.com/mongodb/mongo/commit/fba5adfea43de38102eb0cf7abc5cbd0523398ba

Comment by Githook User [ 09/Feb/15 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-16984 UpdateLifecycleImpl can return empty collectionMetadata even if ns is sharded

(cherry picked from commit 70c51f2644cd56678748fbe877e987903f86f3ab)
Branch: v2.6
https://github.com/mongodb/mongo/commit/2bdd030e14b304d970a0e0cc614344f80400c6e6

Comment by Githook User [ 28/Jan/15 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-16984 Do not rely on ShardedConnectionInfo::get() if not doing normal query

(cherry picked from commit d0e977f7310a1befaa48ffb9edee71e9fc004421)
Branch: v3.0
https://github.com/mongodb/mongo/commit/b059fb303695a7ef90a1489d5d5a4cff3ead707d

Comment by Githook User [ 28/Jan/15 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-16984 UpdateLifecycleImpl can return empty collectionMetadata even if ns is sharded

(cherry picked from commit 70c51f2644cd56678748fbe877e987903f86f3ab)
Branch: v3.0
https://github.com/mongodb/mongo/commit/7bdd9fd94db588c87fe1c3096dc113dbccc9a579

Comment by Githook User [ 27/Jan/15 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-16984 Do not rely on ShardedConnectionInfo::get() if not doing normal query
Branch: master
https://github.com/mongodb/mongo/commit/d0e977f7310a1befaa48ffb9edee71e9fc004421

Comment by Githook User [ 27/Jan/15 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-16984 UpdateLifecycleImpl can return empty collectionMetadata even if ns is sharded
Branch: master
https://github.com/mongodb/mongo/commit/70c51f2644cd56678748fbe877e987903f86f3ab

Comment by Randolph Tan [ 23/Jan/15 ]

Verified that this also fails in master build.

Comment by Matt Dannenberg [ 21/Jan/15 ]

I believe this may be the same root cause as SERVER-16978 as they occur in the same cluster configuration.

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