Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 11-03-2015 06:40 PM
Created 11-04-2015 03:38 PM
Are you looking to restrict the network traffic to a specific interface or make Oozie UI listen on multiple IP addresses assigned to the same server?
If the former, this documentation should help. It suggests to set a configuration property: oozie.http.hostname or ENV variable: OOZIE_HTTP_HOSTNAME
Created 11-04-2015 03:38 PM
Are you looking to restrict the network traffic to a specific interface or make Oozie UI listen on multiple IP addresses assigned to the same server?
If the former, this documentation should help. It suggests to set a configuration property: oozie.http.hostname or ENV variable: OOZIE_HTTP_HOSTNAME
Created 11-04-2015 04:35 PM
Hi Vladimir, I am trying bind Oozie on specific IP.
Upon updating "OOZIE_HTTP_HOSTNAME", and restarting Oozie, I do not see Oozie bind to specific ip.
netstat -pltn | grep 11000
tcp 0 0 0.0.0.0:11000 0.0.0.0:* LISTEN 22072/java
Created 11-04-2015 05:06 PM
I don't see a supported, permanent way of doing this in Oozie. If you want to make a temporary change, you can configure Tomcat to run on a specific IP address. I made a change to /usr/hdp/2.3.0.0-2557/etc/oozie/tomcat-deployment.http/conf/server.xml and added address="#.#.#.#" to <Connector /> to get this to work. Source documentation