Mailing-List: contact user-help@giraph.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@giraph.apache.org
Received-SPF: pass (athena.apache.org: domain of shaposhnik@gmail.com
 designates 209.85.214.177 as permitted sender)
MIME-Version: 1.0
Sender: shaposhnik@gmail.com
In-Reply-To: 
 <CAHuUK3VHVZ7qQFEnCc6--NS8d7bNWnyn6GVpr3OVL0+CMgY8Kw@mail.gmail.com>
References: 
 <CAHuUK3VHVZ7qQFEnCc6--NS8d7bNWnyn6GVpr3OVL0+CMgY8Kw@mail.gmail.com>
Date: Mon, 17 Feb 2014 17:07:04 -0800
Message-ID: 
 <CA+ULb+u5JXeZctaHUtes2D2Qu1CMNrojthHiHPHAcpPAoqfpVQ@mail.gmail.com>
Subject: Re: debugging graph-programs
From: Roman Shaposhnik <roman@shaposhnik.org>
To: user@giraph.apache.org
Content-Type: text/plain; charset=ISO-8859-1

I find running Giraph apps via hadoop's local execution mode
quite useful for debugging.

Thanks,
Roman.

On Mon, Feb 17, 2014 at 4:07 AM, Martin Neumann <mneumann@spotify.com> wrote:
> Hej,
>
> I find Giraph programs quite difficult to debug (all I have is log outputs).
> Anyone has some hints for debugging tools or coding practices to make it
> simpler?
>
> I'm using Giraph 1.1.0 trunk on YARN so I can't use Map/Reduce debugging
> aids (at least I think so, I haven't tried any)
>
> cheers
> Martin