[
https://issues.apache.org/jira/browse/HDFS-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14146575#comment-14146575
]
Colin Patrick McCabe commented on HDFS-6877:
--------------------------------------------
bq. I anticipated a behavior that the application is writing the block in very
slow speed. For instance, a light traffic service opens a log file and only
appends 10KB logs after waking up for every 30 seconds? Or some applications
that dump immediate results (e.g., 1MB) after every 10 minutes? In such cases,
the BlockReceiver thread can live for a long time, until the block is full and
then be closed.
I'm sorry, but your understanding is not correct. The BlockReceiver processes
messages of about 64kb. If the DFSOutputStream doesn't have enough to send a
message, no message is sent. It doesn't matter how slow the client is, the
BlockReceiver will be fast.
So please get rid of this interruption stuff.
> Avoid calling checkDisk and stop active BlockReceiver thread when an HDFS
> volume is removed during a write.
> -----------------------------------------------------------------------------------------------------------
>
> Key: HDFS-6877
> URL: https://issues.apache.org/jira/browse/HDFS-6877
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: datanode
> Affects Versions: 2.5.0
> Reporter: Lei (Eddy) Xu
> Assignee: Lei (Eddy) Xu
> Attachments: HDFS-6877.000.consolidate.txt,
> HDFS-6877.000.delta-HDFS-6727.txt, HDFS-6877.001.combo.txt,
> HDFS-6877.001.patch, HDFS-6877.002.patch, HDFS-6877.003.patch,
> HDFS-6877.004.patch, HDFS-6877.005.patch
>
>
> Avoid calling checkDisk and stop active BlockReceiver thread when an HDFS
> volume is removed during a write.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
