Details
-
Bug
-
Resolution: Fixed
-
Critical
-
7.0.2
-
Untriaged
-
1
-
No
Description
In one of my trials with 500M documents, it is observed that the memory usage of the node which streams the file contents shoots up proportionate to the size of index partitions getting transferred.
Upon digging, it stems from the http.Timeout handler from the Go as it uses a bytes buffer internally.
ref - https://github.com/golang/go/blob/master/src/net/http/server.go#L3396
I have some proposals getting tested and look to fix the issue from my experiments.
And shall create the PR once I am back.
Verified the fix here - http://perf.jenkins.couchbase.com/job/atlas_rebal_dev/9/