thanks mark.
That worked great.
-Mike
Mark Miller wrote:
Honestly, I'm not sure. Yonik did some testing around upgrading from
4.0 to 4.1 and said this was fine - but it sounds like perhaps there
are some hitches.
- Mark
On Mar 4, 2013, at 3:35 PM, "mike st. john"<mstj...@gmail.com> wrote:
Mark,
the odd piece here i think was, this was a 4.0 collection numShards=4
etc etc.
moved to 4.1, i would assume the doc router would have been set to
compositeId, not implicit, or is the move from 4.0 to 4.1 a complete
rebuild from the collections up?
-Mike
Mark Miller wrote:
On Mar 4, 2013, at 3:27 PM, Michael Della
Bitta<michael.della.bi...@appinions.com> wrote:
I personally don't know of one other than starting over with a new
collection, but I'd love to be proven wrong, because I'm actually
in the
same boat as you!
I think it might be possible by using a zookeeper tool to edit
clusterstate.json (i like using the zk eclipse plugin for this type
of thing).
If you create a new collection with the same number of shards and be
sure to specify num shards, you will see the hash ranges that should
be used for each shard. Try updating the clusterstate.json to match
- with the right router and hash ranges.
- Mark
