[
https://issues.apache.org/jira/browse/FLUME-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic updated FLUME-685:
-----------------------------------
Fix Version/s: v0.9.5
Summary: Flume requires restart after HBase goes down (was: Flume
requires restart after HBase goes down
)
> 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
> Fix For: v0.9.5
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
