You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Will McQueen (Created) (JIRA)" <ji...@apache.org> on 2012/02/28 00:15:49 UTC
[jira] [Created] (FLUME-1003) The memory channel does not seem to
respect the capacity
The memory channel does not seem to respect the capacity
--------------------------------------------------------
Key: FLUME-1003
URL: https://issues.apache.org/jira/browse/FLUME-1003
Project: Flume
Issue Type: Bug
Components: Channel
Affects Versions: v1.1.0
Environment: RHEL 6.2 64-bit
Reporter: Will McQueen
Fix For: v1.1.0
Use the following config (no sink configured)
a1.sources = r1
a1.channels = c1
a1.sources.r1.type = SEQ
a1.sources.r1.channels = c1
a1.channels.c1.type = MEMORY
If I run with this config, then the source and channel instance is created. If you add a print statement to ChannelProcessor.processEvent(), you'll see that the source is sending events to the channel. The source generates about 104 events, and then generates an additional one about every second... which is interesting, since the mem channel's default capacity is only 100 and there's no sink.
--
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
[jira] [Assigned] (FLUME-1003) The memory channel does not seem to
respect the capacity
Posted by "Juhani Connolly (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juhani Connolly reassigned FLUME-1003:
--------------------------------------
Assignee: Juhani Connolly
> The memory channel does not seem to respect the capacity
> --------------------------------------------------------
>
> Key: FLUME-1003
> URL: https://issues.apache.org/jira/browse/FLUME-1003
> Project: Flume
> Issue Type: Bug
> Components: Channel
> Affects Versions: v1.1.0
> Environment: RHEL 6.2 64-bit
> Reporter: Will McQueen
> Assignee: Juhani Connolly
> Fix For: v1.1.0
>
>
> Use the following config (no sink configured)
> a1.sources = r1
> a1.channels = c1
> a1.sources.r1.type = SEQ
> a1.sources.r1.channels = c1
> a1.channels.c1.type = MEMORY
> If I run with this config, then the source and channel instance is created. If you add a print statement to ChannelProcessor.processEvent(), you'll see that the source is sending events to the channel. The source generates about 104 events, and then generates an additional one about every second... which is interesting, since the mem channel's default capacity is only 100 and there's no sink.
--
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
[jira] [Updated] (FLUME-1003) The memory channel does not seem to
respect the capacity
Posted by "Mike Percy (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Percy updated FLUME-1003:
------------------------------
Fix Version/s: (was: v1.1.0)
> The memory channel does not seem to respect the capacity
> --------------------------------------------------------
>
> Key: FLUME-1003
> URL: https://issues.apache.org/jira/browse/FLUME-1003
> Project: Flume
> Issue Type: Bug
> Components: Channel
> Affects Versions: v1.1.0
> Environment: RHEL 6.2 64-bit
> Reporter: Will McQueen
> Assignee: Juhani Connolly
>
> Use the following config (no sink configured)
> a1.sources = r1
> a1.channels = c1
> a1.sources.r1.type = SEQ
> a1.sources.r1.channels = c1
> a1.channels.c1.type = MEMORY
> If I run with this config, then the source and channel instance is created. If you add a print statement to ChannelProcessor.processEvent(), you'll see that the source is sending events to the channel. The source generates about 104 events, and then generates an additional one about every second... which is interesting, since the mem channel's default capacity is only 100 and there's no sink.
--
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
[jira] [Resolved] (FLUME-1003) The memory channel does not seem to
respect the capacity
Posted by "Juhani Connolly (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juhani Connolly resolved FLUME-1003.
------------------------------------
Resolution: Not A Problem
Everything working as intended
> The memory channel does not seem to respect the capacity
> --------------------------------------------------------
>
> Key: FLUME-1003
> URL: https://issues.apache.org/jira/browse/FLUME-1003
> Project: Flume
> Issue Type: Bug
> Components: Channel
> Affects Versions: v1.1.0
> Environment: RHEL 6.2 64-bit
> Reporter: Will McQueen
> Assignee: Juhani Connolly
> Fix For: v1.1.0
>
>
> Use the following config (no sink configured)
> a1.sources = r1
> a1.channels = c1
> a1.sources.r1.type = SEQ
> a1.sources.r1.channels = c1
> a1.channels.c1.type = MEMORY
> If I run with this config, then the source and channel instance is created. If you add a print statement to ChannelProcessor.processEvent(), you'll see that the source is sending events to the channel. The source generates about 104 events, and then generates an additional one about every second... which is interesting, since the mem channel's default capacity is only 100 and there's no sink.
--
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
[jira] [Commented] (FLUME-1003) The memory channel does not seem to
respect the capacity
Posted by "Juhani Connolly (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13217757#comment-13217757 ]
Juhani Connolly commented on FLUME-1003:
----------------------------------------
Upon shutdown, the counters seem to show that everything is as it should be
2012-02-28 09:47:47,950 (node-shutdownHook) [INFO - org.apache.flume.source.SequenceGeneratorSource.stop(SequenceGeneratorSource.java:73)] Sequence generator source stopped. Metrics:{ name:null counters:{events.failed=23, events.successful=100} }
Note that 100 succesful, the rest have all failed. Seq source does nothing in the case of a channel exception other than to log it
> The memory channel does not seem to respect the capacity
> --------------------------------------------------------
>
> Key: FLUME-1003
> URL: https://issues.apache.org/jira/browse/FLUME-1003
> Project: Flume
> Issue Type: Bug
> Components: Channel
> Affects Versions: v1.1.0
> Environment: RHEL 6.2 64-bit
> Reporter: Will McQueen
> Assignee: Juhani Connolly
> Fix For: v1.1.0
>
>
> Use the following config (no sink configured)
> a1.sources = r1
> a1.channels = c1
> a1.sources.r1.type = SEQ
> a1.sources.r1.channels = c1
> a1.channels.c1.type = MEMORY
> If I run with this config, then the source and channel instance is created. If you add a print statement to ChannelProcessor.processEvent(), you'll see that the source is sending events to the channel. The source generates about 104 events, and then generates an additional one about every second... which is interesting, since the mem channel's default capacity is only 100 and there's no sink.
--
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
[jira] [Commented] (FLUME-1003) The memory channel does not seem to
respect the capacity
Posted by "Juhani Connolly (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13217742#comment-13217742 ]
Juhani Connolly commented on FLUME-1003:
----------------------------------------
I'll look into this and fix it if there's a bug, though I suspect that the memchannel is just refusing the puts beyond its limit
> The memory channel does not seem to respect the capacity
> --------------------------------------------------------
>
> Key: FLUME-1003
> URL: https://issues.apache.org/jira/browse/FLUME-1003
> Project: Flume
> Issue Type: Bug
> Components: Channel
> Affects Versions: v1.1.0
> Environment: RHEL 6.2 64-bit
> Reporter: Will McQueen
> Fix For: v1.1.0
>
>
> Use the following config (no sink configured)
> a1.sources = r1
> a1.channels = c1
> a1.sources.r1.type = SEQ
> a1.sources.r1.channels = c1
> a1.channels.c1.type = MEMORY
> If I run with this config, then the source and channel instance is created. If you add a print statement to ChannelProcessor.processEvent(), you'll see that the source is sending events to the channel. The source generates about 104 events, and then generates an additional one about every second... which is interesting, since the mem channel's default capacity is only 100 and there's no sink.
--
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