I confirm : I just tried hive.server2.idle.operation.timeout setting it to -60 (seconds), but my veeeeeery slow job have not been killed. The issue here is "what if another user come and try to submit a MapReduce job but the cluster is stuck in an infinite loop ?".
Do you or anyone else have another idea ? Thanks, Loïc Loïc CHANEL Engineering student at TELECOM Nancy Trainee at Worldline - Villeurbanne 2015-07-29 15:34 GMT+02:00 Loïc Chanel <loic.cha...@telecomnancy.net>: > No, because I thought the idea of infinite operation was not very > compatible with the "idle" word (as the operation will not stop running), > but I'll try :-) > Thanks for the idea, > > > Loïc > > Loïc CHANEL > Engineering student at TELECOM Nancy > Trainee at Worldline - Villeurbanne > > 2015-07-29 15:27 GMT+02:00 Xuefu Zhang <xzh...@cloudera.com>: > >> Have you tried hive.server2.idle.operation.timeout? >> >> --Xuefu >> >> On Wed, Jul 29, 2015 at 5:52 AM, Loïc Chanel < >> loic.cha...@telecomnancy.net> wrote: >> >>> Hi all, >>> >>> As I'm trying to build a secured and multi-tenant Hadoop cluster with >>> Hive, I am desperately trying to set a timeout to Hive requests. >>> My idea is that some users can make mistakes such as a join with wrong >>> keys, and therefore start an infinite loop believing that they are just >>> launching a very heavy job. Therefore, I'd like to set a limit to the time >>> a request should take, in order to kill the job automatically if it exceeds >>> it. >>> >>> As such a notion cannot be set directly in YARN, I saw that MapReduce2 >>> provides with its own native timeout property, and I would like to know if >>> Hive provides with the same property someway. >>> >>> Did anyone heard about such a thing ? >>> >>> Thanks in advance for your help, >>> >>> >>> Loïc >>> >>> Loïc CHANEL >>> Engineering student at TELECOM Nancy >>> Trainee at Worldline - Villeurbanne >>> >> >> >
