[ 
https://issues.apache.org/jira/browse/HADOOP-17861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18040992#comment-18040992
 ] 

ASF GitHub Bot commented on HADOOP-17861:
-----------------------------------------

eubnara opened a new pull request, #8106:
URL: https://github.com/apache/hadoop/pull/8106

   <!--
     Thanks for sending a pull request!
       1. If this is your first time, please read our contributor guidelines: 
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
       2. Make sure your PR title starts with JIRA issue id, e.g., 
'HADOOP-17799. Your PR title ...'.
   -->
   
   ### Description of PR
   
   There are some points to improve the performance of YARN Registry DNS Server.
   
   - Do not print unnecessary logs (It just needs change log4j.properties)
     - log4j.logger.org.apache.hadoop.registry.server.dns=WARN
   - Change some loglevels at points which can affect performance degradation.
   - Use "newFixedThreadPool" instead of "newCachedThreadPool" to prevent OOM
   - Use Blocking on TCP handler. Using non-blocking and sleeping some 
time("Thread.sleep(500)") is meaningless.
   
   In our environment, QPS of original yarn dns server is about 5000 (UDP), 100 
(TCP).
   Now, QPS of our improved yarn dns server is about 47000 (UDP), 500 (TCP).
   
   
   I will make a pull request at https://github.com/apache/hadoop soon.
   
   
   
   
   ### How was this patch tested?
   
   Our team members have tested this manually in our cluster.
   
   
   
   ### For code changes:
   
   - [x] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [ ] Object storage: have the integration tests been executed and the 
endpoint declared according to the connector-specific documentation?
   - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   




> improve YARN Registry DNS Server qps
> ------------------------------------
>
>                 Key: HADOOP-17861
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17861
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: registry
>    Affects Versions: 3.1.2
>            Reporter: YUBI LEE
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> There are some points to improve the performance of YARN Registry DNS Server.
> - Do not print unnecessary logs (It just needs change log4j.properties)
> -- log4j.logger.org.apache.hadoop.registry.server.dns=WARN
> - Change some loglevels at points which can affect performance degradation.
> - Use "newFixedThreadPool" instead of "newCachedThreadPool" to prevent OOM
> - Use Blocking on TCP handler. Using non-blocking and sleeping some 
> time("Thread.sleep(500)") is meaningless.
> In our environment, QPS of original yarn dns server is about 5000 (UDP), 100 
> (TCP).
> Now, QPS of our improved yarn dns server is about 47000 (UDP), 500 (TCP).
> I will make a pull request at https://github.com/apache/hadoop soon.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to