You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@hadoop.apache.org by Bob Li <pa...@gmail.com> on 2010/09/02 20:53:30 UTC

Re: apache commons configuration

Hi experts,

For hadoop 0.20.2, we have following task tracker configuration
 <property>
    <name>mapred.local.dir</name>
    <value>/data/mapred/local</value>
  </property>

It seems not what I expected -- the directory /tmp/hadoop-user/mapred/local
was used.

Any suggestion?

Thanks,
Bob

On Wed, Aug 25, 2010 at 4:34 AM, Jeff Hammerbacher <ha...@cloudera.com>wrote:

> For some recent discussion, see
> https://issues.apache.org/jira/browse/HADOOP-6910
>
> On Tue, Aug 24, 2010 at 3:24 AM, Steve Loughran <st...@apache.org> wrote:
>
> > On 24/08/10 10:43, Thomas Koch wrote:
> >
> >> Hi,
> >>
> >> just out of curiosity: Is there any particular reason, why Hadoop
> projects
> >> or
> >> ZooKeeper do not use apache commons configuration[1]?
> >> I'm just evaluating it for an internal project. Would you recommend it
> or
> >> not?
> >> I imagine, that it could help to make projects configurable either via
> XML
> >> or
> >> INI files. Some people may prefer one or the other.
> >>
> >> [1] http://commons.apache.org/configuration/
> >>
> >
> > Someone's discussed it, I'm against because (a) there's a lot of
> historical
> > configuration stuff in there, (b) ini files are less flexible than XML,
> (c)
> > neither of them are very dynamic. when the NN goes down and you want the
> DNs
> > to reconnect to a different host, how do you do that when all data is
> read
> > at start time?
> >
> >
> >
>

Re: apache commons configuration

Posted by Allen Wittenauer <aw...@linkedin.com>.
On Sep 2, 2010, at 11:53 AM, Bob Li wrote:

> Hi experts,
> 
> For hadoop 0.20.2, we have following task tracker configuration
> <property>
>    <name>mapred.local.dir</name>
>    <value>/data/mapred/local</value>
>  </property>
> 
> It seems not what I expected -- the directory /tmp/hadoop-user/mapred/local
> was used.
> 
> Any suggestion?


Config problems like this seem to usually be traced back to broken XML formatting prior to this entry or the property being in the wrong file (in this case, it should be in mapred-site.xml).