[
https://issues.apache.org/jira/browse/FLUME-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287143#comment-13287143
]
Juhani Connolly edited comment on FLUME-1246 at 6/1/12 4:30 AM:
----------------------------------------------------------------
That log is from yesterday before I pulled the new patches. The lack of a start
is happening with the following conf(no need for the completely irrelevant
timestamp for this test):
test.channels.ch1.type = file
test.channels.ch1.checkpointDir =
/home/share/juhani_connolly/flume-1.2.0-incubating-SNAPSHOT/check
test.channels.ch1.dataDirs =
/home/share/juhani_connolly/flume-1.2.0-incubating-SNAPSHOT/filechdata
test.sources.top.type = exec
test.sources.top.command = /usr/bin/top -b -d 1
test.sources.top.restart = true
test.sources.top.restartThrottle = 1000
test.sources.top.channels = ch1
test.sinks.log.type = logger
test.sinks.log.channel = ch1
test.channels = ch1
test.sources = top
test.sinks = log
I'm also attaching a new log
edit: the original problem is likely still there, it is just getting hidden by
the fact that now for some reason the channel is not even having start()
called(refer to flume.log20120601)
was (Author: juhanic):
That log is from yesterday before I pulled the new patches. The lack of a
start is happening with the following conf(no need for the completely
irrelevant timestamp for this test):
test.channels.ch1.type = file
test.channels.ch1.checkpointDir =
/home/share/juhani_connolly/flume-1.2.0-incubating-SNAPSHOT/check
test.channels.ch1.dataDirs =
/home/share/juhani_connolly/flume-1.2.0-incubating-SNAPSHOT/filechdata
test.sources.top.type = exec
test.sources.top.command = /usr/bin/top -b -d 1
test.sources.top.restart = true
test.sources.top.restartThrottle = 1000
test.sources.top.channels = ch1
test.sinks.log.type = logger
test.sinks.log.channel = ch1
test.channels = ch1
test.sources = top
test.sinks = log
I'm also attaching a new log
> FileChannel failing to start, also shutdown impossible without kill
> --------------------------------------------------------------------
>
> Key: FLUME-1246
> URL: https://issues.apache.org/jira/browse/FLUME-1246
> Project: Flume
> Issue Type: Bug
> Components: Channel
> Affects Versions: v1.2.0
> Environment: CentOS 5.4
> Reporter: Juhani Connolly
> Attachments: flume.log, flume.log, flume.log, flume.log.20120601,
> test_conf.conf
>
>
> Reduced to a minimal configuration for simplicity. I can recreate this on
> some machines, and not others. I wouldn't be surprised if it is some machines
> specific issue(test machines on CentOS5.4. On some it worked, others not),
> however whatever exception was thrown when attempting to get created is
> consumed and never passed onwards
> Config:
> test.channels.ch1.type = file
> test.channels.ch1.checkpointDir =
> /home/share/juhani_connolly/flume-1.2.0-incubating-SNAPSHOT/check
> test.channels.ch1.dataDirs =
> /home/share/juhani_connolly/flume-1.2.0-incubating-SNAPSHOT/filechdata
> test.sources.top.type = exec
> test.sources.top.command = /usr/bin top -b -d 1
> test.sources.top.restart = true
> test.sources.top.restartThrottle = 1000
> test.sources.top.interceptors = ts
> test.sources.top.interceptors.ts.type =
> org.apache.flume.interceptor.TimestampInterceptor$Builder
> test.sources.top.channels = ch1
> test.sinks.log.type = logger
> test.sinks.log.channel = ch1
> test.channels = ch1
> test.sources = top
> test.sinks = log
> attaching logs with general/lifecycle loglevel down to debug.
> A solution to this is probably going to be just improving error reporting.
> Another possibly more important element is that flume enters a state from
> which it cannot shutdown without kill -9. It looks like the Interrupts are
> getting swallowed up silently somewhere
--
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
