[jira] Commented: (SOLR-935) DataImportHandler: Add logging to record failure to acquire lock by DataImporter for a given request

["Shalin Shekhar Mangar (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709085#action_12709085 ] 

Shalin Shekhar Mangar commented on SOLR-935:
--------------------------------------------

The logging is fine. But I am not sure of the utility of the event listener. Why would one configure an import to be run so frequently that it can trigger the failure to acquire lock? What useful action can one take in this scenario?

> 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
>             Fix For: 1.4
>
>         Attachments: 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.