[
https://issues.apache.org/jira/browse/HDFS-7358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14204987#comment-14204987
]
stack commented on HDFS-7358:
-----------------------------
In hbase we do 16k dfs.bytes-per-checksum Thanks for filing the 64k issue. I
was going to ask. Instead let me dig and try and add findings to new issue.
I tried the patch on my little rig and it works; no more getting stuck.
We need all this new synchronization on Packet? Any chance of instead tracing
to figure where a Packet might be referenced (and we'd go writeData to the
released internal buf) after its been closed? (Is this how you fixed
TestHFlush?)
nit: rename setClosed to close if you end up making a new patch.
> 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,
> h7358_20141105.patch, h7358_20141106.patch, h7358_20141107.patch,
> h7358_20141108.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)
