ctubbsii commented on issue #1909:
URL: https://github.com/apache/accumulo/issues/1909#issuecomment-774047768


   @dlmarion In answer to your previous question about how frequent the failure 
is: it has failed in 4 out of 4 Jenkins builds since #1896. The ConnectionLoss 
was the first I saw, but the other 3 were:
   
   ```java
   java.lang.AssertionError
        at org.junit.Assert.fail(Assert.java:87)
        at org.junit.Assert.assertTrue(Assert.java:42)
        at org.junit.Assert.assertTrue(Assert.java:53)
        at 
org.apache.accumulo.test.fate.zookeeper.ZooLockIT.testLockSerial(ZooLockIT.java:436)
        at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   ```
   
   One had an repeated message in STDOUT that looked like:
   
   ```
   2021-02-05T04:34:20,692 [zookeeper.ZooLock] DEBUG: 
[zlock#f1fde7ea-8561-4744-a1e0-85fad77cb5f7#] Renewing watch on prior node  
/zltestDeleteWaiting-1685185170-l1/zlock#64cdee91-3fc3-4957-b57c-d6bf315bb550#0000000000
   ```
   
   Two others had:
   
   ```
   2021-02-04T23:37:51,181 [zookeeper.ZooLock] DEBUG: 
[zlock#00000000-0000-0000-0000-aaaaaaaaaaaa#] Ephemeral node 
/zlretryLockSerial/zlock#00000000-0000-0000-0000-aaaaaaaaaaaa#0000000000 created
   2021-02-04T23:37:51,182 [zookeeper.ZooLock] DEBUG: validating and sorting 
children at path /zlretryLockSerial
   2021-02-04T23:37:51,182 [zookeeper.ZooLock] DEBUG: Children nodes: 1
   2021-02-04T23:37:51,183 [zookeeper.ZooLock] DEBUG: - 
zlock#00000000-0000-0000-0000-aaaaaaaaaaaa#0000000000
   2021-02-04T23:37:51,183 [zookeeper.ZooLock] DEBUG: 
[zlock#00000000-0000-0000-0000-aaaaaaaaaaaa#] Setting watcher on 
/zlretryLockSerial/zlock#00000000-0000-0000-0000-aaaaaaaaaaaa#0000000000
   2021-02-04T23:37:51,184 [zookeeper.ZooLock] DEBUG: validating and sorting 
children at path /zlretryLockSerial
   2021-02-04T23:37:51,184 [zookeeper.ZooLock] DEBUG: Children nodes: 1
   2021-02-04T23:37:51,184 [zookeeper.ZooLock] DEBUG: - 
zlock#00000000-0000-0000-0000-aaaaaaaaaaaa#0000000000
   2021-02-04T23:37:51,184 [zookeeper.ZooLock] DEBUG: 
[zlock#00000000-0000-0000-0000-aaaaaaaaaaaa#] First candidate is my lock, 
acquiring...
   2021-02-04T23:37:51,186 [zookeeper.ZooLock] DEBUG: 
[zlock#00000000-0000-0000-0000-bbbbbbbbbbbb#] Ephemeral node 
/zlretryLockSerial/zlock#00000000-0000-0000-0000-bbbbbbbbbbbb#0000000001 created
   2021-02-04T23:37:51,187 [zookeeper.ZooLock] DEBUG: validating and sorting 
children at path /zlretryLockSerial
   2021-02-04T23:37:51,187 [zookeeper.ZooLock] DEBUG: Children nodes: 2
   2021-02-04T23:37:51,187 [zookeeper.ZooLock] DEBUG: - 
zlock#00000000-0000-0000-0000-aaaaaaaaaaaa#0000000000
   2021-02-04T23:37:51,187 [zookeeper.ZooLock] DEBUG: - 
zlock#00000000-0000-0000-0000-bbbbbbbbbbbb#0000000001
   2021-02-04T23:37:51,187 [zookeeper.ZooLock] DEBUG: 
[zlock#00000000-0000-0000-0000-bbbbbbbbbbbb#] Setting watcher on 
/zlretryLockSerial/zlock#00000000-0000-0000-0000-bbbbbbbbbbbb#0000000001
   2021-02-04T23:37:51,188 [zookeeper.ZooLock] DEBUG: validating and sorting 
children at path /zlretryLockSerial
   2021-02-04T23:37:51,188 [zookeeper.ZooLock] DEBUG: Children nodes: 2
   2021-02-04T23:37:51,189 [zookeeper.ZooLock] DEBUG: - 
zlock#00000000-0000-0000-0000-aaaaaaaaaaaa#0000000000
   2021-02-04T23:37:51,189 [zookeeper.ZooLock] DEBUG: - 
zlock#00000000-0000-0000-0000-bbbbbbbbbbbb#0000000001
   2021-02-04T23:37:51,189 [zookeeper.ZooLock] DEBUG: 
[zlock#00000000-0000-0000-0000-bbbbbbbbbbbb#] Lock held by another process with 
ephemeral node: zlock#00000000-0000-0000-0000-aaaaaaaaaaaa#0000000000
   2021-02-04T23:37:51,189 [zookeeper.ZooLock] DEBUG: 
[zlock#00000000-0000-0000-0000-bbbbbbbbbbbb#] Establishing watch on prior node 
/zlretryLockSerial/zlock#00000000-0000-0000-0000-aaaaaaaaaaaa#0000000000
   ```


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to