vaughn
vaughn
+1, Vaughn (1318247699 at qq dot com)
![apache1](https://user-images.githubusercontent.com/11863049/164144244-1f78570f-6aad-4dbb-b9a0-d261391b6f07.jpg) done
The close have been called
rocksdb 单测问题,看着是我们 rocksdb 不太稳定 Caused by: org.apache.hugegraph.exception.ConnectionException: Failed to open RocksDB 'rocksdb-data/m' Caused by: org.rocksdb.RocksDBException: lock hold by current process, acquire time 1702457768 acquiring thread 140088626837248: rocksdb-data/m/LOCK: No locks available
hbase 有一个单测试是这个问题,close 的时候,有事务没 close,这个貌似以前讨论过 Error: shouldPersistDataOnClose(org.apache.tinkerpop.gremlin.structure.GraphTest) Time elapsed: 2.942 s
> hbase 有一个单测试是这个问题,close 的时候,有事务没 close,这个貌似以前讨论过 Error: shouldPersistDataOnClose(org.apache.tinkerpop.gremlin.structure.GraphTest) Time elapsed: 2.942 s
> > hbase 有一个单测试是这个问题,close 的时候,有事务没 close,这个貌似以前讨论过 Error: shouldPersistDataOnClose(org.apache.tinkerpop.gremlin.structure.GraphTest) Time elapsed: 2.942 s 我加了一点debug信息了,可以根据错误日志一起再看看问题 debug 日志如下:看这些日志,close 抛异常,似乎是符合预期的 ```java Error: -14 07:21:46 [main] [ERROR] o.a.h.StandardHugeGraph - Tx '40' is not closed in...
> shouldPersistDataOnClose 也就 CommunityGeneratorTest 这个测试,把这个注释了,其他的貌似就能正常跑了
> CommunityGeneratorTest 我本地尝试将 WAL_PATH, DATA_PATH 按graph 分开,单测就跑过了**一部分**, 后面仍有类似的问题 ![Screenshot2023_12_14_184756](https://github.com/apache/incubator-hugegraph/assets/11863049/c441764e-6449-45a2-a5d1-c7cbd7c0ebf5)
> > CommunityGeneratorTest > > 我本地尝试将 WAL_PATH, DATA_PATH 按graph 分开,单测就跑过了**一部分**, 后面仍有类似的问题 ![Screenshot2023_12_14_184756](https://private-user-images.githubusercontent.com/11863049/290493179-c441764e-6449-45a2-a5d1-c7cbd7c0ebf5.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTEiLCJleHAiOjE3MDI2OTI4NTgsIm5iZiI6MTcwMjY5MjU1OCwicGF0aCI6Ii8xMTg2MzA0OS8yOTA0OTMxNzktYzQ0MTc2NGUtNjQ0OS00NWEyLWE1ZDEtYzdjYmQ3YzBlYmY1LmpwZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFJV05KWUFYNENTVkVINTNBJTJGMjAyMzEyMTYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjMxMjE2VDAyMDkxOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWJjMjNjY2YyMDJhN2Y2OTMyOTQyNDkzNDY4MDY5MThiNzNmZTZmODBiMjM3YjEzYTgyODQyOTBkY2ZmODA1ODUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.KozxqICaTdbikIEOWRC8ZzYLnqR22xglkmOOPqDTzh4) 我尝试在 graph close 的时候,强制关闭 rocksdb 实例,这样似乎一类单测问题就通过了,但是考虑一类场景,如果进程意外挂了,graph 没 close,因为文件锁的存在,似乎下次就无法打开了。。这种会有吗?大佬们觉得如何解决比较合适呢?文件锁直接删了?