Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 3 Mar 2016 15:40:18 +0000 (UTC)
From: "James Clampffer (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12933917.1453750916000.209326.1457019618113@Atlassian.JIRA>
In-Reply-To: <JIRA.12933917.1453750916000@Atlassian.JIRA>
References: <JIRA.12933917.1453750916000@Atlassian.JIRA>
 <JIRA.12933917.1453750916083@arcas>
Subject: [jira] [Commented] (HDFS-9699) libhdfs++: Add appropriate catch
 blocks for ASIO operations that throw
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-9699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177971#comment-15177971 ] 

James Clampffer commented on HDFS-9699:
---------------------------------------

Committed this to HDFS-8707.

> libhdfs++: Add appropriate catch blocks for ASIO operations that throw
> ----------------------------------------------------------------------
>
>                 Key: HDFS-9699
>                 URL: https://issues.apache.org/jira/browse/HDFS-9699
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: hdfs-client
>            Reporter: James Clampffer
>            Assignee: Bob Hansen
>         Attachments: HDFS-6966.HDFS-8707.000.patch, HDFS-9699.HDFS-8707.001.patch, HDFS-9699.HDFS-8707.002.patch, cancel_backtrace.txt
>
>
> libhdfs++ doesn't create exceptions of its own but it should be able to gracefully handle exceptions thrown by libraries it uses, particularly asio.
> libhdfs++ should be able to catch most exceptions within reason either at the call site or in the code that spins up asio worker threads.  Certain system exceptions like std::bad_alloc don't need to be caught because by that point the process is likely in a unrecoverable state.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)