Hi!
You may get worse performance with a thin client compared to an ordinary
client because as the thin client works through an intermediary node, so
your request will always go to node A in your case and then it will be
handled there, a normal client would go straight to the node where the
data is while the thin client first has to go to node A and then from
there to the B node where the data is.
The index data is stored where the data is (B,C) so if your primary data
and backup data is not on node A it will have to pass on the request to
B, Ignite may not have index data on node A but it does know on what
node your data is located so it will go from A to B, it does not have
the request it from C also.
So with an ordinary client your request will go straight to B and
response back to client.
With a thin client your request will go to A and from there to B,
resoponse back to A and then to your client.
Mikael
Den 2020-06-03 kl. 07:22, skrev kay:
Hello, I read this page,
https://apacheignite.readme.io/docs/memory-architecture.
and I would like to know what is going to be happen if there are 3 remote
server nodes(A,B,C)
, and cache mode is partitioned and backups 1.
If I wanna get '1' cache data and my application is connected with node A
using thin client but '1' data is allocated in node B(primary), C(backup).
In these case, I want to know Ignite operating principle for data get.
All node have a index page all data??
I want to know..
I look forward to reply.
Thank you so much.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
