ibessonov edited a comment on pull request #655: URL: https://github.com/apache/ignite-3/pull/655#issuecomment-1038751905
Hi @Myasuka, CI report can be found here: https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_RunAllTests?focusLine=0&branch=pull%2F655&mode=builds#all-projects It's also available on this page in "checks" section. I see a problem in logs and I don't quite get it, the process is stuck: ```"main" #1 prio=5 os_prio=0 cpu=2748.35ms elapsed=444.31s tid=0x00007f1898024800 nid=0x3c70 runnable [0x00007f189f86e000] java.lang.Thread.State: RUNNABLE at org.rocksdb.RocksDB.write0(Native Method) at org.rocksdb.RocksDB.write(RocksDB.java:1784) at org.apache.ignite.internal.storage.rocksdb.RocksDbPartitionStorage.removeAllExact(RocksDbPartitionStorage.java:287) at org.apache.ignite.internal.storage.AbstractPartitionStorageTest.testRemoveAllExact(AbstractPartitionStorageTest.java:543) ``` Do you now any possible reasons for this? Main branch works just fine. **EDIT**: Oh, I think I get it, you can't batch write more than it is configured in write buffer size, otherwise it'll stall in the middle. Is there any way to preemptively detect such situation? I would want large transactions to break the cluster. Should we just avoid using batches when it's possible? Looking forward to your reply, thank you! -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
