Mingliang Liu created HADOOP-13512:
--
Summary: ReloadingX509TrustManager should keep reloading in case
of exception
Key: HADOOP-13512
URL: https://issues.apache.org/jira/browse/HADOOP-13512
Project: H
Tibor Kiss created HADOOP-13513:
---
Summary: Java 1.7 support for org.apache.hadoop.fs.azure testcases
Key: HADOOP-13513
URL: https://issues.apache.org/jira/browse/HADOOP-13513
Project: Hadoop Common
Ewan Higgs created HADOOP-13514:
---
Summary: Upgrade surefire to 2.19.1
Key: HADOOP-13514
URL: https://issues.apache.org/jira/browse/HADOOP-13514
Project: Hadoop Common
Issue Type: Task
Harsh J created HADOOP-13515:
Summary: Redundant transitionToActive call can cause a NameNode to
crash
Key: HADOOP-13515
URL: https://issues.apache.org/jira/browse/HADOOP-13515
Project: Hadoop Common
[
https://issues.apache.org/jira/browse/HADOOP-13271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved HADOOP-13271.
-
Resolution: Cannot Reproduce
Fix Version/s: 2.8.0
> Intermittent failure of TestS
I'm trying to add a new contributor, "shenyinjie", but I'm getting the couldn't
connect to server message; tried on chrome and firefox, and tried to paste the
username in rather than rely on any popup completion.
no joy: has anyone else succeeded at this recently?
-
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
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
Shaik Idris Ali created HADOOP-13516:
Summary: Listing an empty s3a NON root directory throws
FileNotFound.
Key: HADOOP-13516
URL: https://issues.apache.org/jira/browse/HADOOP-13516
Project: Hadoo
[
https://issues.apache.org/jira/browse/HADOOP-13516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved HADOOP-13516.
-
Resolution: Duplicate
Assignee: Lei (Eddy) Xu
Fix Version/s: 2.8.0
> Lis
> 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
[
https://issues.apache.org/jira/browse/HADOOP-13516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran reopened HADOOP-13516:
-
Assignee: Steve Loughran (was: Lei (Eddy) Xu)
> Listing an empty s3a NON root directo
It’s odd that Firefox didn’t work for you. My standard workaround is to use
Firefox, and that’s what I just did successfully for shenyinjie.
It’s quite mysterious to me that this problem would be browser-specific at all
though.
--Chris Nauroth
On 8/18/16, 6:53 AM, "Steve Loughran" wrote:
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
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
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
>
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
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
Steve Loughran created HADOOP-13517:
---
Summary: TestS3NContractRootDir.testRecursiveRootListing failing
Key: HADOOP-13517
URL: https://issues.apache.org/jira/browse/HADOOP-13517
Project: Hadoop Common
Steve Loughran created HADOOP-13518:
---
Summary: backport HADOOP-9258 to branch-2
Key: HADOOP-13518
URL: https://issues.apache.org/jira/browse/HADOOP-13518
Project: Hadoop Common
Issue Type:
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
I just added someone two days ago for MAPREDUCE-6751. My machine is OS
X El Capitan running Chrome 51.0.2704.103.
-Ray
On 8/18/16 6:53 AM, Steve Loughran wrote:
I'm trying to add a new contributor, "shenyinjie", but I'm getting the couldn't
connect to server message; tried on chrome and fire
It happens to me too on both Firefox / Chrome.
+Vinod
> On Aug 18, 2016, at 8:39 AM, Chris Nauroth wrote:
>
> It’s odd that Firefox didn’t work for you. My standard workaround is to use
> Firefox, and that’s what I just did successfully for shenyinjie.
>
> It’s quite mysterious to me that th
23 matches
Mail list logo
