[
https://issues.apache.org/jira/browse/SOLR-17269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17872248#comment-17872248
]
ASF subversion and git services commented on SOLR-17269:
--------------------------------------------------------
Commit b57763e703d409c50a2338b51f6fac24f73cce56 in solr's branch
refs/heads/branch_9x from patsonluk
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=b57763e703d ]
SOLR-17269, SOLR-17386: Fixed SyntheticSolrCore reload issue (#2607)
(cherry picked from commit 83e5778af58c5f037da0ce4fdaaf7bef019e9868)
> 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
> Fix For: 9.7
>
> 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
