hadoop-common-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From patrick sang <silvianhad...@gmail.com>
Subject Re: dump configuration
Date Thu, 29 Sep 2011 18:29:05 GMT
Thanks to all.. especially from SD. that's exactly what i am looking for.

P

On Wed, Sep 28, 2011 at 11:20 PM, Simon Dong <simond301@gmail.com> wrote:

> Or http://jobtracker:50030/conf
>
> -SD
>
> On Wed, Sep 28, 2011 at 2:39 PM, Raj V <rajvish@yahoo.com> wrote:
> > The xml configuration file is also available under hadoop logs on the
> jobtracker.
> >
> > Raj
> >
> >
> >
> >>________________________________
> >>From: "GOEKE, MATTHEW (AG/1000)" <matthew.goeke@monsanto.com>
> >>To: "common-user@hadoop.apache.org" <common-user@hadoop.apache.org>
> >>Sent: Wednesday, September 28, 2011 2:27 PM
> >>Subject: RE: dump configuration
> >>
> >>You could always check the web-ui job history for that particular run,
> open the job.xml, and search for what the value of that parameter was at
> runtime.
> >>
> >>Matt
> >>
> >>-----Original Message-----
> >>From: patrick sang [mailto:silvianhadoop@gmail.com]
> >>Sent: Wednesday, September 28, 2011 4:00 PM
> >>To: common-user@hadoop.apache.org
> >>Subject: dump configuration
> >>
> >>Hi hadoopers,
> >>
> >>I was looking the way to dump hadoop configuration in order to check if
> what
> >>i have just changed
> >>in mapred-site.xml is really kicked in.
> >>
> >>Found that HADOOP-6184
> >><https://issues.apache.org/jira/browse/HADOOP-6184>is exactly what i
> >>want but the thing is I am running CDH3u0 which is
> >>0.20.2 based.
> >>
> >>I wonder if anyone here have a magic to dump the hadoop configuration;
> >>doesn't need to be json
> >>as long as i can check if what i changed in configuration file is really
> >>kicked in.
> >>
> >>PS, i change this "mapred.user.jobconf.limit"
> >>
> >>-P
> >>This e-mail message may contain privileged and/or confidential
> information, and is intended to be received only by persons entitled
> >>to receive such information. If you have received this e-mail in error,
> please notify the sender immediately. Please delete it and
> >>all attachments from any servers, hard drives or any other media. Other
> use of this e-mail by you is strictly prohibited.
> >>
> >>All e-mails and attachments sent and received are subject to monitoring,
> reading and archival by Monsanto, including its
> >>subsidiaries. The recipient of this e-mail is solely responsible for
> checking for the presence of "Viruses" or other "Malware".
> >>Monsanto, along with its subsidiaries, accepts no liability for any
> damage caused by any such code transmitted by or accompanying
> >>this e-mail or any attachment.
> >>
> >>
> >>The information contained in this email may be subject to the export
> control laws and regulations of the United States, potentially
> >>including but not limited to the Export Administration Regulations (EAR)
> and sanctions regulations issued by the U.S. Department of
> >>Treasury, Office of Foreign Asset Controls (OFAC).  As a recipient of
> this information you are obligated to comply with all
> >>applicable U.S. export laws and regulations.
> >>
> >>
> >>
> >>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message