You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "James Clampffer (JIRA)" <ji...@apache.org> on 2017/05/04 20:25:04 UTC

[jira] [Created] (HDFS-11758) libhdfs++: Catch exceptions thrown by runtime hooks

James Clampffer created HDFS-11758:
--------------------------------------

             Summary: libhdfs++: Catch exceptions thrown by runtime hooks
                 Key: HDFS-11758
                 URL: https://issues.apache.org/jira/browse/HDFS-11758
             Project: Hadoop HDFS
          Issue Type: Sub-task
            Reporter: James Clampffer
            Assignee: James Clampffer


Right now there's nothing to stop a user supplied event callback from throwing and unwinding the stack on the asio worker thread.  This can lead to async filesystem operations that never complete because the stack was unwound before setting up the next async io call.

Best practice is to be really careful about what is done inside event hooks and callbacks: don't throw, sleep, or anything else that might block.  I've seen a few issues pop up because a hook was made for monitoring purposes and later on stuff that was able to throw was added without realizing where the exception may end up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org