Dennis Felsing

Edit: 9900 rows is actually expected, I am trying with larger amount of data now. Original text: With these changes I have now managed to reproduce a successful bulk copy...

What I am seeing now on a 6 node rf3 universe after initially running a truncate table accounts is that there are missing rows in the table: ``` yugabyte=# select...

I cannot reproduce this issue anymore with https://github.com/yugabyte/yugabyte-db/commit/03fc5792142beee569bdb6a0406e86fcfcbde666, closing as fixed.

Without xcluster this looks like a simple upgrade test, which we are running and haven't seen this in. The FATAL seems to be on target side, not source, so without...

Also happened in YbAdminSnapshotScheduleTest.ConsecutiveRestore: ``` [m-1] ================== [m-1] WARNING: ThreadSanitizer: heap-use-after-free (pid=29081) [m-1] Read of size 8 at 0x7b480019bce0 by thread T58 (mutexes: write M729718705982151408): [m-1] #0 std::__1::shared_ptr::get() const /opt/yb-build/thirdparty/yugabyte-db-thirdparty-v20210916160346-44ba371965-centos7-x86_64-clang7/installed/tsan/libcxx/include/c++/v1/memory:3911:49...

@priyanshi-yb Is this with `set yb_disable_transactional_writes=true;` or specific gflags? I'll try to reproduce this and https://github.com/yugabyte/yugabyte-db/issues/14113

I see that there were a lot of FATALs on node 2: ``` [yugabyte@ip ~]$ find /mnt/d0 -name '*FATAL.details*' /mnt/d0/yb-data/tserver/logs/yb-tserver.FATAL.details.2022-09-05T15_46_46.pid28930.txt /mnt/d0/yb-data/tserver/logs/yb-tserver.FATAL.details.2022-09-05T15_46_50.pid18501.txt /mnt/d0/yb-data/tserver/logs/yb-tserver.FATAL.details.2022-09-21T10_46_11.pid2149.txt /mnt/d0/yb-data/tserver/logs/yb-tserver.FATAL.details.2022-09-21T10_51_46.pid3698.txt /mnt/d0/yb-data/tserver/logs/yb-tserver.FATAL.details.2022-09-21T10_49_47.pid43912.txt /mnt/d0/yb-data/tserver/logs/yb-tserver.FATAL.details.2022-09-21T10_56_34.pid12027.txt /mnt/d0/yb-data/tserver/logs/yb-tserver.FATAL.details.2022-09-21T11_01_13.pid20756.txt [yugabyte@ip-172-151-77-199 ~]$ cat /mnt/d0/yb-data/tserver/logs/yb-tserver.FATAL.details.2022-09-21T10_46_11.pid2149.txt...

Locally trying to get a repro I’m always getting conflicts as soon as I copy from multiple connections at once: https://gist.github.com/def-/cff997c0d78a76747e8e6af976098411 ``` psycopg2.errors.SerializationFailure: IO error: Errors occurred while reaching out...

I cannot reproduce this issue anymore with https://github.com/yugabyte/yugabyte-db/commit/03fc5792142beee569bdb6a0406e86fcfcbde666, closing as fixed.

@jmeehan16 This is still occurring in 2.8.10.0-b2: ``` ================== WARNING: ThreadSanitizer: data race (pid=24457) Write of size 1 at 0x7b5400010daa by thread T3 (mutexes: write M1004156980073336112): #0 rocksdb::CompactionPicker::MarkL0FilesForDeletion(rocksdb::VersionStorageInfo const*, rocksdb::ImmutableCFOptions...