[
https://issues.apache.org/jira/browse/FLUME-889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13189357#comment-13189357
]
Shu Zhang commented on FLUME-889:
---------------------------------
"In isolation it definitely isn't thread safe, and I don't really think it's a
good idea to make assumptions about the usage patterns. I'll go over it again,
and may add extra unit tests."
I think that's a good idea since configure() is public and some of the javadoc
comments suggests the channel is thread safe. Thanks.
Also it looks like AbstractFileConfigurationProvider would not prevent put()s
and remove()s from being called concurrently with configure() calls, which as
things stand, can corrupt internal state.
> All events in memory channel are lost on reconfiguration
> --------------------------------------------------------
>
> Key: FLUME-889
> URL: https://issues.apache.org/jira/browse/FLUME-889
> Project: Flume
> Issue Type: Bug
> Components: Channel
> Affects Versions: NG alpha 1, NG alpha 2
> Reporter: Shu Zhang
> Assignee: Shu Zhang
> Fix For: v1.1.0
>
> Attachments: FLUME-889-2.patch
>
>
> this line is at the end MemoryChannel.configure(Context)
> queue = new LinkedBlockingDeque<StampedEvent>(capacity);
> memory channel is meant to be dynamically configurable, however every time
> it's reconfigured, all existing events are dropped.
--
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
