[
https://issues.apache.org/jira/browse/SOLR-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kay Kay updated SOLR-935:
-------------------------
Attachment: SOLR-935.patch
New Patch submitted for workflow modification to track failures better.
- Logging is removed in favor of more granular notification.
Context:
New field called EventStatus added to Context ( default value - SUCCESS)
During failure - another event is launched , with the EventStatus field in the
Context set to Failure.
Makes it easy for a plugin to keep track of failures when the delta import did
not launch at all (due to synch. issues), compared to log based debugging.
This patch is independent of SOLR-972, but would be extremely efficient if
SOLR-972 is applied though.
> 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.
