Stan
From: eugene miretsky
Sent: 24 августа 2018 г. 19:45
To: user@ignite.apache.org
Subject: Re: Thin client vs client node performance in Spark
So I decreased the number of spark executors to 2, and the problem went away.
However, what's the general guidline about number of nodes/clients tha
Attached is the error I get from ignitevisorcmd.sh after calling the cache
command (the command just hangs).
To me it looks like all the spark executrors (10 in my test) start a new
client node, and some of those nodes get terminated and restarted as the
executor die. This seems to really confuse
Thanks,
So the way I understand it, thick client will use the affinitly key to send
data to the right node, and hence will split the traiffic between all the
nodes, the thin client will just send the data to one node, and that node
will be responsible to send it to the actual node that owns the
Hi,
Spark integration was implemented before java thin client was released and
thick client performs better than thin one in general. Is your question
related to existence of benchmarks for thin vs thick clients in Spark
integration or just a comparison of these two options?
Thin clients'
Hello,
What are the tradeoffs of using the thin client vs client node? Are there
any benchmarks?
The Spark client is using the latter (client node) - is that for
performance reasons or just legacy?
Cheers,
Eugene
