dlmarion commented on issue #5501: URL: https://github.com/apache/accumulo/issues/5501#issuecomment-2828225466
I'm thinking this may just be an issue with the IT's that create a new Mini instance for each test. IIRC when a new Mini instance is restarted, then ZooKeeper comes up on a different port. In a test where the `ZooPropStore` is used (which might be everything) a `PropStoreWatcher` is created using the `ReadyMonitor`. The `PropStoreWatcher` is set on the chrooted node `/`, and when `PropStoreWatcher.process` sees the disconnect event it sets `ReadyMonitor.haveConnection` to false. Any call to `ZooPropStore.get` after this will hang as it will wait for the ReadyMonitor to regain the connection, which won't happen because the ZooKeeper server is down and won't be coming back up on that port. I think the stack trace in this case is a orphaned thread from a previous test method ultimately timing out and throwing an IllegalStateException. MiniAccumuloClusterImp constructor creates a new ServerContext but it's never closed - although I don't think that would really fix this, because ServerContext.close doesn't clean up everything because it's not meant to be reused. -- 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. To unsubscribe, e-mail: notifications-unsubscr...@accumulo.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
