When running Packetbeat into MySQL server, the server was memory growth (10.834GB)
when logstash is down and Packetbeat supports buffering the events for waiting to send
the memory is over and kills mysql process.

The data collected by topbeat of the packetbeat process

This point MySQL was restarted after memory is over

Using:
Centos 6.6 2.6.32-504.8.1.el6.x86_64
packetbeat version 1.0.0 (amd64)
logstash 1.5.6

Topology:
Packetbeat -> Logstash -> Elasticsearch

Configuration

interfaces:
  device: any

protocols:
  dns:
    include_authorities: true
    include_additionals: true
  mysql:
    ports: [3306]

 logstash:
   hosts: ["localhost:5044"]

I think the Packetbeat it shoulds a setting to prevent max memory consumption for buffering