Return-Path: X-Original-To: apmail-mesos-user-archive@www.apache.org Delivered-To: apmail-mesos-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 91D641816D for ; Thu, 22 Oct 2015 19:07:31 +0000 (UTC) Received: (qmail 26382 invoked by uid 500); 22 Oct 2015 19:07:09 -0000 Delivered-To: apmail-mesos-user-archive@mesos.apache.org Received: (qmail 26322 invoked by uid 500); 22 Oct 2015 19:07:09 -0000 Mailing-List: contact user-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@mesos.apache.org Delivered-To: mailing list user@mesos.apache.org Received: (qmail 26303 invoked by uid 99); 22 Oct 2015 19:07:09 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Oct 2015 19:07:09 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id A29BFC0B1C for ; Thu, 22 Oct 2015 19:07:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.881 X-Spam-Level: ** X-Spam-Status: No, score=2.881 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, WEIRD_PORT=0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=mesosphere.io Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 6wA20jxWJuGQ for ; Thu, 22 Oct 2015 19:07:07 +0000 (UTC) Received: from mail-vk0-f71.google.com (mail-vk0-f71.google.com [209.85.213.71]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 033292303B for ; Thu, 22 Oct 2015 19:07:06 +0000 (UTC) Received: by vkfw189 with SMTP id w189so126640680vkf.1 for ; Thu, 22 Oct 2015 12:07:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mesosphere.io; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=7yapIVotnB1CDg2HZw05muaczNf35y63IrQ4PSuZlYw=; b=UhjkMJAHglBGZ7T6CtuxYbXRbGgXqj647hde/BQ/dmJzHNRz8KwOj9bYja2KhOkVni 0azhlfEMf5T8fVYB79dON1MAziYCMjS9mtV/yqY+x3Z0XX4RVxm3nI63YluJcKzkAnpe jYQNh73nrj/M0QVsyD9/4YmDTaAqR22bqkaNI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=7yapIVotnB1CDg2HZw05muaczNf35y63IrQ4PSuZlYw=; b=AantGfIqe1bvVYSDCOWqgUb4L4ek6VO5jZIIrq5r4jzsNcrbwWGU4dTtsT+LfoXv1R OQp0bd279+8kxI1H5qbVKMcMEpfqe/D8yVDVI2L8qK11rdGbeMQUZQ87owlIJ0+OAJeV 36q5Eq5Xgi7ZxRmVNuH2r3J0Oxy+QouwtVRBjGcsiBgToibG6CBSarEauyJoNSgCPtqT LEJTKECROhjlaCq0szy1v/9UJW4p7wviMCs2SRt9E/Rb0Ot2qF7dRciNPB32bxaodmvw /xqE1OhDnPjLCfxmCNcHRxxh7w0LHOYuRFKXLwjir93y7m0HYxk6GMXxlFPRt2J/JHA0 TMuA== X-Gm-Message-State: ALoCoQlxKkit8yXx3XyfwRFPtAaH1HWhC9oTElfayua5dOU2wig5k8JZQ7rlCrJbUqOLGjX7UHS5 MIME-Version: 1.0 X-Received: by 10.129.31.70 with SMTP id f67mr2447853ywf.114.1445540826147; Thu, 22 Oct 2015 12:07:06 -0700 (PDT) Received: by 10.37.208.213 with HTTP; Thu, 22 Oct 2015 12:07:06 -0700 (PDT) In-Reply-To: References: Date: Thu, 22 Oct 2015 12:07:06 -0700 Message-ID: Subject: Re: spark on mesos with docker issue From: Elizabeth Lingg To: user Content-Type: multipart/alternative; boundary=001a1141e25673bc8b0522b6332d --001a1141e25673bc8b0522b6332d Content-Type: text/plain; charset=UTF-8 Are you using Bridge or Host Networking? -Elizabeth On Thu, Oct 22, 2015 at 12:02 PM, Stavros Kontopoulos < st.kontopoulos@gmail.com> wrote: > Hi, > > Im using spark on mesos on docker. I have linked my slaves to the master > and a > spark repl works fine inside the master container. > > If i try to crate the same spark repl form the host i get stuck at the > point when the framework tries to register to the mesos master (here the > framework is the spark repl itself). > I can ping the container from my host and vice versa. So networking its > not the problem. > What i noticed form the logs is that mesos does not resolve the correct ip: > > Framework failover timeout, removing framework > b3605c33-f573-4d40-806f-b9b0abee2e32-0012 (Spark shell) at > scheduler-b6dbe4f8-4760-4cbe-bb5e-a991e35aba1b@127.0.1.1:40186 > > docker0 interface is on 172.17.x.x and my host is one such ip so i didnt > expect there to see > 127.0.1.1. I have tried several things like spark.driver.host, > SPARK_LOCAL_IP to be set correctly but with no result... > I suspect this is a mesos problem on docker... > > Thnx, > > S. > --001a1141e25673bc8b0522b6332d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Are you using Bridge or Host Networking?

-Elizabeth



On Thu, Oct 22, 2015 at= 12:02 PM, Stavros Kontopoulos <st.kontopoulos@gmail.com> wrote:
Hi,

Im using spark on mesos on docker. I have linked m= y slaves to the master and a
spark repl works fine inside the mast= er container.

If i try to crate the same spark repl form the h= ost i get stuck at the point when the framework tries to register to the me= sos master (here the framework is the spark repl itself).
I c= an ping the container from my host and vice versa. So networking its not th= e problem.
What i noticed form the logs is that mesos does no= t resolve the correct ip:

Framework failover timeout, removing frame= work b3605c33-f573-4d40-806f-b9b0abee2e32-0012 (Spark shell) at scheduler-b6dbe4f8-4760-4cbe-bb5e-a991e35aba1b@127.0.1.1:4018= 6

docker0 interface is on 172.17.x.x and my host is o= ne such ip so i didnt expect there to see
127.0.1.1. I have = tried several things like spark.driver.host, SPARK_LOCAL_IP to be set corre= ctly but with no result...
I suspect this is a mesos problem = on docker...

Thnx,

S.

--001a1141e25673bc8b0522b6332d--