These are chat archives for atomix/atomix

6th
May 2018
Ronnie
@rroller
May 06 2018 03:29
io.atomix.primitive.PrimitiveException$Timeout: null
        at io.atomix.core.lock.impl.BlockingDistributedLock.complete(BlockingDistributedLock.java:77)
        at io.atomix.core.lock.impl.BlockingDistributedLock.tryLock(BlockingDistributedLock.java:57)
        at com.example.runOneIteration(xScheduler.java:55)
        at com.google.common.util.concurrent.AbstractScheduledService$ServiceDelegate$Task.run(AbstractScheduledService.java:193)
        at com.google.common.util.concurrent.Callables$4.run(Callables.java:119)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
I"m able to reproduce that exception by standing up 4 nodes (all on my laptop) .. taking 2 nodes down... then bringing 1 back up
after that, I the BlockingDistributedLock will always throw when i try to acquire a lock. I'm using the latest snapshot version
Ronnie
@rroller
May 06 2018 04:09
atomix/atomix#544
Ronnie
@rroller
May 06 2018 17:24
Updated the issue above with a copy pasteable repro
Jordan Halterman
@kuujo
May 06 2018 20:45
It’s strange. I’ll get back to you tonight
Ronnie
@rroller
May 06 2018 23:48
Thanks. Let me know if there's anything I can do to help debug