Details
-
Bug
-
Resolution: Fixed
-
Critical
-
4.5.0
-
None
-
Untriaged
-
Unknown
Description
Build 1924
This is related to the MB-19003 indexer crashing, but one node had a very high projector RAM usage.
The node in question is: ec2-54-215-123-219.us-west-1.compute.amazonaws.com
Logs are here:
https://s3.amazonaws.com/cb-engineering/perry/indexercrash/collectinfo-2016-04-01T175734-ns_1%40ec2-54-215-123-219.us-west-1.compute.amazonaws.com.zip
https://s3.amazonaws.com/cb-engineering/perry/indexercrash/collectinfo-2016-04-01T175734-ns_1%40ec2-54-219-195-14.us-west-1.compute.amazonaws.com.zip
https://s3.amazonaws.com/cb-engineering/perry/indexercrash/collectinfo-2016-04-01T175734-ns_1%40ec2-54-219-197-161.us-west-1.compute.amazonaws.com.zip
https://s3.amazonaws.com/cb-engineering/perry/indexercrash/collectinfo-2016-04-01T175734-ns_1%40ec2-54-219-255-167.us-west-1.compute.amazonaws.com.zip
https://s3.amazonaws.com/cb-engineering/perry/indexercrash/collectinfo-2016-04-01T175734-ns_1%40ec2-54-219-58-193.us-west-1.compute.amazonaws.com.zip