[prev in list] [next in list] [prev in thread] [next in thread] 

List:       flume-dev
Subject:    [jira] [Comment Edited] (FLUME-1246) FileChannel failing to  start, also shutdown impossible without
From:       "Hari Shreedharan (JIRA)" <jira () apache ! org>
Date:       2012-05-31 19:33:24
Message-ID: 1423364584.23369.1338492804344.JavaMail.jiratomcat () issues-vm
[Download RAW message or body]


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

Hari Shreedharan edited comment on FLUME-1246 at 5/31/12 7:32 PM:
------------------------------------------------------------------

Inder: The race condition issue was fixed in FLUME-1236. If you pull in the latest \
sources, you would not see the race condition between channel start and create \
transaction. The issue Juhani has documented here is different from that. I can see \
in his logs, the log messages added by the fix for FLUME-1236.

Will: Could you please post the full logs, on FLUME-1232 and add a comment there? It \
will be easier to track that way.

                
      was (Author: hshreedharan):
    Inder: The race condition issue was fixed in FLUME-1236. If you pull in the \
latest sources, you would not see the race condition between channel start and create \
transaction. 

Will: Could you please post the full logs, on FLUME-1232 and add a comment there? It \
will be easier to track that way.

                  
> 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
> 
> 
> 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

        


[prev in list] [next in list] [prev in thread] [next in thread]