[
https://issues.apache.org/jira/browse/SOLR-9059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-9059:
---------------------------------
Description:
Currently the StreamHandler opens the client cache only once when the
StreamHandler is initialized. During a collection reload the client cache is
closed by the closeHook, but not re-opened. This causes null pointers as the
CloudSolrClient sets the zkStateReader = null when it's closed.
A simple fix for this is to have the SolrClientCache clear it's internal map of
clients after closing. The next time the cache is accessed it will then create
new clients.
was:
Currently the StreamHandler opens the client cache only once when the
StreamHandler is initialized. During a collection reload the client cache is
closed by the closeHook, but not re-opened. This causes null pointers as the
CloudSolrClient sets the zkStateReader = null when it's closed.
The fix for this is to move the client cache initialization to the inform()
method so that it's re-created following a collection reload.
> StreamHandler should re-create the client cache following reload
> ----------------------------------------------------------------
>
> Key: SOLR-9059
> URL: https://issues.apache.org/jira/browse/SOLR-9059
> Project: Solr
> Issue Type: Bug
> Reporter: Joel Bernstein
> Assignee: Joel Bernstein
> Fix For: 6.1
>
> Attachments: SOLR-9059.patch
>
>
> Currently the StreamHandler opens the client cache only once when the
> StreamHandler is initialized. During a collection reload the client cache is
> closed by the closeHook, but not re-opened. This causes null pointers as the
> CloudSolrClient sets the zkStateReader = null when it's closed.
> A simple fix for this is to have the SolrClientCache clear it's internal map
> of clients after closing. The next time the cache is accessed it will then
> create new clients.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
