Yiqun Lin created HDFS-10778:
Summary: Optimize the output result of FileDistribution processor
in hdfs oiv command
Key: HDFS-10778
URL: https://issues.apache.org/jira/browse/HDFS-10778
Project: Hadoop HD
Wei-Chiu Chuang created HDFS-10777:
--
Summary: DataNode should report&remove volume failures if DU
cannot access files
Key: HDFS-10777
URL: https://issues.apache.org/jira/browse/HDFS-10777
Project: Ha
Thanks Vinod for creating new RC for 2.7.3 release.
+1 (binding) based on following verifications:
- Download src and binary tar ball and verify signature (gpg --verify).
- Build from source Java 1.8.0_31-b13 on Mac native successfully.
- Build from source with Java 1.7.0_79-b15 on Ubuntu VM su
Hi All,
Thank you for all the inputs on HDFS-9395. I have opened HDFS-10776 to discuss
the modifications needed for audit logging to be consistent and comprehensive.
We can move this discussion to the new JIRA.
Appreciate the support.
Regards,Kuhu Shukla
On Thursday, August 18, 2016 12:04 P
>
What is a realistic strategy for us to evolve the HDFS audit log in a
backward-compatible way? If the API is essentially any form of ad-hoc
scripting, then for any proposed audit log format change, I can find a
reason to veto it on grounds of backward incompatibility.
Yeah when log scraping is
Kuhu Shukla created HDFS-10776:
--
Summary: Revisit Hdfs Audit Logging
Key: HDFS-10776
URL: https://issues.apache.org/jira/browse/HDFS-10776
Project: Hadoop HDFS
Issue Type: Bug
Affects Versio
Andrew, thanks for adding your perspective on this.
What is a realistic strategy for us to evolve the HDFS audit log in a
backward-compatible way? If the API is essentially any form of ad-hoc
scripting, then for any proposed audit log format change, I can find a reason
to veto it on grounds of
I believe it was described as some previous audit entries have been
superseded by new ones and that the order may no longer be the same for
other entries.
For what it’s worth, I agree with the assertion that this is a backward
incompatible output - especially for audit logs.
On Thu, Aug 18, 2016
An incompatible APIs change is developer unfriendly. An incompatible behavioral
change is operator unfriendly. Historically, one dimension of incompatibility
has had a lot more mindshare than the other. It's great that this might be
changing for the better.
Where I work when we move from one H
> On 18 Aug 2016, at 14:57, Junping Du wrote:
>
> I think Allen's previous comments are very misleading.
> In my understanding, only incompatible API (RPC, CLIs, WebService, etc.)
> shouldn't land on branch-2, but other incompatible behaviors (logs,
> audit-log, daemon's restart, etc.) should
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/137/
[Aug 17, 2016 10:04:58 AM] (vvasudev) YARN-5455. Update Javadocs for
LinuxContainerExecutor. Contributed by
[Aug 17, 2016 4:22:31 PM] (jlowe) MAPREDUCE-6690. Limit the number of resources
a single map redu
I think Allen's previous comments are very misleading.
In my understanding, only incompatible API (RPC, CLIs, WebService, etc.)
shouldn't land on branch-2, but other incompatible behaviors (logs, audit-log,
daemon's restart, etc.) should get flexible for landing. Otherwise, how could
52 issues
Eisuke Umeda created HDFS-10775:
---
Summary: Under-Replicated Blocks can not be recovered
Key: HDFS-10775
URL: https://issues.apache.org/jira/browse/HDFS-10775
Project: Hadoop HDFS
Issue Type: Bu
13 matches
Mail list logo
