lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shawn Heisey <apa...@elyograg.org>
Subject Re: SOLR Exception with SOLR Cloud 5.1 setup on Linux
Date Tue, 28 Jul 2015 22:54:19 GMT
On 7/28/2015 11:06 AM, sangeetha.subramanian@gtnexus.com wrote:
> Yes I did create two shards and two replicas and later dropped the other one.. Version
is 5.1 . can you please tell me how this can be fixed ??

That's why you're having trouble.  Half the index disappeared when you
deleted that shard, along with the information telling SolrCloud how to
hash documents into that shard.  Now it has no information about where
to index documents matching the hash range of the deleted shard, so an
error is returned when you try.  Adding and deleting shards does *NOT*
change document distribution.  There are only two ways to change how
documents are hashed among your shards:  Either you can split a shard,
making new ones where each has a portion of the hash range of the
original, or you can create an entirely new collection.

To get out of the hole you're in now, either build a new collection with
the actual shard count that you want so it's correctly set up, or edit
the clusterstate in zookeeper to change the hash range (change 80000000
to 00000000) and then restart all your solr servers.  For the latter
option, a complete reindex is also a good idea.

If you build a new collection, you can delete the old one and then set
up a collection alias so that the original name works with the new
collection.  A reindex will be required, because the new collection will
initially have no documents.

Thanks,
Shawn


Mime
View raw message