Hi, Is this issue affected in 0.9.0 and fixed in 0.9.0?
Best, ----------------------------------- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Jialin Qiao (Jira) <[email protected]> 于2019年12月18日周三 下午3:35写道： > > [ > https://issues.apache.org/jira/browse/IOTDB-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Jialin Qiao closed IOTDB-319. > ----------------------------- > Fix Version/s: 0.9.0 > Resolution: Fixed > > > java deadlock (not sure how to reproduce) > > ----------------------------------------- > > > > Key: IOTDB-319 > > URL: https://issues.apache.org/jira/browse/IOTDB-319 > > Project: Apache IoTDB > > Issue Type: Bug > > Affects Versions: 0.9.0 > > Reporter: xiangdong Huang > > Priority: Major > > Labels: hard, pull-request-available > > Fix For: 0.9.0 > > > > Attachments: deadlock.out > > > > Time Spent: 20m > > Remaining Estimate: 0h > > > > Hi, > > my colleague gives me an IoTDB instance which has no response for > "select " SQL. > > (but for Schema query sql, it works). > > I used jstack to check the process and find a deadlock, you can get the > detailed info in the attachment. > > > > Found one Java-level deadlock: > > ============================= > > "pool-2-IoTDB-JDBC-Client-thread-16": > > waiting to lock monitor 0x00007fdab800ff68 (object 0x00000003c7163218, > a org.apache.iotdb.db.query.control.FileReaderManager), > > which is held by "pool-2-IoTDB-JDBC-Client-thread-3" > > "pool-2-IoTDB-JDBC-Client-thread-3": > > waiting for ownable synchronizer 0x00000003c6106f40, (a > java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync), > > which is held by "MergeThread-0" > > "MergeThread-0": > > waiting to lock monitor 0x00007fdab800ff68 (object 0x00000003c7163218, > a org.apache.iotdb.db.query.control.FileReaderManager), > > which is held by "pool-2-IoTDB-JDBC-Client-thread-3" > > > > > > > > -- > This message was sent by Atlassian Jira > (v8.3.4#803005) >
