[ https://issues.apache.org/jira/browse/HADOOP-14222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15939026#comment-15939026 ]
Steve Loughran edited comment on HADOOP-14222 at 3/24/17 10:52 AM: ------------------------------------------------------------------- + to be precise, this is about a closed connection. We can also raise it in all checks for input/output streams being open This means we could all it something like ConnectionClosedException. There's already a SocketClosedException of course. was (Author: ste...@apache.org): + to be precise, this is about a closed connection. We can also raise it in all checks for input/output streams being open > Create specialized IOException subclass to represent closed filesystem > ---------------------------------------------------------------------- > > Key: HADOOP-14222 > URL: https://issues.apache.org/jira/browse/HADOOP-14222 > Project: Hadoop Common > Issue Type: Improvement > Reporter: Ted Yu > Labels: newbie > > I was working on HBASE-17287 where hbase master didn't recognize that file > system had closed due to extended unavailability of hdfs. > Chatting with [~steve_l], he suggested creating IOException subclass to > represent closed filesystem so that downstream projects don't have to rely on > the specific exception message. > The string in existing exception message can't be changed. > We should add clear comment around that part to avoid breakage. -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org