hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Wang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8771) If IPCLoggerChannel#purgeLogsOlderThan takes too long, Namenode could not send another RPC calls to Journalnodes
Date Tue, 06 Oct 2015 00:29:26 GMT

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

Andrew Wang commented on HDFS-8771:
-----------------------------------

Other note is that we probably should update javadoc in LogsPurgeable and elsewhere to indicate
that this is now best-effort and async, depending on the implementation.

> If IPCLoggerChannel#purgeLogsOlderThan takes too long, Namenode could not send another
RPC calls to Journalnodes
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-8771
>                 URL: https://issues.apache.org/jira/browse/HDFS-8771
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Takuya Fukudome
>            Assignee: Kanaka Kumar Avvaru
>         Attachments: HDFS-8771-01.patch, HDFS-8771-02.patch, HDFS-8771-03.patch
>
>
> In our cluster, edits has became huge(about 50GB) accidentally and our Jounalnodes' disks
were busy, therefore {{purgeLogsOlderThan}} took more than 30secs. If {{IPCLoggerChannel#purgeLogsOlderThan}}
takes too much time, Namenode couldn't send other RPC calls to Journalnodes because {{o.a.h.hdfs.qjournal.client.IPCLoggerChannel}}'s
executor is single thread. It will cause namenode shutting down.
> I think IPCLoggerChannel#purgeLogsOlderThan should not block other RPC calls like sendEdits.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message