Hi Andrew
Thanks for update on release plan!
I would like to discuss specifically regarding compatibility of releases.
What is the compatibility to be maintained for GA if we don't merge to
beta1 release? IIUC, till now all the releases were alpha where
compatibility was not that important. All t
Hi All
If you get chance, can you please review the following. I feel, these two are
good candidates for 2.8.2 which is going to release soon.
https://issues.apache.org/jira/browse/HDFS-12084
https://issues.apache.org/jira/browse/HDFS-12299
--Brahma Reddy Battula
steven-wugang created HDFS-12353:
Summary: Modify Dfsuse percent of dfsadmin report inconsistent
with Dfsuse percent of datanode reports.
Key: HDFS-12353
URL: https://issues.apache.org/jira/browse/HDFS-12353
On Thu, Aug 24, 2017 at 2:25 PM, Andrew Wang wrote:
> Do you mind holding this until 3.1? Same reasoning as for the other branch
> merge proposals, we're simply too late in the 3.0.0 release cycle.
That wouldn't be too dire.
That said, this has the same design and impact as YARN federation.
Spec
Chen Liang created HDFS-12352:
-
Summary: [branch-2] Use HDFS specific network topology to choose
datanode in BlockPlacementPolicyDefault
Key: HDFS-12352
URL: https://issues.apache.org/jira/browse/HDFS-12352
Lei (Eddy) Xu created HDFS-12351:
Summary: Explicitly describe the minimal number of DataNodes
required to support an EC policy in EC document.
Key: HDFS-12351
URL: https://issues.apache.org/jira/browse/HDFS-12351
Do you mind holding this until 3.1? Same reasoning as for the other branch
merge proposals, we're simply too late in the 3.0.0 release cycle.
On Thu, Aug 24, 2017 at 1:39 PM, Chris Douglas wrote:
> I'd definitely support merging this to trunk. The implementation is
> almost entirely outside of H
I'd definitely support merging this to trunk. The implementation is
almost entirely outside of HDFS and, as Inigo detailed, has been
tested at scale. The branch is in a functional state with
documentation and tests. -C
On Mon, Aug 21, 2017 at 6:11 PM, Iñigo Goiri wrote:
> Hi all,
>
>
>
> We would
Glad to see the discussion continued in my absence :)
>From a release management perspective, it's *extremely* reasonable to block
the inclusion of new features a month from the planned release date. A
typical software development lifecycle includes weeks of feature freeze and
weeks of code freeze
Ajay Kumar created HDFS-12350:
-
Summary: Support meta tags in Ozone configs
Key: HDFS-12350
URL: https://issues.apache.org/jira/browse/HDFS-12350
Project: Hadoop HDFS
Issue Type: Improvement
Lei (Eddy) Xu created HDFS-12349:
Summary: Improve log message when
Key: HDFS-12349
URL: https://issues.apache.org/jira/browse/HDFS-12349
Project: Hadoop HDFS
Issue Type: Improvement
Thank you very much Varun Vasudev, Wangda Tan, Daniel and all the folks who
helped in getting this feature in this level.
Starting with my +1 (binding).
# Tested a 5 node cluster with resource profiles enabled/disabled (feature
is disabled by default)
# All apis added are marked as Unstable/Evo
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/502/
[Aug 23, 2017 4:56:20 PM] (wangda) YARN-6251. Do async container release to
prevent deadlock during
[Aug 23, 2017 6:37:18 PM] (jzhuge) HADOOP-14251. Credential provider should
handle property key
[Aug 23,
Thank you very much Vrushali, Rohith, Varun and other folks who made this
happen. Great work, really appreciate the same!!
+1 (binding) from my side:
# Tested ATSv2 cluster in a secure cluster. Ran some basic jobs
# Accessed new YARN UI which shows various flows/flow activity etc. Seems
fine.
# B
[
https://issues.apache.org/jira/browse/HDFS-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kihwal Lee resolved HDFS-6964.
--
Resolution: Duplicate
> NN fails to fix under replication leading to data loss
>
15 matches
Mail list logo
