[
https://issues.apache.org/jira/browse/YARN-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14524337#comment-14524337
]
Li Lu commented on YARN-3407:
-----------------------------
Performance tuning for timeline v2 is a comprehensive problem. Instead of
fixing those default values one by one, I think we may want to address the big
problem as a whole, after we're reached into a stable phase for timeline v2.
Since this JIRA is only a small part of performance tuning and has been hanging
for more than a month, I'm proposing we close this JIRA as a won't fix.
> HttpServer2 Max threads in TimelineCollectorManager should be more than 10
> --------------------------------------------------------------------------
>
> Key: YARN-3407
> URL: https://issues.apache.org/jira/browse/YARN-3407
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Affects Versions: YARN-2928
> Reporter: Varun Saxena
> Assignee: Varun Saxena
>
> Currently TimelineCollectorManager sets HttpServer2.HTTP_MAX_THREADS to just
> 10. This value might be too less for serving put requests. By default
> HttpServer2 will have max threads value of 250. We can probably make it
> configurable too so that an optimum value can be configured based on number
> of requests coming to server. Thoughts ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
