[
https://issues.apache.org/jira/browse/HADOOP-13530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrian Muraru updated HADOOP-13530:
-----------------------------------
Description:
fs.s3.buffer.dir defines the tmp folder where files will be written to before
getting sent to S3. Right now this is limited to a single folder which causes
to major issues.
1. You need a drive with enough space to store all the tmp files at once
2. You are limited to the IO speeds of a single drive
This is similar to HADOOP-10610 but applies to {{s3://}} hadoop block fs.
was:
fs.s3.buffer.dir defines the tmp folder where files will be written to before
getting sent to S3. Right now this is limited to a single folder which causes
to major issues.
1. You need a drive with enough space to store all the tmp files at once
2. You are limited to the IO speeds of a single drive
This solution will resolve both and has been tested to increase the S3 write
speed by 2.5x with 10 mappers on hs1.
> Upgrade S3 fs.s3.buffer.dir to support multi directories
> --------------------------------------------------------
>
> Key: HADOOP-13530
> URL: https://issues.apache.org/jira/browse/HADOOP-13530
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs/s3
> Affects Versions: 2.4.0
> Reporter: Adrian Muraru
> Assignee: Ted Malaska
> Priority: Minor
>
> fs.s3.buffer.dir defines the tmp folder where files will be written to before
> getting sent to S3. Right now this is limited to a single folder which
> causes to major issues.
> 1. You need a drive with enough space to store all the tmp files at once
> 2. You are limited to the IO speeds of a single drive
> This is similar to HADOOP-10610 but applies to {{s3://}} hadoop block fs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
