[
https://issues.apache.org/jira/browse/YARN-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14383494#comment-14383494
]
Varun Saxena commented on YARN-3047:
------------------------------------
[~gtCarrera], the threads I am talking about in the design doc are the
HttpServer2 threads. HttpServer2 has a thread pool and it will launch multiple
threads to process requests. And hence our REST calls will also be in parallel.
The thread pool in HttpServer2 works like this.
If an idle thread is available a job, it is directly dispatched, otherwise the
job is queued. After queuing a job, if the total number of threads is less
than the maximum pool size, a new thread is spawned.
This is what I was talking about in the doc. Am I missing something ?
> [Data Serving] Set up ATS reader with basic request serving structure and
> lifecycle
> -----------------------------------------------------------------------------------
>
> Key: YARN-3047
> URL: https://issues.apache.org/jira/browse/YARN-3047
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Sangjin Lee
> Assignee: Varun Saxena
> Attachments: Timeline_Reader(draft).pdf, YARN-3047.001.patch,
> YARN-3047.003.patch, YARN-3047.005.patch, YARN-3047.02.patch,
> YARN-3047.04.patch
>
>
> Per design in YARN-2938, set up the ATS reader as a service and implement the
> basic structure as a service. It includes lifecycle management, request
> serving, and so on.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
