[
https://issues.apache.org/jira/browse/FLUME-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192281#comment-13192281
]
Arvind Prabhakar commented on FLUME-932:
----------------------------------------
Thanks for the feedback Ralph. As I pointed out earlier, this change only
addresses the need to allow named instances. It does not address any other
aspect of the system. The implementation of various components at this stage
lacks a clear thread-safety strategy. We have touched upon this issue in
various discussions before and I agree that we need to nail this down before
the next release. The only reason I modified some methods to add a synchronized
modifier in front was to make it consistent with the other methods in the class
where I felt it was not. For what its worth, some subsystems such as JDBC
channel provider are fully thread safe and have concurrent tests that verify
the correctness in multi-threaded scenario.
In order to address the concurrency requirements, we need to first cut over the
Guava service implementation, and then model the components with it's state
cycle to allow for concurrent access. Adopting this service framework will also
iron out issues such as #4 that you have pointed out (which I think should be a
clean shutdown of previous components before creating new ones).
> Making flume-ng components pluggage and name aware
> --------------------------------------------------
>
> Key: FLUME-932
> URL: https://issues.apache.org/jira/browse/FLUME-932
> Project: Flume
> Issue Type: Improvement
> Reporter: Arvind Prabhakar
> Assignee: Arvind Prabhakar
> Attachments: FLUME-932-1-svn.patch, FLUME-932-2-svn.patch
>
>
> Currently the components in flume-ng are hard wired to use the built in name.
> This implies that within one agent, there can be only one instance of a
> particular component. While the configuration supports having multiple
> components of the same time, the component interfaces themselves need to
> change.
> Also, need to support plugin components for user-provided implementations of
> source/sink/channels where necessary.
--
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
