Hello,
When "partition awareness" is enabled, the client tries to connect to all
server nodes from the connection string. If "partition awareness" is
disabled, only one connection is maintained. Since Ignite 2.11 "partition
awareness" is enabled by default. See [1] for more information.
[1]:
Hi, this is called "partition awareness" [1] - thin client establishes
connections to all known nodes to be able to send requests directly to the
primary node for the given entry.
Multiple connections are also useful for load balancing and improved
reliability.
You can disable this behavior with
>
Hi,
I am running an Ignite 2.12.0 Service Grid with 5 Server Nodes and 32 Thin
Client nodes in a private cloud of RHEL 7.9 VMs. (no docker images).
Doing a sqlline CLI query for connected clients, I get the expected 32
connected clients. However, if I execute netstat (or ss) on all
I'm experiencing a transaction deadlock and would like to understand how
to find out the cause of it.
Snipped from the log I get:
/Deadlock detected:
K1: TX1 holds lock, TX2 waits lock.
K2: TX2 holds lock, TX1 waits lock.
Transactions:
TX1 [txId=GridCacheVersion [topVer=273263429,
