Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-user@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of uclamathguy@gmail.com
 designates 209.85.160.50 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=gaOYG5nJ5lis3Ov/B3TsrVUwsCFr7s9EmbDyRCt1qNeMFVhTK6iD/wEx+FATheZ3r9
         Aj2eX4RVBqJkgV63ukXeWP4MbLErA4nVpR2PPLWCueOSGBCsnOUKmfEYKn4v1e12ulyM
         4Eo0Tzjpy893jLDQnhOQecskqRk/i7tiz8iwE=
MIME-Version: 1.0
In-Reply-To: <C70B086C.26BC1%knoguchi@yahoo-inc.com>
References: <72fc09510910251200n799b3482hdde7aaf99213ba51@mail.gmail.com>
	 <C70B086C.26BC1%knoguchi@yahoo-inc.com>
Date: Mon, 26 Oct 2009 09:06:01 -0700
Message-ID: <72fc09510910260906r37dd3baxcb517d62cd1f1582@mail.gmail.com>
Subject: Re: Streaming ignoring stderr output
From: Ryan Rosario <uclamathguy@gmail.com>
To: common-user@hadoop.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Thanks. I think that I may have tripped on some sort of bug.
Unfortunately, I do not know how to reproduce it and am a bit scared
to try to reproduce it.

I got this to work. I changed the following things, and now my job
completes successfully with stderr written to the logs as output
occurs. What was happening before was that no output was being written
to the stderr logs until a map task completely finished.

-- used print >> sys.stderr, "blah blah" instead of
sys.stderr.write("blah blah")
-- used the reporter:  print >> sys.stderr, "reporter:status:My status message"
-- used only one large input file, rather than splitting the file into
n files. I thought that was required so I could force n mappers, but
apparently not.

I am not sure which one of the above solved the problem. Using
sys.stderr.write() without the reporting format worked for some time.
I don't know why.

- Ryan

On Mon, Oct 26, 2009 at 8:03 AM, Koji Noguchi <knoguchi@yahoo-inc.com> wrote:
> This doesn't solve your stderr/stdout problem, but you can always set the
> timeout to be a bigger value if necessary.
>
> -Dmapred.task.timeout=______ (in milliseconds)
>
> Koji
>
>
> On 10/25/09 12:00 PM, "Ryan Rosario" <uclamathguy@gmail.com> wrote:
>
>> I am using a Python script as a mapper for a Hadoop Streaming (hadoop
>> 0.20.0) job, with reducer NONE. My jobs keep getting killed with "task
>> failed to respond after 600 seconds." I tried sending a heartbeat
>> every minute to stderr using sys.stderr.write in my mapper, but
>> nothing is being output to stderr either on disk (in
>> logs/userlogs/...) or in the web UI. stdout is not even recorded.
>>
>> This also means I have no way of knowing what my tasks are doing at
>> any given moment except to look at the counts produced in syslog.
>>
>> I got it to work once, but have not had any luck since. Any
>> suggestions of things to look at as to why I am not able to get any
>> output? Help is greatly appreciated.
>>
>> - Ryan
>
>


-- 
RRR