Hello,

We started using ELK stack to visuallize our logs, and we observe high CPU
load on machines (Windows servers) where text logs are generated. There
aren't many log files but they can be very large in size. They contain logs
formatted as json documents so there shouldn't be much computation power to
process them. Java process that hosts Logstash log shipper uses somewhat
between 10 and 20% CPU, and that's more than our own applications.

Another observation: all log files are locked, we can't delete old log
files while Logstash process is running.

Best regards

Vagif

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/CA%2Bxi7%2B3W5Su2dkRBE3RcXf8ZSnrZ9FDmx%2BLwHYQGBDYUz0OGOg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to