[ 
https://issues.apache.org/jira/browse/FLUME-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16543856#comment-16543856
 ] 

zhenzhao wang commented on FLUME-3256:
--------------------------------------

Here're some questions I have and some thing I want to point out:
 # We only implement the context based configuration, the component 
configuration is not completely implemented. Not sure which is preferred or 
both are required. I'd appreciate if someone could help me clarify it.
 # Only digest ACL is supported in zookeeper registration now, we plan to add 
more ACK support in the future.

> 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.   
> The patch involved work across our team members, including [~lohit] and 
> several ex team members.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to