1
0
Fork 0

Bug fix 3.4/re add overcommit memory 2 warning (#9643)

* re-add overcommit_memory=2 warning

* updated CHANGELOG
This commit is contained in:
Jan 2019-08-06 14:21:37 +02:00 committed by Matthew Von-Maszewski
parent ab847839df
commit e19c478192
2 changed files with 11 additions and 0 deletions

View File

@ -1,6 +1,8 @@
v3.4.8 (XXXX-XX-XX)
-------------------
* Re-added warning for kernel setting "overcommit_memory=2" if jemalloc is also enabled.
* Significantly reduced "random" 1 second delays in some arangosearch DDL operations.
* Decreased unnecessary wait times for agency callbacks in case they were

View File

@ -81,6 +81,15 @@ void EnvironmentFeature::prepare() {
uint64_t v = basics::StringUtils::uint64(value);
if (v == 2) {
#ifdef ARANGODB_HAVE_JEMALLOC
LOG_TOPIC(WARN, arangodb::Logger::MEMORY)
<< "/proc/sys/vm/overcommit_memory is set to a value of 2. this "
"setting has been found to be problematic";
LOG_TOPIC(WARN, Logger::MEMORY)
<< "execute 'sudo bash -c \"echo 0 > "
<< "/proc/sys/vm/overcommit_memory\"'";
#endif
// from https://www.kernel.org/doc/Documentation/sysctl/vm.txt:
//
// When this flag is 0, the kernel attempts to estimate the amount