Re: Command for Beam worker on Spark cluster

2019-11-12 Thread Kyle Weaver
trol endpoint, logging endpoint, etc. >> >> Where can I extract these parameters from? (In apache_beam Python code, >> those can be extracted from StartWorker request parameters) >> >> Also, how spark executor can find the port that grpc server is running on? >> >

Re: Command for Beam worker on Spark cluster

2019-11-07 Thread Matthew K.
2019 at 5:45 PM From: "Kyle Weaver" To: dev Subject: Re: Command for Beam worker on Spark cluster > Where can I extract these parameters from?   These parameters should be passed automatically when the process is run (note the use of $* in the example scr

Re: Command for Beam worker on Spark cluster

2019-11-06 Thread Kyle Weaver
er is running on? > > *Sent:* Wednesday, November 06, 2019 at 5:07 PM > *From:* "Kyle Weaver" > *To:* dev > *Subject:* Re: Command for Beam worker on Spark cluster > In Docker mode, most everything's taken care of for you, but in process > mode you have to do a l

Re: Command for Beam worker on Spark cluster

2019-11-06 Thread Matthew K.
find the port that grpc server is running on?   Sent: Wednesday, November 06, 2019 at 5:07 PM From: "Kyle Weaver" To: dev Subject: Re: Command for Beam worker on Spark cluster In Docker mode, most everything's taken care of for you, but in process mode you have to do a lot of setu

Re: Command for Beam worker on Spark cluster

2019-11-06 Thread Kyle Weaver
In Docker mode, most everything's taken care of for you, but in process mode you have to do a lot of setup yourself. The command you're looking for is `sdks/python/container/build/target/launcher/linux_amd64/boot`. You will be required to have both that executable (which you can build from source u

Command for Beam worker on Spark cluster

2019-11-06 Thread Matthew K.
Hi all,   I am trying to run *Python* beam pipeline on a Spark cluster. Since workers are running on separate nodes, I am using "PROCESS" for "evironment_type" in pipeline options, but I couldn't find any documentation on what "command" I should pass to "environment_config" to run on the worker,