Alexandre Rafalovitch closed SOLR-300.
    Resolution: Incomplete

There is no way to go forward on this unless somebody really takes it on to 
even validate this.

> create subclass of SingleInstanceLockFactory which warns loadly in the event 
> of concurrent lock attempts
> --------------------------------------------------------------------------------------------------------
>                 Key: SOLR-300
>                 URL: https://issues.apache.org/jira/browse/SOLR-300
>             Project: Solr
>          Issue Type: Wish
>          Components: update
>            Reporter: Hoss Man
>            Priority: Minor
> as noted by yonik in SOLR-240...
> How about SingleInstanceLockFactory to aid in catching concurrency bugs?
>   ...
> or even better, a subclass or other implementation: 
> SingleInstanceWarnLockFactory or SingleInstanceCoordinatedLockFactory that 
> log a failure if obtain() is called for a lock that is already locked.
> we should create a new subclass like Yonik describes and change 
> SolrIndexWriter to use this subclass if/when "single" is specified as the 
> lockType.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to