[ https://issues.apache.org/jira/browse/HDFS-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974016#action_12974016
]
Amit Nithian commented on HDFS-1542:
------------------------------------
How can I verify that latter condition? (DN in the pipeline being inaccessible)? I restarted
the cluster in case but is there some simple checks. I am curious if this bug has always been
in the source code or if this was recently introduced?
> Deadlock in Configuration.writeXml when serialized form is larger than one DFS block
> ------------------------------------------------------------------------------------
>
> Key: HDFS-1542
> URL: https://issues.apache.org/jira/browse/HDFS-1542
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs client
> Affects Versions: 0.20.2, 0.22.0, 0.23.0
> Reporter: Todd Lipcon
> Priority: Critical
> Attachments: deadlock.txt, Test.java
>
>
> Configuration.writeXml holds a lock on itself and then writes the XML to an output stream,
during which DFSOutputStream will try to get a lock on ackQueue/dataQueue. Meanwihle the DataStreamer
thread will call functions like conf.getInt() and deadlock against the other thread, since
it could be the same conf object.
> This causes a deterministic deadlock whenever the serialized form is larger than block
size.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
|