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

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

    Fix Version/s:     (was: 1.4)
                   1.5

I feel that the original concern is addressed. I am pushing it to 1.5 so that 
we can have a detailed look at this later

> 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.5
>
>         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.

Reply via email to