[
https://issues.apache.org/jira/browse/SOLR-17269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17859899#comment-17859899
]
David Smiley commented on SOLR-17269:
-------------------------------------
Pushed to 9x.
https://github.com/apache/solr/commit/ea860477922c2fe7d25274ae7d66de11a0dc19cd
Dunno why there wasn't a bot comment when I pushed
FYI [~epugh], you had erroneously added the CHANGES.txt item on branch_9x under
the backport of an unrelated issue. An example of hour CHANGES.txt management
is annoying and error-prone.
> Don't publish synthetic collection to ZK in solr coordinator nodes
> ------------------------------------------------------------------
>
> Key: SOLR-17269
> URL: https://issues.apache.org/jira/browse/SOLR-17269
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 9.6
> Reporter: Patson Luk
> Priority: Major
> Time Spent: 5h 20m
> Remaining Estimate: 0h
>
> Coordinator node uses a "synthetic collection/core" (Prefixed with
> `.sys.COORDINATOR-COLL-`) to proxy queries to other data node.
> However, such collection was actually registered to the ZK as well (like a
> normal collection). This could be problematic at times when we have other
> tools that read the cluster status and are mistaken that as a real collection.
> The proposal here is the introduction of a new `SyntheticSolrCore` which
> subclasses `SolrCore`, such core bypasses ZK publish steps of regular core
> (and avoid creating core.properties etc) hence preventing other tools from
> detecting such synthetic collection.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
