hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-4189) HADOOP-3245 is incomplete
Date Thu, 18 Sep 2008 23:56:44 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Arun C Murthy updated HADOOP-4189:
----------------------------------

    Status: Open  (was: Patch Available)

Null config values are not the right way to go. At best it should be "-1" in these cases to
let the system pick the default values.

In these specific cases I'm not sure we even need to make them configurable... the system
should just pick the right values?

Do we need to bump up TaskUmbilicalProtocol's version? If so, we at least should add a comment
describing why the change was necessary.

> HADOOP-3245 is incomplete
> -------------------------
>
>                 Key: HADOOP-4189
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4189
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Amar Kamat
>            Assignee: Amar Kamat
>            Priority: Blocker
>             Fix For: 0.19.0
>
>         Attachments: HADOOP-4189-v1.patch, HADOOP-4189-v2.patch, HADOOP-4189-v3.1.patch,
HADOOP-4189-v3.patch, HADOOP-4189.patch
>
>
> There are 2 issues with HADOOP-3245
> - The default block size for the history files in hadoop-default.conf is set to 0. This
file will be empty throughout. It should be made null.
> - Same goes for the buffer size. 
> - InterTrackerProtocol version needs to be bumped.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message