[jira] [Commented] (SPARK-11499) Spark History Server UI should respect protocol when doing redirection
[ https://issues.apache.org/jira/browse/SPARK-11499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14990674#comment-14990674 ] Lukasz Jastrzebski commented on SPARK-11499: There is also https://en.wikipedia.org/wiki/X-Forwarded-For header that HS could support. > Spark History Server UI should respect protocol when doing redirection > -- > > Key: SPARK-11499 > URL: https://issues.apache.org/jira/browse/SPARK-11499 > Project: Spark > Issue Type: Bug > Components: Web UI >Reporter: Lukasz Jastrzebski > > Use case: > Spark history server is behind load balancer secured with ssl certificate, > unfortunately clicking on the application link redirects it to http protocol, > which may be not expose by load balancer, example flow: > * Trying 52.22.220.1... > * Connected to xxx.yyy.com (52.22.220.1) port 8775 (#0) > * WARNING: SSL: Certificate type not set, assuming PKCS#12 format. > * Client certificate: u...@yyy.com > * TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 > * Server certificate: *.yyy.com > * Server certificate: Entrust Certification Authority - L1K > * Server certificate: Entrust Root Certification Authority - G2 > > GET /history/20151030-160604-3039174572-5951-22401-0004 HTTP/1.1 > > Host: xxx.yyy.com:8775 > > User-Agent: curl/7.43.0 > > Accept: */* > > > < HTTP/1.1 302 Found > < Location: > http://xxx.yyy.com:8775/history/20151030-160604-3039174572-5951-22401-0004 > < Connection: close > < Server: Jetty(8.y.z-SNAPSHOT) > < > * Closing connection 0 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Created] (SPARK-11499) Spark Web UI should respect protocol when doing redirection
Lukasz Jastrzebski created SPARK-11499: -- Summary: Spark Web UI should respect protocol when doing redirection Key: SPARK-11499 URL: https://issues.apache.org/jira/browse/SPARK-11499 Project: Spark Issue Type: Bug Reporter: Lukasz Jastrzebski Use case: Spark history server is behind load balancer secured with ssl certificate, unfortunately clicking on the application link redirects it to http protocol, which may be not expose by load balancer, example flow: * Trying 52.22.220.1... * Connected to xxx.yyy.com (52.22.220.1) port 8775 (#0) * WARNING: SSL: Certificate type not set, assuming PKCS#12 format. * Client certificate: u...@yyy.com * TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 * Server certificate: *.yyy.com * Server certificate: Entrust Certification Authority - L1K * Server certificate: Entrust Root Certification Authority - G2 > GET /history/20151030-160604-3039174572-5951-22401-0004 HTTP/1.1 > Host: xxx.yyy.com:8775 > User-Agent: curl/7.43.0 > Accept: */* > < HTTP/1.1 302 Found < Location: http://xxx.yyy.com:8775/history/20151030-160604-3039174572-5951-22401-0004 < Connection: close < Server: Jetty(8.y.z-SNAPSHOT) < * Closing connection 0 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Updated] (SPARK-11499) Spark History Server UI should respect protocol when doing redirection
[ https://issues.apache.org/jira/browse/SPARK-11499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukasz Jastrzebski updated SPARK-11499: --- Summary: Spark History Server UI should respect protocol when doing redirection (was: Spark Web UI should respect protocol when doing redirection) > Spark History Server UI should respect protocol when doing redirection > -- > > Key: SPARK-11499 > URL: https://issues.apache.org/jira/browse/SPARK-11499 > Project: Spark > Issue Type: Bug >Reporter: Lukasz Jastrzebski > > Use case: > Spark history server is behind load balancer secured with ssl certificate, > unfortunately clicking on the application link redirects it to http protocol, > which may be not expose by load balancer, example flow: > * Trying 52.22.220.1... > * Connected to xxx.yyy.com (52.22.220.1) port 8775 (#0) > * WARNING: SSL: Certificate type not set, assuming PKCS#12 format. > * Client certificate: u...@yyy.com > * TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 > * Server certificate: *.yyy.com > * Server certificate: Entrust Certification Authority - L1K > * Server certificate: Entrust Root Certification Authority - G2 > > GET /history/20151030-160604-3039174572-5951-22401-0004 HTTP/1.1 > > Host: xxx.yyy.com:8775 > > User-Agent: curl/7.43.0 > > Accept: */* > > > < HTTP/1.1 302 Found > < Location: > http://xxx.yyy.com:8775/history/20151030-160604-3039174572-5951-22401-0004 > < Connection: close > < Server: Jetty(8.y.z-SNAPSHOT) > < > * Closing connection 0 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Commented] (SPARK-5376) [Mesos] MesosExecutor should have correct resources
[ https://issues.apache.org/jira/browse/SPARK-5376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14359943#comment-14359943 ] Lukasz Jastrzebski commented on SPARK-5376: --- One comment, however if you run multiple Spark applications even tough executor-id == slave-id, multiple executors can be started on the same host. (And every one of them will consume 1 CPU without scheduling any tasks). This can be painful when you want to run multiple streaming applications on Mesos in fine grained mode, because each streaming driver's executors will consume 1 CPU... [Mesos] MesosExecutor should have correct resources --- Key: SPARK-5376 URL: https://issues.apache.org/jira/browse/SPARK-5376 Project: Spark Issue Type: Improvement Components: Mesos Affects Versions: 1.2.0 Reporter: Jongyoul Lee Spark offers task and executor resources. We should fix resources for executor. As is, same cores as tasks and no memories. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Commented] (SPARK-2168) History Server renered page not suitable for load balancing
[ https://issues.apache.org/jira/browse/SPARK-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14048485#comment-14048485 ] Lukasz Jastrzebski commented on SPARK-2168: --- PR opened History Server renered page not suitable for load balancing --- Key: SPARK-2168 URL: https://issues.apache.org/jira/browse/SPARK-2168 Project: Spark Issue Type: Bug Components: Spark Core Affects Versions: 1.0.0 Reporter: Lukasz Jastrzebski Priority: Minor Small issue but still. I run history server through Marathon and balance it through haproxy. The problem is that links generated by HistoryPage (links to completed applications) are absolute, e.g. a href=http://some-server:port/history/...;completedApplicationName/a , but instead they should be relative, e.g. a hfref=/history/...completedApplicationName/a, so they can be load balanced. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SPARK-2168) History Server renered page not suitable for load balancing
[ https://issues.apache.org/jira/browse/SPARK-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukasz Jastrzebski updated SPARK-2168: -- Description: Small issue but still. I run history server through Marathon and balance it through haproxy. The problem is that links generated by HistoryPage (links to completed applications) are absolute, e.g. a href=http://some-server:port/history/...;completedApplicationName/a , but instead they should be relative, e.g. a hfref=/history/...completedApplicationName/a, so they can be load balanced. was: Small issue but still. I run history server through Marathon and balance it through haproxy. The problem is that links generated by HistoryPage (links to completed applications) are absolute, e.g. a href=http://some-server:port/history;http://some-server:port/history... , but instead they should relative just /history, so they can be load balanced. History Server renered page not suitable for load balancing --- Key: SPARK-2168 URL: https://issues.apache.org/jira/browse/SPARK-2168 Project: Spark Issue Type: Bug Components: Spark Core Affects Versions: 1.0.0 Reporter: Lukasz Jastrzebski Priority: Minor Small issue but still. I run history server through Marathon and balance it through haproxy. The problem is that links generated by HistoryPage (links to completed applications) are absolute, e.g. a href=http://some-server:port/history/...;completedApplicationName/a , but instead they should be relative, e.g. a hfref=/history/...completedApplicationName/a, so they can be load balanced. -- This message was sent by Atlassian JIRA (v6.2#6252)
