hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiaobing Zhou (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18078) [C++] Harden RPC by handling various communication abnormalities
Date Sat, 05 Aug 2017 00:42:03 GMT

    [ https://issues.apache.org/jira/browse/HBASE-18078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16115168#comment-16115168

Xiaobing Zhou commented on HBASE-18078:

Posted v9:
# added fault injection infra, see also RpcFaultInjector and RpcClientFaultInjector
# inject fault to close pipeline in ClientDispatcher::operator() to simulate the scenario
to get AsyncSocketException after creating connection and before sending request
# added unit test

AsyncSocketException is expected, however, Broken promise for type unique_ptr<Response>
is returned, will debug into this.

> [C++] Harden RPC by handling various communication abnormalities
> ----------------------------------------------------------------
>                 Key: HBASE-18078
>                 URL: https://issues.apache.org/jira/browse/HBASE-18078
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Xiaobing Zhou
>            Assignee: Xiaobing Zhou
>         Attachments: HBASE-18078.000.patch, HBASE-18078.001.patch, HBASE-18078.002.patch,
HBASE-18078.003.patch, HBASE-18078.004.patch, HBASE-18078.005.patch, HBASE-18078.006.patch,
HBASE-18078.007.patch, HBASE-18078.008.patch, HBASE-18078.009.patch
> RPC layer should handle various communication abnormalities (e.g. connection timeout,
server aborted connection, and so on). Ideally, the corresponding exceptions should be raised
and propagated through handlers of pipeline in client.

This message was sent by Atlassian JIRA

View raw message