[
https://issues.apache.org/jira/browse/OODT-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann resolved OODT-591.
------------------------------------
Resolution: Not a Problem
if the file doesn't get completely ingested, then the catalog is left in an odd
state sometimes. Unfortunately there is no easy/quick way around this and it's
easy to purge these either via a DB query or Lucene query.
> questionable result during file transfer on crawler ingest
> ----------------------------------------------------------
>
> Key: OODT-591
> URL: https://issues.apache.org/jira/browse/OODT-591
> Project: OODT
> Issue Type: Question
> Components: crawler, file manager, radix
> Affects Versions: 0.6
> Environment: radix under centOS
> Reporter: Arni Sumarlidason
> Labels: crawler, failure, radix
> Fix For: 0.9
>
> Attachments: Screenshot.png, ingest.err.log
>
>
> What is the expect result when the crawler fails to move a file due to disk
> constraints?
> In my experience, and I will attach some files for your reference, the file
> that failed to transfer remains in the file manager's catalogue partially
> transferred. At this point the crawler has exited with a failure. Remnants of
> the ingested file remain in the archive.
> I would expect the file to be removed from the catalogue on failure since
> ingestion was reported as a failure and file moved to failed directory.
> please advise.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
