[jira] [Commented] (HADOOP-12415) hdfs and nfs builds broken on -missing compile-time dependency on netty
[
https://issues.apache.org/jira/browse/HADOOP-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117832#comment-15117832
]
Konstantin Boudnik commented on HADOOP-12415:
-
Thanks Vinod!
> hdfs and nfs builds broken on -missing compile-time dependency on netty
> ---
>
> Key: HADOOP-12415
> URL: https://issues.apache.org/jira/browse/HADOOP-12415
> Project: Hadoop Common
> Issue Type: Bug
> Components: nfs
>Affects Versions: 2.7.1
> Environment: Bigtop, plain Linux distro of any kind
>Reporter: Konstantin Boudnik
>Assignee: Tom Zeng
> Fix For: 2.7.2
>
> Attachments: HADOOP-12415.patch
>
>
> As discovered in BIGTOP-2049 {{hadoop-nfs}} module compilation is broken.
> Looks like that HADOOP-11489 is the root-cause of it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12415) hdfs and nfs builds broken on -missing compile-time dependency on netty
[
https://issues.apache.org/jira/browse/HADOOP-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15032502#comment-15032502
]
Konstantin Boudnik commented on HADOOP-12415:
-
The way to reproduce it is described in the JIRA - just look through the
comments, it should be close to the top.
The reason we didn't simply reverted HADOOP-11489 is because the current fix
presents a cleaner solution. Besides, Steve asked to make it more fine-grained
in
[here|https://issues.apache.org/jira/browse/HADOOP-12415?focusedCommentId=14877093=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14877093]
> hdfs and nfs builds broken on -missing compile-time dependency on netty
> ---
>
> Key: HADOOP-12415
> URL: https://issues.apache.org/jira/browse/HADOOP-12415
> Project: Hadoop Common
> Issue Type: Bug
> Components: nfs
>Affects Versions: 2.7.1
> Environment: Bigtop, plain Linux distro of any kind
>Reporter: Konstantin Boudnik
>Assignee: Tom Zeng
> Fix For: 2.8.0
>
> Attachments: HADOOP-12415.patch
>
>
> As discovered in BIGTOP-2049 {{hadoop-nfs}} module compilation is broken.
> Looks like that HADOOP-11489 is the root-cause of it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12415) hdfs and nfs builds broken on -missing compile-time dependency on netty
[
https://issues.apache.org/jira/browse/HADOOP-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15028026#comment-15028026
]
Konstantin Boudnik commented on HADOOP-12415:
-
Steve, arguably this is critical because the build is broken when ran from a
clean slate. I don't mind one way or another, as we just patched the Hadoop in
the Bigtop stack, but ppl using it directly from the release artifacts would be
affected.
> hdfs and nfs builds broken on -missing compile-time dependency on netty
> ---
>
> Key: HADOOP-12415
> URL: https://issues.apache.org/jira/browse/HADOOP-12415
> Project: Hadoop Common
> Issue Type: Bug
> Components: nfs
>Affects Versions: 2.7.1
> Environment: Bigtop, plain Linux distro of any kind
>Reporter: Konstantin Boudnik
>Assignee: Tom Zeng
> Fix For: 2.8.0
>
> Attachments: HADOOP-12415.patch
>
>
> As discovered in BIGTOP-2049 {{hadoop-nfs}} module compilation is broken.
> Looks like that HADOOP-11489 is the root-cause of it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-12415) hdfs and nfs builds broken on -missing compile-time dependency on netty
[
https://issues.apache.org/jira/browse/HADOOP-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik updated HADOOP-12415:
Target Version/s: 2.8.0, 2.7.2 (was: 2.8.0)
> hdfs and nfs builds broken on -missing compile-time dependency on netty
> ---
>
> Key: HADOOP-12415
> URL: https://issues.apache.org/jira/browse/HADOOP-12415
> Project: Hadoop Common
> Issue Type: Bug
> Components: nfs
>Affects Versions: 2.7.1
> Environment: Bigtop, plain Linux distro of any kind
>Reporter: Konstantin Boudnik
>Assignee: Tom Zeng
> Attachments: HADOOP-12415.patch
>
>
> As discovered in BIGTOP-2049 {{hadoop-nfs}} module compilation is broken.
> Looks like that HADOOP-11489 is the root-cause of it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12415) hdfs and nfs builds broken on -missing compile-time dependency on netty
[
https://issues.apache.org/jira/browse/HADOOP-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026041#comment-15026041
]
Konstantin Boudnik commented on HADOOP-12415:
-
Ok, I have pushed the fix into trunk and branch-2
Looks like 2.7.2 is still going, can I add into the train? Will do in the
morning unless hear otherwise. Thanks!
> hdfs and nfs builds broken on -missing compile-time dependency on netty
> ---
>
> Key: HADOOP-12415
> URL: https://issues.apache.org/jira/browse/HADOOP-12415
> Project: Hadoop Common
> Issue Type: Bug
> Components: nfs
>Affects Versions: 2.7.1
> Environment: Bigtop, plain Linux distro of any kind
>Reporter: Konstantin Boudnik
>Assignee: Tom Zeng
> Attachments: HADOOP-12415.patch
>
>
> As discovered in BIGTOP-2049 {{hadoop-nfs}} module compilation is broken.
> Looks like that HADOOP-11489 is the root-cause of it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-12415) hdfs and nfs builds broken on -missing compile-time dependency on netty
[
https://issues.apache.org/jira/browse/HADOOP-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik updated HADOOP-12415:
Fix Version/s: 2.8.0
> hdfs and nfs builds broken on -missing compile-time dependency on netty
> ---
>
> Key: HADOOP-12415
> URL: https://issues.apache.org/jira/browse/HADOOP-12415
> Project: Hadoop Common
> Issue Type: Bug
> Components: nfs
>Affects Versions: 2.7.1
> Environment: Bigtop, plain Linux distro of any kind
>Reporter: Konstantin Boudnik
>Assignee: Tom Zeng
> Fix For: 2.8.0
>
> Attachments: HADOOP-12415.patch
>
>
> As discovered in BIGTOP-2049 {{hadoop-nfs}} module compilation is broken.
> Looks like that HADOOP-11489 is the root-cause of it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-12415) hdfs and nfs builds broken on -missing compile-time dependency on netty
[
https://issues.apache.org/jira/browse/HADOOP-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik updated HADOOP-12415:
Resolution: Fixed
Status: Resolved (was: Patch Available)
The fix has been pushed. Thanks for the contribution, Tom!
> hdfs and nfs builds broken on -missing compile-time dependency on netty
> ---
>
> Key: HADOOP-12415
> URL: https://issues.apache.org/jira/browse/HADOOP-12415
> Project: Hadoop Common
> Issue Type: Bug
> Components: nfs
>Affects Versions: 2.7.1
> Environment: Bigtop, plain Linux distro of any kind
>Reporter: Konstantin Boudnik
>Assignee: Tom Zeng
> Fix For: 2.8.0
>
> Attachments: HADOOP-12415.patch
>
>
> As discovered in BIGTOP-2049 {{hadoop-nfs}} module compilation is broken.
> Looks like that HADOOP-11489 is the root-cause of it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12415) hdfs and nfs builds broken on -missing compile-time dependency on netty
[
https://issues.apache.org/jira/browse/HADOOP-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15005048#comment-15005048
]
Konstantin Boudnik commented on HADOOP-12415:
-
I think we're good here. Sorry, I dropped the ball - should've been committing
this a while ago. Will do over the weekend.
> hdfs and nfs builds broken on -missing compile-time dependency on netty
> ---
>
> Key: HADOOP-12415
> URL: https://issues.apache.org/jira/browse/HADOOP-12415
> Project: Hadoop Common
> Issue Type: Bug
> Components: nfs
>Affects Versions: 2.7.1
> Environment: Bigtop, plain Linux distro of any kind
>Reporter: Konstantin Boudnik
>Assignee: Tom Zeng
> Attachments: HADOOP-12415.patch
>
>
> As discovered in BIGTOP-2049 {{hadoop-nfs}} module compilation is broken.
> Looks like that HADOOP-11489 is the root-cause of it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12415) hdfs and nfs builds broken on -missing compile-time dependency on netty
[
https://issues.apache.org/jira/browse/HADOOP-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14968168#comment-14968168
]
Konstantin Boudnik commented on HADOOP-12415:
-
I will commit this later in the day, Steve. Thanks for the review.
> hdfs and nfs builds broken on -missing compile-time dependency on netty
> ---
>
> Key: HADOOP-12415
> URL: https://issues.apache.org/jira/browse/HADOOP-12415
> Project: Hadoop Common
> Issue Type: Bug
> Components: nfs
>Affects Versions: 2.7.1
> Environment: Bigtop, plain Linux distro of any kind
>Reporter: Konstantin Boudnik
>Assignee: Tom Zeng
> Attachments: HADOOP-12415.patch
>
>
> As discovered in BIGTOP-2049 {{hadoop-nfs}} module compilation is broken.
> Looks like that HADOOP-11489 is the root-cause of it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12415) hdfs and nfs builds broken on -missing compile-time dependency on netty
[
https://issues.apache.org/jira/browse/HADOOP-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14964139#comment-14964139
]
Konstantin Boudnik commented on HADOOP-12415:
-
Let's get it in, then?
> hdfs and nfs builds broken on -missing compile-time dependency on netty
> ---
>
> Key: HADOOP-12415
> URL: https://issues.apache.org/jira/browse/HADOOP-12415
> Project: Hadoop Common
> Issue Type: Bug
> Components: nfs
>Affects Versions: 2.7.1
> Environment: Bigtop, plain Linux distro of any kind
>Reporter: Konstantin Boudnik
>Assignee: Tom Zeng
> Attachments: HADOOP-12415.patch
>
>
> As discovered in BIGTOP-2049 {{hadoop-nfs}} module compilation is broken.
> Looks like that HADOOP-11489 is the root-cause of it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-11945) Add Apache Ignite to the "Hadoop-related projects"
[ https://issues.apache.org/jira/browse/HADOOP-11945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HADOOP-11945: Summary: Add Apache Ignite to the "Hadoop-related projects" (was: Add Apache Ignite (incubating) to the "Hadoop-related projects") > Add Apache Ignite to the "Hadoop-related projects" > -- > > Key: HADOOP-11945 > URL: https://issues.apache.org/jira/browse/HADOOP-11945 > Project: Hadoop Common > Issue Type: Improvement > Components: site >Affects Versions: 2.5.2 >Reporter: Konstantin Boudnik >Assignee: Konstantin Boudnik >Priority: Minor > Fix For: site > > > Apache Ignite (incubating) has the implementation of HDFS compatible > in-memory file system (IGFS) and in-memory MapReduce accelerator. These two > components allow Ignite users to run OLTP/SQL/computational workloads on top > of HDFS storage. > Let's add this project to the list of Hadoop related ones. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HADOOP-7481) Wire AOP test in Mavenized Hadoop common
[ https://issues.apache.org/jira/browse/HADOOP-7481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik resolved HADOOP-7481. Resolution: Won't Fix Release Note: Ain't gonna happen clearly: the FI has been removed from the source tree, so there's no point of keeping this ticket open. > Wire AOP test in Mavenized Hadoop common > > > Key: HADOOP-7481 > URL: https://issues.apache.org/jira/browse/HADOOP-7481 > Project: Hadoop Common > Issue Type: Sub-task >Reporter: Alejandro Abdelnur >Assignee: Konstantin Boudnik > > We ned add a Maven profile that activates the AOP injection and runs the > necessary AOPed tests. I believe there should be a Maven plugin for doing > that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HADOOP-7730) Allow TestCLI to be run against a cluster
[ https://issues.apache.org/jira/browse/HADOOP-7730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik resolved HADOOP-7730. Resolution: Won't Fix Release Note: The resolution has been done in the Bigtop a few years ago. Closing this one as of irrelevant to the project. Target Version/s: 1.3.0, 0.22.1 (was: 0.22.1, 1.3.0) > Allow TestCLI to be run against a cluster > - > > Key: HADOOP-7730 > URL: https://issues.apache.org/jira/browse/HADOOP-7730 > Project: Hadoop Common > Issue Type: Test > Components: test >Affects Versions: 0.20.205.0, 0.22.0 >Reporter: Konstantin Boudnik >Assignee: Konstantin Boudnik > Attachments: HADOOP-7730.patch, HADOOP-7730.trunk.patch, > HADOOP-7730.trunk.patch > > > Use the same CLI test to test cluster bits (see HDFS-1762 for more info) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12415) hdfs and nfs builds broken on -missing compile-time dependency on netty
[
https://issues.apache.org/jira/browse/HADOOP-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14900920#comment-14900920
]
Konstantin Boudnik commented on HADOOP-12415:
-
Don't worry - I haven't said anything about 'blaming'. I simply stated that the
issue can be reproduced in any environment.
> hdfs and nfs builds broken on -missing compile-time dependency on netty
> ---
>
> Key: HADOOP-12415
> URL: https://issues.apache.org/jira/browse/HADOOP-12415
> Project: Hadoop Common
> Issue Type: Bug
> Components: nfs
>Affects Versions: 2.7.1
> Environment: Bigtop, plain Linux distro of any kind
>Reporter: Konstantin Boudnik
>Assignee: Tom Zeng
> Attachments: HADOOP-12415.patch
>
>
> As discovered in BIGTOP-2049 {{hadoop-nfs}} module compilation is broken.
> Looks like that HADOOP-11489 is the root-cause of it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12415) hdfs and nfs builds broken on -missing compile-time dependency on netty
[
https://issues.apache.org/jira/browse/HADOOP-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14877236#comment-14877236
]
Konstantin Boudnik commented on HADOOP-12415:
-
Steve, the bug isn't Bigtop specific. As any other integration bug it is easily
found with bigtop, but one can run the build from 2.7.1 release and step on the
same issue. Hence, renaming the bug again.
> hdfs and nfs builds broken on -missing compile-time dependency on netty
> ---
>
> Key: HADOOP-12415
> URL: https://issues.apache.org/jira/browse/HADOOP-12415
> Project: Hadoop Common
> Issue Type: Bug
> Components: nfs
>Affects Versions: 2.7.1
> Environment: Bigtop, plain Linux distro of any kind
>Reporter: Konstantin Boudnik
>Assignee: Tom Zeng
> Attachments: HADOOP-12415.patch
>
>
> As discovered in BIGTOP-2049 {{hadoop-nfs}} module compilation is broken.
> Looks like that HADOOP-11489 is the root-cause of it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-12415) hdfs and nfs builds broken on -missing compile-time dependency on netty
[
https://issues.apache.org/jira/browse/HADOOP-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik updated HADOOP-12415:
Summary: hdfs and nfs builds broken on -missing compile-time dependency on
netty (was: hdfs and nfs builds broken on Bigtop -missing compile-time
dependency on netty)
> hdfs and nfs builds broken on -missing compile-time dependency on netty
> ---
>
> Key: HADOOP-12415
> URL: https://issues.apache.org/jira/browse/HADOOP-12415
> Project: Hadoop Common
> Issue Type: Bug
> Components: nfs
>Affects Versions: 2.7.1
> Environment: Bigtop, plain Linux distro of any kind
>Reporter: Konstantin Boudnik
>Assignee: Tom Zeng
> Attachments: HADOOP-12415.patch
>
>
> As discovered in BIGTOP-2049 {{hadoop-nfs}} module compilation is broken.
> Looks like that HADOOP-11489 is the root-cause of it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-12415) hdfs and nfs builds broken on Bigtop -missing compile-time dependency on netty
[
https://issues.apache.org/jira/browse/HADOOP-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik updated HADOOP-12415:
Environment: Bigtop, plain Linux distro of any kind (was: Bigtop)
> hdfs and nfs builds broken on Bigtop -missing compile-time dependency on netty
> --
>
> Key: HADOOP-12415
> URL: https://issues.apache.org/jira/browse/HADOOP-12415
> Project: Hadoop Common
> Issue Type: Bug
> Components: nfs
>Affects Versions: 2.7.1
> Environment: Bigtop, plain Linux distro of any kind
>Reporter: Konstantin Boudnik
>Assignee: Tom Zeng
> Attachments: HADOOP-12415.patch
>
>
> As discovered in BIGTOP-2049 {{hadoop-nfs}} module compilation is broken.
> Looks like that HADOOP-11489 is the root-cause of it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12415) Hadoop build is broken because of missed compile-time dependency
[
https://issues.apache.org/jira/browse/HADOOP-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14803269#comment-14803269
]
Konstantin Boudnik commented on HADOOP-12415:
-
Might be a red-herring, because we surely didn't observe the problem in 2.6 and
this exclusion has been sitting in for 2+ years.
> Hadoop build is broken because of missed compile-time dependency
>
>
> Key: HADOOP-12415
> URL: https://issues.apache.org/jira/browse/HADOOP-12415
> Project: Hadoop Common
> Issue Type: Bug
> Components: nfs
>Affects Versions: 2.7.1
>Reporter: Konstantin Boudnik
>Assignee: Tom Zeng
> Attachments: HADOOP-12415.patch
>
>
> As discovered in BIGTOP-2049 {{hadoop-nfs}} module compilation is broken.
> Looks like that HADOOP-11489 is the root-cause of it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12415) Hadoop build is broken because of missed compile-time dependency
[
https://issues.apache.org/jira/browse/HADOOP-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14791175#comment-14791175
]
Konstantin Boudnik commented on HADOOP-12415:
-
Andrew, please follow the discussion over here BIGTOP-2049. test-patch isn't
really the golden standard when it comes to the testing of the
depedency-related changes, as it most likely has pre-populated maven cache.
> Hadoop build is broken because of missed compile-time dependency
>
>
> Key: HADOOP-12415
> URL: https://issues.apache.org/jira/browse/HADOOP-12415
> Project: Hadoop Common
> Issue Type: Bug
> Components: nfs
>Affects Versions: 2.7.1
>Reporter: Konstantin Boudnik
>Assignee: Tom Zeng
> Attachments: HADOOP-12415.patch
>
>
> As discovered in BIGTOP-2049 {{hadoop-nfs}} module compilation is broken.
> Looks like that HADOOP-11489 is the root-cause of it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12415) Hadoop build is broken because of missed compile-time dependency
[
https://issues.apache.org/jira/browse/HADOOP-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14791114#comment-14791114
]
Konstantin Boudnik commented on HADOOP-12415:
-
+1 the patch looks correct and the placement of the dependency is right. If
anything HADOOP-11489 has introduced the bug. I will commit this in a bit to
the trunk and branch-2. Thanks for the patch, [~tomzeng]!
> Hadoop build is broken because of missed compile-time dependency
>
>
> Key: HADOOP-12415
> URL: https://issues.apache.org/jira/browse/HADOOP-12415
> Project: Hadoop Common
> Issue Type: Bug
> Components: nfs
>Affects Versions: 2.7.1
>Reporter: Konstantin Boudnik
>Assignee: Tom Zeng
> Attachments: HADOOP-12415.patch
>
>
> As discovered in BIGTOP-2049 {{hadoop-nfs}} module compilation is broken.
> Looks like that HADOOP-11489 is the root-cause of it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-11489) Dropping dependency on io.netty from hadoop-nfs' pom.xml
[ https://issues.apache.org/jira/browse/HADOOP-11489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14745945#comment-14745945 ] Konstantin Boudnik commented on HADOOP-11489: - Indeed it should and this is why I opened HADOOP-12415 > Dropping dependency on io.netty from hadoop-nfs' pom.xml > > > Key: HADOOP-11489 > URL: https://issues.apache.org/jira/browse/HADOOP-11489 > Project: Hadoop Common > Issue Type: Task > Components: nfs >Affects Versions: 2.6.0 >Reporter: Ted Yu >Assignee: Ted Yu >Priority: Minor > Fix For: 2.7.0 > > Attachments: hadoop-11489-001.patch > > > hadoop-nfs pom.xml has compile time dependency on io.netty > This dependency can be dropped. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12415) Hadoop build is broken because of missed compile-time dependency
[
https://issues.apache.org/jira/browse/HADOOP-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14745828#comment-14745828
]
Konstantin Boudnik commented on HADOOP-12415:
-
A fix is proposed
[here|https://issues.apache.org/jira/browse/BIGTOP-2049?focusedCommentId=14745749=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14745749]
> Hadoop build is broken because of missed compile-time dependency
>
>
> Key: HADOOP-12415
> URL: https://issues.apache.org/jira/browse/HADOOP-12415
> Project: Hadoop Common
> Issue Type: Bug
> Components: nfs
>Affects Versions: 2.7.1
>Reporter: Konstantin Boudnik
>
> As discovered in BIGTOP-2049 {{hadoop-nfs}} module compilation is broken.
> Looks like that HADOOP-11489 is the root-cause of it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HADOOP-12415) Hadoop build is broken because of missed compile-time dependency
Konstantin Boudnik created HADOOP-12415:
---
Summary: Hadoop build is broken because of missed compile-time
dependency
Key: HADOOP-12415
URL: https://issues.apache.org/jira/browse/HADOOP-12415
Project: Hadoop Common
Issue Type: Bug
Components: nfs
Affects Versions: 2.7.1
Reporter: Konstantin Boudnik
As discovered in BIGTOP-2049 {{hadoop-nfs}} module compilation is broken. Looks
like that HADOOP-11489 is the root-cause of it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HADOOP-11945) Add Apache Ignite (incubating) to the Hadoop-related projects
Konstantin Boudnik created HADOOP-11945: --- Summary: Add Apache Ignite (incubating) to the Hadoop-related projects Key: HADOOP-11945 URL: https://issues.apache.org/jira/browse/HADOOP-11945 Project: Hadoop Common Issue Type: Improvement Components: site Affects Versions: 2.5.2 Reporter: Konstantin Boudnik Assignee: Konstantin Boudnik Fix For: site Apache Ignite (incubating) has the implementation of HDFS compatible in-memory file system (IGFS) and in-memory MapReduce accelerator. These two components allow Ignite users to run OLTP/SQL/computational workloads on top of HDFS storage. Let's add this project to the list of Hadoop related ones. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-11945) Add Apache Ignite (incubating) to the Hadoop-related projects
[ https://issues.apache.org/jira/browse/HADOOP-11945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HADOOP-11945: Priority: Minor (was: Major) Add Apache Ignite (incubating) to the Hadoop-related projects --- Key: HADOOP-11945 URL: https://issues.apache.org/jira/browse/HADOOP-11945 Project: Hadoop Common Issue Type: Improvement Components: site Affects Versions: 2.5.2 Reporter: Konstantin Boudnik Assignee: Konstantin Boudnik Priority: Minor Fix For: site Apache Ignite (incubating) has the implementation of HDFS compatible in-memory file system (IGFS) and in-memory MapReduce accelerator. These two components allow Ignite users to run OLTP/SQL/computational workloads on top of HDFS storage. Let's add this project to the list of Hadoop related ones. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-10641) Introduce Coordination Engine interface
[ https://issues.apache.org/jira/browse/HADOOP-10641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14085170#comment-14085170 ] Konstantin Boudnik commented on HADOOP-10641: - Looks like new pom.xml file is missing the ASL boiler-plate. Introduce Coordination Engine interface --- Key: HADOOP-10641 URL: https://issues.apache.org/jira/browse/HADOOP-10641 Project: Hadoop Common Issue Type: New Feature Affects Versions: 3.0.0 Reporter: Konstantin Shvachko Assignee: Plamen Jeliazkov Attachments: HADOOP-10641.patch, HADOOP-10641.patch, HADOOP-10641.patch, HADOOP-10641.patch, hadoop-coordination.patch Coordination Engine (CE) is a system, which allows to agree on a sequence of events in a distributed system. In order to be reliable CE should be distributed by itself. Coordination Engine can be based on different algorithms (paxos, raft, 2PC, zab) and have different implementations, depending on use cases, reliability, availability, and performance requirements. CE should have a common API, so that it could serve as a pluggable component in different projects. The immediate beneficiaries are HDFS (HDFS-6469) and HBase (HBASE-10909). First implementation is proposed to be based on ZooKeeper. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HADOOP-10641) Introduce Coordination Engine
[
https://issues.apache.org/jira/browse/HADOOP-10641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14064621#comment-14064621
]
Konstantin Boudnik commented on HADOOP-10641:
-
As has been proposed above and agreed during the meet-up yesterday, I will go
ahead and clear new branch {{ConsensusNode}} off the trunk, so we'll start
adding the implementation there.
Introduce Coordination Engine
-
Key: HADOOP-10641
URL: https://issues.apache.org/jira/browse/HADOOP-10641
Project: Hadoop Common
Issue Type: New Feature
Affects Versions: 3.0.0
Reporter: Konstantin Shvachko
Assignee: Plamen Jeliazkov
Attachments: HADOOP-10641.patch, HADOOP-10641.patch,
HADOOP-10641.patch, hadoop-coordination.patch
Coordination Engine (CE) is a system, which allows to agree on a sequence of
events in a distributed system. In order to be reliable CE should be
distributed by itself.
Coordination Engine can be based on different algorithms (paxos, raft, 2PC,
zab) and have different implementations, depending on use cases, reliability,
availability, and performance requirements.
CE should have a common API, so that it could serve as a pluggable component
in different projects. The immediate beneficiaries are HDFS (HDFS-6469) and
HBase (HBASE-10909).
First implementation is proposed to be based on ZooKeeper.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (HADOOP-10641) Introduce Coordination Engine
[ https://issues.apache.org/jira/browse/HADOOP-10641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065754#comment-14065754 ] Konstantin Boudnik commented on HADOOP-10641: - I think in the code we refer to it as CNode or ConsensusNode, hence the name for the branch. Introduce Coordination Engine - Key: HADOOP-10641 URL: https://issues.apache.org/jira/browse/HADOOP-10641 Project: Hadoop Common Issue Type: New Feature Affects Versions: 3.0.0 Reporter: Konstantin Shvachko Assignee: Plamen Jeliazkov Attachments: HADOOP-10641.patch, HADOOP-10641.patch, HADOOP-10641.patch, hadoop-coordination.patch Coordination Engine (CE) is a system, which allows to agree on a sequence of events in a distributed system. In order to be reliable CE should be distributed by itself. Coordination Engine can be based on different algorithms (paxos, raft, 2PC, zab) and have different implementations, depending on use cases, reliability, availability, and performance requirements. CE should have a common API, so that it could serve as a pluggable component in different projects. The immediate beneficiaries are HDFS (HDFS-6469) and HBase (HBASE-10909). First implementation is proposed to be based on ZooKeeper. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HADOOP-10641) Introduce Coordination Engine
[ https://issues.apache.org/jira/browse/HADOOP-10641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14061397#comment-14061397 ] Konstantin Boudnik commented on HADOOP-10641: - bq. I'm not comfortable with committing this to Hadoop trunk before it's actually something that Hadop trunk will use. This is a chicken-n-egg problem, don't you think? You don't want to get this piece into common before something in the trunk will use it. However, it isn't possible to have _anything_ in the trunk to use the APO until it is committed. Am I missing anything? Introduce Coordination Engine - Key: HADOOP-10641 URL: https://issues.apache.org/jira/browse/HADOOP-10641 Project: Hadoop Common Issue Type: New Feature Affects Versions: 3.0.0 Reporter: Konstantin Shvachko Assignee: Plamen Jeliazkov Attachments: HADOOP-10641.patch, HADOOP-10641.patch, HADOOP-10641.patch, hadoop-coordination.patch Coordination Engine (CE) is a system, which allows to agree on a sequence of events in a distributed system. In order to be reliable CE should be distributed by itself. Coordination Engine can be based on different algorithms (paxos, raft, 2PC, zab) and have different implementations, depending on use cases, reliability, availability, and performance requirements. CE should have a common API, so that it could serve as a pluggable component in different projects. The immediate beneficiaries are HDFS (HDFS-6469) and HBase (HBASE-10909). First implementation is proposed to be based on ZooKeeper. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HADOOP-10641) Introduce Coordination Engine
[ https://issues.apache.org/jira/browse/HADOOP-10641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14059098#comment-14059098 ] Konstantin Boudnik commented on HADOOP-10641: - bq. Please give me a little more credit than this. Even though it may not be mentioned in the design doc, it's fairly transparent that the primary goal of this work is to introduce a plugin point for WANdisco's coordination engine implementation into Hadoop. And as Konstantin said elsewhere: Hadoop has a number of features that are targeted to a proprietary technologies, which doesn't seem to be bothering anyone this far. So, I can't consider this as a real objection. Introduce Coordination Engine - Key: HADOOP-10641 URL: https://issues.apache.org/jira/browse/HADOOP-10641 Project: Hadoop Common Issue Type: New Feature Affects Versions: 3.0.0 Reporter: Konstantin Shvachko Assignee: Plamen Jeliazkov Attachments: HADOOP-10641.patch, HADOOP-10641.patch, HADOOP-10641.patch, hadoop-coordination.patch Coordination Engine (CE) is a system, which allows to agree on a sequence of events in a distributed system. In order to be reliable CE should be distributed by itself. Coordination Engine can be based on different algorithms (paxos, raft, 2PC, zab) and have different implementations, depending on use cases, reliability, availability, and performance requirements. CE should have a common API, so that it could serve as a pluggable component in different projects. The immediate beneficiaries are HDFS (HDFS-6469) and HBase (HBASE-10909). First implementation is proposed to be based on ZooKeeper. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HADOOP-10641) Introduce Coordination Engine
[ https://issues.apache.org/jira/browse/HADOOP-10641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14055383#comment-14055383 ] Konstantin Boudnik commented on HADOOP-10641: - [~atm] HDFS-6469 doesn't have _a lot of objections_ really. It has some questions, but they are already pretty much covered, IMO, by [~shv]. So it doesn't looks like HDFS ticket is blocking the passage of this one. Introduce Coordination Engine - Key: HADOOP-10641 URL: https://issues.apache.org/jira/browse/HADOOP-10641 Project: Hadoop Common Issue Type: New Feature Affects Versions: 3.0.0 Reporter: Konstantin Shvachko Assignee: Plamen Jeliazkov Attachments: HADOOP-10641.patch, HADOOP-10641.patch, HADOOP-10641.patch, hadoop-coordination.patch Coordination Engine (CE) is a system, which allows to agree on a sequence of events in a distributed system. In order to be reliable CE should be distributed by itself. Coordination Engine can be based on different algorithms (paxos, raft, 2PC, zab) and have different implementations, depending on use cases, reliability, availability, and performance requirements. CE should have a common API, so that it could serve as a pluggable component in different projects. The immediate beneficiaries are HDFS (HDFS-6469) and HBase (HBASE-10909). First implementation is proposed to be based on ZooKeeper. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HADOOP-10128) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/HADOOP-10128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039095#comment-14039095 ] Konstantin Boudnik commented on HADOOP-10128: - Will do, give me a few minutes. Please delete old releases from mirroring system Key: HADOOP-10128 URL: https://issues.apache.org/jira/browse/HADOOP-10128 Project: Hadoop Common Issue Type: Bug Environment: http://www.apache.org/dist/hadoop/common/ http://www.apache.org/dist/hadoop/core/ Reporter: Sebb To reduce the load on the ASF mirrors, projects are required to delete old releases. Please can you remove all non-current releases? i.e. anything except 0.23.9 1.2.1 2.2.0 Thanks. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HADOOP-10128) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/HADOOP-10128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039658#comment-14039658 ] Konstantin Boudnik commented on HADOOP-10128: - I have removed 2.0.6-alpha. It seems that 2.2.0 and 2.3.0 are still around although the current points to 2.4.0. Worth yanking these two out? Please delete old releases from mirroring system Key: HADOOP-10128 URL: https://issues.apache.org/jira/browse/HADOOP-10128 Project: Hadoop Common Issue Type: Bug Environment: http://www.apache.org/dist/hadoop/common/ http://www.apache.org/dist/hadoop/core/ Reporter: Sebb To reduce the load on the ASF mirrors, projects are required to delete old releases. Please can you remove all non-current releases? i.e. anything except 0.23.9 1.2.1 2.2.0 Thanks. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HADOOP-10641) Introduce Coordination Engine
[ https://issues.apache.org/jira/browse/HADOOP-10641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14020341#comment-14020341 ] Konstantin Boudnik commented on HADOOP-10641: - Good point [~atm]! While other projects might take an advantage of coordinated intent approach, the HDFS and HBase are the only two right now that are focusing on real HA with low MTTR. I am just a bit hesitant of over-generalizing things ;) Introduce Coordination Engine - Key: HADOOP-10641 URL: https://issues.apache.org/jira/browse/HADOOP-10641 Project: Hadoop Common Issue Type: New Feature Affects Versions: 3.0.0 Reporter: Konstantin Shvachko Assignee: Plamen Jeliazkov Attachments: HADOOP-10641.patch, HADOOP-10641.patch, HADOOP-10641.patch Coordination Engine (CE) is a system, which allows to agree on a sequence of events in a distributed system. In order to be reliable CE should be distributed by itself. Coordination Engine can be based on different algorithms (paxos, raft, 2PC, zab) and have different implementations, depending on use cases, reliability, availability, and performance requirements. CE should have a common API, so that it could serve as a pluggable component in different projects. The immediate beneficiaries are HDFS (HDFS-6469) and HBase (HBASE-10909). First implementation is proposed to be based on ZooKeeper. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HADOOP-10641) Introduce Coordination Engine
[ https://issues.apache.org/jira/browse/HADOOP-10641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HADOOP-10641: Attachment: (was: HADOOP-10641.patch) Introduce Coordination Engine - Key: HADOOP-10641 URL: https://issues.apache.org/jira/browse/HADOOP-10641 Project: Hadoop Common Issue Type: New Feature Affects Versions: 3.0.0 Reporter: Konstantin Shvachko Assignee: Plamen Jeliazkov Attachments: HADOOP-10641.patch Coordination Engine (CE) is a system, which allows to agree on a sequence of events in a distributed system. In order to be reliable CE should be distributed by itself. Coordination Engine can be based on different algorithms (paxos, raft, 2PC, zab) and have different implementations, depending on use cases, reliability, availability, and performance requirements. CE should have a common API, so that it could serve as a pluggable component in different projects. The immediate beneficiaries are HDFS (HDFS-6469) and HBase (HBASE-10909). First implementation is proposed to be based on ZooKeeper. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HADOOP-10641) Introduce Coordination Engine
[ https://issues.apache.org/jira/browse/HADOOP-10641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HADOOP-10641: Attachment: HADOOP-10641.patch Introduce Coordination Engine - Key: HADOOP-10641 URL: https://issues.apache.org/jira/browse/HADOOP-10641 Project: Hadoop Common Issue Type: New Feature Affects Versions: 3.0.0 Reporter: Konstantin Shvachko Assignee: Plamen Jeliazkov Attachments: HADOOP-10641.patch Coordination Engine (CE) is a system, which allows to agree on a sequence of events in a distributed system. In order to be reliable CE should be distributed by itself. Coordination Engine can be based on different algorithms (paxos, raft, 2PC, zab) and have different implementations, depending on use cases, reliability, availability, and performance requirements. CE should have a common API, so that it could serve as a pluggable component in different projects. The immediate beneficiaries are HDFS (HDFS-6469) and HBase (HBASE-10909). First implementation is proposed to be based on ZooKeeper. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HADOOP-10637) Add snapshot and several dfsadmin tests into TestCLI
[ https://issues.apache.org/jira/browse/HADOOP-10637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HADOOP-10637: Issue Type: Test (was: Improvement) Add snapshot and several dfsadmin tests into TestCLI Key: HADOOP-10637 URL: https://issues.apache.org/jira/browse/HADOOP-10637 Project: Hadoop Common Issue Type: Test Components: test Affects Versions: 3.0.0 Reporter: Dasha Boudnik Attachments: HADOOP-10637.patch, HADOOP-10637.patch Add the following commands to TestCLI: appendToFile text rmdir rmdir with ignore-fail-on-non-empty df expunge getmerge allowSnapshot disallowSnapshot createSnapshot renameSnapshot deleteSnapshot refreshUserToGroupsMappings refreshSuperUserGroupsConfiguration setQuota clrQuota setSpaceQuota setBalancerBandwidth finalizeUpgrade -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HADOOP-10637) Add snapshot and several dfsadmin tests into TestCLI
[ https://issues.apache.org/jira/browse/HADOOP-10637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HADOOP-10637: Issue Type: Improvement (was: Test) Add snapshot and several dfsadmin tests into TestCLI Key: HADOOP-10637 URL: https://issues.apache.org/jira/browse/HADOOP-10637 Project: Hadoop Common Issue Type: Improvement Components: test Affects Versions: 3.0.0 Reporter: Dasha Boudnik Attachments: HADOOP-10637.patch, HADOOP-10637.patch Add the following commands to TestCLI: appendToFile text rmdir rmdir with ignore-fail-on-non-empty df expunge getmerge allowSnapshot disallowSnapshot createSnapshot renameSnapshot deleteSnapshot refreshUserToGroupsMappings refreshSuperUserGroupsConfiguration setQuota clrQuota setSpaceQuota setBalancerBandwidth finalizeUpgrade -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HADOOP-10637) Add snapshot and several dfsadmin tests into TestCLI
[ https://issues.apache.org/jira/browse/HADOOP-10637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HADOOP-10637: Affects Version/s: 3.0.0 Add snapshot and several dfsadmin tests into TestCLI Key: HADOOP-10637 URL: https://issues.apache.org/jira/browse/HADOOP-10637 Project: Hadoop Common Issue Type: Improvement Components: test Affects Versions: 3.0.0 Reporter: Dasha Boudnik Attachments: HADOOP-10637.patch, HADOOP-10637.patch Add the following commands to TestCLI: appendToFile text rmdir rmdir with ignore-fail-on-non-empty df expunge getmerge allowSnapshot disallowSnapshot createSnapshot renameSnapshot deleteSnapshot refreshUserToGroupsMappings refreshSuperUserGroupsConfiguration setQuota clrQuota setSpaceQuota setBalancerBandwidth finalizeUpgrade -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HADOOP-10637) Add snapshot and several dfsadmin tests into TestCLI
[ https://issues.apache.org/jira/browse/HADOOP-10637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14013123#comment-14013123 ] Konstantin Boudnik commented on HADOOP-10637: - Looks like this should go to HDFS-6297 as these should belong to hdfs specific CLI tests. Add snapshot and several dfsadmin tests into TestCLI Key: HADOOP-10637 URL: https://issues.apache.org/jira/browse/HADOOP-10637 Project: Hadoop Common Issue Type: Improvement Components: test Affects Versions: 3.0.0 Reporter: Dasha Boudnik Attachments: HADOOP-10637.patch, HADOOP-10637.patch Add the following commands to TestCLI: appendToFile text rmdir rmdir with ignore-fail-on-non-empty df expunge getmerge allowSnapshot disallowSnapshot createSnapshot renameSnapshot deleteSnapshot refreshUserToGroupsMappings refreshSuperUserGroupsConfiguration setQuota clrQuota setSpaceQuota setBalancerBandwidth finalizeUpgrade -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HADOOP-10390) DFSCIOTest looks for the wrong version of libhdfs
[
https://issues.apache.org/jira/browse/HADOOP-10390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13932068#comment-13932068
]
Konstantin Boudnik commented on HADOOP-10390:
-
[~decster]], {{HADOOP_HOME/lib/native}} is root owned in an deployed cluster.
However, running tests as root is a big no-no, normally (as I commented above).
Also, this location is managed by a package when the cluster is installed.
Adding/removing stuff into a package realm is - again - is a bad idea. Is it
possible to keep these elsewhere?
DFSCIOTest looks for the wrong version of libhdfs
-
Key: HADOOP-10390
URL: https://issues.apache.org/jira/browse/HADOOP-10390
Project: Hadoop Common
Issue Type: Bug
Components: test
Affects Versions: 2.0.0-alpha
Reporter: wenwupeng
Assignee: Binglin Chang
Attachments: HADOOP-10390.v1.patch, HADOOP-10390.v2.patch
Run benckmark DFSCIOTest failed at libhdfs.so.1
hadoop jar
./share/hadoop/mapreduce/hadoop-mapreduce-client-jobclient-2.3.0-tests.jar
DFSCIOTest -write -nrFiles 1 -fileSize 100
DFSCIOTest.0.0.1
14/03/06 02:52:55 INFO fs.DFSCIOTest: nrFiles = 1
14/03/06 02:52:55 INFO fs.DFSCIOTest: fileSize (MB) = 100
14/03/06 02:52:55 INFO fs.DFSCIOTest: bufferSize = 100
14/03/06 02:52:55 WARN util.NativeCodeLoader: Unable to load native-hadoop
library for your platform... using builtin-java classes where applicable
File /hadoop/hadoop-smoke/libhdfs/libhdfs.so.1 does not exist
can get libhdfs.so.0.0.0 under ./lib/native
[root@namenode hadoop-smoke]# find ./ -name libhdfs*
./lib/native/libhdfs.so
./lib/native/libhdfs.so.0.0.0
./lib/native/libhdfs.a
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (HADOOP-10390) DFSCIOTest looks for the wrong version of libhdfs
[
https://issues.apache.org/jira/browse/HADOOP-10390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13932109#comment-13932109
]
Konstantin Boudnik commented on HADOOP-10390:
-
I am sorry - I misread the change, I think. Please disregard my comment about
the permissions. However, the binary executables should belong to {{bin/}}
rather than {{lib/}} directory. Any particular reasons to expect them to be
under {{lib/native}} ?
DFSCIOTest looks for the wrong version of libhdfs
-
Key: HADOOP-10390
URL: https://issues.apache.org/jira/browse/HADOOP-10390
Project: Hadoop Common
Issue Type: Bug
Components: test
Affects Versions: 2.0.0-alpha
Reporter: wenwupeng
Assignee: Binglin Chang
Attachments: HADOOP-10390.v1.patch, HADOOP-10390.v2.patch
Run benckmark DFSCIOTest failed at libhdfs.so.1
hadoop jar
./share/hadoop/mapreduce/hadoop-mapreduce-client-jobclient-2.3.0-tests.jar
DFSCIOTest -write -nrFiles 1 -fileSize 100
DFSCIOTest.0.0.1
14/03/06 02:52:55 INFO fs.DFSCIOTest: nrFiles = 1
14/03/06 02:52:55 INFO fs.DFSCIOTest: fileSize (MB) = 100
14/03/06 02:52:55 INFO fs.DFSCIOTest: bufferSize = 100
14/03/06 02:52:55 WARN util.NativeCodeLoader: Unable to load native-hadoop
library for your platform... using builtin-java classes where applicable
File /hadoop/hadoop-smoke/libhdfs/libhdfs.so.1 does not exist
can get libhdfs.so.0.0.0 under ./lib/native
[root@namenode hadoop-smoke]# find ./ -name libhdfs*
./lib/native/libhdfs.so
./lib/native/libhdfs.so.0.0.0
./lib/native/libhdfs.a
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (HADOOP-10390) DFSCIOTest looks for the wrong version of libhdfs
[ https://issues.apache.org/jira/browse/HADOOP-10390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13932226#comment-13932226 ] Konstantin Boudnik commented on HADOOP-10390: - bq. The reason why I suggested the lib/native is because previously hdfs_read and hdfs_write were under the same directory as libhdfs.so* Sorry, I am confused - were where? in the tarball or the packaged versions of Hadoop? DFSCIOTest looks for the wrong version of libhdfs - Key: HADOOP-10390 URL: https://issues.apache.org/jira/browse/HADOOP-10390 Project: Hadoop Common Issue Type: Bug Components: test Affects Versions: 2.0.0-alpha Reporter: wenwupeng Assignee: Binglin Chang Attachments: HADOOP-10390.v1.patch, HADOOP-10390.v2.patch Run benckmark DFSCIOTest failed at libhdfs.so.1 hadoop jar ./share/hadoop/mapreduce/hadoop-mapreduce-client-jobclient-2.3.0-tests.jar DFSCIOTest -write -nrFiles 1 -fileSize 100 DFSCIOTest.0.0.1 14/03/06 02:52:55 INFO fs.DFSCIOTest: nrFiles = 1 14/03/06 02:52:55 INFO fs.DFSCIOTest: fileSize (MB) = 100 14/03/06 02:52:55 INFO fs.DFSCIOTest: bufferSize = 100 14/03/06 02:52:55 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable File /hadoop/hadoop-smoke/libhdfs/libhdfs.so.1 does not exist can get libhdfs.so.0.0.0 under ./lib/native [root@namenode hadoop-smoke]# find ./ -name libhdfs* ./lib/native/libhdfs.so ./lib/native/libhdfs.so.0.0.0 ./lib/native/libhdfs.a -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HADOOP-10390) DFSCIOTest looks for the wrong version of libhdfs
[ https://issues.apache.org/jira/browse/HADOOP-10390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13931001#comment-13931001 ] Konstantin Boudnik commented on HADOOP-10390: - Actually, keep in mind that in a normal deployment all these directories are owned by root, hence test would be have some impossible requirements. I'd pick a neutral location for these binaries. DFSCIOTest looks for the wrong version of libhdfs - Key: HADOOP-10390 URL: https://issues.apache.org/jira/browse/HADOOP-10390 Project: Hadoop Common Issue Type: Bug Components: test Affects Versions: 2.0.0-alpha Reporter: wenwupeng Assignee: Binglin Chang Attachments: HADOOP-10390.v1.patch Run benckmark DFSCIOTest failed at libhdfs.so.1 hadoop jar ./share/hadoop/mapreduce/hadoop-mapreduce-client-jobclient-2.3.0-tests.jar DFSCIOTest -write -nrFiles 1 -fileSize 100 DFSCIOTest.0.0.1 14/03/06 02:52:55 INFO fs.DFSCIOTest: nrFiles = 1 14/03/06 02:52:55 INFO fs.DFSCIOTest: fileSize (MB) = 100 14/03/06 02:52:55 INFO fs.DFSCIOTest: bufferSize = 100 14/03/06 02:52:55 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable File /hadoop/hadoop-smoke/libhdfs/libhdfs.so.1 does not exist can get libhdfs.so.0.0.0 under ./lib/native [root@namenode hadoop-smoke]# find ./ -name libhdfs* ./lib/native/libhdfs.so ./lib/native/libhdfs.so.0.0.0 ./lib/native/libhdfs.a -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HADOOP-10390) DFSCIOTest looks for the wrong version of libhdfs
[ https://issues.apache.org/jira/browse/HADOOP-10390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13926032#comment-13926032 ] Konstantin Boudnik commented on HADOOP-10390: - I think it makes sense to re-purpose this ticket and fix all the test issues at once instead of stretching the process into a few different issues. DFSCIOTest looks for the wrong version of libhdfs - Key: HADOOP-10390 URL: https://issues.apache.org/jira/browse/HADOOP-10390 Project: Hadoop Common Issue Type: Bug Components: test Affects Versions: 2.0.0-alpha Reporter: wenwupeng Assignee: Binglin Chang Attachments: HADOOP-10390.v1.patch Run benckmark DFSCIOTest failed at libhdfs.so.1 hadoop jar ./share/hadoop/mapreduce/hadoop-mapreduce-client-jobclient-2.3.0-tests.jar DFSCIOTest -write -nrFiles 1 -fileSize 100 DFSCIOTest.0.0.1 14/03/06 02:52:55 INFO fs.DFSCIOTest: nrFiles = 1 14/03/06 02:52:55 INFO fs.DFSCIOTest: fileSize (MB) = 100 14/03/06 02:52:55 INFO fs.DFSCIOTest: bufferSize = 100 14/03/06 02:52:55 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable File /hadoop/hadoop-smoke/libhdfs/libhdfs.so.1 does not exist can get libhdfs.so.0.0.0 under ./lib/native [root@namenode hadoop-smoke]# find ./ -name libhdfs* ./lib/native/libhdfs.so ./lib/native/libhdfs.so.0.0.0 ./lib/native/libhdfs.a -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HADOOP-10390) DFSCIOTest looks for the wrong version of libhdfs
[ https://issues.apache.org/jira/browse/HADOOP-10390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13926042#comment-13926042 ] Konstantin Boudnik commented on HADOOP-10390: - In the interest of full disclosure: the same fix (as in the patch) exists in Cloudera's source tarball since 5/9/2012. Things that make you go 'hmmm' DFSCIOTest looks for the wrong version of libhdfs - Key: HADOOP-10390 URL: https://issues.apache.org/jira/browse/HADOOP-10390 Project: Hadoop Common Issue Type: Bug Components: test Affects Versions: 2.0.0-alpha Reporter: wenwupeng Assignee: Binglin Chang Attachments: HADOOP-10390.v1.patch Run benckmark DFSCIOTest failed at libhdfs.so.1 hadoop jar ./share/hadoop/mapreduce/hadoop-mapreduce-client-jobclient-2.3.0-tests.jar DFSCIOTest -write -nrFiles 1 -fileSize 100 DFSCIOTest.0.0.1 14/03/06 02:52:55 INFO fs.DFSCIOTest: nrFiles = 1 14/03/06 02:52:55 INFO fs.DFSCIOTest: fileSize (MB) = 100 14/03/06 02:52:55 INFO fs.DFSCIOTest: bufferSize = 100 14/03/06 02:52:55 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable File /hadoop/hadoop-smoke/libhdfs/libhdfs.so.1 does not exist can get libhdfs.so.0.0.0 under ./lib/native [root@namenode hadoop-smoke]# find ./ -name libhdfs* ./lib/native/libhdfs.so ./lib/native/libhdfs.so.0.0.0 ./lib/native/libhdfs.a -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HADOOP-10390) DFSCIOTest looks for the wrong version of libhdfs
[ https://issues.apache.org/jira/browse/HADOOP-10390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13926073#comment-13926073 ] Konstantin Boudnik commented on HADOOP-10390: - sorry, I had the patch applied in my workspace. Yet, on CDH4 DFSCIO is working while it doesn't on open source installation starting back from 2.0.6-alpha DFSCIOTest looks for the wrong version of libhdfs - Key: HADOOP-10390 URL: https://issues.apache.org/jira/browse/HADOOP-10390 Project: Hadoop Common Issue Type: Bug Components: test Affects Versions: 2.0.0-alpha Reporter: wenwupeng Assignee: Binglin Chang Attachments: HADOOP-10390.v1.patch Run benckmark DFSCIOTest failed at libhdfs.so.1 hadoop jar ./share/hadoop/mapreduce/hadoop-mapreduce-client-jobclient-2.3.0-tests.jar DFSCIOTest -write -nrFiles 1 -fileSize 100 DFSCIOTest.0.0.1 14/03/06 02:52:55 INFO fs.DFSCIOTest: nrFiles = 1 14/03/06 02:52:55 INFO fs.DFSCIOTest: fileSize (MB) = 100 14/03/06 02:52:55 INFO fs.DFSCIOTest: bufferSize = 100 14/03/06 02:52:55 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable File /hadoop/hadoop-smoke/libhdfs/libhdfs.so.1 does not exist can get libhdfs.so.0.0.0 under ./lib/native [root@namenode hadoop-smoke]# find ./ -name libhdfs* ./lib/native/libhdfs.so ./lib/native/libhdfs.so.0.0.0 ./lib/native/libhdfs.a -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HADOOP-10390) DFSCIOTest looks for the wrong version of libhdfs
[
https://issues.apache.org/jira/browse/HADOOP-10390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13925434#comment-13925434
]
Konstantin Boudnik commented on HADOOP-10390:
-
Bigtop's hadoop-config.sh - in fact the very same script that is used by _any_
commercial Hadoop distro - are setting {{java.library.path}} correctly. I have
validated it.
Yet, the test is failing.
DFSCIOTest looks for the wrong version of libhdfs
-
Key: HADOOP-10390
URL: https://issues.apache.org/jira/browse/HADOOP-10390
Project: Hadoop Common
Issue Type: Bug
Components: test
Affects Versions: 2.0.0-alpha
Reporter: wenwupeng
Assignee: Binglin Chang
Attachments: HADOOP-10390.v1.patch
Run benckmark DFSCIOTest failed at libhdfs.so.1
hadoop jar
./share/hadoop/mapreduce/hadoop-mapreduce-client-jobclient-2.3.0-tests.jar
DFSCIOTest -write -nrFiles 1 -fileSize 100
DFSCIOTest.0.0.1
14/03/06 02:52:55 INFO fs.DFSCIOTest: nrFiles = 1
14/03/06 02:52:55 INFO fs.DFSCIOTest: fileSize (MB) = 100
14/03/06 02:52:55 INFO fs.DFSCIOTest: bufferSize = 100
14/03/06 02:52:55 WARN util.NativeCodeLoader: Unable to load native-hadoop
library for your platform... using builtin-java classes where applicable
File /hadoop/hadoop-smoke/libhdfs/libhdfs.so.1 does not exist
can get libhdfs.so.0.0.0 under ./lib/native
[root@namenode hadoop-smoke]# find ./ -name libhdfs*
./lib/native/libhdfs.so
./lib/native/libhdfs.so.0.0.0
./lib/native/libhdfs.a
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (HADOOP-10390) DFSCIOTest looks for the wrong version of libhdfs
[ https://issues.apache.org/jira/browse/HADOOP-10390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924437#comment-13924437 ] Konstantin Boudnik commented on HADOOP-10390: - s/words/works/ DFSCIOTest looks for the wrong version of libhdfs - Key: HADOOP-10390 URL: https://issues.apache.org/jira/browse/HADOOP-10390 Project: Hadoop Common Issue Type: Bug Components: test Affects Versions: 2.0.0-alpha Reporter: wenwupeng Assignee: Binglin Chang Attachments: HADOOP-10390.v1.patch Run benckmark DFSCIOTest failed at libhdfs.so.1 hadoop jar ./share/hadoop/mapreduce/hadoop-mapreduce-client-jobclient-2.3.0-tests.jar DFSCIOTest -write -nrFiles 1 -fileSize 100 DFSCIOTest.0.0.1 14/03/06 02:52:55 INFO fs.DFSCIOTest: nrFiles = 1 14/03/06 02:52:55 INFO fs.DFSCIOTest: fileSize (MB) = 100 14/03/06 02:52:55 INFO fs.DFSCIOTest: bufferSize = 100 14/03/06 02:52:55 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable File /hadoop/hadoop-smoke/libhdfs/libhdfs.so.1 does not exist can get libhdfs.so.0.0.0 under ./lib/native [root@namenode hadoop-smoke]# find ./ -name libhdfs* ./lib/native/libhdfs.so ./lib/native/libhdfs.so.0.0.0 ./lib/native/libhdfs.a -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HADOOP-10167) Mark hadoop-common source as UTF-8 in Maven pom files / refactoring
[ https://issues.apache.org/jira/browse/HADOOP-10167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HADOOP-10167: Fix Version/s: 2.3.0 3.0.0 Mark hadoop-common source as UTF-8 in Maven pom files / refactoring --- Key: HADOOP-10167 URL: https://issues.apache.org/jira/browse/HADOOP-10167 Project: Hadoop Common Issue Type: Improvement Components: build Affects Versions: 2.0.6-alpha Environment: Fedora 19 x86-64 Reporter: Mikhail Antonov Labels: build Fix For: 3.0.0, 2.3.0 Attachments: HADOOP-10167-1.patch While looking at BIGTOP-831, turned out that the way Bigtop calls maven build / site:site generation causes the errors like this: [ERROR] Exit code: 1 - /home/user/jenkins/workspace/BigTop-RPM/label/centos-6-x86_64-HAD-1-buildbot/bigtop-repo/build/hadoop/rpm/BUILD/hadoop-2.0.2-alpha-src/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/metrics2/source/JvmMetricsInfo.java:31: error: unmappable character for encoding ANSI_X3.4-1968 [ERROR] JvmMetrics(JVM related metrics etc.), // record info?? Making the whole hadoop-common to use UTF-8 fixes that and seems in general good thing to me. Attaching first version of patch for review. Original issue was observed on openjdk 7 (x86-64). -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (HADOOP-10167) Mark hadoop-common source as UTF-8 in Maven pom files / refactoring
[ https://issues.apache.org/jira/browse/HADOOP-10167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13880445#comment-13880445 ] Konstantin Boudnik commented on HADOOP-10167: - Patch looks good - there was a line with trailing whitespaces that I've fixed for the same of time. Committing now. Mark hadoop-common source as UTF-8 in Maven pom files / refactoring --- Key: HADOOP-10167 URL: https://issues.apache.org/jira/browse/HADOOP-10167 Project: Hadoop Common Issue Type: Improvement Components: build Affects Versions: 2.0.6-alpha Environment: Fedora 19 x86-64 Reporter: Mikhail Antonov Labels: build Fix For: 3.0.0, 2.3.0 Attachments: HADOOP-10167-1.patch While looking at BIGTOP-831, turned out that the way Bigtop calls maven build / site:site generation causes the errors like this: [ERROR] Exit code: 1 - /home/user/jenkins/workspace/BigTop-RPM/label/centos-6-x86_64-HAD-1-buildbot/bigtop-repo/build/hadoop/rpm/BUILD/hadoop-2.0.2-alpha-src/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/metrics2/source/JvmMetricsInfo.java:31: error: unmappable character for encoding ANSI_X3.4-1968 [ERROR] JvmMetrics(JVM related metrics etc.), // record info?? Making the whole hadoop-common to use UTF-8 fixes that and seems in general good thing to me. Attaching first version of patch for review. Original issue was observed on openjdk 7 (x86-64). -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (HADOOP-10167) Mark hadoop-common source as UTF-8 in Maven pom files / refactoring
[ https://issues.apache.org/jira/browse/HADOOP-10167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HADOOP-10167: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk, branch-2, branch-2.3 Thank you Mikhail Mark hadoop-common source as UTF-8 in Maven pom files / refactoring --- Key: HADOOP-10167 URL: https://issues.apache.org/jira/browse/HADOOP-10167 Project: Hadoop Common Issue Type: Improvement Components: build Affects Versions: 2.0.6-alpha Environment: Fedora 19 x86-64 Reporter: Mikhail Antonov Labels: build Fix For: 3.0.0, 2.3.0 Attachments: HADOOP-10167-1.patch While looking at BIGTOP-831, turned out that the way Bigtop calls maven build / site:site generation causes the errors like this: [ERROR] Exit code: 1 - /home/user/jenkins/workspace/BigTop-RPM/label/centos-6-x86_64-HAD-1-buildbot/bigtop-repo/build/hadoop/rpm/BUILD/hadoop-2.0.2-alpha-src/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/metrics2/source/JvmMetricsInfo.java:31: error: unmappable character for encoding ANSI_X3.4-1968 [ERROR] JvmMetrics(JVM related metrics etc.), // record info?? Making the whole hadoop-common to use UTF-8 fixes that and seems in general good thing to me. Attaching first version of patch for review. Original issue was observed on openjdk 7 (x86-64). -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (HADOOP-10110) hadoop-auth has a build break due to missing dependency
[
https://issues.apache.org/jira/browse/HADOOP-10110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13877211#comment-13877211
]
Konstantin Boudnik commented on HADOOP-10110:
-
I will commit this as soon as my SVN password issue is resolved (hopefully by
tomorrow). If someone want to commit it before - please do!
hadoop-auth has a build break due to missing dependency
---
Key: HADOOP-10110
URL: https://issues.apache.org/jira/browse/HADOOP-10110
Project: Hadoop Common
Issue Type: Bug
Components: build
Affects Versions: 2.0.6-alpha, 2.2.0
Reporter: Chuan Liu
Assignee: Chuan Liu
Priority: Blocker
Fix For: 3.0.0, 2.3.0
Attachments: HADOOP-10110.patch
We have a build break in hadoop-auth if build with maven cache cleaned. The
error looks like the follows. The problem exists on both Windows and Linux.
If you have old jetty jars in your maven cache, you won't see the error.
{noformat}
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1:29.469s
[INFO] Finished at: Mon Nov 18 12:30:36 PST 2013
[INFO] Final Memory: 37M/120M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:testCompile
(default-testCompile) on project hadoop-auth: Compilation failure:
Compilation failure:
[ERROR]
/home/chuan/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/client/AuthenticatorTestCase.java:[84,13]
cannot access org.mortbay.component.AbstractLifeCycle
[ERROR] class file for org.mortbay.component.AbstractLifeCycle not found
[ERROR] server = new Server(0);
[ERROR]
/home/chuan/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/client/AuthenticatorTestCase.java:[94,29]
cannot access org.mortbay.component.LifeCycle
[ERROR] class file for org.mortbay.component.LifeCycle not found
[ERROR] server.getConnectors()[0].setHost(host);
[ERROR]
/home/chuan/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/client/AuthenticatorTestCase.java:[96,10]
cannot find symbol
[ERROR] symbol : method start()
[ERROR] location: class org.mortbay.jetty.Server
[ERROR]
/home/chuan/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/client/AuthenticatorTestCase.java:[102,12]
cannot find symbol
[ERROR] symbol : method stop()
[ERROR] location: class org.mortbay.jetty.Server
[ERROR] - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR] mvn goals -rf :hadoop-auth
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (HADOOP-10110) hadoop-auth has a build break due to missing dependency
[
https://issues.apache.org/jira/browse/HADOOP-10110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik updated HADOOP-10110:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk, branch-2, and branch-2.3. Thank you, Chuan!
hadoop-auth has a build break due to missing dependency
---
Key: HADOOP-10110
URL: https://issues.apache.org/jira/browse/HADOOP-10110
Project: Hadoop Common
Issue Type: Bug
Components: build
Affects Versions: 2.0.6-alpha, 2.2.0
Reporter: Chuan Liu
Assignee: Chuan Liu
Priority: Blocker
Fix For: 3.0.0, 2.3.0
Attachments: HADOOP-10110.patch
We have a build break in hadoop-auth if build with maven cache cleaned. The
error looks like the follows. The problem exists on both Windows and Linux.
If you have old jetty jars in your maven cache, you won't see the error.
{noformat}
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1:29.469s
[INFO] Finished at: Mon Nov 18 12:30:36 PST 2013
[INFO] Final Memory: 37M/120M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:testCompile
(default-testCompile) on project hadoop-auth: Compilation failure:
Compilation failure:
[ERROR]
/home/chuan/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/client/AuthenticatorTestCase.java:[84,13]
cannot access org.mortbay.component.AbstractLifeCycle
[ERROR] class file for org.mortbay.component.AbstractLifeCycle not found
[ERROR] server = new Server(0);
[ERROR]
/home/chuan/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/client/AuthenticatorTestCase.java:[94,29]
cannot access org.mortbay.component.LifeCycle
[ERROR] class file for org.mortbay.component.LifeCycle not found
[ERROR] server.getConnectors()[0].setHost(host);
[ERROR]
/home/chuan/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/client/AuthenticatorTestCase.java:[96,10]
cannot find symbol
[ERROR] symbol : method start()
[ERROR] location: class org.mortbay.jetty.Server
[ERROR]
/home/chuan/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/client/AuthenticatorTestCase.java:[102,12]
cannot find symbol
[ERROR] symbol : method stop()
[ERROR] location: class org.mortbay.jetty.Server
[ERROR] - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR] mvn goals -rf :hadoop-auth
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (HADOOP-10110) hadoop-auth has a build break due to missing dependency
[
https://issues.apache.org/jira/browse/HADOOP-10110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13872335#comment-13872335
]
Konstantin Boudnik commented on HADOOP-10110:
-
+1 on the patch.
hadoop-auth has a build break due to missing dependency
---
Key: HADOOP-10110
URL: https://issues.apache.org/jira/browse/HADOOP-10110
Project: Hadoop Common
Issue Type: Bug
Components: build
Affects Versions: 2.0.6-alpha, 2.2.0
Reporter: Chuan Liu
Assignee: Chuan Liu
Priority: Blocker
Fix For: 3.0.0, 2.3.0
Attachments: HADOOP-10110.patch
We have a build break in hadoop-auth if build with maven cache cleaned. The
error looks like the follows. The problem exists on both Windows and Linux.
If you have old jetty jars in your maven cache, you won't see the error.
{noformat}
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1:29.469s
[INFO] Finished at: Mon Nov 18 12:30:36 PST 2013
[INFO] Final Memory: 37M/120M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:testCompile
(default-testCompile) on project hadoop-auth: Compilation failure:
Compilation failure:
[ERROR]
/home/chuan/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/client/AuthenticatorTestCase.java:[84,13]
cannot access org.mortbay.component.AbstractLifeCycle
[ERROR] class file for org.mortbay.component.AbstractLifeCycle not found
[ERROR] server = new Server(0);
[ERROR]
/home/chuan/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/client/AuthenticatorTestCase.java:[94,29]
cannot access org.mortbay.component.LifeCycle
[ERROR] class file for org.mortbay.component.LifeCycle not found
[ERROR] server.getConnectors()[0].setHost(host);
[ERROR]
/home/chuan/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/client/AuthenticatorTestCase.java:[96,10]
cannot find symbol
[ERROR] symbol : method start()
[ERROR] location: class org.mortbay.jetty.Server
[ERROR]
/home/chuan/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/client/AuthenticatorTestCase.java:[102,12]
cannot find symbol
[ERROR] symbol : method stop()
[ERROR] location: class org.mortbay.jetty.Server
[ERROR] - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR] mvn goals -rf :hadoop-auth
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (HADOOP-10110) hadoop-auth has a build break due to missing dependency
[
https://issues.apache.org/jira/browse/HADOOP-10110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik updated HADOOP-10110:
Affects Version/s: 2.0.6-alpha
hadoop-auth has a build break due to missing dependency
---
Key: HADOOP-10110
URL: https://issues.apache.org/jira/browse/HADOOP-10110
Project: Hadoop Common
Issue Type: Bug
Affects Versions: 3.0.0, 2.0.6-alpha
Reporter: Chuan Liu
Assignee: Chuan Liu
Priority: Blocker
Fix For: 3.0.0, 2.3.0
Attachments: HADOOP-10110.patch
We have a build break in hadoop-auth if build with maven cache cleaned. The
error looks like the follows. The problem exists on both Windows and Linux.
If you have old jetty jars in your maven cache, you won't see the error.
{noformat}
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1:29.469s
[INFO] Finished at: Mon Nov 18 12:30:36 PST 2013
[INFO] Final Memory: 37M/120M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:testCompile
(default-testCompile) on project hadoop-auth: Compilation failure:
Compilation failure:
[ERROR]
/home/chuan/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/client/AuthenticatorTestCase.java:[84,13]
cannot access org.mortbay.component.AbstractLifeCycle
[ERROR] class file for org.mortbay.component.AbstractLifeCycle not found
[ERROR] server = new Server(0);
[ERROR]
/home/chuan/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/client/AuthenticatorTestCase.java:[94,29]
cannot access org.mortbay.component.LifeCycle
[ERROR] class file for org.mortbay.component.LifeCycle not found
[ERROR] server.getConnectors()[0].setHost(host);
[ERROR]
/home/chuan/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/client/AuthenticatorTestCase.java:[96,10]
cannot find symbol
[ERROR] symbol : method start()
[ERROR] location: class org.mortbay.jetty.Server
[ERROR]
/home/chuan/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/client/AuthenticatorTestCase.java:[102,12]
cannot find symbol
[ERROR] symbol : method stop()
[ERROR] location: class org.mortbay.jetty.Server
[ERROR] - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR] mvn goals -rf :hadoop-auth
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (HADOOP-10110) hadoop-auth has a build break due to missing dependency
[
https://issues.apache.org/jira/browse/HADOOP-10110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik updated HADOOP-10110:
Component/s: build
hadoop-auth has a build break due to missing dependency
---
Key: HADOOP-10110
URL: https://issues.apache.org/jira/browse/HADOOP-10110
Project: Hadoop Common
Issue Type: Bug
Components: build
Affects Versions: 3.0.0, 2.0.6-alpha
Reporter: Chuan Liu
Assignee: Chuan Liu
Priority: Blocker
Fix For: 3.0.0, 2.3.0
Attachments: HADOOP-10110.patch
We have a build break in hadoop-auth if build with maven cache cleaned. The
error looks like the follows. The problem exists on both Windows and Linux.
If you have old jetty jars in your maven cache, you won't see the error.
{noformat}
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1:29.469s
[INFO] Finished at: Mon Nov 18 12:30:36 PST 2013
[INFO] Final Memory: 37M/120M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:testCompile
(default-testCompile) on project hadoop-auth: Compilation failure:
Compilation failure:
[ERROR]
/home/chuan/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/client/AuthenticatorTestCase.java:[84,13]
cannot access org.mortbay.component.AbstractLifeCycle
[ERROR] class file for org.mortbay.component.AbstractLifeCycle not found
[ERROR] server = new Server(0);
[ERROR]
/home/chuan/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/client/AuthenticatorTestCase.java:[94,29]
cannot access org.mortbay.component.LifeCycle
[ERROR] class file for org.mortbay.component.LifeCycle not found
[ERROR] server.getConnectors()[0].setHost(host);
[ERROR]
/home/chuan/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/client/AuthenticatorTestCase.java:[96,10]
cannot find symbol
[ERROR] symbol : method start()
[ERROR] location: class org.mortbay.jetty.Server
[ERROR]
/home/chuan/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/client/AuthenticatorTestCase.java:[102,12]
cannot find symbol
[ERROR] symbol : method stop()
[ERROR] location: class org.mortbay.jetty.Server
[ERROR] - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR] mvn goals -rf :hadoop-auth
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Reopened] (HADOOP-10110) hadoop-auth has a build break due to missing dependency
[
https://issues.apache.org/jira/browse/HADOOP-10110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik reopened HADOOP-10110:
-
Needed to be ported back into 2.0.x line as it's breaking the build there as
well
hadoop-auth has a build break due to missing dependency
---
Key: HADOOP-10110
URL: https://issues.apache.org/jira/browse/HADOOP-10110
Project: Hadoop Common
Issue Type: Bug
Components: build
Affects Versions: 3.0.0, 2.0.6-alpha
Reporter: Chuan Liu
Assignee: Chuan Liu
Priority: Blocker
Fix For: 3.0.0, 2.3.0
Attachments: HADOOP-10110.patch
We have a build break in hadoop-auth if build with maven cache cleaned. The
error looks like the follows. The problem exists on both Windows and Linux.
If you have old jetty jars in your maven cache, you won't see the error.
{noformat}
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1:29.469s
[INFO] Finished at: Mon Nov 18 12:30:36 PST 2013
[INFO] Final Memory: 37M/120M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:testCompile
(default-testCompile) on project hadoop-auth: Compilation failure:
Compilation failure:
[ERROR]
/home/chuan/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/client/AuthenticatorTestCase.java:[84,13]
cannot access org.mortbay.component.AbstractLifeCycle
[ERROR] class file for org.mortbay.component.AbstractLifeCycle not found
[ERROR] server = new Server(0);
[ERROR]
/home/chuan/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/client/AuthenticatorTestCase.java:[94,29]
cannot access org.mortbay.component.LifeCycle
[ERROR] class file for org.mortbay.component.LifeCycle not found
[ERROR] server.getConnectors()[0].setHost(host);
[ERROR]
/home/chuan/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/client/AuthenticatorTestCase.java:[96,10]
cannot find symbol
[ERROR] symbol : method start()
[ERROR] location: class org.mortbay.jetty.Server
[ERROR]
/home/chuan/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/client/AuthenticatorTestCase.java:[102,12]
cannot find symbol
[ERROR] symbol : method stop()
[ERROR] location: class org.mortbay.jetty.Server
[ERROR] - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR] mvn goals -rf :hadoop-auth
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (HADOOP-9905) remove dependency of zookeeper for hadoop-client
[ https://issues.apache.org/jira/browse/HADOOP-9905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13750318#comment-13750318 ] Konstantin Boudnik commented on HADOOP-9905: I presume it also affects 2.0.6-alpha, right? remove dependency of zookeeper for hadoop-client Key: HADOOP-9905 URL: https://issues.apache.org/jira/browse/HADOOP-9905 Project: Hadoop Common Issue Type: Bug Affects Versions: 3.0.0, 2.1.0-beta Reporter: Vinay Assignee: Vinay Attachments: HADOOP-9905.patch zookeeper dependency was added for ZKFC, which will not be used by client. Better remove the dependency of zookeeper jar for hadoop-client -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9905) remove dependency of zookeeper for hadoop-client
[ https://issues.apache.org/jira/browse/HADOOP-9905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13750358#comment-13750358 ] Konstantin Boudnik commented on HADOOP-9905: Also, it seems that the patch actually adds the dependency to hadoop-client. Am I reading the patch wrong? remove dependency of zookeeper for hadoop-client Key: HADOOP-9905 URL: https://issues.apache.org/jira/browse/HADOOP-9905 Project: Hadoop Common Issue Type: Bug Affects Versions: 3.0.0, 2.1.0-beta Reporter: Vinay Assignee: Vinay Attachments: HADOOP-9905.patch zookeeper dependency was added for ZKFC, which will not be used by client. Better remove the dependency of zookeeper jar for hadoop-client -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9905) remove dependency of zookeeper for hadoop-client
[ https://issues.apache.org/jira/browse/HADOOP-9905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13750487#comment-13750487 ] Konstantin Boudnik commented on HADOOP-9905: Thanks, I knew I was misreading it... needs more coffee. remove dependency of zookeeper for hadoop-client Key: HADOOP-9905 URL: https://issues.apache.org/jira/browse/HADOOP-9905 Project: Hadoop Common Issue Type: Bug Affects Versions: 3.0.0, 2.1.0-beta Reporter: Vinay Assignee: Vinay Attachments: HADOOP-9905.patch zookeeper dependency was added for ZKFC, which will not be used by client. Better remove the dependency of zookeeper jar for hadoop-client -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7659) fs -getmerge isn't guaranteed to work well over non-HDFS filesystems
[
https://issues.apache.org/jira/browse/HADOOP-7659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13730358#comment-13730358
]
Konstantin Boudnik commented on HADOOP-7659:
Harsh, do you need a help on this? I can backport the patch into branch-2
unless you're planning to do it.
fs -getmerge isn't guaranteed to work well over non-HDFS filesystems
Key: HADOOP-7659
URL: https://issues.apache.org/jira/browse/HADOOP-7659
Project: Hadoop Common
Issue Type: Improvement
Components: fs
Affects Versions: 0.20.204.0
Reporter: Harsh J
Assignee: Harsh J
Priority: Minor
Fix For: 3.0.0
Attachments: HADOOP-7659.patch
When you use {{fs -getmerge}} with HDFS, you are guaranteed file list sorting
(part-0, part-1, onwards). When you use the same with other FSes we
bundle, the ordering of listing is not guaranteed at all. This is cause of
http://download.oracle.com/javase/6/docs/api/java/io/File.html#list() which
we use internally for native file listing.
This should either be documented as a known issue on -getmerge help
pages/mans, or a consistent ordering (similar to HDFS) must be applied atop
the listing. I suspect the latter only makes it worthy for what we include -
while other FSes out there still have to deal with this issue. Perhaps we
need a recommendation doc note added to our API?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9562) Create REST interface for HDFS health data
[ https://issues.apache.org/jira/browse/HADOOP-9562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711286#comment-13711286 ] Konstantin Boudnik commented on HADOOP-9562: Trevor, my understanding is that HDFS-5004 would be an alternative approach to this new REST interface, right? Create REST interface for HDFS health data -- Key: HADOOP-9562 URL: https://issues.apache.org/jira/browse/HADOOP-9562 Project: Hadoop Common Issue Type: Improvement Components: fs Affects Versions: 3.0.0, 2.0.4-alpha Reporter: Trevor Lorimer Priority: Minor Attachments: HADOOP-9562.diff The HDFS health screen (dfshealth.jsp) displays basic Version, Security and Health information concerning the NameNode, currently this information is accessible from classes in the org.apache.hadoop,hdfs.server.namenode package and cannot be accessed outside the NameNode. This becomes prevalent if the data is required to be displayed using a new user interface. The proposal is to create a REST interface to expose the NameNode information displayed on dfshealth.jsp using GET methods. Wrapper classes will be created to serve the data to the REST root resource within the hadoop-hdfs project. This will enable the HDFS health screen information to be accessed remotely. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9562) Create REST interface for HDFS health data
[ https://issues.apache.org/jira/browse/HADOOP-9562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HADOOP-9562: --- Affects Version/s: 3.0.0 Create REST interface for HDFS health data -- Key: HADOOP-9562 URL: https://issues.apache.org/jira/browse/HADOOP-9562 Project: Hadoop Common Issue Type: Improvement Components: fs Affects Versions: 3.0.0, 2.0.4-alpha Reporter: Trevor Lorimer Priority: Minor Attachments: HADOOP-9562.diff The HDFS health screen (dfshealth.jsp) displays basic Version, Security and Health information concerning the NameNode, currently this information is accessible from classes in the org.apache.hadoop,hdfs.server.namenode package and cannot be accessed outside the NameNode. This becomes prevalent if the data is required to be displayed using a new user interface. The proposal is to create a REST interface to expose all the information displayed on dfshealth.jsp using GET methods. Wrapper classes will be created to serve the data to the REST root resource within the hadoop-hdfs project. This will enable the HDFS health screen information to be accessed remotely. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9562) Create REST interface for HDFS health data
[ https://issues.apache.org/jira/browse/HADOOP-9562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701147#comment-13701147 ] Konstantin Boudnik commented on HADOOP-9562: The patch looks good at the first glance - I will read more into it over the weekend. Create REST interface for HDFS health data -- Key: HADOOP-9562 URL: https://issues.apache.org/jira/browse/HADOOP-9562 Project: Hadoop Common Issue Type: Improvement Components: fs Affects Versions: 3.0.0, 2.0.4-alpha Reporter: Trevor Lorimer Priority: Minor Attachments: HADOOP-9562.diff The HDFS health screen (dfshealth.jsp) displays basic Version, Security and Health information concerning the NameNode, currently this information is accessible from classes in the org.apache.hadoop,hdfs.server.namenode package and cannot be accessed outside the NameNode. This becomes prevalent if the data is required to be displayed using a new user interface. The proposal is to create a REST interface to expose all the information displayed on dfshealth.jsp using GET methods. Wrapper classes will be created to serve the data to the REST root resource within the hadoop-hdfs project. This will enable the HDFS health screen information to be accessed remotely. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9675) releasenotes.html always shows up as modified because of line endings issues
[ https://issues.apache.org/jira/browse/HADOOP-9675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13696221#comment-13696221 ] Konstantin Boudnik commented on HADOOP-9675: I agree: fixing the generator is the way to go. CRLF in the html file is a symptom. releasenotes.html always shows up as modified because of line endings issues Key: HADOOP-9675 URL: https://issues.apache.org/jira/browse/HADOOP-9675 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.1.0-beta Reporter: Sandy Ryza Assignee: Colin Patrick McCabe Attachments: HADOOP-9675.001.patch hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html shows up as modified even though I haven't touched it, and I can't check it out or reset to a previous version to make that go away. The only thing I can do to neutralize it is to put it in a dummy commit, but I have to do this every time I switch branches or rebase. This appears to have began after the release notes commit (8c5676830bb176157b2dc28c48cd3dd0a9712741), and must be due to a line endings change. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9615) Hadoop Jar command not working when used with Spring ORM
[ https://issues.apache.org/jira/browse/HADOOP-9615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13676756#comment-13676756 ] Konstantin Boudnik commented on HADOOP-9615: How is that a Hadoop issue? Hadoop Jar command not working when used with Spring ORM Key: HADOOP-9615 URL: https://issues.apache.org/jira/browse/HADOOP-9615 Project: Hadoop Common Issue Type: Bug Components: fs Affects Versions: 2.0.0-alpha Environment: CentOS, Reporter: Deepa Vasanthkumar Labels: hadoop-2.0 Unable to invoke 'hadoop jar' command for class, which contains Spring persistance unit. The problem is that, the jar file uses Spring ORM for loading the persistance configurations, and based on these configurations, i need to move the files to HDFS. While invoking the jar with hadoop jar command (having spring orm injected) the exception is as: Exception in thread main org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.dao.annotation.PersistenceExceptionTranslationPostProcessor#0' defined in class path resource [applicationContext.xml Error creating bean with name 'entityManagerFactory' defined in class path resource [applicationContext.xml]: Invocation of init method failed; nested exception is java.lang.IllegalStateException: Conflicting persistence unit definitions for name 'Persistance': file:/home/user/Desktop/ABC/apnJar.jar, file:/tmp/hadoop-user/hadoop-unjar2841422106164401019/ Caused by: java.lang.IllegalStateException: Conflicting persistence unit definitions for name 'Persistance': -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9615) Hadoop Jar command not working when used with Spring ORM
[ https://issues.apache.org/jira/browse/HADOOP-9615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HADOOP-9615: --- Target Version/s: (was: 2.0.4-alpha) Hadoop Jar command not working when used with Spring ORM Key: HADOOP-9615 URL: https://issues.apache.org/jira/browse/HADOOP-9615 Project: Hadoop Common Issue Type: Bug Components: fs Affects Versions: 2.0.0-alpha Environment: CentOS, Reporter: Deepa Vasanthkumar Labels: hadoop-2.0 Unable to invoke 'hadoop jar' command for class, which contains Spring persistance unit. The problem is that, the jar file uses Spring ORM for loading the persistance configurations, and based on these configurations, i need to move the files to HDFS. While invoking the jar with hadoop jar command (having spring orm injected) the exception is as: Exception in thread main org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.dao.annotation.PersistenceExceptionTranslationPostProcessor#0' defined in class path resource [applicationContext.xml Error creating bean with name 'entityManagerFactory' defined in class path resource [applicationContext.xml]: Invocation of init method failed; nested exception is java.lang.IllegalStateException: Conflicting persistence unit definitions for name 'Persistance': file:/home/user/Desktop/ABC/apnJar.jar, file:/tmp/hadoop-user/hadoop-unjar2841422106164401019/ Caused by: java.lang.IllegalStateException: Conflicting persistence unit definitions for name 'Persistance': -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9615) Hadoop Jar command not working when used with Spring ORM
[ https://issues.apache.org/jira/browse/HADOOP-9615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13676760#comment-13676760 ] Konstantin Boudnik commented on HADOOP-9615: I am removing 2.0.4-alpha target is that version has been released long time ago. Hadoop Jar command not working when used with Spring ORM Key: HADOOP-9615 URL: https://issues.apache.org/jira/browse/HADOOP-9615 Project: Hadoop Common Issue Type: Bug Components: fs Affects Versions: 2.0.0-alpha Environment: CentOS, Reporter: Deepa Vasanthkumar Labels: hadoop-2.0 Unable to invoke 'hadoop jar' command for class, which contains Spring persistance unit. The problem is that, the jar file uses Spring ORM for loading the persistance configurations, and based on these configurations, i need to move the files to HDFS. While invoking the jar with hadoop jar command (having spring orm injected) the exception is as: Exception in thread main org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.dao.annotation.PersistenceExceptionTranslationPostProcessor#0' defined in class path resource [applicationContext.xml Error creating bean with name 'entityManagerFactory' defined in class path resource [applicationContext.xml]: Invocation of init method failed; nested exception is java.lang.IllegalStateException: Conflicting persistence unit definitions for name 'Persistance': file:/home/user/Desktop/ABC/apnJar.jar, file:/tmp/hadoop-user/hadoop-unjar2841422106164401019/ Caused by: java.lang.IllegalStateException: Conflicting persistence unit definitions for name 'Persistance': -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9620) Stabilize branch-2 on Windows
[ https://issues.apache.org/jira/browse/HADOOP-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13676115#comment-13676115 ] Konstantin Boudnik commented on HADOOP-9620: Let me get it straight: the unit tests failures were invisible before and during the merge and then popped up once the commit was finished? Stabilize branch-2 on Windows - Key: HADOOP-9620 URL: https://issues.apache.org/jira/browse/HADOOP-9620 Project: Hadoop Common Issue Type: Bug Affects Versions: 2.1.0-beta Reporter: Chuan Liu After merging trunk change into branch-2, we are seeing a new set of unit test failures in branch-2 on Windows. This an umbrella jira to track the remaining issues in branch-2 on Windows with the goal to stabilize branch-2 on Windows and achieve 100% unit test pass rate. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9620) Umbrella jira to track windows unit test failures on branch-2
[ https://issues.apache.org/jira/browse/HADOOP-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13676554#comment-13676554 ] Konstantin Boudnik commented on HADOOP-9620: Oh, yes - that totally makes sense. Appreciate the explanation! Umbrella jira to track windows unit test failures on branch-2 - Key: HADOOP-9620 URL: https://issues.apache.org/jira/browse/HADOOP-9620 Project: Hadoop Common Issue Type: Bug Affects Versions: 2.1.0-beta Reporter: Chuan Liu -After merging trunk change into branch-2, we are seeing a new set of unit test failures- We are seeing some unit test failures in branch-2 on Windows. This is an umbrella jira to track the remaining issues in branch-2 on Windows with the goal to stabilize branch-2 on Windows and achieve 100% unit test pass rate. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9614) smart-test-patch.sh hangs for new version of patch (2.7.1)
[ https://issues.apache.org/jira/browse/HADOOP-9614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HADOOP-9614: --- Fix Version/s: (was: 2.0.5-alpha) smart-test-patch.sh hangs for new version of patch (2.7.1) -- Key: HADOOP-9614 URL: https://issues.apache.org/jira/browse/HADOOP-9614 Project: Hadoop Common Issue Type: Bug Affects Versions: 3.0.0, 0.23.7, 2.0.4-alpha Reporter: Ravi Prakash Assignee: Ravi Prakash Fix For: 3.0.0, 0.23.8 Attachments: HADOOP-9614.patch, HADOOP-9614.patch patch -p0 -E --dry-run prints checking file for the new version of patch(2.7.1) rather than patching file as it did for older versions. This causes TMP2 to become empty, which causes the script to hang on this command forever: PREFIX_DIRS_AND_FILES=$(cut -d '/' -f 1 | sort | uniq) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9613) Updated jersey pom dependencies
[ https://issues.apache.org/jira/browse/HADOOP-9613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HADOOP-9613: --- Fix Version/s: (was: 2.0.5-alpha) 2.1.0-beta Updated jersey pom dependencies --- Key: HADOOP-9613 URL: https://issues.apache.org/jira/browse/HADOOP-9613 Project: Hadoop Common Issue Type: Bug Components: build Affects Versions: 3.0.0, 2.0.5-alpha Reporter: Timothy St. Clair Labels: maven Fix For: 3.0.0, 2.1.0-beta Attachments: HADOOP-9613.patch There is a missing pom.xml dependencies exposed when running a mvn-rpmbuild against system dependencies. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9397) Incremental dist tar build fails
[ https://issues.apache.org/jira/browse/HADOOP-9397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13671989#comment-13671989 ] Konstantin Boudnik commented on HADOOP-9397: Seems like this JIRA is logged under trunk section in CHANGES.txt, instead of being in 2.1.0-beta part Incremental dist tar build fails Key: HADOOP-9397 URL: https://issues.apache.org/jira/browse/HADOOP-9397 Project: Hadoop Common Issue Type: Bug Components: build Affects Versions: 3.0.0 Reporter: Jason Lowe Assignee: Chris Nauroth Fix For: 3.0.0, 2.1.0-beta Attachments: HADOOP-9397.1.patch Building a dist tar build when the dist tarball already exists from a previous build fails. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9605) Update junit dependency
[ https://issues.apache.org/jira/browse/HADOOP-9605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670529#comment-13670529 ] Konstantin Boudnik commented on HADOOP-9605: Oh... I am sorry - you right of course. That makes sense - let me commit the patch then. Update junit dependency --- Key: HADOOP-9605 URL: https://issues.apache.org/jira/browse/HADOOP-9605 Project: Hadoop Common Issue Type: Improvement Components: build Affects Versions: 3.0.0, 2.0.5-beta Reporter: Timothy St. Clair Labels: maven Attachments: HADOOP-9605.patch1, HADOOP-9605.patch2 Simple update of the junit dependency to use newer version. E.g. when running maven-rpmbuild on Fedora 18. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9607) Fixes in Javadoc build
[ https://issues.apache.org/jira/browse/HADOOP-9607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670578#comment-13670578 ] Konstantin Boudnik commented on HADOOP-9607: +1 - it was an annoying problem and I am glad it was fixed! Fixes in Javadoc build -- Key: HADOOP-9607 URL: https://issues.apache.org/jira/browse/HADOOP-9607 Project: Hadoop Common Issue Type: Bug Components: documentation Affects Versions: 3.0.0, 2.0.5-beta Reporter: Timothy St. Clair Priority: Minor Labels: documentation Attachments: HADOOP-9607.patch It appears that some non-ascii characters have crept into the code, which cause an issue when building javadocs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9605) Update junit dependency
[ https://issues.apache.org/jira/browse/HADOOP-9605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HADOOP-9605: --- Fix Version/s: 2.0.5-beta Update junit dependency --- Key: HADOOP-9605 URL: https://issues.apache.org/jira/browse/HADOOP-9605 Project: Hadoop Common Issue Type: Improvement Components: build Affects Versions: 3.0.0, 2.0.5-beta Reporter: Timothy St. Clair Labels: maven Fix For: 2.0.5-beta Attachments: HADOOP-9605.patch1, HADOOP-9605.patch2 Simple update of the junit dependency to use newer version. E.g. when running maven-rpmbuild on Fedora 18. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9605) Update junit dependency
[ https://issues.apache.org/jira/browse/HADOOP-9605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HADOOP-9605: --- Resolution: Fixed Release Note: I have committed the patch both to trunk and branch-2. Thanks Timothy! Status: Resolved (was: Patch Available) Update junit dependency --- Key: HADOOP-9605 URL: https://issues.apache.org/jira/browse/HADOOP-9605 Project: Hadoop Common Issue Type: Improvement Components: build Affects Versions: 3.0.0, 2.0.5-beta Reporter: Timothy St. Clair Labels: maven Fix For: 2.0.5-beta Attachments: HADOOP-9605.patch1, HADOOP-9605.patch2 Simple update of the junit dependency to use newer version. E.g. when running maven-rpmbuild on Fedora 18. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9607) Fixes in Javadoc build
[ https://issues.apache.org/jira/browse/HADOOP-9607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HADOOP-9607: --- Resolution: Fixed Fix Version/s: 2.0.5-beta Status: Resolved (was: Patch Available) I have committed the patch both to trunk and branch-2. Thanks Timothy! Fixes in Javadoc build -- Key: HADOOP-9607 URL: https://issues.apache.org/jira/browse/HADOOP-9607 Project: Hadoop Common Issue Type: Bug Components: documentation Affects Versions: 3.0.0, 2.0.5-beta Reporter: Timothy St. Clair Priority: Minor Labels: documentation Fix For: 2.0.5-beta Attachments: HADOOP-9607.patch It appears that some non-ascii characters have crept into the code, which cause an issue when building javadocs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9605) Update junit dependency
[ https://issues.apache.org/jira/browse/HADOOP-9605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HADOOP-9605: --- Assignee: Konstantin Boudnik Update junit dependency --- Key: HADOOP-9605 URL: https://issues.apache.org/jira/browse/HADOOP-9605 Project: Hadoop Common Issue Type: Improvement Components: build Affects Versions: 3.0.0, 2.0.5-beta Reporter: Timothy St. Clair Assignee: Konstantin Boudnik Labels: maven Fix For: 2.0.5-beta Attachments: HADOOP-9605.patch1, HADOOP-9605.patch2 Simple update of the junit dependency to use newer version. E.g. when running maven-rpmbuild on Fedora 18. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9605) Update junit dependency
[ https://issues.apache.org/jira/browse/HADOOP-9605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HADOOP-9605: --- Release Note: (was: I have committed the patch both to trunk and branch-2. Thanks Timothy!) I have committed the patch both to trunk and branch-2. Thanks Timothy! Update junit dependency --- Key: HADOOP-9605 URL: https://issues.apache.org/jira/browse/HADOOP-9605 Project: Hadoop Common Issue Type: Improvement Components: build Affects Versions: 3.0.0, 2.0.5-beta Reporter: Timothy St. Clair Labels: maven Fix For: 2.0.5-beta Attachments: HADOOP-9605.patch1, HADOOP-9605.patch2 Simple update of the junit dependency to use newer version. E.g. when running maven-rpmbuild on Fedora 18. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9605) Update junit dependency
[ https://issues.apache.org/jira/browse/HADOOP-9605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HADOOP-9605: --- Assignee: (was: Konstantin Boudnik) Update junit dependency --- Key: HADOOP-9605 URL: https://issues.apache.org/jira/browse/HADOOP-9605 Project: Hadoop Common Issue Type: Improvement Components: build Affects Versions: 3.0.0, 2.0.5-beta Reporter: Timothy St. Clair Labels: maven Fix For: 2.0.5-beta Attachments: HADOOP-9605.patch1, HADOOP-9605.patch2 Simple update of the junit dependency to use newer version. E.g. when running maven-rpmbuild on Fedora 18. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9605) Update junit dependency
[ https://issues.apache.org/jira/browse/HADOOP-9605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13669750#comment-13669750 ] Konstantin Boudnik commented on HADOOP-9605: While pretty tiny, I'd suggest to split the patch in two: - dependency's version bump - and update for the rule to be separated Update junit dependency --- Key: HADOOP-9605 URL: https://issues.apache.org/jira/browse/HADOOP-9605 Project: Hadoop Common Issue Type: Improvement Components: build Affects Versions: 3.0.0, 2.0.5-beta Reporter: Timothy St. Clair Labels: maven Attachments: HADOOP-9605.patch Simple update of the junit dependency to use newer version. E.g. when running maven-rpmbuild on Fedora 18. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9605) Update junit dependency
[ https://issues.apache.org/jira/browse/HADOOP-9605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13669775#comment-13669775 ] Konstantin Boudnik commented on HADOOP-9605: I should've be more explicit - I am sorry - I meant that test update also needs to go to a separate JIRA. +1 on the version bump, as it seems that javac warnings are legitimate. Update junit dependency --- Key: HADOOP-9605 URL: https://issues.apache.org/jira/browse/HADOOP-9605 Project: Hadoop Common Issue Type: Improvement Components: build Affects Versions: 3.0.0, 2.0.5-beta Reporter: Timothy St. Clair Labels: maven Attachments: HADOOP-9605.patch1, HADOOP-9605.patch2 Simple update of the junit dependency to use newer version. E.g. when running maven-rpmbuild on Fedora 18. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9407) commons-daemon 1.0.3 dependency has bad group id causing build issues
[ https://issues.apache.org/jira/browse/HADOOP-9407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HADOOP-9407: --- Fix Version/s: 2.0.4.1-alpha commons-daemon 1.0.3 dependency has bad group id causing build issues - Key: HADOOP-9407 URL: https://issues.apache.org/jira/browse/HADOOP-9407 Project: Hadoop Common Issue Type: Bug Components: build Affects Versions: 2.0.3-alpha, 2.0.4-alpha Reporter: Sangjin Lee Assignee: Sangjin Lee Labels: 2.0.4 Fix For: 2.0.5-beta, 2.0.4.1-alpha Attachments: HDFS-4497.patch The commons-daemon dependency of the hadoop-hdfs module has been at version 1.0.3 for a while. However, 1.0.3 has a pretty well-known groupId error in its pom (org.apache.commons as opposed to commons-daemon). This problem has since been corrected on commons-daemon starting 1.0.4. This causes build problems for many who depend on hadoop-hdfs directly and indirectly, however. Maven can skip over this metadata inconsistency. But other less forgiving build systems such as ivy and gradle have much harder time working around this problem. For example, in gradle, pretty much the only obvious way to work around this is to override this dependency version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9407) commons-daemon 1.0.3 dependency has bad group id causing build issues
[ https://issues.apache.org/jira/browse/HADOOP-9407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1320#comment-1320 ] Konstantin Boudnik commented on HADOOP-9407: I have just committed this fix to 2.0.4.1-alpha release (branch-2.0.4-alpha). Thank you Sangjin. commons-daemon 1.0.3 dependency has bad group id causing build issues - Key: HADOOP-9407 URL: https://issues.apache.org/jira/browse/HADOOP-9407 Project: Hadoop Common Issue Type: Bug Components: build Affects Versions: 2.0.3-alpha, 2.0.4-alpha Reporter: Sangjin Lee Assignee: Sangjin Lee Labels: 2.0.4 Fix For: 2.0.5-beta, 2.0.4.1-alpha Attachments: HDFS-4497.patch The commons-daemon dependency of the hadoop-hdfs module has been at version 1.0.3 for a while. However, 1.0.3 has a pretty well-known groupId error in its pom (org.apache.commons as opposed to commons-daemon). This problem has since been corrected on commons-daemon starting 1.0.4. This causes build problems for many who depend on hadoop-hdfs directly and indirectly, however. Maven can skip over this metadata inconsistency. But other less forgiving build systems such as ivy and gradle have much harder time working around this problem. For example, in gradle, pretty much the only obvious way to work around this is to override this dependency version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9407) commons-daemon 1.0.3 dependency has bad group id causing build issues
[ https://issues.apache.org/jira/browse/HADOOP-9407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1337#comment-1337 ] Konstantin Boudnik commented on HADOOP-9407: I see this already committed to the branch-2, which is in my understanding is effectively tracking 2.0.5 release now. So, I guess the ticket should be closed. commons-daemon 1.0.3 dependency has bad group id causing build issues - Key: HADOOP-9407 URL: https://issues.apache.org/jira/browse/HADOOP-9407 Project: Hadoop Common Issue Type: Bug Components: build Affects Versions: 2.0.3-alpha, 2.0.4-alpha Reporter: Sangjin Lee Assignee: Sangjin Lee Labels: 2.0.4 Fix For: 2.0.5-beta, 2.0.4.1-alpha Attachments: HDFS-4497.patch The commons-daemon dependency of the hadoop-hdfs module has been at version 1.0.3 for a while. However, 1.0.3 has a pretty well-known groupId error in its pom (org.apache.commons as opposed to commons-daemon). This problem has since been corrected on commons-daemon starting 1.0.4. This causes build problems for many who depend on hadoop-hdfs directly and indirectly, however. Maven can skip over this metadata inconsistency. But other less forgiving build systems such as ivy and gradle have much harder time working around this problem. For example, in gradle, pretty much the only obvious way to work around this is to override this dependency version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9597) FileSystem open() API is not clear if FileNotFoundException is throw when the path does not exist
[ https://issues.apache.org/jira/browse/HADOOP-9597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HADOOP-9597: --- Fix Version/s: (was: 2.0.4.1-alpha) FileSystem open() API is not clear if FileNotFoundException is throw when the path does not exist - Key: HADOOP-9597 URL: https://issues.apache.org/jira/browse/HADOOP-9597 Project: Hadoop Common Issue Type: Sub-task Components: documentation, fs Affects Versions: 2.0.4-alpha Reporter: Jerry He Priority: Minor The current FileSystem open() method throws a generic IOException in its API specification. Some FileSystem implementations (DFS, RawLocalFileSystem ...) throws more specific FileNotFoundException if the path does not exist. Some throws IOException only (FTPFileSystem, HftpFileSystem ...). If we have a new FileSystem implementation, what should we follow exactly for open()? What should the application expect in this case. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9407) commons-daemon 1.0.3 dependency has bad group id causing build issues
[ https://issues.apache.org/jira/browse/HADOOP-9407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HADOOP-9407: --- Resolution: Fixed Status: Resolved (was: Patch Available) Fixed in both targetted releases. CLosing. commons-daemon 1.0.3 dependency has bad group id causing build issues - Key: HADOOP-9407 URL: https://issues.apache.org/jira/browse/HADOOP-9407 Project: Hadoop Common Issue Type: Bug Components: build Affects Versions: 2.0.3-alpha, 2.0.4-alpha Reporter: Sangjin Lee Assignee: Sangjin Lee Labels: 2.0.4 Fix For: 2.0.5-beta, 2.0.4.1-alpha Attachments: HDFS-4497.patch The commons-daemon dependency of the hadoop-hdfs module has been at version 1.0.3 for a while. However, 1.0.3 has a pretty well-known groupId error in its pom (org.apache.commons as opposed to commons-daemon). This problem has since been corrected on commons-daemon starting 1.0.4. This causes build problems for many who depend on hadoop-hdfs directly and indirectly, however. Maven can skip over this metadata inconsistency. But other less forgiving build systems such as ivy and gradle have much harder time working around this problem. For example, in gradle, pretty much the only obvious way to work around this is to override this dependency version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9562) Create REST interface for HDFS health data
[
https://issues.apache.org/jira/browse/HADOOP-9562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13662669#comment-13662669
]
Konstantin Boudnik commented on HADOOP-9562:
Trevor, for a patch to go trough automatic testing system it needs to be
generated against trunk.
Also, a quick look at the patch shows that you have some irrelevant changes in
it:
- .../hadoop-common/src/main/docs/releasenotes.html seems to be included
because it has some CRLF issues in branch-2 as the result of autogeneration or
something.
- the licenses _have_ to be ASL 2.0 and they have to present in all new files
- class {{NodesInfo}} is empty. Is this expected?
Please address these issue in the second version. BTW, you can keep the same
name of the patch file and JIRA will automatically detect new version.
Create REST interface for HDFS health data
--
Key: HADOOP-9562
URL: https://issues.apache.org/jira/browse/HADOOP-9562
Project: Hadoop Common
Issue Type: Improvement
Components: fs
Affects Versions: 2.0.4-alpha
Reporter: Trevor Lorimer
Priority: Minor
Attachments: 0001-HAD-162-Final-revision-refactor.patch
The HDFS health screen (dfshealth.jsp) displays basic Version, Security and
Health information concerning the NameNode, currently this information is
accessible from classes in the org.apache.hadoop,hdfs.server.namenode package
and cannot be accessed outside the NameNode. This becomes prevalent if the
data is required to be displayed using a new user interface.
The proposal is to create a REST interface to expose all the information
displayed on dfshealth.jsp using GET methods. Wrapper classes will be created
to serve the data to the REST root resource within the hadoop-hdfs project.
This will enable the HDFS health screen information to be accessed remotely.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9562) Create REST interface for HDFS health data
[ https://issues.apache.org/jira/browse/HADOOP-9562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13659727#comment-13659727 ] Konstantin Boudnik commented on HADOOP-9562: Is the http proxy REST friendly/compatible? Create REST interface for HDFS health data -- Key: HADOOP-9562 URL: https://issues.apache.org/jira/browse/HADOOP-9562 Project: Hadoop Common Issue Type: New Feature Components: fs Affects Versions: 2.0.4-alpha Reporter: Trevor Lorimer Priority: Minor The HDFS health screen (dfshealth.jsp) displays basic Version, Security and Health information concerning the NameNode, currently this information is accessible from classes in the org.apache.hadoop,hdfs.server.namenode package and cannot be accessed outside the NameNode. This becomes prevalent if the data is required to be displayed using a new user interface. The proposal is to create a REST interface to expose all the information displayed on dfshealth.jsp using GET methods. Wrapper classes will be created to serve the data to the REST root resource within the hadoop-hdfs project. This will enable the HDFS health screen information to be accessed remotely. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9562) Create REST interface for HDFS health data
[ https://issues.apache.org/jira/browse/HADOOP-9562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HADOOP-9562: --- Issue Type: Improvement (was: New Feature) Create REST interface for HDFS health data -- Key: HADOOP-9562 URL: https://issues.apache.org/jira/browse/HADOOP-9562 Project: Hadoop Common Issue Type: Improvement Components: fs Affects Versions: 2.0.4-alpha Reporter: Trevor Lorimer Priority: Minor The HDFS health screen (dfshealth.jsp) displays basic Version, Security and Health information concerning the NameNode, currently this information is accessible from classes in the org.apache.hadoop,hdfs.server.namenode package and cannot be accessed outside the NameNode. This becomes prevalent if the data is required to be displayed using a new user interface. The proposal is to create a REST interface to expose all the information displayed on dfshealth.jsp using GET methods. Wrapper classes will be created to serve the data to the REST root resource within the hadoop-hdfs project. This will enable the HDFS health screen information to be accessed remotely. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9562) Create REST interface for HDFS health data
[ https://issues.apache.org/jira/browse/HADOOP-9562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13659756#comment-13659756 ] Konstantin Boudnik commented on HADOOP-9562: I musta missed something: the JIRA is for like 3 REST calls to provide convenient RO access to some of the data that is already available either in the form of basic HTML webpage or via JMX. It isn't even a new feature - it is minor improvement and should be treated as such. If there's a need for a new web-backend in HDFS - it's isn't a part of this JIRA: not by a long shot, really. Create REST interface for HDFS health data -- Key: HADOOP-9562 URL: https://issues.apache.org/jira/browse/HADOOP-9562 Project: Hadoop Common Issue Type: Improvement Components: fs Affects Versions: 2.0.4-alpha Reporter: Trevor Lorimer Priority: Minor The HDFS health screen (dfshealth.jsp) displays basic Version, Security and Health information concerning the NameNode, currently this information is accessible from classes in the org.apache.hadoop,hdfs.server.namenode package and cannot be accessed outside the NameNode. This becomes prevalent if the data is required to be displayed using a new user interface. The proposal is to create a REST interface to expose all the information displayed on dfshealth.jsp using GET methods. Wrapper classes will be created to serve the data to the REST root resource within the hadoop-hdfs project. This will enable the HDFS health screen information to be accessed remotely. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9562) Create REST interface for HDFS health data
[ https://issues.apache.org/jira/browse/HADOOP-9562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13660336#comment-13660336 ] Konstantin Boudnik commented on HADOOP-9562: bq. I'm happy to help review and vote on this, if you are happy to deal with the inconsistencies of adding features to what you declared to be a feature-frozen release. Steve, I'd be really thankful if you can tell me where the notion of adding features to what you declared to be a feature-frozen release coming from? I can bet good money that I haven't said that. Please clarify. Create REST interface for HDFS health data -- Key: HADOOP-9562 URL: https://issues.apache.org/jira/browse/HADOOP-9562 Project: Hadoop Common Issue Type: Improvement Components: fs Affects Versions: 2.0.4-alpha Reporter: Trevor Lorimer Priority: Minor The HDFS health screen (dfshealth.jsp) displays basic Version, Security and Health information concerning the NameNode, currently this information is accessible from classes in the org.apache.hadoop,hdfs.server.namenode package and cannot be accessed outside the NameNode. This becomes prevalent if the data is required to be displayed using a new user interface. The proposal is to create a REST interface to expose all the information displayed on dfshealth.jsp using GET methods. Wrapper classes will be created to serve the data to the REST root resource within the hadoop-hdfs project. This will enable the HDFS health screen information to be accessed remotely. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-9528) org.apache.hadoop.ha.TestZKFailoverController.testCedeActive is failing intermittently
Konstantin Boudnik created HADOOP-9528:
--
Summary:
org.apache.hadoop.ha.TestZKFailoverController.testCedeActive is failing
intermittently
Key: HADOOP-9528
URL: https://issues.apache.org/jira/browse/HADOOP-9528
Project: Hadoop Common
Issue Type: Bug
Components: ha
Affects Versions: 2.0.4-alpha
Reporter: Konstantin Boudnik
Unit tests is failing with a message like
{{Should take ~3 seconds to rejoin. Only took 2276ms before rejoining.}}
A looking into the test shows the only 2.8 seconds and more is considered to be
{{about 3 seconds}}. Say 2.7 seconds won't be considered {{about 3 seconds}}
contrary to elementary school arithmetic.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9407) commons-daemon 1.0.3 dependency has bad group id causing build issues
[ https://issues.apache.org/jira/browse/HADOOP-9407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13638315#comment-13638315 ] Konstantin Boudnik commented on HADOOP-9407: I have reopened to ticket to be able to back-ported to branch-2.0.4-alpha. Patch available wasn't needed. commons-daemon 1.0.3 dependency has bad group id causing build issues - Key: HADOOP-9407 URL: https://issues.apache.org/jira/browse/HADOOP-9407 Project: Hadoop Common Issue Type: Bug Components: build Affects Versions: 2.0.3-alpha, 2.0.4-alpha Reporter: Sangjin Lee Assignee: Sangjin Lee Labels: 2.0.4 Fix For: 2.0.5-beta Attachments: HDFS-4497.patch The commons-daemon dependency of the hadoop-hdfs module has been at version 1.0.3 for a while. However, 1.0.3 has a pretty well-known groupId error in its pom (org.apache.commons as opposed to commons-daemon). This problem has since been corrected on commons-daemon starting 1.0.4. This causes build problems for many who depend on hadoop-hdfs directly and indirectly, however. Maven can skip over this metadata inconsistency. But other less forgiving build systems such as ivy and gradle have much harder time working around this problem. For example, in gradle, pretty much the only obvious way to work around this is to override this dependency version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9407) commons-daemon 1.0.3 dependency has bad group id causing build issues
[ https://issues.apache.org/jira/browse/HADOOP-9407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13635457#comment-13635457 ] Konstantin Boudnik commented on HADOOP-9407: I have raised it again on the voting thread with a neutral vote (-0). For a variety of reasons I am not very optimistic that RC will be re-spun at this point. commons-daemon 1.0.3 dependency has bad group id causing build issues - Key: HADOOP-9407 URL: https://issues.apache.org/jira/browse/HADOOP-9407 Project: Hadoop Common Issue Type: Bug Components: build Affects Versions: 2.0.3-alpha, 2.0.4-alpha Reporter: Sangjin Lee Assignee: Sangjin Lee Labels: 2.0.4 Fix For: 2.0.5-beta Attachments: HDFS-4497.patch The commons-daemon dependency of the hadoop-hdfs module has been at version 1.0.3 for a while. However, 1.0.3 has a pretty well-known groupId error in its pom (org.apache.commons as opposed to commons-daemon). This problem has since been corrected on commons-daemon starting 1.0.4. This causes build problems for many who depend on hadoop-hdfs directly and indirectly, however. Maven can skip over this metadata inconsistency. But other less forgiving build systems such as ivy and gradle have much harder time working around this problem. For example, in gradle, pretty much the only obvious way to work around this is to override this dependency version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (HADOOP-9407) commons-daemon 1.0.3 dependency has bad group id causing build issues
[ https://issues.apache.org/jira/browse/HADOOP-9407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik reopened HADOOP-9407: I think it needs to be added to branch-2.0.4-alpha as well before the release goes out. commons-daemon 1.0.3 dependency has bad group id causing build issues - Key: HADOOP-9407 URL: https://issues.apache.org/jira/browse/HADOOP-9407 Project: Hadoop Common Issue Type: Bug Components: build Affects Versions: 2.0.3-alpha Reporter: Sangjin Lee Assignee: Sangjin Lee Fix For: 2.0.5-beta Attachments: HDFS-4497.patch The commons-daemon dependency of the hadoop-hdfs module has been at version 1.0.3 for a while. However, 1.0.3 has a pretty well-known groupId error in its pom (org.apache.commons as opposed to commons-daemon). This problem has since been corrected on commons-daemon starting 1.0.4. This causes build problems for many who depend on hadoop-hdfs directly and indirectly, however. Maven can skip over this metadata inconsistency. But other less forgiving build systems such as ivy and gradle have much harder time working around this problem. For example, in gradle, pretty much the only obvious way to work around this is to override this dependency version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9407) commons-daemon 1.0.3 dependency has bad group id causing build issues
[ https://issues.apache.org/jira/browse/HADOOP-9407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HADOOP-9407: --- Affects Version/s: 2.0.4-alpha commons-daemon 1.0.3 dependency has bad group id causing build issues - Key: HADOOP-9407 URL: https://issues.apache.org/jira/browse/HADOOP-9407 Project: Hadoop Common Issue Type: Bug Components: build Affects Versions: 2.0.3-alpha, 2.0.4-alpha Reporter: Sangjin Lee Assignee: Sangjin Lee Fix For: 2.0.5-beta Attachments: HDFS-4497.patch The commons-daemon dependency of the hadoop-hdfs module has been at version 1.0.3 for a while. However, 1.0.3 has a pretty well-known groupId error in its pom (org.apache.commons as opposed to commons-daemon). This problem has since been corrected on commons-daemon starting 1.0.4. This causes build problems for many who depend on hadoop-hdfs directly and indirectly, however. Maven can skip over this metadata inconsistency. But other less forgiving build systems such as ivy and gradle have much harder time working around this problem. For example, in gradle, pretty much the only obvious way to work around this is to override this dependency version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-9407) commons-daemon 1.0.3 dependency has bad group id causing build issues
[ https://issues.apache.org/jira/browse/HADOOP-9407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated HADOOP-9407: --- Labels: 2.0.4 (was: ) commons-daemon 1.0.3 dependency has bad group id causing build issues - Key: HADOOP-9407 URL: https://issues.apache.org/jira/browse/HADOOP-9407 Project: Hadoop Common Issue Type: Bug Components: build Affects Versions: 2.0.3-alpha, 2.0.4-alpha Reporter: Sangjin Lee Assignee: Sangjin Lee Labels: 2.0.4 Fix For: 2.0.5-beta Attachments: HDFS-4497.patch The commons-daemon dependency of the hadoop-hdfs module has been at version 1.0.3 for a while. However, 1.0.3 has a pretty well-known groupId error in its pom (org.apache.commons as opposed to commons-daemon). This problem has since been corrected on commons-daemon starting 1.0.4. This causes build problems for many who depend on hadoop-hdfs directly and indirectly, however. Maven can skip over this metadata inconsistency. But other less forgiving build systems such as ivy and gradle have much harder time working around this problem. For example, in gradle, pretty much the only obvious way to work around this is to override this dependency version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
