[
https://issues.apache.org/jira/browse/SOLR-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-1258:
---------------------------
Fix Version/s: (was: 1.4)
Summary: health check file: relative path evaluated against CWD
(directory were app was started) (was: health check file assumed to be in the
place where application is started)
I agree that this should be considered a bug, but changing the behavior is non
trivial, particularly without confusing existing users on upgrade.
(it would be easier if we were just testing for the existence of the file,
SolrResourceLoader has code to do this in a cascading manner checking the conf
dir, instanceDir, and finally CWD) but since Solr *creates* this file, we need
a concrete location. Long term it would make sense to move this healthcheck
config out of the legacy <admin> section in solrconfig, and make it an init
option on the PingRequestHandler (and move the enable/disable options
processing to that handler) if/when we do that we can change the semantics of
a relative directory.
Since Solr has functioned this way for so long, and it has a simple workaround
i don't think we should hold back 1.4 waiting on this (but if someone comes up
with a nice clean patch, by all means we can move forward)
> 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
> Components: clients - java
> Affects Versions: 1.4
> Environment: Mac
> Reporter: Jay
> Priority: Minor
> Original Estimate: 5h
> Remaining Estimate: 5h
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
