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 (Created) (JIRA)" <ji...@apache.org> on 2011/10/11 09:00:30 UTC
[jira] [Created] (FLUME-784) MemoryChannel should poll with timeout
on take() rather than block indefinitely
MemoryChannel should poll with timeout on take() rather than block indefinitely
-------------------------------------------------------------------------------
Key: FLUME-784
URL: https://issues.apache.org/jira/browse/FLUME-784
Project: Flume
Issue Type: Bug
Affects Versions: NG alpha 1
Reporter: E. Sammer
Assignee: E. Sammer
Fix For: NG alpha 1
MemoryChannel is currently completely blocking; it uses ArrayBlockingQueue#put() and #take() rather than offer() and poll(). This is suboptimal for certain runner strategies and background tasks. For now, MemoryChannel should use #poll(x) where x is some reasonable (ideally configurable) timeout.
--
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-784) MemoryChannel should poll with
timeout on take() rather than block indefinitely
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124794#comment-13124794 ]
Hudson commented on FLUME-784:
------------------------------
Integrated in flume-728 #32 (See [https://builds.apache.org/job/flume-728/32/])
FLUME-784: MemoryChannel should poll with timeout on take() rather than block indefinitely
esammer : http://svn.apache.org/viewvc/?view=rev&rev=1181636
Files :
* /incubator/flume/branches/flume-728/flume-ng-core/src/main/java/org/apache/flume/channel/MemoryChannel.java
> MemoryChannel should poll with timeout on take() rather than block indefinitely
> -------------------------------------------------------------------------------
>
> Key: FLUME-784
> URL: https://issues.apache.org/jira/browse/FLUME-784
> Project: Flume
> Issue Type: Bug
> Affects Versions: NG alpha 1
> Reporter: E. Sammer
> Assignee: E. Sammer
> Fix For: NG alpha 1
>
>
> MemoryChannel is currently completely blocking; it uses ArrayBlockingQueue#put() and #take() rather than offer() and poll(). This is suboptimal for certain runner strategies and background tasks. For now, MemoryChannel should use #poll(x) where x is some reasonable (ideally configurable) timeout.
--
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] [Closed] (FLUME-784) MemoryChannel should poll with timeout
on take() rather than block indefinitely
Posted by "E. Sammer (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
E. Sammer closed FLUME-784.
---------------------------
> MemoryChannel should poll with timeout on take() rather than block indefinitely
> -------------------------------------------------------------------------------
>
> Key: FLUME-784
> URL: https://issues.apache.org/jira/browse/FLUME-784
> Project: Flume
> Issue Type: Bug
> Affects Versions: NG alpha 1
> Reporter: E. Sammer
> Assignee: E. Sammer
> Fix For: NG alpha 1
>
>
> MemoryChannel is currently completely blocking; it uses ArrayBlockingQueue#put() and #take() rather than offer() and poll(). This is suboptimal for certain runner strategies and background tasks. For now, MemoryChannel should use #poll(x) where x is some reasonable (ideally configurable) timeout.
--
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-784) MemoryChannel should poll with
timeout on take() rather than block indefinitely
Posted by "E. Sammer (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
E. Sammer resolved FLUME-784.
-----------------------------
Resolution: Fixed
Committed to flume-728 branch.
> MemoryChannel should poll with timeout on take() rather than block indefinitely
> -------------------------------------------------------------------------------
>
> Key: FLUME-784
> URL: https://issues.apache.org/jira/browse/FLUME-784
> Project: Flume
> Issue Type: Bug
> Affects Versions: NG alpha 1
> Reporter: E. Sammer
> Assignee: E. Sammer
> Fix For: NG alpha 1
>
>
> MemoryChannel is currently completely blocking; it uses ArrayBlockingQueue#put() and #take() rather than offer() and poll(). This is suboptimal for certain runner strategies and background tasks. For now, MemoryChannel should use #poll(x) where x is some reasonable (ideally configurable) timeout.
--
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