Hi :)
The following table is easily the largest in eventlogging and growing
fastest:
114G UniversalLanguageSelector-tofu_7629564
Is there a plan for purging old data from this one? I realize it's mostly
new data; just wondering if growth will be unbounded.
Why does it have an odd name "-tofu"? Is it intended?
There is a duplicate table called UniversalLanguageSelecTor-tofu_7629564 --
note the uppercase T -- with a single row. Is that needed?
The next biggest are:
67G PageContentSaveComplete_5588433.ibd
61G MediaViewer_8572637.ibd
57G MediaViewer_8245578.ibd
33G MobileWebClickTracking_5929948.ibd
BR
Sean
---
DBA @ WMF
(to public list and cc-ing Nemo)
Hello,
Since last time we had an increase in throughput in Even Logging Nemo had
to notify us via e-mail this is just a brief note to the list to say that
we now have throughput monitoring for event logging and it is working.
We had a throughput spike today that we shall be investigating.
Thanks,
Nuria
---------- Forwarded message ----------
From: <icinga(a)neon.wikimedia.org>
Date: Wed, Jun 25, 2014 at 4:46 AM
Subject: ** PROBLEM alert - tungsten/Throughput of event logging events is
CRITICAL **
To: nuria(a)wikimedia.org
❤❤❤❤❤ Icinga ❤❤❤❤❤
Notification Type: PROBLEM
Service: Throughput of event logging events
Host: tungsten
Address: 10.64.0.18
State: CRITICAL
Date/Time: Wed Jun 25 02:46:22 UTC 2014
Additional Info:
CRITICAL: 7.14% of data exceeded the critical threshold [500.0]
Love, Icinga