[
https://issues.apache.org/jira/browse/NIFI-6367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16865843#comment-16865843
]
Evan Reynolds commented on NIFI-6367:
-------------------------------------
[~kefevs] - thank you! It threw a SdkClientException - that is NOT exactly the
same as the issue I found, so I'm really glad you posted that. But
SdkClientException extends AmazonClientException, which is caught (I checked
1.7.1 code and they are caught there too) so I'm not certain I quite have this
figured out yet. I made the unit tests throw that exception and it transferred
the file to the failure queue, which isn't the behavior you saw.
Do you still have the stack trace? I'd love to see the lines for FetchS3Object
and a few lines of where it went afterwards if that's possible, mostly to use
the line numbers to double check what it did in the code. (Since you had to
type it over - two or three filenames and line numbers are all I really need.)
> FetchS3Processor responds to md5 error on download by doing download again,
> again, and again
> --------------------------------------------------------------------------------------------
>
> Key: NIFI-6367
> URL: https://issues.apache.org/jira/browse/NIFI-6367
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.7.1
> Environment: NIFI (CentOS 7.2) with FetchS3Object running towards S3
> enviroment (non public). Enviroment / S3 had errors that introduced md5
> errors on sub 0.5% of downloads. Downloads with md5 errors accumulated in the
> input que of the processor.
> Reporter: Kefevs Pirkibo
> Assignee: Evan Reynolds
> Priority: Critical
>
> (6months old, but don't see changes in the relevant parts of the code, though
> I might be mistaken. This might be hard to replicate, so suggest a code
> wizard check if this is still a problem. )
> Case: NIFI running with FetchS3Object processor(s) towards S3 enviroment (non
> public). The enviroment and S3 had in combination hardware errors that
> resulted in sporadic md5 errors on the same files over and over again. Md5
> errors resulted in an unhandled AmazonClientException, and the file was
> downloaded yet again. (Reverted to the input que, first in line.) In our case
> this was identified after a number of days, with substantial bandwidth usage.
> It did not help that the FetchS3Objects where running with multiple
> instances, and after days accumulated the bad md5 checksum files for
> continuous download.
> Suggest: Someone code savy check what happens to files that are downloaded
> with bad md5, if they are reverted to the que due to uncought exception or
> other means, then this is still a potential problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
