You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "E. Sammer (Updated) (JIRA)" <ji...@apache.org> on 2011/10/31 00:01:32 UTC
[jira] [Updated] (FLUME-822) JDBC channel lock acquisition failure
during take()
[ https://issues.apache.org/jira/browse/FLUME-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
E. Sammer updated FLUME-822:
----------------------------
Description:
The jdbc channel implementation (using Derby) results in a lock acquisition error upon take().
It appears as if the event is successfully inserted by the source, but the sink fails to receive the event in the allotted time. The configuration used was as follows.
==
localhost.sources = avro nc
localhost.sinks = logger log2
localhost.channels = ch1 ch2
localhost.channels.ch1.type = memory
localhost.channels.ch1.capacity = 10000
localhost.sources.avro.type = avro
localhost.sources.avro.bind = 0.0.0.0
localhost.sources.avro.port = 41414
localhost.sources.avro.channels = ch1
localhost.sinks.logger.type = logger
localhost.sinks.logger.channel = ch1
#
localhost.channels.ch2.type = jdbc
localhost.sources.nc.type = netcat
localhost.sources.nc.bind = 0.0.0.0
localhost.sources.nc.port = 41415
localhost.sources.nc.name = nc
localhost.sources.nc.channels = ch2
localhost.sinks.log2.type = logger
localhost.sinks.log2.channel = ch2
==
The path in use is nc(netcat) -> ch2(jdbc) -> log2(logger) with minimal configuration. I'll attach log output shortly.
was:
The jdbc channel implementation (using Derby) results in a lock acquisition error upon take().
It appears as if the event is successfully inserted by the source, but the sink fails to receive the event in the allotted time. The configuration used was as follows.
{code}
localhost.sources = avro nc
localhost.sinks = logger log2
localhost.channels = ch1 ch2
localhost.channels.ch1.type = memory
localhost.channels.ch1.capacity = 10000
localhost.sources.avro.type = avro
localhost.sources.avro.bind = 0.0.0.0
localhost.sources.avro.port = 41414
localhost.sources.avro.channels = ch1
localhost.sinks.logger.type = logger
localhost.sinks.logger.channel = ch1
#
localhost.channels.ch2.type = jdbc
localhost.sources.nc.type = netcat
localhost.sources.nc.bind = 0.0.0.0
localhost.sources.nc.port = 41415
localhost.sources.nc.name = nc
localhost.sources.nc.channels = ch2
localhost.sinks.log2.type = logger
localhost.sinks.log2.channel = ch2
{code}
The path in use is nc(netcat) -> ch2(jdbc) -> log2(logger) with minimal configuration. I'll attach log output shortly.
> JDBC channel lock acquisition failure during take()
> ---------------------------------------------------
>
> Key: FLUME-822
> URL: https://issues.apache.org/jira/browse/FLUME-822
> Project: Flume
> Issue Type: Bug
> Affects Versions: NG alpha 1
> Reporter: E. Sammer
> Assignee: Arvind Prabhakar
> Priority: Blocker
> Fix For: NG alpha 2
>
>
> The jdbc channel implementation (using Derby) results in a lock acquisition error upon take().
> It appears as if the event is successfully inserted by the source, but the sink fails to receive the event in the allotted time. The configuration used was as follows.
> ==
> localhost.sources = avro nc
> localhost.sinks = logger log2
> localhost.channels = ch1 ch2
> localhost.channels.ch1.type = memory
> localhost.channels.ch1.capacity = 10000
> localhost.sources.avro.type = avro
> localhost.sources.avro.bind = 0.0.0.0
> localhost.sources.avro.port = 41414
> localhost.sources.avro.channels = ch1
> localhost.sinks.logger.type = logger
> localhost.sinks.logger.channel = ch1
> #
> localhost.channels.ch2.type = jdbc
> localhost.sources.nc.type = netcat
> localhost.sources.nc.bind = 0.0.0.0
> localhost.sources.nc.port = 41415
> localhost.sources.nc.name = nc
> localhost.sources.nc.channels = ch2
> localhost.sinks.log2.type = logger
> localhost.sinks.log2.channel = ch2
> ==
> The path in use is nc(netcat) -> ch2(jdbc) -> log2(logger) with minimal configuration. I'll attach log output shortly.
--
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