[
https://issues.apache.org/jira/browse/SOLR-15258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17415179#comment-17415179
]
Ilan Ginzburg commented on SOLR-15258:
--------------------------------------
[~nazerke] I believe I have found an issue in this code (I didn't run it but
[~dsmiley] confirmed).
From {{CoreContainer.load()}}, when {{ZkContainer.initZooKeeper()}} is called,
if the {{bootstrap_conf}} property is {{true}} then
{{ConfigSetService.bootstrapConf()}} is called.
If cores are then discovered this in turn calls
{{getConfigSetService().uploadConfig()}} on the {{CoreContainer}}.
{{CoreContainer.getConfigSetService()}} then returns the uninitialized
{{coreConfigService}}, likely leading to a null pointer exception (given
{{coreConfigService}} is initialized later in the {{load()}} method).
> ConfigSetService: add CRUD operations, subsume ZkConfigManager
> ---------------------------------------------------------------
>
> Key: SOLR-15258
> URL: https://issues.apache.org/jira/browse/SOLR-15258
> Project: Solr
> Issue Type: Improvement
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Minor
> Fix For: main (9.0)
>
> Time Spent: 9.5h
> Remaining Estimate: 0h
>
> Increase the scope of ConfigSetService with CRUD operations and anything else
> so that it can be the one place to go for anything ConfigSet related. This
> should be easier to understand/maintain, and also improve the efficacy of the
> plug-ability of ConfigSetService.
> It's likely ZkConfigManager will disappear, with most of its functionality
> moving into CloudConfigSetService (ZK). A number of places in SolrCloud use
> ZkConfigManager that will change to use the ConfigSetService instead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
