[
https://issues.apache.org/jira/browse/FLUME-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13851036#comment-13851036
]
Viksit Gaur commented on FLUME-330:
-----------------------------------
I can confirm that this issue still exists in Flume 1.4.0-bin
Hadoop versions
-rw-rw-r-- 1 ubuntu ubuntu 279781 Dec 17 22:24 commons-httpclient-3.0.1.jar
-rw-rw-r-- 1 ubuntu ubuntu 58160 Dec 17 22:24 commons-codec-1.4.jar
-rw-rw-r-- 1 ubuntu ubuntu 321806 Dec 17 22:24 jets3t-0.6.1.jar
-rw-rw-r-- 1 ubuntu ubuntu 4203147 Dec 17 22:24 hadoop-core-1.2.1.jar
> Collector outputing to S3 sink fails and doesn't recover when S3 returns
> consecutive 404 status code
> ----------------------------------------------------------------------------------------------------
>
> Key: FLUME-330
> URL: https://issues.apache.org/jira/browse/FLUME-330
> Project: Flume
> Issue Type: Bug
> Components: Node
> Affects Versions: v0.9.1u1
> Environment: Ubuntu 9.10 x86
> $ flume version
> Flume 0.9.1+29
> Git repository
> rev 1b753ff62e62a05ca9ac9f3ee8782b5eb8c48da7
> Compiled by bruno on Sun Oct 10 15:25:07 PDT 2010
> Reporter: Disabled imported user
> Priority: Critical
>
> My collector is sourced to autoCollectorSource and sinked to S3N. The
> collector occasionally fails and doesn't recover until I restart the node.
> Looking at the agents, they all have backed up logged messages. Once the
> consumer node is restarted, the agents resume normally and the logged
> messages slowly deplete. This happens at least a couple times a week.
> Below is relevant log output:
> 2010-11-08 09:25:47,451 WARN
> org.jets3t.service.impl.rest.httpclient.RestS3Service: Response
> '/logs%2Fredirector%2Finsertdate%3D2010-11-08%2Finserthour%3D00%2Fweblog-domU-12-31-39-01-5D-24.compute-1.internal-log.00000018.20101108-092546510%2B0000.2386949180521782.seq.gz'
> - Unexpected response code 404, expected 200
> 2010-11-08 09:25:47,470 WARN
> org.jets3t.service.impl.rest.httpclient.RestS3Service: Response
> '/logs%2Fredirector%2Finsertdate%3D2010-11-08%2Finserthour%3D00%2Fweblog-domU-12-31-39-01-5D-24.compute-1.internal-log.00000018.20101108-092546510%2B0000.2386949180521782.seq.gz_%24folder%24'
> - Unexpected response code 404, expected 200
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
