[
https://issues.apache.org/jira/browse/HDFS-10409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15316716#comment-15316716
]
Hadoop QA commented on HDFS-10409:
----------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s
{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} docker {color} | {color:red} 3m 59s
{color} | {color:red} Docker failed to build yetus/hadoop:0cf5e66. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12808417/HDFS-10409.HDFS-8707.000.patch
|
| JIRA Issue | HDFS-10409 |
| Console output |
https://builds.apache.org/job/PreCommit-HDFS-Build/15662/console |
| Powered by | Apache Yetus 0.3.0 http://yetus.apache.org |
This message was automatically generated.
> libhdfs++: Something is holding connection_state_lock in RpcConnectionImpl
> destructor
> -------------------------------------------------------------------------------------
>
> Key: HDFS-10409
> URL: https://issues.apache.org/jira/browse/HDFS-10409
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: James Clampffer
> Assignee: James Clampffer
> Attachments: HDFS-10409.HDFS-8707.000.patch, locked_dtor.patch
>
>
> The destructor to RpcConnectionImpl grabs a lock using a std::lock_guard<>.
> It turns out something is already holding the lock when this happens. Best
> bet is something that looks like:
> {code}
> void SomeFunctionThatShouldntTakeLock(){
> std::lock_guard<std::mutex> bad(connection_state_lock_)
> conn_.reset(); //conn is a shared_ptr to RpcConnectionImpl
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
