Hi, We are using processing timer to implement some state clean up logic. After switching from FsStateBackend to RocksDB, we encounter a lot of segfault from the Time Trigger threads when accessing/clearing state value.
We currently uses the latest 1.3-SNAPSHOT, with the patch upgrading RocksDB to 5.6.1, because the seg faults happen less frequently with this version than with the original FRocksDB Perhaps, there's some race conditions here. Any insights would be much appreciated. Best regards, Kien