forked from rethinkdb/rethinkdb
-
Notifications
You must be signed in to change notification settings - Fork 9
Open
Description
Hello,
we migrated from official 2.3.6 to 2.3.6-srh-extra , released on Thu. IO went nicely down as expected, unfortunately large memory-leak occured
-
it doesn't happen (so much) on node having only 1 r/w intensive table - primary replica. Removed secondary replicas, so the usage went down.

-
other nodes having multiple primary/secondary replicas keeps rising in memory usage since deploy

Build is made from release https://github.com/srh/rethinkdb/releases/tag/v2.3.6-srh-extra +patch de5d96e .
- Debian Stretch, cache-size=4096 (datadir is not large, partition usage 2.8G), no configuration of user_value
- gcc build rised segmentation fault during linking, didn't finish (same problem when trying to build official 2.3.6)
- clang build completed - missing web_assets in release were built using nodejs from nodesource.com
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels