Page History

...

Knox already handles the topology-based HA configuration to a degree. At topology generation time, if there are multiple hosts in the cluster for the associated service, Knox will add the URLs to the <service/> element.
If there is also an entry for that service in the HaProvider configuration, then the service will be proxied in an HA manner.

...

• Identify the nature of all the supported services
  • Which ones services are purely topology-based?
    
    • WEBHCAT
    • HBASE
    Which ones are
    • OOZIE
    • WEBHDFS
    • ?
      
      
  • Which services are currently ZooKeeper-based?
    • HIVE (HS2ZooKeeperURLManager)
    • HBASE (HBaseZooKeeperURLManager)
    • Kafka (KafkaZooKeeperURLManager)
    • SOLR (SOLRZooKeeperURLManager)
    • ?
      
      
  • Could ZooKeeper support be added for any services which do no currently support it?
    
    
• For the ZooKeeper-based-HA services, determine if the ZooKeeper details are available from the service's configuration via Ambari.
  
  
• Determine how to leverage the cluster discovery data to generate the ZooKeeper HA configuration for the relevant declared topology services.
  
  
• Investigate moving service-specific HA configuration from the HaProvider configuration to the service declaration.
  This just makes more logical sense, and it will make shared provider configurations applicable to more topologies (i.e., more reusable).