You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/11/30 19:07:00 UTC
[jira] [Commented] (SOLR-12182) Can not switch urlScheme in 7x if
there are any cores in the cluster
[ https://issues.apache.org/jira/browse/SOLR-12182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17240984#comment-17240984 ]
ASF subversion and git services commented on SOLR-12182:
--------------------------------------------------------
Commit a0492840ee8690ddf48369665c744d16c7dd30cb in lucene-solr's branch refs/heads/master from Timothy Potter
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=a049284 ]
SOLR-12182: Don't persist base_url in ZK as the scheme is variable, compute from node_name instead (#2010)
> Can not switch urlScheme in 7x if there are any cores in the cluster
> --------------------------------------------------------------------
>
> Key: SOLR-12182
> URL: https://issues.apache.org/jira/browse/SOLR-12182
> Project: Solr
> Issue Type: Bug
> Affects Versions: 7.0, 7.1, 7.2
> Reporter: Anshum Gupta
> Assignee: Timothy Potter
> Priority: Major
> Fix For: master (9.0)
>
> Attachments: SOLR-12182.patch, SOLR-12182_20200423.patch
>
> Time Spent: 5h
> Remaining Estimate: 0h
>
> I was trying to enable TLS on a cluster that was already in use i.e. had existing collections and ended up with down cores, that wouldn't come up and the following core init errors in the logs:
> *org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: replica with coreNodeName core_node4 exists but with a different name or base_url.*
> What is happening here is that the core/replica is defined in the clusterstate with the urlScheme as part of it's base URL e.g. *"base_url":"http:hostname:port/solr"*.
> Switching the urlScheme in Solr breaks this convention as the host now uses HTTPS instead.
> Actually, I ran into this with an older version because I was running with *legacyCloud=false* and then realized that we switched that to the default behavior only in 7x i.e while most users did not hit this issue with older versions, unless they overrode the legacyCloud value explicitly, users running 7x are bound to run into this more often.
> Switching the value of legacyCloud to true, bouncing the cluster so that the clusterstate gets flushed, and then setting it back to false is a workaround but a bit risky one if you don't know if you have any old cores lying around.
> Ideally, I think we shouldn't prepend the urlScheme to the base_url value and use the urlScheme on the fly to construct it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org