Spark on DCOS: Make dispatcher reachable from outside the cluster
We have installed spark service from the marathon catalogue on a DCOS cluster.
The json configuration of the service goes like this:
"service":
"name": "spark",
"cpus": 1,
"mem": 1024,
"role": "*",
"service_account": "",
"service_account_secret": "",
"user": "root",
"docker-image": "mesosphere/spark:2.3.1-2.2.1-2-hadoop-2.6",
"log-level": "INFO",
"spark-history-server-url": "http://internal-tfef5a-int-master-elb-1145533197.eu-east-1.elb.amazonaws.com/service/spark-history",
"UCR_containerizer": false,
"use_bootstrap_for_IP_detect": false
,
"hdfs":
"config-url": "http://api.hdfs.marathon.l4lb.thisdcos.directory/v1/endpoints"
Given that the marathon ui does not directly allow editing of the service port, what is the proper way to expose the dispatcher so one can perform spark-submit from his/her own workstation?
amazon-web-services apache-spark mesos marathon dcos
asked Nov 15 '18 at 10:20
pkaramolpkaramol
2,20511849
add a comment |
We have installed spark service from the marathon catalogue on a DCOS cluster.
The json configuration of the service goes like this:
"service":
"name": "spark",
"cpus": 1,
"mem": 1024,
"role": "*",
"service_account": "",
"service_account_secret": "",
"user": "root",
"docker-image": "mesosphere/spark:2.3.1-2.2.1-2-hadoop-2.6",
"log-level": "INFO",
"spark-history-server-url": "http://internal-tfef5a-int-master-elb-1145533197.eu-east-1.elb.amazonaws.com/service/spark-history",
"UCR_containerizer": false,
"use_bootstrap_for_IP_detect": false
,
"hdfs":
"config-url": "http://api.hdfs.marathon.l4lb.thisdcos.directory/v1/endpoints"
Given that the marathon ui does not directly allow editing of the service port, what is the proper way to expose the dispatcher so one can perform spark-submit from his/her own workstation?
amazon-web-services apache-spark mesos marathon dcos
asked Nov 15 '18 at 10:20
pkaramolpkaramol
2,20511849
add a comment |
We have installed spark service from the marathon catalogue on a DCOS cluster.
The json configuration of the service goes like this:
"service":
"name": "spark",
"cpus": 1,
"mem": 1024,
"role": "*",
"service_account": "",
"service_account_secret": "",
"user": "root",
"docker-image": "mesosphere/spark:2.3.1-2.2.1-2-hadoop-2.6",
"log-level": "INFO",
"spark-history-server-url": "http://internal-tfef5a-int-master-elb-1145533197.eu-east-1.elb.amazonaws.com/service/spark-history",
"UCR_containerizer": false,
"use_bootstrap_for_IP_detect": false
,
"hdfs":
"config-url": "http://api.hdfs.marathon.l4lb.thisdcos.directory/v1/endpoints"
Given that the marathon ui does not directly allow editing of the service port, what is the proper way to expose the dispatcher so one can perform spark-submit from his/her own workstation?
amazon-web-services apache-spark mesos marathon dcos
asked Nov 15 '18 at 10:20
pkaramolpkaramol
2,20511849
We have installed spark service from the marathon catalogue on a DCOS cluster.
The json configuration of the service goes like this:
"service":
"name": "spark",
"cpus": 1,
"mem": 1024,
"role": "*",
"service_account": "",
"service_account_secret": "",
"user": "root",
"docker-image": "mesosphere/spark:2.3.1-2.2.1-2-hadoop-2.6",
"log-level": "INFO",
"spark-history-server-url": "http://internal-tfef5a-int-master-elb-1145533197.eu-east-1.elb.amazonaws.com/service/spark-history",
"UCR_containerizer": false,
"use_bootstrap_for_IP_detect": false
,
"hdfs":
"config-url": "http://api.hdfs.marathon.l4lb.thisdcos.directory/v1/endpoints"
Given that the marathon ui does not directly allow editing of the service port, what is the proper way to expose the dispatcher so one can perform spark-submit from his/her own workstation?
amazon-web-services apache-spark mesos marathon dcos
amazon-web-services apache-spark mesos marathon dcos
asked Nov 15 '18 at 10:20
pkaramolpkaramol
2,20511849
asked Nov 15 '18 at 10:20
pkaramolpkaramol
2,20511849
asked Nov 15 '18 at 10:20
pkaramolpkaramol
2,20511849
asked Nov 15 '18 at 10:20
pkaramolpkaramol
2,20511849
asked Nov 15 '18 at 10:20
pkaramolpkaramol
2,20511849
2,20511849
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You should run your dispatcher behind edge proxy. See here how to do it.
Another way is to run it on a public agent. It could be done by setting acceptedResourceRoles":["slave_public"] see here
answered Nov 15 '18 at 13:40
janiszjanisz
5,25632552
if I edit my json service configuration (for thesparkservice I installed from the catalogue) and addacceptedResourceRoles":["slave_public"], will this make it automatically exposed / routable from my workstation?
– pkaramol
Nov 15 '18 at 13:45
Nope. It will be only available with IP and port obtained manually from marathon. To get routable endpoint on one port you need to set up a proxy.
– janisz
Nov 15 '18 at 13:48
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53317215%2fspark-on-dcos-make-dispatcher-reachable-from-outside-the-cluster%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You should run your dispatcher behind edge proxy. See here how to do it.
Another way is to run it on a public agent. It could be done by setting acceptedResourceRoles":["slave_public"] see here
answered Nov 15 '18 at 13:40
janiszjanisz
5,25632552
if I edit my json service configuration (for thesparkservice I installed from the catalogue) and addacceptedResourceRoles":["slave_public"], will this make it automatically exposed / routable from my workstation?
– pkaramol
Nov 15 '18 at 13:45
Nope. It will be only available with IP and port obtained manually from marathon. To get routable endpoint on one port you need to set up a proxy.
– janisz
Nov 15 '18 at 13:48
add a comment |
You should run your dispatcher behind edge proxy. See here how to do it.
Another way is to run it on a public agent. It could be done by setting acceptedResourceRoles":["slave_public"] see here
answered Nov 15 '18 at 13:40
janiszjanisz
5,25632552
if I edit my json service configuration (for thesparkservice I installed from the catalogue) and addacceptedResourceRoles":["slave_public"], will this make it automatically exposed / routable from my workstation?
– pkaramol
Nov 15 '18 at 13:45
Nope. It will be only available with IP and port obtained manually from marathon. To get routable endpoint on one port you need to set up a proxy.
– janisz
Nov 15 '18 at 13:48
add a comment |
You should run your dispatcher behind edge proxy. See here how to do it.
Another way is to run it on a public agent. It could be done by setting acceptedResourceRoles":["slave_public"] see here
answered Nov 15 '18 at 13:40
janiszjanisz
5,25632552
You should run your dispatcher behind edge proxy. See here how to do it.
Another way is to run it on a public agent. It could be done by setting acceptedResourceRoles":["slave_public"] see here
answered Nov 15 '18 at 13:40
janiszjanisz
5,25632552
answered Nov 15 '18 at 13:40
janiszjanisz
5,25632552
answered Nov 15 '18 at 13:40
janiszjanisz
5,25632552
answered Nov 15 '18 at 13:40
janiszjanisz
5,25632552
5,25632552
if I edit my json service configuration (for thesparkservice I installed from the catalogue) and addacceptedResourceRoles":["slave_public"], will this make it automatically exposed / routable from my workstation?
– pkaramol
Nov 15 '18 at 13:45
Nope. It will be only available with IP and port obtained manually from marathon. To get routable endpoint on one port you need to set up a proxy.
– janisz
Nov 15 '18 at 13:48
add a comment |
if I edit my json service configuration (for thesparkservice I installed from the catalogue) and addacceptedResourceRoles":["slave_public"], will this make it automatically exposed / routable from my workstation?
– pkaramol
Nov 15 '18 at 13:45
Nope. It will be only available with IP and port obtained manually from marathon. To get routable endpoint on one port you need to set up a proxy.
– janisz
Nov 15 '18 at 13:48
if I edit my json service configuration (for the
spark service I installed from the catalogue) and add acceptedResourceRoles":["slave_public"], will this make it automatically exposed / routable from my workstation?– pkaramol
Nov 15 '18 at 13:45
if I edit my json service configuration (for the
spark service I installed from the catalogue) and add acceptedResourceRoles":["slave_public"], will this make it automatically exposed / routable from my workstation?– pkaramol
Nov 15 '18 at 13:45
Nope. It will be only available with IP and port obtained manually from marathon. To get routable endpoint on one port you need to set up a proxy.
– janisz
Nov 15 '18 at 13:48
Nope. It will be only available with IP and port obtained manually from marathon. To get routable endpoint on one port you need to set up a proxy.
– janisz
Nov 15 '18 at 13:48
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53317215%2fspark-on-dcos-make-dispatcher-reachable-from-outside-the-cluster%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
