dlmarion commented on issue #2030: URL: https://github.com/apache/accumulo/issues/2030#issuecomment-852198441
Here's the snippet from the manager log (with my log changes): ``` 2021-06-01T14:47:54,043 [tableOps.Utils] INFO : namespace +default (69c29b96a0cc24bc) locked for read operation: COMPACT 2021-06-01T14:47:54,060 [tableOps.Utils] INFO : table 1 (69c29b96a0cc24bc) locked for read operation: COMPACT 2021-06-01T14:47:54,507 [accumulo.audit] INFO : operation: permitted; user: root; client: 127.0.0.1:59340; action: authenticate; 2021-06-01T14:47:54,516 [accumulo.audit] INFO : operation: permitted; user: root; client: 127.0.0.1:59340; action: authenticate; 2021-06-01T14:47:54,542 [accumulo.audit] INFO : operation: permitted; user: root; client: 127.0.0.1:59340; action: authenticate; 2021-06-01T14:47:54,542 [accumulo.audit] INFO : operation: permitted; user: root; client: 127.0.0.1:59340; action: deleteTable; targetTable: DeleteCancelsMajCIT_test0; 2021-06-01T14:47:54,556 [accumulo.audit] INFO : operation: permitted; user: root; client: 127.0.0.1:59340; action: authenticate; 2021-06-01T14:47:54,557 [tableOps.Utils] INFO : namespace +default (252a9562646ec62e) locked for read operation: DELETE 2021-06-01T14:47:54,561 [tableOps.Utils] INFO : table 1 (252a9562646ec62e) locked by another operation, will retry ``` Is this the intended design for the DistributedReadWriteLock? Only 1 concurrent READ lock? This seems to deviate from it's parent class, https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/util/concurrent/locks/ReadWriteLock.html -- 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]
