aboutsummaryrefslogtreecommitdiff
path: root/repl
diff options
context:
space:
mode:
authorCodingCat <zhunansjtu@gmail.com>2014-02-08 23:39:17 -0800
committerReynold Xin <rxin@apache.org>2014-02-08 23:39:17 -0800
commitb6dba10ae59215b5c4e40f7632563f592f138c87 (patch)
tree4cbb7da28058367413dbfe0877d5332447afbfec /repl
parent2ef37c93664d74de6d7f6144834883a4a4ef79b7 (diff)
downloadspark-b6dba10ae59215b5c4e40f7632563f592f138c87.tar.gz
spark-b6dba10ae59215b5c4e40f7632563f592f138c87.tar.bz2
spark-b6dba10ae59215b5c4e40f7632563f592f138c87.zip
Merge pull request #556 from CodingCat/JettyUtil. Closes #556.
[SPARK-1060] startJettyServer should explicitly use IP information https://spark-project.atlassian.net/browse/SPARK-1060 In the current implementation, the webserver in Master/Worker is started with val (srv, bPort) = JettyUtils.startJettyServer("0.0.0.0", port, handlers) inside startJettyServer: val server = new Server(currentPort) //here, the Server will take "0.0.0.0" as the hostname, i.e. will always bind to the IP address of the first NIC this can cause wrong IP binding, e.g. if the host has two NICs, N1 and N2, the user specify the SPARK_LOCAL_IP as the N2's IP address, however, when starting the web server, for the reason stated above, it will always bind to the N1's address Author: CodingCat <zhunansjtu@gmail.com> == Merge branch commits == commit 6c6d9a8ccc9ec4590678a3b34cb03df19092029d Author: CodingCat <zhunansjtu@gmail.com> Date: Thu Feb 6 14:53:34 2014 -0500 startJettyServer should explicitly use IP information
Diffstat (limited to 'repl')
0 files changed, 0 insertions, 0 deletions