Ok... thanks Igor!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I mean, mutex should be taken for the entire transaction of course.
Best Regards,
Igor
On Thu, Jan 14, 2021 at 7:49 PM Igor Sapego wrote:
> That's true. We need to implement async reading from client socket to
> handle cases like this one properly. Currently as a workaround I can
> only
That's true. We need to implement async reading from client socket to
handle cases like this one properly. Currently as a workaround I can
only suggest guarding the whole client with mutex or create separate
clients for threads that do transactional operations.
I filed a ticket for the issue [1].
Hello all,
We're developing a multithread application using one C++ Thin Client to
connect to a cluster with a single Server Node. The C++ Thin Client version
is "master" from January 21.
We have implemented a "lock-and-update" system based on the "GetAndPut"
function and
