Add an Oozie server component

The relational database that backs the Oozie Server should also be made highly available using best practices defined for the database system in use and should be done after consultation with your in-house DBA. Using the default installed Derby database instance is not supported with multiple Oozie Server instances; therefore, you must use an existing relational database. When using Apache Derby for the Oozie Server, you do not have the option to add Oozie Server components to your cluster.
High availability for Oozie requires the use of an external virtual IP address or load balancer to direct traffic to the Oozie servers.

In Ambari Web, browse to the host on which you want to install another Oozie Server.
On the Host page, click +Add.
Click Oozie Server from the list.
Ambari installs the new Oozie Server.
Configure your external load balancer.
Update the Oozie configuration.
1. Browse to Services > Oozie > Configs.
2. In oozie-site, add the following property values:
  
  oozie.zookeeper.connection.string
  
  List of ZooKeeper hosts with ports: for example,
  c6401.ambari.apache.org:2181,
  c6402.ambari.apache.org:2181,
  c6403.ambari.apache.org:2181
  
  oozie.services.ext
  
  org.apache.oozie.service.ZKLocksService,
  
  org.apache.oozie.service.ZKXLogStreamingService,
  
  org.apache.oozie.service.ZKJobsConcurrencyService
  
  oozie.base.url
  
  http://[CLOADBALANCER_HOSTNAME]:11000/oozie
3. In oozie-env, uncomment the oozie_base_url property and change its value to point to the load balancer.
  export oozie_base_url="http://<loadbalance.hostname>:11000/oozie"
Restart Oozie.
Update the HDFS configuration properties for the Oozie proxy user.
1. Browse to Services > HDFS > Configs.
2. In core-site, update the hadoop.proxyuser.oozie.hosts property to include the newly added Oozie Server host.
  Use commas to separate multiple host names.
Restart services.

Review and confirm all recommended configuration changes.