[ 
https://issues.apache.org/jira/browse/SOLR-7942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14717202#comment-14717202
 ] 

ASF subversion and git services commented on SOLR-7942:
-------------------------------------------------------

Commit 1698203 from [email protected] in branch 'dev/branches/branch_5x'
[ https://svn.apache.org/r1698203 ]

SOLR-7942: Previously removed unlockOnStartup option (LUCENE-6508) now logs 
warning if configured, will be an error in 6.0.  Also improved error msg if an 
index is locked on startup (merge r1698200)

> fix error logging when index is locked on startup, add deprecation warning if 
> unlockOnStartup is configured
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-7942
>                 URL: https://issues.apache.org/jira/browse/SOLR-7942
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Hoss Man
>            Assignee: Hoss Man
>            Priority: Minor
>             Fix For: Trunk, 5.4
>
>         Attachments: SOLR-7942.patch
>
>
> LUCENE-6508 removed support for unlockOnStartup, but the way the changes are 
> made are inconsistent with how other config options have been deprecated in 
> the past, and cause a confusing error message if an index is locked on 
> startup...
> * in 5x, the SolrConfig constructor should log a warning if the 
> unlockOnStartup option is specified (regardless of whether it's true or 
> false) so users know they need to cleanup their configs and change their 
> expectations (even if they never get - or have not yet gotten - a lock 
> problem)
> * in SolrCore, the LockObtainFailedException that is thrown if the index is 
> locked should _not_ say "{{Solr now longer supports forceful unlocking via 
> 'unlockOnStartup'}}"
> ** besides the no/now typo, this wording missleads users into thinking that 
> the LockObtainFailedException error is in some way related to that config 
> option -- creating an implication that using that option lead them to this 
> error.  we shouldn't mention that here.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to