Hello!
I'm not sure what you are trying to do and why you felt the need to
over-complicate the solution.
Regards,
--
Ilya Kasnacheev
пн, 15 июн. 2020 г. в 09:10, adipro :
> Can you please suggest an efficient solution?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Can you please suggest an efficient solution?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello!
Why do you open connection inside the semaphore? You are supposed to open
connection(s) in advance, only issue updates inside the semaphore.
The whole approach is questionable (no sense to use thin JDBC if you
already have Ignite node) but this one is a killer. You also seem to open a
new
Can someone please help regarding this issue?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Thanks for the reply.
But I've two doubts here.
1. If you check the code, I used ignite semaphore and if i remove that
sempahore checking, then I'm getting JDBC connection issues as multiple
threads access that particular code.
We run 100s of threads. Is there any way where we can run in
Hi,
A Streamer -- using IgniteDataStreamer.addData(..) does not guarantee
consistency.
from doc: Note that streamer will stream data concurrently by multiple
internal threads, so the data may get to remote nodes in different order
from which it was added to the streamer.
see:
Can anyone tell if this code guarantees all the rows to be inserted right
after all the statements are executed?
IgniteSemaphore semaphore = null;
try {
semaphore =
cacheHolder.getJDBCSemaphore(IgniteLocks.JDBC_LOCK.getLockValue());
