In yarn, JVM does not exit after processing one HDFS block. If another
block is being processed by same JVM, it is called setup() again?

I discovered that my setup() method needs 15 seconds to execute.

Assuming this is an MR (via MR2) job you speak of, have you
enabled/are you speaking of the Uber task feature? That may do this.

On Mon, Aug 6, 2012 at 3:23 AM, Radim Kolar <[EMAIL PROTECTED]> wrote:
> In yarn, JVM does not exit after processing one HDFS block. If another block
> is being processed by same JVM, it is called setup() again?
>
> I discovered that my setup() method needs 15 seconds to execute.

--
Harsh J