You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Alexander Lorenz-Alten (Created) (JIRA)" <ji...@apache.org> on 2012/03/03 09:05:57 UTC
[jira] [Created] (FLUME-1015) S3 sink on flumeNG
S3 sink on flumeNG
------------------
Key: FLUME-1015
URL: https://issues.apache.org/jira/browse/FLUME-1015
Project: Flume
Issue Type: New Feature
Components: Sinks+Sources
Affects Versions: NG alpha 1
Reporter: Alexander Lorenz-Alten
Fix For: v1.1.0
I noticed a need on S3 sinks in flumeNG in our mailing list, should be implemented. S3 from flume 0.93 works, .94 not (some user reports).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLUME-1015) S3 sink on flumeNG
Posted by "E. Sammer (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222089#comment-13222089 ]
E. Sammer commented on FLUME-1015:
----------------------------------
I'm confused. Hadoop's FileSystem abstraction supports writing to S3. Maybe we don't expose direct configuration for it, but it was never a separate sink in 0.9. Should we not use Hadoop's implementation (I'm fine with that)?
> S3 sink on flumeNG
> ------------------
>
> Key: FLUME-1015
> URL: https://issues.apache.org/jira/browse/FLUME-1015
> Project: Flume
> Issue Type: New Feature
> Components: Sinks+Sources
> Affects Versions: NG alpha 1
> Reporter: Alexander Lorenz-Alten
> Labels: s3, sink
> Fix For: v1.1.0
>
>
> I noticed a need on S3 sinks in flumeNG in our mailing list, should be implemented. S3 from flume 0.93 works, .94 not (some user reports).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (FLUME-1015) S3 sink on flumeNG
Posted by "Alexander Lorenz-Alten (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Lorenz-Alten resolved FLUME-1015.
-------------------------------------------
Resolution: Fixed
flume uses hdfs abstraction, we don't need a separate configuration for. We add a notice in the upcoming guide about.
> S3 sink on flumeNG
> ------------------
>
> Key: FLUME-1015
> URL: https://issues.apache.org/jira/browse/FLUME-1015
> Project: Flume
> Issue Type: New Feature
> Components: Sinks+Sources
> Affects Versions: NG alpha 1
> Reporter: Alexander Lorenz-Alten
> Labels: s3, sink
> Fix For: v1.1.0
>
>
> I noticed a need on S3 sinks in flumeNG in our mailing list, should be implemented. S3 from flume 0.93 works, .94 not (some user reports).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (FLUME-1015) S3 sink on flumeNG
Posted by "Alexander Lorenz-Alten (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Lorenz-Alten reassigned FLUME-1015:
---------------------------------------------
Assignee: Alexander Lorenz-Alten
> S3 sink on flumeNG
> ------------------
>
> Key: FLUME-1015
> URL: https://issues.apache.org/jira/browse/FLUME-1015
> Project: Flume
> Issue Type: New Feature
> Components: Sinks+Sources
> Affects Versions: NG alpha 1
> Reporter: Alexander Lorenz-Alten
> Assignee: Alexander Lorenz-Alten
> Labels: s3, sink
> Fix For: v1.1.0
>
>
> I noticed a need on S3 sinks in flumeNG in our mailing list, should be implemented. S3 from flume 0.93 works, .94 not (some user reports).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FLUME-1015) S3 sink on flumeNG
Posted by "Arvind Prabhakar (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arvind Prabhakar updated FLUME-1015:
------------------------------------
Fix Version/s: (was: v1.1.0)
notrack
> S3 sink on flumeNG
> ------------------
>
> Key: FLUME-1015
> URL: https://issues.apache.org/jira/browse/FLUME-1015
> Project: Flume
> Issue Type: New Feature
> Components: Sinks+Sources
> Affects Versions: NG alpha 1
> Reporter: Alexander Lorenz-Alten
> Assignee: Alexander Lorenz-Alten
> Labels: s3, sink
> Fix For: notrack
>
>
> I noticed a need on S3 sinks in flumeNG in our mailing list, should be implemented. S3 from flume 0.93 works, .94 not (some user reports).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLUME-1015) S3 sink on flumeNG
Posted by "Alexander Lorenz-Alten (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222195#comment-13222195 ]
Alexander Lorenz-Alten commented on FLUME-1015:
-----------------------------------------------
You're right. I'll add a line into the guide and close the jira.
> S3 sink on flumeNG
> ------------------
>
> Key: FLUME-1015
> URL: https://issues.apache.org/jira/browse/FLUME-1015
> Project: Flume
> Issue Type: New Feature
> Components: Sinks+Sources
> Affects Versions: NG alpha 1
> Reporter: Alexander Lorenz-Alten
> Labels: s3, sink
> Fix For: v1.1.0
>
>
> I noticed a need on S3 sinks in flumeNG in our mailing list, should be implemented. S3 from flume 0.93 works, .94 not (some user reports).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLUME-1015) S3 sink on flumeNG
Posted by "Prashanth Jonnalagadda (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283739#comment-13283739 ]
Prashanth Jonnalagadda commented on FLUME-1015:
-----------------------------------------------
Hello,
flume-ng (version 1.2.0) fails while writing to S3 sink since it gets back 404 response code. The files with data is created on S3 though.
Hadoop version used is 0.20.2-cdh3u4
Followed all the steps documented in the jira - https://issues.cloudera.org/browse/FLUME-66
and also I tried swapping out hadoop-core.jar that comes with CDH, with emr-hadoop-core-0.20.jar that comes with EC2 hadoop cluster instance as suggested in the following blog post - http://eric.lubow.org/2011/system-administration/distributed-flume-setup-with-an-s3-sink/ but the issue still remains.
Following errors are seen in the log:
2012-05-25 05:04:28,889 WARN httpclient.RestS3Service: Response '/flumedata%2FFlumeData.122585423857995.tmp_%24folder%24' - Unexpected response code 404, expected 200
2012-05-25 05:04:28,964 INFO s3native.NativeS3FileSystem: OutputStream for key 'flumedata/FlumeData.122585423857995.tmp' writing to tempfile '/tmp/hadoop-root/s3/output-8042215269186280519.tmp'
2012-05-25 05:04:28,972 INFO s3native.NativeS3FileSystem: OutputStream for key 'flumedata/FlumeData.122585423857995.tmp' closed. Now beginning upload
2012-05-25 05:04:29,044 INFO s3native.NativeS3FileSystem: OutputStream for key 'flumedata/FlumeData.122585423857995.tmp' upload complete
2012-05-25 05:04:29,074 INFO hdfs.BucketWriter: Renaming s3n://flume-ng/flumedata/FlumeData.122585423857995.tmp to s3n://flume-ng/flumedata/FlumeData.122585423857995
2012-05-25 05:04:29,097 WARN httpclient.RestS3Service: Response '/flumedata%2FFlumeData.122585423857995' - Unexpected response code 404, expected 200
2012-05-25 05:04:29,120 WARN httpclient.RestS3Service: Response '/flumedata%2FFlumeData.122585423857995_%24folder%24' - Unexpected response code 404, expected 200
2012-05-25 05:04:29,203 WARN httpclient.RestS3Service: Response '/flumedata' - Unexpected response code 404, expected 200
2012-05-25 05:04:29,224 WARN httpclient.RestS3Service: Response '/flumedata_%24folder%24' - Unexpected response code 404, expected 200
2012-05-25 05:04:29,608 INFO hdfs.BucketWriter: Creating s3n://flume-ng/flumedata/FlumeData.122585423857996.tmp
2012-05-25 05:04:29,720 WARN httpclient.RestS3Service: Response '/flumedata%2FFlumeData.122585423857996.tmp' - Unexpected response code 404, expected 200
2012-05-25 05:04:29,748 WARN httpclient.RestS3Service: Response '/flumedata%2FFlumeData.122585423857996.tmp_%24folder%24' - Unexpected response code 404, expected 200
2012-05-25 05:04:29,791 INFO s3native.NativeS3FileSystem: OutputStream for key 'flumedata/FlumeData.122585423857996.tmp' writing to tempfile '/tmp/hadoop-root/s3/output-2477068572058013384.tmp'
2012-05-25 05:04:29,793 INFO s3native.NativeS3FileSystem: OutputStream for key 'flumedata/FlumeData.122585423857996.tmp' closed. Now beginning upload
2012-05-25 05:04:29,828 INFO s3native.NativeS3FileSystem: OutputStream for key 'flumedata/FlumeData.122585423857996.tmp' upload complete
Any help in this regard is highly appreciated.
> S3 sink on flumeNG
> ------------------
>
> Key: FLUME-1015
> URL: https://issues.apache.org/jira/browse/FLUME-1015
> Project: Flume
> Issue Type: New Feature
> Components: Sinks+Sources
> Affects Versions: NG alpha 1
> Reporter: Alexander Alten-Lorenz
> Assignee: Alexander Alten-Lorenz
> Labels: s3, sink
> Fix For: notrack
>
>
> I noticed a need on S3 sinks in flumeNG in our mailing list, should be implemented. S3 from flume 0.93 works, .94 not (some user reports).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira