hey guys, this is a long shot but i'll ask anyway. We're running YARN and HiveServer2 (v2.1.0) and noticing "random" kills - what looks to me - being issued by HiveServer2.
we've turned DEBUG log level on for the Application Master container and see the following in the logs: 2016-10-05 02:06:18,365 DEBUG [IPC Server handler 0 on 34013] org.apache.hadoop.ipc.Server: IPC Server handler 0 on 34013: *org.apache.hadoop.mapreduce.v2.api.MRClientProtocolPB.killJob from 172.19.75.137:35616 <http://172.19.75.137:35616>* Call#6603343 Retry#0 for RpcKind RPC_PROTOCOL_BUFFER 2016-10-05 02:06:18,365 DEBUG [IPC Server handler 0 on 34013] org.apache.hadoop.security.UserGroupInformation: PrivilegedAction as:dwr (auth:SIMPLE) from:org.apache.hadoop.ipc.Server$Handler.run(Server.java:2038) 2016-10-05 02:06:18,368 INFO [IPC Server handler 0 on 34013] org.apache.hadoop.mapreduce.v2.app.client.MRClientService: Kill job job_1475268554936_14906 received from dwr (auth:SIMPLE) at 172.19.75.137 host 172.19.75.137 is where the HiveServer2 process is running. i'm not seeing anything in the HiveServer2 logs at all that is related to this job. that's whole 'nother problem. also rerunning the M/R job works fine. so its very weird why out of the blue HS2 would issue a KILL. this happens three or four times every day with random jobs. Any thoughts greatly appreciated. Cheers, Stephen.
