Re: [VOTE] Release Apache Hadoop Ozone 0.2.1-alpha (RC0)
Thanks Marton for the first release of ozone. +1 (non-binding) - Verified the signature - Built from source - Tested ozone shell and ozone fs commands using robot - Deployed pseudo ozone cluster and verified basic shell commands > On Sep 26, 2018, at 10:29 AM, Shashikant Banerjee > wrote: > > Hi Marton, > > +1 (non-binding) > > 1. Verified the Signature > 3. Built from source. > 4. Ran Robot tests to verify all RPC and Rest commands > 4. Deployed Pseudo ozone cluster and verified basic commands. > > Thanks > Shashi > > On 9/26/18, 8:26 AM, "Bharat Viswanadham" > wrote: > >Hi Marton, >Thank You for the first ozone release. >+1 (non-binding) > >1. Verified signatures. >2. Built from source. >3. Ran a docker cluster using docker files from ozone tar ball. Tested > ozone shell commands. >4. Ran ozone-hdfs cluster and verified ozone is started as a plugin when > datanode boots up. > >Thanks, >Bharat > > > > >On 9/19/18, 2:49 PM, "Elek, Marton" wrote: > >Hi all, > >After the recent discussion about the first Ozone release I've created >the first release candidate (RC0) for Apache Hadoop Ozone 0.2.1-alpha. > >This release is alpha quality: it’s not recommended to use in > production >but we believe that it’s stable enough to try it out the feature set > and >collect feedback. > >The RC artifacts are available from: >https://home.apache.org/~elek/ozone-0.2.1-alpha-rc0/ > >The RC tag in git is: ozone-0.2.1-alpha-RC0 (968082ffa5d) > >Please try the release and vote; the vote will run for the usual 5 >working days, ending on September 26, 2018 10pm UTC time. > >The easiest way to try it out is: > >1. Download the binary artifact >2. Read the docs at ./docs/index.html >3. TLDR; cd compose/ozone && docker-compose up -d > > >Please try it out, vote, or just give us feedback. > >Thank you very much, >Marton > >ps: At next week, we will have a BoF session at ApacheCon North > Europe, >Montreal on Monday evening. Please join, if you are interested, or > need >support to try out the package or just have any feedback. > > >- >To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org >For additional commands, e-mail: common-dev-h...@hadoop.apache.org > > > > >- >To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org >For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org > > > > > - > To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org > - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
Re: [VOTE] Release Apache Hadoop Ozone 0.2.1-alpha (RC0)
Hi Marton, +1 (non-binding) 1. Verified the Signature 3. Built from source. 4. Ran Robot tests to verify all RPC and Rest commands 4. Deployed Pseudo ozone cluster and verified basic commands. Thanks Shashi On 9/26/18, 8:26 AM, "Bharat Viswanadham" wrote: Hi Marton, Thank You for the first ozone release. +1 (non-binding) 1. Verified signatures. 2. Built from source. 3. Ran a docker cluster using docker files from ozone tar ball. Tested ozone shell commands. 4. Ran ozone-hdfs cluster and verified ozone is started as a plugin when datanode boots up. Thanks, Bharat On 9/19/18, 2:49 PM, "Elek, Marton" wrote: Hi all, After the recent discussion about the first Ozone release I've created the first release candidate (RC0) for Apache Hadoop Ozone 0.2.1-alpha. This release is alpha quality: it’s not recommended to use in production but we believe that it’s stable enough to try it out the feature set and collect feedback. The RC artifacts are available from: https://home.apache.org/~elek/ozone-0.2.1-alpha-rc0/ The RC tag in git is: ozone-0.2.1-alpha-RC0 (968082ffa5d) Please try the release and vote; the vote will run for the usual 5 working days, ending on September 26, 2018 10pm UTC time. The easiest way to try it out is: 1. Download the binary artifact 2. Read the docs at ./docs/index.html 3. TLDR; cd compose/ozone && docker-compose up -d Please try it out, vote, or just give us feedback. Thank you very much, Marton ps: At next week, we will have a BoF session at ApacheCon North Europe, Montreal on Monday evening. Please join, if you are interested, or need support to try out the package or just have any feedback. - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org - To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
Re: [VOTE] Release Apache Hadoop Ozone 0.2.1-alpha (RC0)
Correction: My vote is NON-BINDING. Sorry for the confusion. Thanks, Hanisha On 9/25/18, 7:29 PM, "Hanisha Koneru" wrote: >Thanks Marton for putting together the first RC for Ozone. > >+1 (binding) > >Verified the following: > - Verified the signature > - Built from Source > - Deployed Pseudo HDFS and Ozone clusters and verified basic operations > > >Thanks, >Hanisha > > > > > > > > >On 9/19/18, 2:49 PM, "Elek, Marton" wrote: > >>Hi all, >> >>After the recent discussion about the first Ozone release I've created >>the first release candidate (RC0) for Apache Hadoop Ozone 0.2.1-alpha. >> >>This release is alpha quality: it’s not recommended to use in production >>but we believe that it’s stable enough to try it out the feature set and >>collect feedback. >> >>The RC artifacts are available from: >>https://home.apache.org/~elek/ozone-0.2.1-alpha-rc0/ >> >>The RC tag in git is: ozone-0.2.1-alpha-RC0 (968082ffa5d) >> >>Please try the release and vote; the vote will run for the usual 5 >>working days, ending on September 26, 2018 10pm UTC time. >> >>The easiest way to try it out is: >> >>1. Download the binary artifact >>2. Read the docs at ./docs/index.html >>3. TLDR; cd compose/ozone && docker-compose up -d >> >> >>Please try it out, vote, or just give us feedback. >> >>Thank you very much, >>Marton >> >>ps: At next week, we will have a BoF session at ApacheCon North Europe, >>Montreal on Monday evening. Please join, if you are interested, or need >>support to try out the package or just have any feedback. >> >> >>- >>To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org >>For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org >>
Re: [VOTE] Release Apache Hadoop Ozone 0.2.1-alpha (RC0)
Hi Marton, Thank You for the first ozone release. +1 (non-binding) 1. Verified signatures. 2. Built from source. 3. Ran a docker cluster using docker files from ozone tar ball. Tested ozone shell commands. 4. Ran ozone-hdfs cluster and verified ozone is started as a plugin when datanode boots up. Thanks, Bharat On 9/19/18, 2:49 PM, "Elek, Marton" wrote: Hi all, After the recent discussion about the first Ozone release I've created the first release candidate (RC0) for Apache Hadoop Ozone 0.2.1-alpha. This release is alpha quality: it’s not recommended to use in production but we believe that it’s stable enough to try it out the feature set and collect feedback. The RC artifacts are available from: https://home.apache.org/~elek/ozone-0.2.1-alpha-rc0/ The RC tag in git is: ozone-0.2.1-alpha-RC0 (968082ffa5d) Please try the release and vote; the vote will run for the usual 5 working days, ending on September 26, 2018 10pm UTC time. The easiest way to try it out is: 1. Download the binary artifact 2. Read the docs at ./docs/index.html 3. TLDR; cd compose/ozone && docker-compose up -d Please try it out, vote, or just give us feedback. Thank you very much, Marton ps: At next week, we will have a BoF session at ApacheCon North Europe, Montreal on Monday evening. Please join, if you are interested, or need support to try out the package or just have any feedback. - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
Re: [VOTE] Release Apache Hadoop Ozone 0.2.1-alpha (RC0)
Thanks Marton for putting together the first RC for Ozone. +1 (binding) Verified the following: - Verified the signature - Built from Source - Deployed Pseudo HDFS and Ozone clusters and verified basic operations Thanks, Hanisha On 9/19/18, 2:49 PM, "Elek, Marton" wrote: >Hi all, > >After the recent discussion about the first Ozone release I've created >the first release candidate (RC0) for Apache Hadoop Ozone 0.2.1-alpha. > >This release is alpha quality: it’s not recommended to use in production >but we believe that it’s stable enough to try it out the feature set and >collect feedback. > >The RC artifacts are available from: >https://home.apache.org/~elek/ozone-0.2.1-alpha-rc0/ > >The RC tag in git is: ozone-0.2.1-alpha-RC0 (968082ffa5d) > >Please try the release and vote; the vote will run for the usual 5 >working days, ending on September 26, 2018 10pm UTC time. > >The easiest way to try it out is: > >1. Download the binary artifact >2. Read the docs at ./docs/index.html >3. TLDR; cd compose/ozone && docker-compose up -d > > >Please try it out, vote, or just give us feedback. > >Thank you very much, >Marton > >ps: At next week, we will have a BoF session at ApacheCon North Europe, >Montreal on Monday evening. Please join, if you are interested, or need >support to try out the package or just have any feedback. > > >- >To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org >For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org >
[jira] [Resolved] (HADOOP-15407) Support Windows Azure Storage - Blob file system in Hadoop
[
https://issues.apache.org/jira/browse/HADOOP-15407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved HADOOP-15407.
-
Resolution: Fixed
Fix Version/s: 3.2.0
Release Note: The abfs connector in the hadoop-azure module supports
Microsoft Azure Datalake (Gen 2), which at the time of writing (September 2018)
was in preview, soon to go GA. As with all cloud connectors, corner-cases will
inevitably surface. If you encounter one, please file a bug report.
This is now done: ABFS is ready to play with in Hadoop 3.2.0; problems which
arise will get addressed in later JIRAs. adding something to the release notes.
> Support Windows Azure Storage - Blob file system in Hadoop
> --
>
> Key: HADOOP-15407
> URL: https://issues.apache.org/jira/browse/HADOOP-15407
> Project: Hadoop Common
> Issue Type: New Feature
> Components: fs/azure
>Affects Versions: 3.2.0
>Reporter: Esfandiar Manii
>Assignee: Da Zhou
>Priority: Blocker
> Fix For: 3.2.0
>
> Attachments: HADOOP-15407-001.patch, HADOOP-15407-002.patch,
> HADOOP-15407-003.patch, HADOOP-15407-004.patch, HADOOP-15407-008.patch,
> HADOOP-15407-HADOOP-15407-008.patch, HADOOP-15407-HADOOP-15407.006.patch,
> HADOOP-15407-HADOOP-15407.007.patch, HADOOP-15407-HADOOP-15407.008.patch
>
>
> *{color:#212121}Description{color}*
> This JIRA adds a new file system implementation, ABFS, for running Big Data
> and Analytics workloads against Azure Storage. This is a complete rewrite of
> the previous WASB driver with a heavy focus on optimizing both performance
> and cost.
> {color:#212121} {color}
> *{color:#212121}High level design{color}*
> At a high level, the code here extends the FileSystem class to provide an
> implementation for accessing blobs in Azure Storage. The scheme abfs is used
> for accessing it over HTTP, and abfss for accessing over HTTPS. The following
> URI scheme is used to address individual paths:
> {color:#212121} {color}
>
> {color:#212121}abfs[s]://@.dfs.core.windows.net/{color}
> {color:#212121} {color}
> {color:#212121}ABFS is intended as a replacement to WASB. WASB is not
> deprecated but is in pure maintenance mode and customers should upgrade to
> ABFS once it hits General Availability later in CY18.{color}
> {color:#212121}Benefits of ABFS include:{color}
> {color:#212121}· Higher scale (capacity, throughput, and IOPS) Big
> Data and Analytics workloads by allowing higher limits on storage
> accounts{color}
> {color:#212121}· Removing any ramp up time with Storage backend
> partitioning; blocks are now automatically sharded across partitions in the
> Storage backend{color}
> {color:#212121} . This avoids the need for using
> temporary/intermediate files, increasing the cost (and framework complexity
> around committing jobs/tasks){color}
> {color:#212121}· Enabling much higher read and write throughput on
> single files (tens of Gbps by default){color}
> {color:#212121}· Still retaining all of the Azure Blob features
> customers are familiar with and expect, and gaining the benefits of future
> Blob features as well{color}
> {color:#212121}ABFS incorporates Hadoop Filesystem metrics to monitor the
> file system throughput and operations. Ambari metrics are not currently
> implemented for ABFS, but will be available soon.{color}
> {color:#212121} {color}
> *{color:#212121}Credits and history{color}*
> Credit for this work goes to (hope I don't forget anyone): Shane Mainali,
> {color:#212121}Thomas Marquardt, Zichen Sun, Georgi Chalakov, Esfandiar
> Manii, Amit Singh, Dana Kaban, Da Zhou, Junhua Gu, Saher Ahwal, Saurabh Pant,
> and James Baker. {color}
> {color:#212121} {color}
> *Test*
> ABFS has gone through many test procedures including Hadoop file system
> contract tests, unit testing, functional testing, and manual testing. All the
> Junit tests provided with the driver are capable of running in both
> sequential/parallel fashion in order to reduce the testing time.
> {color:#212121}Besides unit tests, we have used ABFS as the default file
> system in Azure HDInsight. Azure HDInsight will very soon offer ABFS as a
> storage option. (HDFS is also used but not as default file system.) Various
> different customer and test workloads have been run against clusters with
> such configurations for quite some time. Benchmarks such as Tera*, TPC-DS,
> Spark Streaming and Spark SQL, and others have been run to do scenario,
> performance, and functional testing. Third parties and customers have also
> done various testing of ABFS.{color}
> {color:#212121}The current version reflects to the version of the code
> tested and used in our production environment.{color}
--
[jira] [Created] (HADOOP-15792) typo in AzureBlobFileSystem.getIsNamespaceEnabeld
Steve Loughran created HADOOP-15792:
---
Summary: typo in AzureBlobFileSystem.getIsNamespaceEnabeld
Key: HADOOP-15792
URL: https://issues.apache.org/jira/browse/HADOOP-15792
Project: Hadoop Common
Issue Type: Sub-task
Components: fs/azure
Affects Versions: 3.2.0
Reporter: Steve Loughran
There's a typo in the visible-for-test method {{
AzureBlobFileSystem.getIsNamespaceEnabeld}}
Trivial to fix, just postponing until after the 3.2.x branch
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
Re: [VOTE] Release Apache Hadoop Ozone 0.2.1-alpha (RC0)
Hi Marton, +1 (binding) 1. Verified the Signature 2. Verified the Checksums - MD5 and Sha* 3. Build from Sources. 4. Ran all RPC and REST commands against the cluster via Robot. 5. Tested the OzoneFS functionality Thank you very much for creating the first release of Ozone. --Anu On 9/19/18, 2:49 PM, "Elek, Marton" wrote: Hi all, After the recent discussion about the first Ozone release I've created the first release candidate (RC0) for Apache Hadoop Ozone 0.2.1-alpha. This release is alpha quality: it’s not recommended to use in production but we believe that it’s stable enough to try it out the feature set and collect feedback. The RC artifacts are available from: https://home.apache.org/~elek/ozone-0.2.1-alpha-rc0/ The RC tag in git is: ozone-0.2.1-alpha-RC0 (968082ffa5d) Please try the release and vote; the vote will run for the usual 5 working days, ending on September 26, 2018 10pm UTC time. The easiest way to try it out is: 1. Download the binary artifact 2. Read the docs at ./docs/index.html 3. TLDR; cd compose/ozone && docker-compose up -d Please try it out, vote, or just give us feedback. Thank you very much, Marton ps: At next week, we will have a BoF session at ApacheCon North Europe, Montreal on Monday evening. Please join, if you are interested, or need support to try out the package or just have any feedback. - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-15791) Remove Ozone related sources from the 3.2 branch
Elek, Marton created HADOOP-15791:
-
Summary: Remove Ozone related sources from the 3.2 branch
Key: HADOOP-15791
URL: https://issues.apache.org/jira/browse/HADOOP-15791
Project: Hadoop Common
Issue Type: Bug
Reporter: Elek, Marton
Assignee: Elek, Marton
As it is discussed at HDDS-341 and written in the original proposal of Ozone
merge, we can remove all the ozone/hdds projects from the 3.2 release branch.
{quote}
* On trunk (as opposed to release branches) HDSL will be a separate module in
Hadoop's source tree. This will enable the HDSL to work on their trunk and the
Hadoop trunk without making releases for every change.
* Hadoop's trunk will only build HDSL if a non-default profile is enabled.
* When Hadoop creates a release branch, the RM will delete the HDSL module
from the branch.
{quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86
For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/907/ [Sep 24, 2018 6:50:28 AM] (sunilg) YARN-8742. [UI2] Container logs on Application / Service pages on UI2 [Sep 24, 2018 3:49:47 PM] (sunilg) HDFS-13937. Multipart Uploader APIs to be marked as private/unstable in [Sep 24, 2018 5:10:11 PM] (bharat) HDDS-447. Separate ozone-dist and hadoop-dist projects with real [Sep 24, 2018 5:40:30 PM] (weichiu) HDFS-13876. HttpFS: Implement ALLOWSNAPSHOT, DISALLOWSNAPSHOT. [Sep 24, 2018 6:37:05 PM] (gifuma) YARN-8696. [AMRMProxy] FederationInterceptor upgrade: home sub-cluster [Sep 24, 2018 7:53:21 PM] (liuml07) HADOOP-15781 S3A assumed role tests failing due to changed error text in [Sep 24, 2018 8:42:55 PM] (bharat) HDDS-441. Create new s3gateway daemon. Contributed by Elek Marton. [Sep 24, 2018 8:52:53 PM] (wangda) MAPREDUCE-7125. JobResourceUploader creates LocalFileSystem when it's [Sep 24, 2018 10:54:02 PM] (haibochen) YARN-6338. Typos in Docker docs: contains => containers. (Contributed by [Sep 24, 2018 11:04:28 PM] (haibochen) YARN-8616. systemClock should be used in RMAppImpl instead of -1 overall The following subsystems voted -1: asflicense findbugs hadolint pathlen unit xml The following subsystems voted -1 but were configured to be filtered/ignored: cc checkstyle javac javadoc pylint shellcheck shelldocs whitespace The following subsystems are considered long running: (runtime bigger than 1h 0m 0s) unit Specific tests: XML : Parsing Error(s): hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp/public/crossdomain.xml FindBugs : module:hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-submarine org.apache.hadoop.yarn.submarine.runtimes.yarnservice.YarnServiceUtils.getComponentArrayJson(String, int, String) concatenates strings using + in a loop At YarnServiceUtils.java:using + in a loop At YarnServiceUtils.java:[line 123] Failed CTEST tests : test_test_libhdfs_threaded_hdfs_static test_libhdfs_threaded_hdfspp_test_shim_static Failed junit tests : hadoop.hdfs.server.datanode.TestDataNodeMultipleRegistrations hadoop.yarn.server.nodemanager.containermanager.TestNMProxy hadoop.yarn.applications.distributedshell.TestDistributedShell hadoop.yarn.service.TestServiceAM hadoop.yarn.service.TestServiceManager cc: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/907/artifact/out/diff-compile-cc-root.txt [4.0K] javac: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/907/artifact/out/diff-compile-javac-root.txt [300K] checkstyle: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/907/artifact/out/diff-checkstyle-root.txt [17M] hadolint: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/907/artifact/out/diff-patch-hadolint.txt [4.0K] pathlen: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/907/artifact/out/pathlen.txt [12K] pylint: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/907/artifact/out/diff-patch-pylint.txt [24K] shellcheck: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/907/artifact/out/diff-patch-shellcheck.txt [20K] shelldocs: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/907/artifact/out/diff-patch-shelldocs.txt [12K] whitespace: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/907/artifact/out/whitespace-eol.txt [9.4M] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/907/artifact/out/whitespace-tabs.txt [1.1M] xml: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/907/artifact/out/xml.txt [4.0K] findbugs: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/907/artifact/out/branch-findbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-applications_hadoop-yarn-submarine-warnings.html [8.0K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/907/artifact/out/branch-findbugs-hadoop-hdds_client.txt [4.0K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/907/artifact/out/branch-findbugs-hadoop-hdds_container-service.txt [8.0K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/907/artifact/out/branch-findbugs-hadoop-hdds_framework.txt [4.0K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/907/artifact/out/branch-findbugs-hadoop-hdds_server-scm.txt [12K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/907/artifact/out/branch-findbugs-hadoop-hdds_tools.txt [4.0K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/907/artifact/out/branch-findbugs-hadoop-ozone_client.txt [8.0K]
[jira] [Resolved] (HADOOP-15135) S3a to support get/set permissions through S3 object tags
[ https://issues.apache.org/jira/browse/HADOOP-15135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved HADOOP-15135. - Resolution: Won't Fix > S3a to support get/set permissions through S3 object tags > - > > Key: HADOOP-15135 > URL: https://issues.apache.org/jira/browse/HADOOP-15135 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 >Reporter: Steve Loughran >Priority: Major > > Azure wasb supports get/set permissions (for persistence only) to help round > trip distcp operations. > Could aws tags be used similarly? -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-15788) Improve Distcp for long-haul/cloud deployments
Steve Loughran created HADOOP-15788: --- Summary: Improve Distcp for long-haul/cloud deployments Key: HADOOP-15788 URL: https://issues.apache.org/jira/browse/HADOOP-15788 Project: Hadoop Common Issue Type: Improvement Components: tools/distcp Affects Versions: 3.2.0 Reporter: Steve Loughran There are a number of outstanding distcp options related to: extensibility, failure reporting/cleanup, long-haul options, cloud performance. Hadoop 3.1 added some speedups; follow this up with others. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
