Mailing-List: contact dev-help@gearpump.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@gearpump.incubator.apache.org
Date: Thu, 19 May 2016 11:54:12 +0000 (UTC)
From: "Karol Brejna (JIRA)" <jira@apache.org>
To: dev@gearpump.incubator.apache.org
Message-ID: <JIRA.12971124.1463658801000.235146.1463658852845@Atlassian.JIRA>
In-Reply-To: <JIRA.12971124.1463658801000@Atlassian.JIRA>
References: <JIRA.12971124.1463658801000@Atlassian.JIRA> <JIRA.12971124.1463658801433@arcas>
Subject: [jira] [Created] (GEARPUMP-147) java.lang.ClassNotFoundException
 when running on worker with worker.executor-share-same-jvm-as-worker = true
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 19 May 2016 11:54:18 -0000

Karol Brejna created GEARPUMP-147:
-------------------------------------

             Summary: java.lang.ClassNotFoundException when running on worker with worker.executor-share-same-jvm-as-worker = true
                 Key: GEARPUMP-147
                 URL: https://issues.apache.org/jira/browse/GEARPUMP-147
             Project: Apache Gearpump
          Issue Type: Task
            Reporter: Karol Brejna


Doing GEARPUMP-146 I hit a problem: I was able to run a master on pc and a worker on raspi. After deploying wordcountjava-2.11-0.8.0-assembly.jar the example didn't start.

I reproduced this on "pure pc" cluster.

I've prepared dedicated config files:
* gear.pc.conf			   - normal (default) configuration for master and workers ran on a PC
* gear.pc.slimworker.conf  - intends to have lower requirements for memory, cpu - to be used on a device (raspi, edison)


*Obtaining binary and creating config files*
{code}
wget https://github.com/gearpump/gearpump/releases/download/0.8.0/gearpump-2.11-0.8.0.zip
unzip gearpump-2.11-0.8.0.zip
cd gearpump-2.11-0.8.0
cp conf/gear.conf conf/gear.original.conf 
cp conf/gear.conf conf/gear.pc.conf 
cp conf/gear.conf conf/gear.pc.slimworker.conf 
{code}

*Preparing "PC" conf*
The only real change here is putting the IP of the machine that will run the master:
{code}
  cluster {
    masters = ["192.168.1.115:3000"]
  }
  
  hostname = "192.168.1.115"
{code}
  
*Preparing device conf*
Compared to previous config, this config should set up less worker slots, smaller -Xmx jvm switch for worker, and executor-share-same-jvm-as-worker set to true:  
{code}
  worker.slots = 100
  worker.executor-share-same-jvm-as-worker = true

  executor {
    vmargs = "-server -Xms512M -Xmx512M -Xss1M -XX:+HeapDumpOnOutOfMemoryError -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=80 -XX:+UseParNewGC -XX:NewRatio=3  -Djava.rmi.server.hostname=localhost"
    extraClasspath = ""
  }
{code}


*Running the cluster:*
{code}
echo "Starting the master"
cp conf/gear.pc.conf conf/gear.conf
bin/master -ip 192.168.1.115 -port 3000 &

echo "Starting services"
bin/services &

echo "Starting a worker (configured as on the device)"
cp conf/gear.pc.slimworker.conf conf/gear.conf
bin/worker &
{code}

*Deploing the DAG*
I've deployed wordcountjava-2.11-0.8.0-assembly.jar.
The app deploys, but doesn't run.

After changing   worker.executor-share-same-jvm-as-worker  to false and restarting the cluster, example dag works.
  

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)