You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Smiley (JIRA)" <ji...@apache.org> on 2014/03/16 06:02:52 UTC
[jira] [Updated] (SOLR-935) DataImportHandler: Add logging to
record failure to acquire lock by DataImporter for a given request
[ https://issues.apache.org/jira/browse/SOLR-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Smiley updated SOLR-935:
------------------------------
Fix Version/s: (was: 4.7)
4.8
> DataImportHandler: Add logging to record failure to acquire lock by DataImporter for a given request
> -----------------------------------------------------------------------------------------------------
>
> Key: SOLR-935
> URL: https://issues.apache.org/jira/browse/SOLR-935
> Project: Solr
> Issue Type: Improvement
> Components: contrib - DataImportHandler
> Environment: Java 6, Tomcat 6.0.18
> Reporter: Karthik K
> Assignee: Noble Paul
> Fix For: 4.8
>
> Attachments: SOLR-935.patch, SOLR-935.patch, SOLR-935.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> There is a possibility of 2 threads to be in DataImporter:runCmd, until before importLock.tryLock() method and then depending on the scheduling - one of them is allowed to pass through from then .
> We need to log the failure of the other as to unable to start because of the failure to acquire the mutex, to distinguish between successful start of import and failure to do so.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org