SammiChen created HDFS-12405:
Summary: Complete remove "removed" state erasure coding policy
during Namenode restart
Key: HDFS-12405
URL: https://issues.apache.org/jira/browse/HDFS-12405
Project: Hadoop H
[
https://issues.apache.org/jira/browse/HDFS-11744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mukul Kumar Singh resolved HDFS-11744.
--
Resolution: Duplicate
This has already been fixed. Duping it
> Ozone: Implement the tra
Thanks for starting this thread, Wangda!
+1 for establishing a faster cadence now itself.
One word of caution though. The same I expressed while we were trying to do
both 2.8 and 3.0 releases at the same time. Please try avoiding concurrent
releases and splitting community bandwidth - it's not
As I mentioned in the [VOTE] thread at [1], for Timeline Service v2, we
are thinking about merging to branch2 some time in the next couple of weeks.
So far, we have been maintaining a branch2 based YARN-5355_branch2 along
with our trunk based feature branch YARN-5355. Varun Saxena has been
dilig
Thanks everyone.
It has been over a week (~9 days) since TSv2 has been merged to trunk with
no problems thus far. We are now thinking about merging timeline service v2
to branch2 some time in the next few weeks.
So far, we have been maintaining a branch2 based YARN-5355_branch2 along
with our tru
https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+3+release+status+updates
2017-09-07
Slightly early update since I'll be out tomorrow. We're one week out, and
focus is on blocker burndown.
Highlights:
- 3.1.0 release planning is underway, led by Wangda. Target release date
is in
Hi folks,
This vote closes today. I see a -1 from Allen on inclusion in beta1. I see
there's active fixing going on, but given that we're one week out from RC0,
I think we should drop this from beta1.
Allen, Jian, others, is this reasonable? What release should we retarget
this for? I don't have
Thanks for all your valuable feedbacks.
Regarding to security issues for alpha features: I completely agree with
Larry: ideally, all alpha features should be disabled by default.
Steve/Arun/Haibo: could you please comment about feature's rough merge plan
and status (like alpha/beta).
I will wait
Hi Subru,
We are also discussing the merge of HDFS-10467 (Router-based federation)
and we would like to target 2.9 to do a full release together with YARN
federation.
Chris Douglas already arranged the integration into trunk for 3.0.0 GA.
Regarding the points to cover:
1. API compatibility: we jus
Yongjun Zhang created HDFS-12404:
Summary: Name of config introduced by HDFS-12357 need to be
changed from authorization.provider to attribute.provider
Key: HDFS-12404
URL: https://issues.apache.org/jira/browse/HD
There's also the DataNode data directory layout. FS edit logs should also
be included if we're including the fsimage.
Historically we've bumped these in minor and major releases, though I'm not
sure whether precedent supports the practice. It means you can't downgrade,
and features that need metad
On 7 Sep 2017, at 19:13, Daniel Templeton
mailto:dan...@cloudera.com>> wrote:
Good point. I think it would be valuable to enumerate the policies around the
versioned state stores. We have the three you listed. We should probably
include the HDFS fsimage in that list. Any others?
S3Guard n
Good point. I think it would be valuable to enumerate the policies
around the versioned state stores. We have the three you listed. We
should probably include the HDFS fsimage in that list. Any others?
I also want to add a section that clarifies when it's OK to change the
visibility or audi
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/516/
[Sep 6, 2017 6:51:51 AM] (cdouglas) HADOOP-12077. Provide a multi-URI
replication Inode for ViewFs.
[Sep 6, 2017 8:19:34 PM] (junping_du) YARN-7148. TestLogsCLI fails in trunk and
branch-2 and javadoc erro
14 matches
Mail list logo
