You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2007/07/13 20:52:04 UTC
[jira] Created: (SOLR-300) create subclass of
SingleInstanceLockFactory which warns loadly in the event of concurrent
lock attempts
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: Improvement
Reporter: Hoss Man
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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-300) create subclass of
SingleInstanceLockFactory which warns loadly in the event of concurrent
lock attempts
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man updated SOLR-300:
--------------------------
Component/s: update
Priority: Minor (was: Major)
Issue Type: Wish (was: Improvement)
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.