[
https://issues.apache.org/jira/browse/HADOOP-7457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Shvachko reopened HADOOP-7457:
-
Reopening this to port changes to 0.22 branch. Currently common build fails
because
to fix hadoop config template
-
Key: HADOOP-7658
URL: https://issues.apache.org/jira/browse/HADOOP-7658
Project: Hadoop Common
Issue Type: Bug
Reporter: Giridharan Kesavan
hadoop rpm config template
[
https://issues.apache.org/jira/browse/HADOOP-7228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-7228.
--
Resolution: Won't Fix
Surprise.
> jar names are not compatible with 0.20.2
>
Add support for LZ4 compression
---
Key: HADOOP-7657
URL: https://issues.apache.org/jira/browse/HADOOP-7657
Project: Hadoop Common
Issue Type: Improvement
Reporter: Mr Bsd
According to several benchm
Thanks for your support. I've opened
INFRA-3937 Request for Hadoop Jiras: add custom field "Target Version/s"
[field type Version Picker]
if anyone wishes to follow the issue.
--Matt
On Fri, Sep 16, 2011 at 9:21 AM, Rottinghuis, Joep wrote:
> Non-binding +1
>
> Joep
> __
YARN RM fails to start
--
Key: HADOOP-7656
URL: https://issues.apache.org/jira/browse/HADOOP-7656
Project: Hadoop Common
Issue Type: Bug
Affects Versions: 0.24.0
Environment: [criccomi@criccomi-ld trunk]$ svn
provide a small validation script that smoke tests the installed cluster
Key: HADOOP-7655
URL: https://issues.apache.org/jira/browse/HADOOP-7655
Project: Hadoop Common
[
https://issues.apache.org/jira/browse/HADOOP-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uma Maheswara Rao G resolved HADOOP-2120.
-
Resolution: Not A Problem
> dfs -getMerge does not do what it says it does
> ---
On Sep 15, 2011, at 2:26 AM, Steve Loughran wrote:
> These are all good ideas. The other trick -which has been discussed recently
> in the context of the Platform Scheduler- is to run HDFS across all nodes,
> but switch the workload of the cluster between Hadoop jobs (MR, Graph,
> Hamster), and
>
>
>
>These are all good ideas. The other trick -which has been discussed
>recently in the context of the Platform Scheduler- is to run HDFS across
>all nodes, but switch the workload of the cluster between Hadoop jobs
>(MR, Graph, Hamster), and other work (Grid jobs). That way the
>filesystem is
Change maven setup to not run tests by default
--
Key: HADOOP-7654
URL: https://issues.apache.org/jira/browse/HADOOP-7654
Project: Hadoop Common
Issue Type: Wish
Components: build
Aff
For those who are not aware of 6-year old history :-), Sameer, Owen and I
made a trip to Wisconsin, Madison to meet with Miron Livny, who built
Condor, exploring how matchmaking could be used with MapReduce
(pre-hadoop) in October 2005. (We believed it could be used for
locality-aware scheduling.)
[
https://issues.apache.org/jira/browse/HADOOP-7647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eli Collins resolved HADOOP-7647.
-
Resolution: Fixed
Hadoop Flags: [Reviewed]
Thanks Doug. I've committed this.
> Update byl
[
https://issues.apache.org/jira/browse/HADOOP-7634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eli Collins resolved HADOOP-7634.
-
Resolution: Fixed
Fix Version/s: (was: 0.20.205.0)
0.20.206.0
14 matches
Mail list logo
