Re: About 2.7.4 Release
Is there any reason to wait for 2.8 with 2.7.4? Unfortunately the previous thread about release cadence has been ended without final decision. But if I understood well, there was more or less an agreement about that it would be great to achieve more frequent releases, if possible (with or without written rules and EOL policy). I personally prefer to be more closer to the scheduling part of the proposal: "A minor release on the latest major line should be every 6 months, and a maintenance release on a minor release (as there may be concurrently maintained minor releases) every 2 months". I don't know what is the hardest part of creating new minor/maintenance releases. But if the problems are technical (smoketesting, unit tests, old release script, anything else) I would be happy to do any task for new maintenance releases (or more frequent releases). Regards, Marton From: Akira Ajisaka Sent: Tuesday, March 07, 2017 7:34 AM To: Brahma Reddy Battula; Hadoop Common; yarn-...@hadoop.apache.org; Hdfs-dev; mapreduce-...@hadoop.apache.org Subject: Re: About 2.7.4 Release Probably 2.8.0 will be released soon. https://issues.apache.org/jira/browse/HADOOP-13866?focusedCommentId=15898379&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15898379 I'm thinking 2.7.4 release process starts after 2.8.0 release, so 2.7.4 will be released in April or May. (hopefully) Thoughts? Regards, Akira On 2017/03/01 21:01, Brahma Reddy Battula wrote: > Hi All > > It has been six months for branch-2.7 release.. is there any near plan for > 2.7.4..? > > > Thanks&Regards > Brahma Reddy Battula > > - 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
Re: About 2.7.4 Release
I don't think there should be any linkage between releasing 2.8.0 and 2.7.4. If we have a volunteer for releasing 2.7.4, we should go full speed ahead. We still need a volunteer from a PMC member or a committer as some tasks may require certain privileges, but I don't think it precludes working with others to close down the release. I for one would like to see more frequent releases, and being able to automate release steps more would go a long way. On Tue, Mar 7, 2017 at 2:16 AM, Marton Elek wrote: > Is there any reason to wait for 2.8 with 2.7.4? > > Unfortunately the previous thread about release cadence has been ended > without final decision. But if I understood well, there was more or less an > agreement about that it would be great to achieve more frequent releases, > if possible (with or without written rules and EOL policy). > > I personally prefer to be more closer to the scheduling part of the > proposal: > > "A minor release on the latest major line should be every 6 months, and a > maintenance release on a minor release (as there may be concurrently > maintained minor releases) every 2 months". > > I don't know what is the hardest part of creating new minor/maintenance > releases. But if the problems are technical (smoketesting, unit tests, old > release script, anything else) I would be happy to do any task for new > maintenance releases (or more frequent releases). > > Regards, > Marton > > > > From: Akira Ajisaka > Sent: Tuesday, March 07, 2017 7:34 AM > To: Brahma Reddy Battula; Hadoop Common; yarn-...@hadoop.apache.org; > Hdfs-dev; mapreduce-...@hadoop.apache.org > Subject: Re: About 2.7.4 Release > > Probably 2.8.0 will be released soon. > https://issues.apache.org/jira/browse/HADOOP-13866? > focusedCommentId=15898379&page=com.atlassian.jira. > plugin.system.issuetabpanels:comment-tabpanel#comment-15898379 > > I'm thinking 2.7.4 release process starts after 2.8.0 release, > so 2.7.4 will be released in April or May. (hopefully) > > Thoughts? > > Regards, > Akira > > On 2017/03/01 21:01, Brahma Reddy Battula wrote: > > Hi All > > > > It has been six months for branch-2.7 release.. is there any near plan > for 2.7.4..? > > > > > > Thanks&Regards > > Brahma Reddy Battula > > > > > > - > 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 > >
Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86
For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/338/ [Mar 6, 2017 11:04:03 AM] (yqlin) HDFS-8741. Proper error msg to be printed when invalid operation type is [Mar 6, 2017 4:34:51 PM] (aajisaka) HADOOP-14108. CLI MiniCluster: add an option to specify NameNode HTTP [Mar 6, 2017 6:47:15 PM] (wang) HDFS-11441. Add escaping to error message in KMS web UI. Contributed by [Mar 6, 2017 10:02:49 PM] (rchiang) YARN-5665. Enhance documentation for [Mar 6, 2017 11:04:13 PM] (wang) HDFS-11498. Make RestCsrfPreventionHandler and WebHdfsHandler compatible [Mar 7, 2017 12:39:53 AM] (arp) HDFS-10838. Last full block report received time for each DN should be [Mar 7, 2017 1:00:13 AM] (liuml07) HADOOP-14048. REDO operation of WASB#AtomicRename should create [Mar 7, 2017 1:10:11 AM] (liuml07) Revert "HADOOP-13930. Azure: Add Authorization support to WASB. [Mar 7, 2017 1:16:36 AM] (liuml07) HADOOP-13930. Azure: Add Authorization support to WASB. Contributed by [Mar 7, 2017 4:10:59 AM] (aajisaka) MAPREDUCE-6855. Specify charset when create String in [Mar 7, 2017 4:22:11 AM] (aajisaka) Treat encrypted files as private. Contributed by Daniel Templeton. [Mar 7, 2017 6:14:55 AM] (aajisaka) HADOOP-14087. S3A typo in pom.xml test exclusions. Contributed by Aaron -1 overall The following subsystems voted -1: asflicense unit 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: Failed junit tests : hadoop.hdfs.server.datanode.TestDataNodeMultipleRegistrations hadoop.hdfs.server.datanode.TestDataNodeVolumeFailureReporting hadoop.hdfs.server.datanode.TestDataNodeVolumeFailure hadoop.hdfs.server.datanode.TestDirectoryScanner hadoop.hdfs.server.datanode.fsdataset.impl.TestSpaceReservation hadoop.yarn.server.nodemanager.containermanager.scheduler.TestContainerSchedulerQueuing hadoop.yarn.server.timeline.webapp.TestTimelineWebServices hadoop.yarn.server.TestContainerManagerSecurity hadoop.yarn.server.TestMiniYarnClusterNodeUtilization hadoop.yarn.server.TestDiskFailures hadoop.mapred.TestMRTimelineEventHandling Timed out junit tests : org.apache.hadoop.hdfs.server.blockmanagement.TestBlockStatsMXBean cc: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/338/artifact/out/diff-compile-cc-root.txt [4.0K] javac: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/338/artifact/out/diff-compile-javac-root.txt [176K] checkstyle: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/338/artifact/out/diff-checkstyle-root.txt [17M] pylint: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/338/artifact/out/diff-patch-pylint.txt [20K] shellcheck: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/338/artifact/out/diff-patch-shellcheck.txt [24K] shelldocs: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/338/artifact/out/diff-patch-shelldocs.txt [12K] whitespace: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/338/artifact/out/whitespace-eol.txt [11M] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/338/artifact/out/whitespace-tabs.txt [1.3M] javadoc: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/338/artifact/out/diff-javadoc-javadoc-root.txt [2.2M] unit: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/338/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt [420K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/338/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager.txt [36K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/338/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-applicationhistoryservice.txt [12K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/338/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-tests.txt [324K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/338/artifact/out/patch-unit-hadoop-mapreduce-project_hadoop-mapreduce-client_hadoop-mapreduce-client-jobclient.txt [88K] asflicense: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/338/artifact/out/patch-asflicense-problems.txt [4.0K] Powered by Apache Yetus 0.5.0-SNAPSHOT http://yetus.apache.org - To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org For additional comm
Apache Hadoop qbt Report: trunk+JDK8 on Linux/ppc64le
For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/250/ [Mar 6, 2017 4:34:51 PM] (aajisaka) HADOOP-14108. CLI MiniCluster: add an option to specify NameNode HTTP [Mar 6, 2017 6:47:15 PM] (wang) HDFS-11441. Add escaping to error message in KMS web UI. Contributed by [Mar 6, 2017 10:02:49 PM] (rchiang) YARN-5665. Enhance documentation for [Mar 6, 2017 11:04:13 PM] (wang) HDFS-11498. Make RestCsrfPreventionHandler and WebHdfsHandler compatible [Mar 7, 2017 12:39:53 AM] (arp) HDFS-10838. Last full block report received time for each DN should be [Mar 7, 2017 1:00:13 AM] (liuml07) HADOOP-14048. REDO operation of WASB#AtomicRename should create [Mar 7, 2017 1:10:11 AM] (liuml07) Revert "HADOOP-13930. Azure: Add Authorization support to WASB. [Mar 7, 2017 1:16:36 AM] (liuml07) HADOOP-13930. Azure: Add Authorization support to WASB. Contributed by [Mar 7, 2017 4:10:59 AM] (aajisaka) MAPREDUCE-6855. Specify charset when create String in [Mar 7, 2017 4:22:11 AM] (aajisaka) Treat encrypted files as private. Contributed by Daniel Templeton. [Mar 7, 2017 6:14:55 AM] (aajisaka) HADOOP-14087. S3A typo in pom.xml test exclusions. Contributed by Aaron -1 overall The following subsystems voted -1: compile unit The following subsystems voted -1 but were configured to be filtered/ignored: cc javac The following subsystems are considered long running: (runtime bigger than 1h 0m 0s) unit Specific tests: Failed junit tests : hadoop.security.TestRaceWhenRelogin hadoop.hdfs.TestDFSRemove hadoop.hdfs.TestReconstructStripedFile hadoop.hdfs.tools.offlineImageViewer.TestOfflineImageViewer hadoop.hdfs.server.datanode.metrics.TestDataNodeOutlierDetectionViaMetrics hadoop.hdfs.server.datanode.checker.TestThrottledAsyncChecker hadoop.hdfs.server.datanode.TestDataNodeVolumeFailure hadoop.hdfs.server.datanode.TestDataNodeVolumeFailureReporting hadoop.hdfs.web.TestWebHdfsTimeouts hadoop.yarn.server.timeline.TestRollingLevelDB hadoop.yarn.server.timeline.TestTimelineDataManager hadoop.yarn.server.timeline.TestLeveldbTimelineStore hadoop.yarn.server.timeline.webapp.TestTimelineWebServices hadoop.yarn.server.timeline.recovery.TestLeveldbTimelineStateStore hadoop.yarn.server.timeline.TestRollingLevelDBTimelineStore hadoop.yarn.server.applicationhistoryservice.TestApplicationHistoryServer hadoop.yarn.server.resourcemanager.recovery.TestLeveldbRMStateStore hadoop.yarn.server.resourcemanager.TestRMRestart hadoop.yarn.server.TestMiniYarnClusterNodeUtilization hadoop.yarn.server.TestContainerManagerSecurity hadoop.yarn.server.timeline.TestLevelDBCacheTimelineStore hadoop.yarn.server.timeline.TestOverrideTimelineStoreYarnClient hadoop.yarn.server.timeline.TestEntityGroupFSTimelineStore hadoop.yarn.applications.distributedshell.TestDistributedShell hadoop.mapred.TestShuffleHandler hadoop.mapreduce.v2.hs.TestHistoryServerLeveldbStateStoreService Timed out junit tests : org.apache.hadoop.hdfs.server.datanode.TestFsDatasetCache compile: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/250/artifact/out/patch-compile-root.txt [132K] cc: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/250/artifact/out/patch-compile-root.txt [132K] javac: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/250/artifact/out/patch-compile-root.txt [132K] unit: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/250/artifact/out/patch-unit-hadoop-common-project_hadoop-common.txt [136K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/250/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt [384K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/250/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager.txt [16K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/250/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-applicationhistoryservice.txt [52K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/250/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt [72K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/250/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-tests.txt [324K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/250/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-timeline-pluginstorage.txt [28K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/
[jira] [Created] (HDFS-11509) Ozone: Fix TestEndpoint test regression
Anu Engineer created HDFS-11509: --- Summary: Ozone: Fix TestEndpoint test regression Key: HDFS-11509 URL: https://issues.apache.org/jira/browse/HDFS-11509 Project: Hadoop HDFS Issue Type: Sub-task Components: ozone Affects Versions: HDFS-7240 Reporter: Anu Engineer Assignee: Anu Engineer Fixes test end point regression, with this fix most of the tests in ozone branch is stable. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
[jira] [Resolved] (HDFS-11507) NetworkTopology#chooseRandom may run into a dead loop due to race condition
[
https://issues.apache.org/jira/browse/HDFS-11507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chen Liang resolved HDFS-11507.
---
Resolution: Not A Problem
> NetworkTopology#chooseRandom may run into a dead loop due to race condition
> ---
>
> Key: HDFS-11507
> URL: https://issues.apache.org/jira/browse/HDFS-11507
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
>Reporter: Chen Liang
>Assignee: Chen Liang
>
> {{NetworkTopology#chooseRandom()}} works as:
> 1. counts the number of available nodes as {{availableNodes}},
> 2. checks how many nodes are excluded, deduct from {{availableNodes}}
> 3. if {{availableNodes}} still > 0, then there are nodes available.
> 4. keep looping to find that node
> But now imagine, in the meantime, the actually available nodes got removed in
> step 3 or step 4, and all remaining nodes are excluded nodes. Then, although
> there are no more nodes actually available, the code would still run as
> {{availableNodes}} > 0, and then it would keep getting excluded node and loop
> forever, as
> {{if (excludedNodes == null || !excludedNodes.contains(ret))}}
> will always be false.
> We may fix this by expanding the while loop to also include the
> {{availableNodes}} calculation. Such that we re-calculate {{availableNodes}}
> every time it fails to find an available node.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
Re: About 2.7.4 Release
Our release steps are documented on the wiki: 2.6/2.7: https://wiki.apache.org/hadoop/HowToReleasePreDSBCR 2.8+: https://wiki.apache.org/hadoop/HowToRelease I think given the push toward 2.8 and 3.0, there's less interest in streamlining the 2.6 and 2.7 release processes. CHANGES.txt is the biggest pain, and that's fixed in 2.8+. Current pain points for 2.8+ include: # fixing up JIRA versions and the release notes, though I somewhat addressed this with the versions script for 3.x # making and staging an RC and sending the vote email still requires a lot of manual steps # publishing the release is also quite manual I think the RC issues can be attacked with enough scripting. Steve had an ant file that automated a lot of this for slider. I think it'd be nice to have a nightly Jenkins job that builds an RC, since I've spent a day or two for each 3.x alpha fixing build issues. Publishing can be attacked via a mix of scripting and revamping the darned website. Forrest is pretty bad compared to the newer static site generators out there (e.g. need to write XML instead of markdown, it's hard to review a staging site because of all the absolute links, hard to customize, did I mention XML?), and the look and feel of the site is from the 00s. We don't actually have that much site content, so it should be possible to migrate to a new system. On Tue, Mar 7, 2017 at 9:13 AM, Sangjin Lee wrote: > I don't think there should be any linkage between releasing 2.8.0 and > 2.7.4. If we have a volunteer for releasing 2.7.4, we should go full speed > ahead. We still need a volunteer from a PMC member or a committer as some > tasks may require certain privileges, but I don't think it precludes > working with others to close down the release. > > I for one would like to see more frequent releases, and being able to > automate release steps more would go a long way. > > On Tue, Mar 7, 2017 at 2:16 AM, Marton Elek wrote: > > > Is there any reason to wait for 2.8 with 2.7.4? > > > > Unfortunately the previous thread about release cadence has been ended > > without final decision. But if I understood well, there was more or less > an > > agreement about that it would be great to achieve more frequent releases, > > if possible (with or without written rules and EOL policy). > > > > I personally prefer to be more closer to the scheduling part of the > > proposal: > > > > "A minor release on the latest major line should be every 6 months, and a > > maintenance release on a minor release (as there may be concurrently > > maintained minor releases) every 2 months". > > > > I don't know what is the hardest part of creating new minor/maintenance > > releases. But if the problems are technical (smoketesting, unit tests, > old > > release script, anything else) I would be happy to do any task for new > > maintenance releases (or more frequent releases). > > > > Regards, > > Marton > > > > > > > > From: Akira Ajisaka > > Sent: Tuesday, March 07, 2017 7:34 AM > > To: Brahma Reddy Battula; Hadoop Common; yarn-...@hadoop.apache.org; > > Hdfs-dev; mapreduce-...@hadoop.apache.org > > Subject: Re: About 2.7.4 Release > > > > Probably 2.8.0 will be released soon. > > https://issues.apache.org/jira/browse/HADOOP-13866? > > focusedCommentId=15898379&page=com.atlassian.jira. > > plugin.system.issuetabpanels:comment-tabpanel#comment-15898379 > > > > I'm thinking 2.7.4 release process starts after 2.8.0 release, > > so 2.7.4 will be released in April or May. (hopefully) > > > > Thoughts? > > > > Regards, > > Akira > > > > On 2017/03/01 21:01, Brahma Reddy Battula wrote: > > > Hi All > > > > > > It has been six months for branch-2.7 release.. is there any near plan > > for 2.7.4..? > > > > > > > > > Thanks&Regards > > > Brahma Reddy Battula > > > > > > > > > > - > > 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: About 2.7.4 Release
I was planning to take this up, celebrating my return from my paternity leave of absence for quite a while. Marton, let me know if you do want to take this up instead and we can work together. Thanks +Vinod > On Mar 7, 2017, at 9:13 AM, Sangjin Lee wrote: > > If we have a volunteer for releasing 2.7.4, we should go full speed > ahead. We still need a volunteer from a PMC member or a committer as some > tasks may require certain privileges, but I don't think it precludes > working with others to close down the release.
Re: About 2.7.4 Release
> On Mar 7, 2017, at 2:51 PM, Andrew Wang wrote: > I think it'd be nice to > have a nightly Jenkins job that builds an RC, Just a reminder that any such build cannot be used for an actual release: http://www.apache.org/legal/release-policy.html#owned-controlled-hardware - To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
[jira] [Resolved] (HDFS-11183) Document XOR policy XOR-2-1-64k support in HDFS
[ https://issues.apache.org/jira/browse/HDFS-11183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang resolved HDFS-11183. Resolution: Not A Problem Yea, I looked at the XOR-related docs while working on the other JIRA, and I think it's sufficient for now. Thanks for following up Sammi, resolving this one. > Document XOR policy XOR-2-1-64k support in HDFS > --- > > Key: HDFS-11183 > URL: https://issues.apache.org/jira/browse/HDFS-11183 > Project: Hadoop HDFS > Issue Type: Task >Affects Versions: 3.0.0-alpha2 >Reporter: SammiChen >Assignee: SammiChen > Labels: hdfs-ec-3.0-must-do > > A new EC policy XOR-2-1-64k is added in HDFS. This task is to update HDFS > related documents about how to use this policy -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
[jira] [Created] (HDFS-11510) Revamp erasure coding user documentation
Andrew Wang created HDFS-11510: -- Summary: Revamp erasure coding user documentation Key: HDFS-11510 URL: https://issues.apache.org/jira/browse/HDFS-11510 Project: Hadoop HDFS Issue Type: Improvement Components: documentation Affects Versions: 3.0.0-alpha3 Reporter: Andrew Wang Assignee: Andrew Wang After we finish more of the must-do EC changes targeted for 3.0, it'd be good to take a fresh look at the EC documentation to make sure it's comprehensive, particularly how to choose a good erasure coding policy for your cluster and how to enable policies. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
