My bad. Looks like the thrift server is cycling through various AMs it
started when the thrift server was started. I think this is different from
either Hive 2.0.1 or LLAP.

On Mon, Mar 27, 2017 at 11:38 PM, Premal Shah <premal.j.s...@gmail.com>
wrote:

> Hi,
> I have a thrift server to run queries using LLAP. There is script
> connecting to this thrift server and running queries back to back. I am
> tailing the thrift server logs and looks like every query is being run by a
> new application master, which is adding overhead. Is there a reason, the
> same App Master is not to run multiple queries. This does not happen when
> not using LLAP ie. the same AM runs multiple queries. Is there a setting
> I'm missing or is this expected behavior.
>
> Hive 2.1.1 and Hadoop 2.7.2
>
>
> Also, the application ids are out of order as you can see from the bolded
> text.
>
>
>
> Query ID = hadoop_20170328052835_09ba338e-cc63-4d6f-a5d0-9c8e43548d1a
> Total jobs = 1
> Launching Job 1 out of 1
>
>
> Status: Running (Executing on YARN cluster with App id
> *application_1490656022550_0893*)
>
> ------------------------------------------------------------
> ----------------------------------
>         VERTICES      MODE        STATUS  TOTAL  COMPLETED  RUNNING
>  PENDING  FAILED  KILLED
> ------------------------------------------------------------
> ----------------------------------
> Map 1 ..........      llap     SUCCEEDED     26         26        0
>  0       0       0
> Reducer 2 ......      llap     SUCCEEDED      1          1        0
>  0       0       0
> ------------------------------------------------------------
> ----------------------------------
> VERTICES: 02/02  [==========================>>] 100%  ELAPSED TIME: 8.76
> s
> ------------------------------------------------------------
> ----------------------------------
> OK
> Query ID = hadoop_20170328053107_b769a605-08ae-48d1-baa8-39096fdad17d
> Total jobs = 1
> Launching Job 1 out of 1
>
> Status: Running (Executing on YARN cluster with App id
> *application_1490656022550_0863*)
>
> ------------------------------------------------------------
> ----------------------------------
>         VERTICES      MODE        STATUS  TOTAL  COMPLETED  RUNNING
>  PENDING  FAILED  KILLED
> ------------------------------------------------------------
> ----------------------------------
> Map 1 ..........      llap     SUCCEEDED     26         26        0
>  0       0       0
> Reducer 2 ......      llap     SUCCEEDED      1          1        0
>  0       0       0
> ------------------------------------------------------------
> ----------------------------------
> VERTICES: 02/02  [==========================>>] 100%  ELAPSED TIME: 33.33
> s
> ------------------------------------------------------------
> ----------------------------------
> OK
> Query ID = hadoop_20170328053142_a23de218-2812-41ef-8419-02aaaf2b9dab
> Total jobs = 1
> Launching Job 1 out of 1
>
>
> Status: Running (Executing on YARN cluster with App id
> *application_1490656022550_0865*)
>
> ------------------------------------------------------------
> ----------------------------------
>         VERTICES      MODE        STATUS  TOTAL  COMPLETED  RUNNING
>  PENDING  FAILED  KILLED
> ------------------------------------------------------------
> ----------------------------------
> Map 1 ..........      llap     SUCCEEDED     26         26        0
>  0       0       0
> Reducer 2 ......      llap     SUCCEEDED      1          1        0
>  0       0       0
> ------------------------------------------------------------
> ----------------------------------
> VERTICES: 02/02  [==========================>>] 100%  ELAPSED TIME: 8.49
> s
> ------------------------------------------------------------
> ----------------------------------
> OK
> Query ID = hadoop_20170328053153_8677d9d6-e748-4eb7-bfeb-1f1abdbb367c
> Total jobs = 1
> Launching Job 1 out of 1
>
>
> --
> Regards,
> Premal Shah.
>



-- 
Regards,
Premal Shah.

Reply via email to