[
https://issues.apache.org/jira/browse/SOLR-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263178#comment-13263178
]
Greg Bowyer commented on SOLR-723:
----------------------------------
So this is an issue with core swaps in 3.6 I have an interest in fixing this
but does the solr-cloud work make this irrelevant ?
My thoughts were more towards that the jmx tree should just exist for each
alias as a duplicate of the original named core rather than links or aliases
which are quite hard to get most monitoring tools to respect.
> SolrCore & aliasing/swapping may lead to confusing JMX
> ------------------------------------------------------
>
> Key: SOLR-723
> URL: https://issues.apache.org/jira/browse/SOLR-723
> Project: Solr
> Issue Type: Bug
> Affects Versions: 1.3
> Reporter: Henri Biestro
> Priority: Minor
>
> As mentioned by Yonik in SOLR-647, JMX registers the core with its name.
> After swapping or re-aliasing the core, the JMX tracking name does not
> correspond to the actual core anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
