For a broker that should be holding almost nothing this looks very suspicious:
total 779M -rw-r--r-- 1 999 docker 32M Jul 11 06:51 db-3393.log -rw-r--r-- 1 999 docker 32M Jul 11 09:21 db-3394.log -rw-r--r-- 1 999 docker 32M Jul 14 09:26 db-3444.log -rw-r--r-- 1 999 docker 684M Jul 14 09:26 db.data -rw-r--r-- 1 999 docker 3.2M Jul 14 09:26 db.redo -rw-r--r-- 1 999 docker 8 Jul 5 17:53 lock I'm used to hunting down problems with reaping db index logs in the past, but not with very large db.data files. Googling around doesn't reveal much, either. Can anyone advise on this? Another of our brokers: total 647M -rw-r--r-- 1 999 docker 32M Jul 14 09:30 db-2647.log -rw-r--r-- 1 999 docker 635M Jul 14 09:30 db.data -rw-r--r-- 1 999 docker 3.2M Jul 14 09:30 db.redo -rw-r--r-- 1 999 docker 8 Jul 5 17:55 lock Seems worryingly consistent. Unsure what I'm looking at. Thanks, James
