MongoDB 1.5.5 (unstable) Released

[Eliot Horowitz]

MongoDB 1.5.5 is out and ready for testing.
1.5.5 is in the 1.5 development series and is not intended for production.

We're getting very close to 1.6.0, so we would appreciate as many
people testing as possible.
In 1.5.5 sharding should be very testable so the more people playing
with it the better.

Some notable changes:
- numerous sharding enhancements
- compound key support for sharding
- better query yielding
- geo $box fixes
- Windows service logging fixes

Downloads: http://www.mongodb.org/downloads
Change Log: http://jira.mongodb.org/browse/SERVER/fixforversion/10169

-Eliot

[Phil Plante]

Is anyone else having problems with chunkSize not being set?

I have tried chunkSize=1 3 different times with 1.5.5, I was running
everything locally as a test. My data was 200mb, shouldn't this have
been split between my two shards somewhat evenly?

[Eliot Horowitz]

Can you send the output of db.printShardingStatus()?
may want to start a new thread if its not obvious from that

> --
> You received this message because you are subscribed to the Google Groups "mongodb-user" group.
> To post to this group, send email to mongod...@googlegroups.com.
> To unsubscribe from this group, send email to mongodb-user...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/mongodb-user?hl=en.
>
>

[Phil Plante]

Here are the stats output:
> db.stats()
{
"collections" : 6,
"objects" : 200354,
"avgObjSize" : 811.1187997244876,
"dataSize" : 162510896,
"storageSize" : 195025664,
"numExtents" : 26,
"indexes" : 4,
"indexSize" : 6578176,
"fileSize" : 1006632960,
"ok" : 1
}

Here is sharding status output:
> db.printShardingStatus()
--- Sharding Status ---
sharding version: { "_id" : 1, "version" : 3 }
shards:
{ "_id" : "shard1", "host" : "127.0.0.1:10001" }
{ "_id" : "shard2", "host" : "127.0.0.1:10002" }
databases:
{ "_id" : "admin", "partitioned" : false, "primary" : "config" }
{ "_id" : "dataengine", "partitioned" : true, "primary" : "shard2" }
{ "_id" : "mongolog", "partitioned" : false, "primary" : "shard2" }
{ "_id" : "666b49556536b55f65180f5fe0c24145", "partitioned" : false,
"primary" : "shard1" }
{ "_id" : "81dbc055ce6aa07007b908f57d2547ca", "partitioned" : true,
"primary" : "shard1", "sharded" : { "81dbc055ce6aa07007b908f57d2547ca.
4c4129ef2e58ed0c7d0001f5" : { "key" : { "_id" : 1 }, "unique" :
false } } }
81dbc055ce6aa07007b908f57d2547ca.4c4129ef2e58ed0c7d0001f5 chunks:
{ "_id" : { $minKey : 1 } } -->> { "_id" : { $maxKey : 1 } } on :
shard1 { "t" : 1000, "i" : 0 }

[Phil Plante]

Im using MapReduce to calculate some aggregated data, and I end up
seeing activity on shard1, none on shard2.

My mongos is started with chunkSize=1

[Phil Plante]

Any idea on this?

[Tim Hawkins]

It sounds like the server has not picked up on the "--chunkSize 1" option for some reason.

I have recently created a three shard server on 1.5.5 running on os x 10.6, with a chunkSize of 1, and it all worked fine, so the 1.5.5 release seems to be able to do what you ask.

@eliot, it would be useful to have printShardingStatus dump the chunksSize, is there any other way to determine from the config server collections what the requested chunkSize that mongos is using is?.