hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anu Engineer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-11492) Ozone: Add the ability to handle sendContainerReport Command
Date Mon, 13 Mar 2017 17:08:41 GMT

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

Anu Engineer commented on HDFS-11492:

bq. Do you want to handle SCM commands in a new thread, or after heartbeat finished? 
Yes, you are right the plan is to queue the command and handle these commands in a different
thread. The number of commands may not be very huge, so we will have just one thread that
processes commands sequentially.

bq. Do you have any pattern design about this part? 
As I mentioned the current thought is to add a single thread. For example, in the case of
the sendContianerReport command, it will iterate through all containers which are closed and
send container reports for those containers.

> Ozone: Add the ability to handle sendContainerReport Command
> ------------------------------------------------------------
>                 Key: HDFS-11492
>                 URL: https://issues.apache.org/jira/browse/HDFS-11492
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ozone
>    Affects Versions: HDFS-7240
>            Reporter: Anu Engineer
>            Assignee: Anu Engineer
> Once a container report is ready datanodes sends that information to SCM. SCM returns
a command asking the data node to send container report. Add the ability to handle this command
on datanode side and send the actual container Report.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message