You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flume.apache.org by "zhenzhao wang (JIRA)" <ji...@apache.org> on 2018/07/13 22:08:00 UTC
[jira] [Commented] (FLUME-3256) Adding Register Service Component
and Zookeeper registration for service discovery
[ https://issues.apache.org/jira/browse/FLUME-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16543792#comment-16543792 ]
zhenzhao wang commented on FLUME-3256:
--------------------------------------
Here's the review board link https://reviews.apache.org/r/67917/
> Adding Register Service Component and Zookeeper registration for service discovery
> -----------------------------------------------------------------------------------
>
> Key: FLUME-3256
> URL: https://issues.apache.org/jira/browse/FLUME-3256
> Project: Flume
> Issue Type: New Feature
> Reporter: zhenzhao wang
> Priority: Major
> Labels: patch
> Fix For: 1.9.0
>
> Attachments: FLUME-3256-0.patch
>
>
> We're going to introduce following feature/function in the patch:
> # Adding a register service component interface so developer could develop their own agent service registration machoism for source process.
> # A zookeeper register service which will create node on Zookeeper with service url. So clients could use zookeeper to find available flume agents.
> We have used this feature internally for years and it had been working very well. Some refactor was done from our internal patch to make it more generic. In our internal usage, our flume agents register to different zookeeper paths as different tiers to serve different kinds of events with different SLA.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@flume.apache.org
For additional commands, e-mail: issues-help@flume.apache.org