When you use Oozie HA with Kerberos, you have to set oozie.authentication.kerberos.principal to HTTP/<load-balancer-host> instead of HTTP/<oozie-server-host>. This allows clients to connect to any of the Oozie servers through the load balancer. However, it also blocks clients from directly talking to any of the Oozie servers. In and of itself, that's okay, but it turns out that in most cases, it also blocks the Oozie servers from talking to each other, namely for log streaming, the sharelibupdate command, and collating instrumentation/metrics (OOZIE-1676).
Ultimately, what we need to do is allow Oozie to use both HTTP/<load-balancer-host> and HTTP/<oozie-server-host> at the same time so that clients (including Oozie servers, users, Web UI, etc) can talk to Oozie both through the load balancer and directly. If my understanding of
HADOOP-10158 is correct, HADOOP-10158 adds this ability. For this JIRA, we should update Oozie to take advantage of HADOOP-10158.