That's true. And that's my point. A user has defaults set in both and can't
use Solr with 7x. Are you saying that we've never supported switching an
existing collection created with legacyCloud set to true/default to false?
As in fail to load? Nowhere in the upgrade notes, for instance, is any
notice like "If upgrading existing 6x installations with legacyCloud set to
true/ default you must set it to true to use Solr.

Effectively that means they can never get to legacyCloud=false without
hand-editing each and every core.properties file or starting over.

On Oct 16, 2017 5:48 PM, "Varun Thacker" <[email protected]> wrote:

> Hi Erick,
>
> In Solr 6.x legacyCloud defaults to true
> In Solr 7.x legacyCloud defaults to false ( ZK as truth as per
> https://issues.apache.org/jira/browse/SOLR-8256 )
>
> On Mon, Oct 16, 2017 at 5:29 PM, Erick Erickson <[email protected]>
> wrote:
>
>> Check me out to see if I'm hallucinating....
>>
>> Create a collection with 6x _without_ changing legacyCloud (i.e. it
>> defaults to "false).
>> Try opening it with 7x
>> BOOOM
>>
>> I'm seeing:
>> Caused by: org.apache.solr.common.SolrException: No coreNodeName for
>> CoreDescriptor[name=eoe_shard1_replica1;instanceDir=/Users/
>> Erick/apache/solrJiras/branch_7x/solr/example/cloud/node1/
>> solr/eoe_shard1_replica1]
>>
>> The problem is that legacyCloud now defaults to true, and 6x does
>> _not_ save coreNodeName to core.properties files. However,
>> ZkController.checkStateInZk requires that coreNodeName be non-null and
>> it's read from core.properties.
>>
>> I get the exact same behavior when I create a collection in 6x then
>> change legacyCloud to false and restart 6x Solr.
>>
>> I don't think this should hold up 7.1 because of the issue from last
>> week, people affected by this can set legacyCloud=true to get by.
>>
>> Or I need to see an eye doctor.
>>
>> Raise a JIRA?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>

Reply via email to