[
https://issues.apache.org/jira/browse/HDFS-7358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199282#comment-14199282
]
Tsz Wo Nicholas Sze commented on HDFS-7358:
-------------------------------------------
> ... grepping 'Waiting for ack' I see us skipping packet seqnos. See below.
> See doubled '8', '22', and '26'.
For all these case, the next seq numbers (i.e. 9, 23, 27) are missing. I guess
it the same as the seqno=43 case mentioned previously -- Client call flush().
At that time, bytesCurBlock==lastFlushOffset so that the packet is discarded
without being queued/sent. (I beg you won't see "Queued packet" for seq 9, 23
and 27.) Client will wait for the previous seq no. That why there are doubled
seq no shown in "Waiting for ack".
> Clients may get stuck waiting when using ByteArrayManager
> ---------------------------------------------------------
>
> Key: HDFS-7358
> URL: https://issues.apache.org/jira/browse/HDFS-7358
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs-client
> Reporter: Tsz Wo Nicholas Sze
> Assignee: Tsz Wo Nicholas Sze
> Attachments: h7358_20141104.patch, h7358_20141104_wait_timeout.patch
>
>
> [~stack] reported that clients might get stuck waiting when using
> ByteArrayManager; see [his
> comments|https://issues.apache.org/jira/browse/HDFS-7276?focusedCommentId=14197036&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14197036].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
