[
https://issues.apache.org/jira/browse/SOLR-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-1258:
---------------------------
Component/s: (was: clients - java)
Description:
The following element gives admin the ability to enable/disable a solr instance
without taking it down
{noformat}
<admin>
<defaultQuery>solr</defaultQuery>
<!-- configure a healthcheck file for servers behind a loadbalancer
-->
<healthcheck type="file">server-enabled</healthcheck>
</admin>
{noformat}
There is a problem with where the file 'server-enabled' is placed. Currently it
appears that file is relative to the place where the server is stared. This
causes trouble to deployment since theoretically the server could be started
anywhere. My suggestion is to have the file relative to solr home so that it
does not dependent on where the server is started.
was:
The following element gives admin the ability to enable/disable a solr instance
without taking it down
<admin>
<defaultQuery>solr</defaultQuery>
<!-- configure a healthcheck file for servers behind a loadbalancer
-->
<healthcheck type="file">server-enabled</healthcheck>
</admin>
There is a problem with where the file 'server-enabled' is placed. Currently it
appears that file is relative to the place where the server is stared. This
causes trouble to deployment since theoretically the server could be started
anywhere. My suggestion is to have the file relative to solr home so that it
does not dependent on where the server is started.
Fix Version/s: 4.0
This issue popped up on the #solr IRC channel today, and looking over the issue
and the code i think that for Solr 4.0 we should bite the bullet and...
* move the configuration of the filename to an init param on the
PingRequestHandler itself
** ie: {{<str name="healthcheckFile">server-enabled</str>}}
** default would be no file (as today) which would mean healthchecking doesn't
apply (just the query)
* change the way the path is resolve to be relative to the dataDir
** much less kludgy and confusing
** something solr should deinitely be able to write to
** way more freindly to multi-core setups
* add a new example where "/admin/ping" is configured in solrconfig.xml
** completely remove the example healthcheck from the {{<admin>}} block
* don't bother trying to be backcompatible with the old configuration
** anyone using that syntax successfully is likely already using an absolute
path, and will notice very quickly that it isn't working, and will be able to
quickly see from CHANGES.txt that if they move that absolute path to the
PingREquestHandler config everything works fine
Any objections?
> health check file: relative path evaluated against CWD (directory were app
> was started)
> ---------------------------------------------------------------------------------------
>
> Key: SOLR-1258
> URL: https://issues.apache.org/jira/browse/SOLR-1258
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 1.4
> Environment: Mac
> Reporter: Jay
> Assignee: Hoss Man
> Priority: Minor
> Fix For: 4.0
>
> Original Estimate: 5h
> Remaining Estimate: 5h
>
> The following element gives admin the ability to enable/disable a solr
> instance without taking it down
> {noformat}
> <admin>
> <defaultQuery>solr</defaultQuery>
> <!-- configure a healthcheck file for servers behind a loadbalancer
> -->
> <healthcheck type="file">server-enabled</healthcheck>
> </admin>
> {noformat}
> There is a problem with where the file 'server-enabled' is placed. Currently
> it appears that file is relative to the place where the server is stared.
> This causes trouble to deployment since theoretically the server could be
> started anywhere. My suggestion is to have the file relative to solr home so
> that it does not dependent on where the server is started.
--
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]
