Info

concurrency_replication* suites have high memory usage on UBSan, so we run them differently for now while the underlying cause is still being investigated

Top User Comments

daniel.gottlieb@10gen.com commented on Mon, 25 Feb 2019 15:41:06 +0000: max.hirschhorn is the relation we've seen between the system allocator and memory usage sufficient to say we've "understood" the cause? If so, SERVER-26300 has been pushed which may mean this is ready for a look. max.hirschhorn@10gen.com commented on Wed, 31 Oct 2018 17:24:38 +0000: Does this ticket still need to be in investigating status? What do we need to figure out to schedule it? april.schoffer, we need to figure out the root cause behind the memory pressure when running with UBSan (undefined behavior sanitizer) enabled. The work that has been done on this ticket was to stop the bleeding in the linked BF ticket, but we need to understand the actual problem in order to revert those changes. april.schoffer commented on Wed, 31 Oct 2018 16:21:26 +0000: Does this ticket still need to be in investigating status? What do we need to figure out to schedule it? max.hirschhorn@10gen.com commented on Thu, 6 Sep 2018 15:48:22 +0000: Do you want to file a separate ticket for blacklisting that suite? No - I wasn't sure if it would give a clue as to where the memory pressure is coming from. robert.guo commented on Thu, 6 Sep 2018 13:56:24 +0000: max.hirschhorn Nope, that was an oversight as the simultaneous suite didn't fail in the BF ticket. Do you want to file a separate ticket for blacklisting that suite? max.hirschhorn@10gen.com commented on Thu, 6 Sep 2018 03:26:10 +0000: robert.guo, I forget - did you already look into why the concurrency_simultaneous_replication task doesn't have this issue on the UBSan builder? max.hirschhorn@10gen.com commented on Wed, 5 Sep 2018 04:18:39 +0000: The concurrency_replication_multi_stmt_txn_ubsan.yml test suite introduced by the changes from 806b9c3 as part of SERVER-35037 should also be reverted once the memory pressure issue is understood and fixed. max.hirschhorn@10gen.com commented on Wed, 11 Jul 2018 16:42:23 +0000: Bumping this out far into the future. It's something we should definitely continue to look into but isn't the most pressing thing now that the UBSan builder has returned to being green. https://evergreen.mongodb.com/build/mongodb_mongo_master_ubuntu1604_debug_ubsan_80c7c825a44cf99b17e81f4233445c7ab1927706_18_07_11_01_45_09 xgen-internal-githook commented on Fri, 6 Jul 2018 20:32:33 +0000: Author: {'username': 'guoyr', 'name': 'Robert Guo', 'email': 'robert.guo@10gen.com'} Message: SERVER-35964 create UBSan concurrency_replication* tasks (cherry picked from commit a6e2c10af2dcfa862c6afa0fb1504a5d2b092d09) Branch: v4.0 https://github.com/mongodb/mongo/commit/a73913de26efe8e7b15d7d058ee8bccb6534a7c6 xgen-internal-githook commented on Thu, 5 Jul 2018 23:31:43 +0000: Author: {'username': 'guoyr', 'name': 'Robert Guo', 'email': 'robert.guo@10gen.com'} Message: SERVER-35964 create UBSan concurrency_replication* tasks Branch: master https://github.com/mongodb/mongo/commit/a6e2c10af2dcfa862c6afa0fb1504a5d2b092d09

Steps to Reproduce