Glad to help!
On Tue, 6 Aug, 2024, 17:37 Ilango, wrote:
>
> Thanks Praboth. Passing —master attr in spark connect command worked like
> charm. I am able to submit spark connect to my existing stand-alone cluster
>
> Thanks for saving my day once again :)
>
> Thanks,
> Elango
>
>
> On Tue, 6 Aug
Thanks Praboth. Passing —master attr in spark connect command worked like
charm. I am able to submit spark connect to my existing stand-alone cluster
Thanks for saving my day once again :)
Thanks,
Elango
On Tue, 6 Aug 2024 at 6:08 PM, Prabodh Agarwal
wrote:
> Do you get some error on passing
Do you get some error on passing the master option to your spark connect
command?
On Tue, 6 Aug, 2024, 15:36 Ilango, wrote:
>
>
>
> Thanks Prabodh. I'm having an issue with the Spark Connect connection as
> the `spark.master` value is set to `local[*]` in Spark Connect UI, whereas
> the actual m
Thanks Prabodh. I'm having an issue with the Spark Connect connection as
the `spark.master` value is set to `local[*]` in Spark Connect UI, whereas
the actual master node for our Spark standalone cluster is different. I am
passing that master node ip in the Spark Connect Connection. But still it
is
There is an executors tab on spark connect. It's contents are generally
similar to the workers section of the spark master ui.
You might need to specify --master option in your spark connect command if
you haven't done so yet.
On Tue, 6 Aug, 2024, 14:19 Ilango, wrote:
>
> Hi all,
>
> I am evalu
Hi all,
I am evaluating the use of Spark Connect with my Spark stand-alone cluster,
which has a master node and 3 worker nodes. I have successfully created a
Spark Connect connection. However, when submitting Spark SQL queries, the
jobs are being executed only on the master node, and I do not obse
