When an application specifies the ReplayChannels argument when constructing a LogReader, memory consumption of the process monotonically increases as the log is replayed. In our testing, it was growing at ~400MB/s and hit ~48GB before getting killed by the oom_killer.
Removing that argument from LogReader’s constructor seems to fix the issue.
When an application specifies the ReplayChannels argument when constructing a LogReader, memory consumption of the process monotonically increases as the log is replayed. In our testing, it was growing at ~400MB/s and hit ~48GB before getting killed by the oom_killer.
Removing that argument from LogReader’s constructor seems to fix the issue.