You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Erick Erickson (JIRA)" <ji...@apache.org> on 2013/03/03 19:03:13 UTC
[jira] [Resolved] (SOLR-727) appcontext, host and port of the Solr
application must be available through API
[ https://issues.apache.org/jira/browse/SOLR-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erick Erickson resolved SOLR-727.
---------------------------------
Resolution: Won't Fix
SPRING_CLEANING_2013 We can reopen if necessary.
> appcontext, host and port of the Solr application must be available through API
> -------------------------------------------------------------------------------
>
> Key: SOLR-727
> URL: https://issues.apache.org/jira/browse/SOLR-727
> Project: Solr
> Issue Type: New Feature
> Reporter: Noble Paul
>
> This is a part of requirement for SOLR-561 . It will be a very nice feature to have the admin console of the master show details of the
> slaves also. To do so The master must know about the slaves. The slaves may be able to register themselves with master but the slaves
> do not know the port number and the context in which the app is deployed.
> The CoreContainer (or any other suitable place) can keep this information with itself so any handler can consume this. Other than the port number everything else is
> available at the startup time.The port number can be obtained soon after the first request is served by the slave .
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org