Hi WangYQ, yes, you're basically right - best is you set up a load balancer for each of the Oozie instances and add its address to all the configuration entries where a single Oozie server address used to be.
E.g. http://load-balancer-host:11000/oozie or https://load-balancer-host:11443/oozie. Regards, Andras -- Andras PIROS Software Engineer <http://www.cloudera.com/> On Tue, Dec 20, 2016 at 1:10 PM, WangYQ <wangyongqiang0...@163.com> wrote: > in > http://blog.cloudera.com/blog/2014/03/inside-apache-oozie-ha/ > > > Architecture: Access > > Usually, when you use the Oozie client, REST API, or Web UI, there’s a > single address to use (http://myhost:11000/oozie, for example). But now > that you have multiple Oozie servers, you have multiple addresses to which > users can connect — so what happens if the one they pick goes down? There > are also many clients or tools that only support a single entry point for > Oozie, such as the JobTracker. To fix this issue, you need to provide a > single address that will round-robin between the Oozie servers. > > You can use a load balancer, a virtual IP address, or DNS round-robin for > this purpose. As with the database, this setup technically needs to be HA > as well. > > > > > > > > we need make a single address to oozie by ourselves? > > such as load balancer, a virtual IP address, or DNS round-robin > > does oozie provide a simple method? > > > > > >
