I raised a JIRA with this, SOLR-8257
-
Best regards
--
View this message in context:
http://lucene.472066.n3.nabble.com/DELETEREPLICA-command-shouldn-t-delete-de-last-replica-of-a-shard-tp4239054p4239139.html
Sent from the Solr - User mailing list archive at Nabble.com.
On Sun, Nov 8, 2015 at 11:20 PM, Erick Erickson
wrote:
> I see your point. In the custom routing case where it _is_ reasonable
> to delete all replicas in a shard, DELETESHARD does the trick.
>
> It's reasonable to raise a JIRA I think so we have a record of the
> discussion/decision.
>
There is
I see your point. In the custom routing case where it _is_ reasonable
to delete all replicas in a shard, DELETESHARD does the trick.
It's reasonable to raise a JIRA I think so we have a record of the
discussion/decision.
Erick
On Sun, Nov 8, 2015 at 9:13 AM, Yago Riveiro wrote:
> I don't know i
Thanks.
But since the docs are incorrect as far as current behavior is
concerned, I'll change the info on the CWiki to reflect the current
state of affairs.
I just did a brief test with creating a collection with legacyCloud
set to false and no change.
Erick
On Thu, Sep 4, 2014 at 12:06 PM, Sha
Yeah, this all feedbacks into the ZK as Truth mode that we've been talking
about. The documentation is misleading because yes, if a node comes back
up, then it will add itself to the cluster state. There are plans to change
that behaviour once we've thought through more use-cases and are ready to
b
