hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bob Hansen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-10231) libhdfs++: Fix race conditions in RPC layer
Date Mon, 04 Apr 2016 15:57:25 GMT

     [ https://issues.apache.org/jira/browse/HDFS-10231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Bob Hansen updated HDFS-10231:
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Committed with c2e1e23d8ea9a6002c1aafe18f7e6e7e41bb3301

> libhdfs++: Fix race conditions in RPC layer
> -------------------------------------------
>                 Key: HDFS-10231
>                 URL: https://issues.apache.org/jira/browse/HDFS-10231
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: hdfs-client
>            Reporter: James Clampffer
>            Assignee: Bob Hansen
>         Attachments: HDFS-10231.HDFS-8707.000.patch, HDFS-10231.HDFS-8707.001.patch,
HDFS-10231.HDFS-8707.002.patch, HDFS-10231.HDFS-8707.003.patch
> Namenode calls seem to hang and the retry logic never properly kicks in.  It looks like
there's a race condition that leads to a failed rpc call never properly passing the request
object to the new RpcConnectionImpl so things hang forever.  RpcConnectionImpl objects are
also kept alive longer than they should because of a shared_ptr cycle between them and the
timeout tracking objects.

This message was sent by Atlassian JIRA

View raw message