You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Bessenyei Balázs Donát (JIRA)" <ji...@apache.org> on 2016/09/24 09:55:20 UTC
[jira] [Commented] (FLUME-2996) Flume process shutdown automaticly
[ https://issues.apache.org/jira/browse/FLUME-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15518792#comment-15518792 ]
Bessenyei Balázs Donát commented on FLUME-2996:
-----------------------------------------------
Hi [~hehailin],
Thank you for the bug report.
Can you please provide a little more information to help? (Such as your config file you are using, the environment you are trying to run Flume in, etc.)
Probably a few more lines from the log could be useful. (Any errors maybe?)
> Flume process shutdown automaticly
> ----------------------------------
>
> Key: FLUME-2996
> URL: https://issues.apache.org/jira/browse/FLUME-2996
> Project: Flume
> Issue Type: Bug
> Environment: Amazon Linux
> Reporter: hailin
>
> hi guys,
> I install flume from apache-flume-1.6.0-bin.tar.gz, and startup flume with some my custom configure file with cmd line like this:
> bin/flume-ng agent -Dflume.monitoring.type=http -Dflume.monitoring.port=41414 -c conf -f conf/flume.conf --name a1 -Dflume.root.logger=INFO,DAILY
> it works fine without any issue, but after several hours when I check the process, I found it was shutdown automaticly. Bellow is the flume log information:
> .....
> 24 Sep 2016 05:53:59,391 INFO [agent-shutdown-hook] (org.apache.flume.lifecycle.LifecycleSupervisor.stop:79) - Stopping lifecycle supervisor 10
> 24 Sep 2016 05:53:59,394 INFO [agent-shutdown-hook] (org.apache.flume.instrumentation.MonitoredCounterGroup.stop:150) - Component type: SINK, name: sink_kinesis_stream stopped
> 24 Sep 2016 05:53:59,394 INFO [agent-shutdown-hook] (org.apache.flume.instrumentation.MonitoredCounterGroup.stop:156) - Shutdown Metric for type: SINK, name: sink_kinesis_stream. sink.start.time == 1474685921906
> ....
> Can anyone help me fix it? How can I do to stop this issue as our bussiness already block because of this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)