Thanks Erick!
As I said, user error! ;)
Tom
On 21/11/17 22:41, Erick Erickson wrote:
I think you're confusing shards with replicas.
numShards is 2, each with one replica. Therefore half of your docs
will wind up on one replica and half on the other. If you're adding a
single doc, by definition it'll be placed on only one of the two
shards. If your shards had multiple replicas, all of the replicas
associated with that shard would change.
Best,
Erick
On Tue, Nov 21, 2017 at 12:56 PM, Tom Barber <magicaltr...@apache.org> wrote:
Hi folks
I can't find an answer to this, and its clearly user error, we have a
collection in solrcloud that is started numShards=2 replicationFactor=1 solr
seems happy the collection seems happy. Yet when we post and update to it and
then look at the record again, it seems to only affect one core and not the
second.
What are we likely to be doing wrong in our config or update to prevent the
replication?
Thanks
Tom
--
Spicule Limited is registered in England & Wales. Company Number: 09954122.
Registered office: First Floor, Telecom House, 125-135 Preston Road,
Brighton, England, BN1 6AF. VAT No. 251478891.
All engagements are subject to Spicule Terms and Conditions of Business.
This email and its contents are intended solely for the individual to whom
it is addressed and may contain information that is confidential,
privileged or otherwise protected from disclosure, distributing or copying.
Any views or opinions presented in this email are solely those of the
author and do not necessarily represent those of Spicule Limited. The
company accepts no liability for any damage caused by any virus transmitted
by this email. If you have received this message in error, please notify us
immediately by reply email before deleting it from your system. Service of
legal notice cannot be effected on Spicule Limited by email.
