Thanks for the explaination Erick!. I will try out your recommendation.
On Sun, Apr 17, 2016 at 3:34 PM, Erick Erickson
wrote:
> bq: So inorder for me move the shards to its own instances, I will have to
> take a down time and move the newly created shards & replicas to its own
> instances.
>
bq: So inorder for me move the shards to its own instances, I will have to
take a down time and move the newly created shards & replicas to its own
instances.
No, this is not true.
The easiest way to move things around is use the collections API
ADDREPLICA command after splitting.
Let's call th
Erik thanks for the reply. In my current prod setup I anticipate the number
of documents to grow almost 5 times by the end of the year and therefore
planning on how to scale when required. We have high query volume and
growing dataset, that is why would like to scale by sharding & replication.
In
Why don't you think splitting the shards will do what you need?
Admittedly it will have to be applied to each shard and will
double the number of shards you have, that's the current
limitation. At the end, though, you will have 4 shards when
you used to have 2 and you can move them around to whatev
I found ticket https://issues.apache.org/jira/browse/SOLR-5025 which talks
about sharding in solrcloud. Are there any plans to address this issue in
near future?
Can any of the users on the forum comment how they are handling this
scenario in production?
Thanks
On Fri, Apr 15, 2016 at 4:28 PM, Jay
Hi,
I have an existing collection which has 2 shards, one on each node in the
cloud. Now I want to split the existing collection into 3 shards because of
increase in volume of data. And create this new shard on a new node in the
solrCloud.
I read about splitting a shard & creating a shard, but n
