search

logsearch / logsearch-boshrelease

A BOSH-scalable Elasticsearch+Logstash+Kibana release
http://www.logsearch.io
Apache License 2.0
57 stars 46 forks source link

Don't run ELS on parser #208

Closed mtekel closed 8 years ago

mtekel commented 8 years ago

There is already elasticsearch deployed as a part of parser job. No need to run another elasticsearch on the same VM. Moreover, ELS is configured to consume 46% of the VM memory, which in case of 2 ELSes means that the VM runs out of memory, starts swapping heavily and becomes unresponsive.

cromega commented 8 years ago

@mtekel: the change you are trying to undo came from this commit: https://github.com/logsearch/logsearch-boshrelease/commit/8d50e5e5933d84841eb033c76da60dc4041ffb17

We got rid of the nested ElasticSearch and changed the release so we use the same ElasticSearch job as used in the other jobs.

Could you explain what you have done that resulted in 2 ElasticSearch processes running on your parsers?

mtekel commented 8 years ago

Deployed v200. I haven't checked if it was fixed since (which is was). When are you planning to make a new release?

cromega commented 8 years ago

@mtekel: deployed v200 or upgraded to v200? If it's a fresh deployment and you actually have 2 ES processes running on the parsers then it's a massive bug in the release and we will fix it ASAP once we figured out how it happened. If that's the case, would you send me your deployment manifest?

cromega commented 8 years ago

@mtekel: ah, I see it is fixed now, good to hear. We will probably cut a new release very soon.