[jira] [Commented] (FLUME-685) Flume requires restart after HBase goes down

["Otis Gospodnetic (JIRA)" <ji...@apache.org>]

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

Otis Gospodnetic commented on FLUME-685:
----------------------------------------

This looks nice and simple to me.  Is it OK to have the retry time be hard-coded to 60 seconds or can one override that somehow?

> Flume requires restart after HBase goes down

> ---------------------------------------------
>
>                 Key: FLUME-685
>                 URL: https://issues.apache.org/jira/browse/FLUME-685
>             Project: Flume
>          Issue Type: Bug
>    Affects Versions: v0.9.3
>            Reporter: Otis Gospodnetic
>         Attachments: FLUME-685.patch, FLUME-685.patch, FLUME-685.patch
>
>
> As mentioned in https://groups.google.com/a/cloudera.org/group/flume-user/browse_thread/thread/9e3739a6267c8d35 , we've observed that when HBase goes down and is restarted, one or more Flume processes need to be restarted, too, in order for Flume's HBase sink (the attr one) to resume sending data to HBase. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira