Closed
Bug 1007273
Opened 11 years ago
Closed 11 years ago
Loggins elasticsearch dying
Categories
(Webmaker Graveyard :: DevOps, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: johns, Assigned: johns)
References
Details
× Oops! ElasticsearchException[java.lang.OutOfMemoryError: Java heap space]
Got this getting one day worth of data.
Assignee | ||
Comment 1•11 years ago
|
||
Followed these recs on the three ES servers:
http://stackoverflow.com/questions/18132719/how-to-change-elasticsearch-max-size
Assignee | ||
Comment 3•11 years ago
|
||
Since we're sending literally 3 million log messages per day, this is not keeping up.
I've been keeping a rolling three days of logs to ensure this service stays up. I've also sent my es configs to Laura Thompson, our MoCo friend with lots of ES experience, in the hopes she can provide me some knowledge.
Additionally, on June 6th I'll be attending a class on the ELK stack which will cover scaling best practices.
Assignee | ||
Comment 4•11 years ago
|
||
As I'm writing my own node.js and looking to use messina, I note this in the readme:
If you'd like to combine a single request/response cycle into a single log message, simply set combinedOutput: true:
var messina = require('messina');
var log = messina('myapp');
app.use(log.middleware({ combinedOutput: true }));
We should do that.
Assignee | ||
Comment 5•11 years ago
|
||
Booyah.
Resolved by applying actual knowledge instead of wildly guessing about settings. :)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 6•11 years ago
|
||
woo! \o/
You need to log in
before you can comment on or make changes to this bug.
Description
•