hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Payne (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-9945) Datanode command for evicting writers
Date Thu, 07 Apr 2016 12:48:25 GMT

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

Eric Payne updated HDFS-9945:
-----------------------------
       Resolution: Fixed
    Fix Version/s: 2.8.0
           Status: Resolved  (was: Patch Available)

> Datanode command for evicting writers
> -------------------------------------
>
>                 Key: HDFS-9945
>                 URL: https://issues.apache.org/jira/browse/HDFS-9945
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>          Components: datanode
>            Reporter: Kihwal Lee
>            Assignee: Kihwal Lee
>             Fix For: 2.8.0
>
>         Attachments: HDFS-9945.patch, HDFS-9945.v2.patch
>
>
> It will be useful if there is a command to evict writers from a datanode. When a set
of datanodes are being decommissioned, they can get blocked by slow writers at the end.  It
was rare in the old days since mapred jobs didn't last too long, but with many different types
of apps running on today's YARN cluster, we are often see very long tail in datanode decommissioning.
> I propose a new dfsadmin command, {{evictWriters}}, to be added. I initially thought
about having namenode automatically telling datanodes on decommissioning, but realized that
having a command is more flexible. E.g. users can choose not to do this at all, choose when
to evict writers, or whether to try multiple times for whatever reasons.



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

Mime
View raw message