rowe created HADOOP-14148:
-
Summary: hdfs command handing in futex
Key: HADOOP-14148
URL: https://issues.apache.org/jira/browse/HADOOP-14148
Project: Hadoop Common
Issue Type: Bug
Affects
> On 6 Mar 2017, at 09:10, Simon Scott wrote:
>
> Yes it is. But the registration of the FsUrlStreamHandlerFactory has surely
> influenced the JDK in some manner?
>
Not at that point, I don't think. Why not comment out the hadoop code and rerun
'
>
Jin Hyuk Chang created HADOOP-14149:
---
Summary: Incorrect location of service provider configuration file
on Azure Data lake Filesystem
Key: HADOOP-14149
URL: https://issues.apache.org/jira/browse/HADOOP-14149
[
https://issues.apache.org/jira/browse/HADOOP-13606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Zhuge reopened HADOOP-13606:
-
Assignee: John Zhuge (was: Steve Loughran)
> swift FS to add a service load metadata file
>
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/337/
[Mar 6, 2017 1:30:01 AM] (aajisaka) HADOOP-14056. Update maven-javadoc-plugin
to 2.10.4.
-1 overall
The following subsystems voted -1:
asflicense unit
The following subsystems voted -1 but
were
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/249/
[Mar 6, 2017 1:30:01 AM] (aajisaka) HADOOP-14056. Update maven-javadoc-plugin
to 2.10.4.
[Mar 6, 2017 11:04:03 AM] (yqlin) HDFS-8741. Proper error msg to be printed
when invalid operation type is
-1
[
https://issues.apache.org/jira/browse/HADOOP-14023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Mackrory resolved HADOOP-14023.
Resolution: Resolved
Yes this is fixed. The root of the problem was an imperfect way of
[
https://issues.apache.org/jira/browse/HADOOP-14149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Zhuge resolved HADOOP-14149.
-
Resolution: Duplicate
Thank you [~jinhyukch...@gmail.com] for reporting the issue and
Hi folks,
Looks like H9 is having problems cleaning the workspace, leading to a lot
of silent precommit failures. I filed this INFRA JIRA:
https://issues.apache.org/jira/browse/INFRA-13618
It's quite possible you'll have to retrigger pending precommit runs, the
HDFS runs are pretty red.
Best,
[
https://issues.apache.org/jira/browse/HADOOP-14022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved HADOOP-14022.
-
Resolution: Duplicate
> S3 connections fails if in-URI AWS secret key contains '+' and
Do you have a link to your old job somewhere?
I'm also wondering what causes this; does this issue surface in the same
way each time?
Also wondering, should we nuke the workspace before every run, for improved
reliability?
On Mon, Mar 6, 2017 at 1:08 PM, Allen Wittenauer
I also found this older JIRA I filed for H9. Either this box is suspect, or
we have a disproportionate number of our builds running on it.
https://issues.apache.org/jira/browse/INFRA-13234
On Mon, Mar 6, 2017 at 1:17 PM, Andrew Wang
wrote:
> Do you have a link to your
> On Mar 6, 2017, at 11:27 AM, Andrew Wang wrote:
> Looks like H9 is having problems cleaning the workspace, leading to a lot
> of silent precommit failures. I filed this INFRA JIRA:
> https://issues.apache.org/jira/browse/INFRA-13618
Have we tried writing a job that
> On Mar 6, 2017, at 1:17 PM, Andrew Wang wrote:
>
> Do you have a link to your old job somewhere?
Nope, but it’s trivial to write. single job that only runs on H9 that
removes that other job’s workspace dir. You can also try using the “Wipe out
current
> On Mar 6, 2017, at 1:57 PM, Andrew Wang wrote:
>
> I'll leave it there so it's ready for next time. If this keeps happening on
> H9, then I'm going to ask infra to reimage it. FWIW I haven't seen this on
> our internal unit test runs, so it points to an H9-specific
[
https://issues.apache.org/jira/browse/HADOOP-10856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Wang resolved HADOOP-10856.
--
Resolution: Won't Fix
I agree with Tucu's assessment above, we don't need to do finer-grained
[
https://issues.apache.org/jira/browse/HADOOP-9357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Wang resolved HADOOP-9357.
-
Resolution: Invalid
I'm going to just resolve this one, unlikely we're going to make any
Thanks Allen. I wrote this little job that does what we want:
https://builds.apache.org/view/H-L/view/Hadoop/job/hadoop-clean-h9/
The bad directory is some NN metadata dir, which could come from basically
any minicluster test.
I'll leave it there so it's ready for next time. If this keeps
Santhosh G Nayak created HADOOP-14150:
-
Summary: Implement getHomeDirectory() method in
NativeAzureFileSystem
Key: HADOOP-14150
URL: https://issues.apache.org/jira/browse/HADOOP-14150
Project:
Thanks Steve for starting the discussion.
Now I commit and cherry-pick patches with the -S option and have not
faced any problems.
-Akira
On 2017/02/24 20:36, Steve Loughran wrote:
For the next few days I'm experimenting with the -S option on signing commits,
which tells git to ask gpg to
Probably 2.8.0 will be released soon.
https://issues.apache.org/jira/browse/HADOOP-13866?focusedCommentId=15898379=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
Dear Apache Hadoop community,
My name is Aitor Osa and I'm currently working in the Telematics group of
Mondragon Unibertsitatea, Mondragon university.
As part of our research, we are trying to implement CP-ABE
(http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.
475.2538=rep1=pdf) crypto
Yes it is. But the registration of the FsUrlStreamHandlerFactory has surely
influenced the JDK in some manner?
-Original Message-
From: Steve Loughran [mailto:ste...@hortonworks.com]
Sent: 03 March 2017 21:49
Cc: common-dev@hadoop.apache.org
Subject: Re: FsUrlStreamHandlerFactory and
23 matches
Mail list logo