GC (Allocation Failure)

while i am getting below logs then kiban not showing logs ...need help.

10014.695: [GC (Allocation Failure) 1531122K->1258470K(4160256K), 0.0214068 secs]
10015.756: [GC (Allocation Failure) 1531110K->1258425K(4160256K), 0.0214237 secs]
10016.894: [GC (Allocation Failure) 1531065K->1258611K(4160256K), 0.0300174 secs]
10017.861: [GC (Allocation Failure) 1531251K->1257962K(4160256K), 0.0275830 secs]
10018.904: [GC (Allocation Failure) 1530602K->1258007K(4160256K), 0.0210158 secs]

If you want a response you are better off providing more deatils around version, OS and configuration.

Why do you need help? What concerns you about these messages?

Your JVM is spending 3 hundreths of a second processing GC about once every 1.1 seconds. That's a very good GC efficiency. The fact that you are getting AFs when you have 2.5 GB free heap suggests you have a lot of heap fragmentation, but unless that is causing a lot of GC it is not an issue.

Is this the right way to give multiple input..because i am not geeting logs on kibana. due to this i have to restart logstash after some interval continuously.
input {
beats {
port => 5044
}
}

input {
cloudwatch_logs {
log_group => [ "/aws/rds/instance/trips3m-prod-master/slowquery" ]
region => "us-east-1"
type=> "rds"
}
}

input {
cloudwatch_logs {
log_group => [ "/aws/rds/instance/trips3m-read-private-new/slowquery" ]
region => "us-east-1"
type=> "rds_slave"
}
}

output {
elasticsearch {
hosts => ["http://0.0.0.0:9200"]
index => "%{[@metadata][indexname]}-%{+YYYY.MM.dd}"
}

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.