Thanks; that is *exactly* the behavior I'm talking about. I tried to find an
existing issue before posting but missed this one somehow.
Ramkumar R. Aiyengar wrote
> There's already an issue for this,
> https://issues.apache.org/jira/browse/SOLR-5209, we were once bitten by
> the
> same issue, wh
There's already an issue for this,
https://issues.apache.org/jira/browse/SOLR-5209, we were once bitten by the
same issue, when we were trying to relocate a shard. As Mark mentions, the
idea was to do this in zk truth mode, the link also references where that
work is being done.
On 31 Jan 2014 23:1
Mark, I appreciate all the context.
...
Mark Miller-3 wrote
> What do you mean you are hosed?
>
> All the SolrCores should be gone, so why does it matter so much that the
> collection is gone? In the days before the collections api, if you wanted
> to then create the collection again, just creat
We also really need to update the docs to use the collections API rather
than the pre configured core as well. I've been aiming to get the
preconfigured core (and hence collection) out of there by default for
solrcloud, but it's not easy, because I do think it still makes some sense
for non solrclo
It's expected behaviour. It's expected to change with the zk=cluster_truth
mode that I hope we can start squeezing into 4.7.
In the first couple releases of SolrCloud, there was no collections API. I
did not have time to make it. Even what went in for the collections api was
banged out in a very s
