[
https://issues.apache.org/jira/browse/FLUME-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13227328#comment-13227328
]
Juhani Connolly commented on FLUME-1026:
----------------------------------------
I'll go over this, and post an initial pass.
There are certain aspects that I think have not been settled and will require
discussion hopefully we can get a dialogue started about them.
One of these is the calling configure() on running components. IMO channels are
expected to be thread safe while sinks/sources don't need to be as they are
normally only accessed by a single thread. However as they are reconfigured,
things have the potential to break.
Are we to expect all sinks/sources to be internally thread safe so as to be
able to have configure() called at any time?
Or do we expect external locking?
A third option is that owning runners must be stopped before reconfiguration of
the component and then restarted. The last method could mean a fair bit less
overhead/complexity in synchronization.
> Document Thread Safety Guarantees
> ---------------------------------
>
> Key: FLUME-1026
> URL: https://issues.apache.org/jira/browse/FLUME-1026
> Project: Flume
> Issue Type: Bug
> Components: Docs
> Affects Versions: v1.1.0
> Reporter: Will McQueen
> Fix For: v1.1.0
>
>
--
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
