[
https://issues.apache.org/jira/browse/SOLR-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757773#action_12757773
]
Hoss Man commented on SOLR-1427:
--------------------------------
bq. Hoss, where in the SolrResourceLoader do you see other puts into the
infoRegistry happening?
I didn't say i saw other puts in SolrResourceLoader, I said now there are puts
in SolrResourceLoader, but none of the existing puts (in other files) were
removed even though in some cases they are now redundent.
One Example...
RequestHandlers.initHandlersFromConfig calls core.createRequestHandler which
uses SolrResourceLoader to create every RequestHandler, and then
initHandlersFromConfig also calls RequestHandlers.register which adds the
handler to core.getInfoRegistry().
But we problem shouldn't just remove any redundent looking puts on
core.getInfoRegistry(), because they night not be redundant in all cases
(RequestHandler.register could conceivable be used to register a Handler that
some other plugin created w/o using SOlrResourceLoader) ... so the redundancy
isn't necessarily bad, it just raised a red flag -- and explains where the
thread hang came from: registering RequestHandlers twice didn't cause the hang,
it was the fact that the second registration happened during the latch on the
searchExecutor.
> SearchComponents aren't listed on registry.jsp
> ----------------------------------------------
>
> Key: SOLR-1427
> URL: https://issues.apache.org/jira/browse/SOLR-1427
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
> Assignee: Grant Ingersoll
> Priority: Minor
> Fix For: 1.4
>
> Attachments: SOLR-1427.afterlatch.patch, SOLR-1427.patch,
> SOLR-1427.patch, SOLR-1427.patch
>
>
> SearchComponent implements SolrInfoMBean using getCategory() of "OTHER" but
> they aren't listed on the registry.jsp display of loaded plugins.
> This may be a one-of-glitch because of the way SearchComponents get loaded,
> or it may indicate some other problem with the infoRegistry.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
