Created 07-25-2022 05:05 AM
Hey Team ,
i am using DAS most of the time its very slow , i would like to know how i will find App_Id application_1654575913119_3886895 From hive_20220725051805_76a0f15d-c15f-4c90-b73f-eb8e6bc1c4c1 Hive Query
i have Hive_Query_id want to find App_Id
Hive_Query_id :- hive_20220725051805_76a0f15d-c15f-4c90-b73f-eb8e6bc1c4c1
App_Id :-application_1654575913119_3886895
Thanks
Imran Chaush
Created 07-25-2022 07:52 AM
AppId should be logged in client console/logs, please see the following example:
INFO : Executing command(queryId=hive_20220725071031_107b4076-21e0-4da0-8cdd-d6c9e34c15de): <<query>>
...
INFO : Status: Running (Executing on YARN cluster with App id application_1658422185646_0004)
Otherwise HS2 logs should help to find the AppId.
Following the execution thread of the queryId to find the corresponding AppId, please see following example.
2022-07-25 07:10:32,112 INFO org.apache.hadoop.hive.ql.Driver: [HiveServer2-Background-Pool: Thread-123456]: Executing command(queryId=hive_20220725071031_107b4076-21e0-4da0-8cdd-d6c9e34c15de): <<query>>
2022-07-25 07:10:32,196 INFO org.apache.tez.client.TezClient: [HiveServer2-Background-Pool: Thread-123456]: Submitting dag to TezSession, sessionName=HIVE-xxxx, applicationId=application_1658422185646_0004, dagName=<<query>>) (Stage-1), callerContext={ context=HIVE, callerType=HIVE_QUERY_ID, callerId=hive_20220725071031_107b4076-21e0-4da0-8cdd-d6c9e34c15de }
Created 07-25-2022 11:47 PM
Hi ,
So the application id which comes before the dagName, is the correct application id which we searching for the executing Thread Id.
Regards,
Sivakumar.S
Created 07-28-2022 10:41 PM
@Imran_chaush, did any of the replies helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.
Regards,
Vidya Sargur,Created 07-29-2022 01:11 AM
Not Yet