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

Larry McCay edited comment on KNOX-1010 at 9/12/17 8:16 PM:
------------------------------------------------------------

[~pzampino] - Who do you see populating the Zookeeper structures with the 
discovered artifacts?

I can see multiple possibilities here:

1. management UIs and commands themselves would have to know these details and 
publish to ZK appropriately
2. management UIs and commands can just call the Knox Admin API which would 
have to be aware of a ZK quorum and publish the details appropriately. Then all 
UIs and commands get it for free.

#2 makes a lot of sense but we need to consider the fact that multiple 
instances would potentially be updating the ZK schema for the same change - 
especially in an Ambari managed world. So multiple writers to ZK and change 
notifications of the same change being discovered by each Knox instance for 
each of the instance-driven updates to ZK may cause some unnecessary thrashing.


was (Author: lmccay):
[~pzampino] - Who do you see populating the Zookeeper structures with the 
discovered artifacts?

> Remote Discovery of Knox Topology Configuration
> -----------------------------------------------
>
>                 Key: KNOX-1010
>                 URL: https://issues.apache.org/jira/browse/KNOX-1010
>             Project: Apache Knox
>          Issue Type: Sub-task
>          Components: Server
>            Reporter: Phil Zampino
>              Labels: kip-8
>             Fix For: 0.14.0
>
>
> To support HA deployments, Knox should be able to discover simple topology 
> descriptors and provider configuration remotely.
> - Define the ZooKeeper structure for remote config (simple desc, externalized 
> provider) discovery
> - Determine the best way to interact with ZooKeeper (REST, or some other 
> client binding)
> - Simple descriptor discovery
> - External provider config discovery



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to