You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flume.apache.org by "Mark Thomas (JIRA)" <ji...@apache.org> on 2011/08/01 22:39:09 UTC

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

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

Mark Thomas commented on FLUME-1:
---------------------------------

Note that the ASF infra team is in the process of importing the existing FLUME issues. This import will over-write this issue and it will need to be re-created.

> Flume requires restart after HBase goes down
> --------------------------------------------
>
>                 Key: FLUME-1
>                 URL: https://issues.apache.org/jira/browse/FLUME-1
>             Project: Flume
>          Issue Type: Bug
>            Reporter: Otis Gospodnetic
>
> 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