lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noble Paul (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SOLR-935) DataImportHandler: Add logging to record failure to acquire lock by DataImporter for a given request
Date Thu, 21 May 2009 06:16:45 GMT

     [ https://issues.apache.org/jira/browse/SOLR-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Noble Paul updated SOLR-935:
----------------------------

    Attachment: SOLR-935.patch

the partial fix. It logs a warning if it fails to acquire a lock


I am still not convinced of the EventListener part

> 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: Kay Kay
>            Assignee: Noble Paul
>             Fix For: 1.4
>
>         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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message