Re: Semaphore Lock Not Acquired. Race issue?

2020-06-03 Thread adipro
When I removed the stopped Server node IP from Client IP list and server IP list and start both clients, it is working fine. Although I couldn't reproduce it again. If I found it again, I'll try taking dumps and reply it in this thread. Java version -> jdk 1.8.0_152 Ignite version -> 8.7.10

Semaphore Lock Not Acquired. Race issue?

2020-06-02 Thread adipro
Server 1 -> Let's say IP is X. Status is running. Server 2 -> Let's say IP is Y. Status is not running. We stopped this node for various reasons. Client1 -> TcpDiscoveryVmIpFinder ipAddress list has two server IPs - X,Y Client 2 -> TcpDiscoveryVmIpFinder ipAddress list has two server IPs -

Re: Semaphore Lock Not Acquired. Race issue?

2020-06-02 Thread akorensh
Also wanted to mention that there is a working semaphore example available: https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/datastructures/IgniteSemaphoreExample.java -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Semaphore Lock Not Acquired. Race issue?

2020-06-02 Thread akorensh
Hi, In an older version there was an issue that caused this condition https://issues.apache.org/jira/browse/IGNITE-8987 Send a reproducer, mention the version you are using, along with Ignite logs(from both nodes) and a stack trace of both servers when this condition occurs. How to