I have committed a fix for 4.6
http://issues.apache.org/jira/browse/SOLR-5295
On Wed, Oct 2, 2013 at 10:34 AM, Shalin Shekhar Mangar
shalinman...@gmail.com wrote:
Thanks for reporting this Brett. This is indeed a bug. A workaround is to
specify replicationFactor=1 with the createShard
Shalin,
Thanks for the fix. There's still part of the underlying issue that I
consider a bug or a documentation problem: how do I adjust maxShardsPerNode
after my collection has been created, and/or how can I disable it being
checked/used at all? It seems odd to me that I have to set it to an odd
You are right Brett. There's plenty more to be done. I can't promise when
all these improvements will be done but at least some should make it to 4.6
https://issues.apache.org/jira/browse/SOLR-5128
On Wed, Oct 2, 2013 at 9:35 PM, Brett Hoerner br...@bretthoerner.comwrote:
Shalin,
Thanks for
It seems that changes in 4.5 collection configuration now require users to
set a maxShardsPerNode (or it defaults to 1).
Maybe this was the case before, but with the new CREATESHARD API it seems a
very restrictive. I've just created a very simple test collection on 3
machines where I set
Related, 1 more try:
Created collection starting with 4 shards on 1 box. Had to set
maxShardsPerNode to 4 to do this.
Now I want to roll over my time window, so to attempt to deal with the
problems noted above I delete the oldest shard first. That works fine.
Now I try to add my new shard,
Thanks for reporting this Brett. This is indeed a bug. A workaround is to
specify replicationFactor=1 with the createShard command which will create
only one replica even if maxShardsPerNode=1000 at collection level.
I'll open an issue.
On Wed, Oct 2, 2013 at 7:25 AM, Brett Hoerner
