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

Hudson commented on HDFS-14276:
-------------------------------

FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #17163 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/17163/])
HDFS-14276. [SBN read] Reduce tailing overhead. Contributed by Wei-Chiu 
(ayushsaxena: rev 0f598aed13d0fc55908bab3f1653f20084153299)
* (edit) 
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestNameNodeMXBean.java
* (edit) 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/ha/EditLogTailer.java


> [SBN read] Reduce tailing overhead
> ----------------------------------
>
>                 Key: HDFS-14276
>                 URL: https://issues.apache.org/jira/browse/HDFS-14276
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: ha, namenode
>    Affects Versions: 3.3.0
>         Environment: Hardware: 4-node cluster, each node has 4 core, Xeon 
> 2.5Ghz, 25GB memory.
> Software: CentOS 7.4, CDH 6.0 + Consistent Reads from Standby, Kerberos, SSL, 
> RPC encryption + Data Transfer Encryption.
>            Reporter: Wei-Chiu Chuang
>            Assignee: Ayush Saxena
>            Priority: Major
>             Fix For: 3.3.0
>
>         Attachments: HDFS-14276-01.patch, HDFS-14276.000.patch, Screen Shot 
> 2019-02-12 at 10.51.41 PM.png, Screen Shot 2019-02-14 at 11.50.37 AM.png
>
>
> When Observer setsĀ {{dfs.ha.tail-edits.period}} = {{0ms}}, it tails edit log 
> continuously in order to fetch the latest edits, but there is a lot of 
> overhead in doing so.
> Critically, edit log tailer should _not_ update NameDirSize metric every 
> time. It has nothing to do with fetching edits, and it involves lots of 
> directory space calculation.
> Profiler suggests a non-trivial chunk of time is spent for nothing.
> Other than this, the biggest overhead is in the communication to 
> serialize/deserialize messages to/from JNs. I am looking for ways to reduce 
> the cost because it's burning 30% of my CPU time even when the cluster is 
> idle.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

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

Reply via email to