[
https://issues.apache.org/jira/browse/HADOOP-5859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713307#action_12713307
]
Suresh Srinivas commented on HADOOP-5859:
-----------------------------------------
Comments on the latest patch:
# Can you add a comment where dataQueue and ackQueue are declared, that both
these data structures are synchronized on dataQueue object
# Can you retain the code formatting where you think the existing code is fine.
That makes the patch size smaller and applying patches to the changed code
easier.
# Move static variable to the beginning of the class {{DFSOutputStream}}
# {{maxRecoveryErrorCount}} should become static
# Do we need so many volatile variables. Can one thread flag close and the
DataStreamer does all the closing of internal variables
# As we discussed, in {{ResponseProcessor.run()}} add notify when exception is
caught
> FindBugs : fix "wait() or sleep() with locks held" warnings in hdfs
> -------------------------------------------------------------------
>
> Key: HADOOP-5859
> URL: https://issues.apache.org/jira/browse/HADOOP-5859
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Reporter: Kan Zhang
> Assignee: Kan Zhang
> Attachments: 5859-21.patch, 5859-22.patch, 5859-26.patch,
> 5859-4.patch, 5859-5.patch, 5859-8.patch
>
>
> This JIRA fixes the following warnings:
> SWL org.apache.hadoop.hdfs.DFSClient$DFSOutputStream.closeInternal() calls
> Thread.sleep() with a lock held
> TLW wait() with two locks held in
> org.apache.hadoop.hdfs.DFSClient$DFSOutputStream.flushInternal()
> TLW wait() with two locks held in
> org.apache.hadoop.hdfs.DFSClient$DFSOutputStream.flushInternal()
> TLW wait() with two locks held in
> org.apache.hadoop.hdfs.DFSClient$DFSOutputStream.writeChunk(byte[], int, int,
> byte[])
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
