Details
-
Bug
-
Resolution: Fixed
-
Blocker
-
2.0
-
Security Level: Public
-
None
-
2
Description
I have a crash dump that shows that simple index build over 1.2 million of small docs eats tons of ram. I'm going to attach erlang crash dump where you can see second biggest process (0.7277.2 or sort by stack+heap) is index updater.
NOTE: crash itself was caused by attempt to grab diag so biggest process died because of that, but real cause seems to be index building.