hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kanaka Kumar Avvaru (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-8771) If IPCLoggerChannel#purgeLogsOlderThan takes too long, Namenode could not send another RPC calls to Journalnodes
Date Wed, 16 Sep 2015 12:55:46 GMT

     [ https://issues.apache.org/jira/browse/HDFS-8771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kanaka Kumar Avvaru updated HDFS-8771:
--------------------------------------
    Attachment: HDFS-8771-03.patch

> 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