qa.drupal.org log returning mysql error

I guess the query should be optimized a bit. Maybe some judicially placed indices would help.

mysql> explain SELECT pifr_log.log_id AS log_id, pifr_client_pifr_log.client_id AS pifr_client_pifr_log_client_id, pifr_test_pifr_log.test_id AS pifr_test_pifr_log_test_id, pifr_test_pifr_log.type AS pifr_test_pifr_log_type, pifr_test_pifr_log.title AS pifr_test_pifr_log_title, pifr_log.code AS pifr_log_code, pifr_log.timestamp AS pifr_log_timestamp, pifr_log.log_id AS pifr_log_log_id FROM pifr_log pifr_log INNER JOIN pifr_test pifr_test_pifr_log ON pifr_log.test_id = pifr_test_pifr_log.test_id LEFT JOIN pifr_client pifr_client_pifr_log ON pifr_log.client_id = pifr_client_pifr_log.client_id ORDER BY pifr_log_log_id DESC LIMIT 0, 50 ;
+----+-------------+----------------------+--------+---------------+---------+---------+--------------------------------------+-------+---------------------------------+
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra |
+----+-------------+----------------------+--------+---------------+---------+---------+--------------------------------------+-------+---------------------------------+
| 1 | SIMPLE | pifr_test_pifr_log | ALL | PRIMARY | NULL | NULL | NULL | 27205 | Using temporary; Using filesort |
| 1 | SIMPLE | pifr_log | ref | test_id | test_id | 4 | drupal_qa.pifr_test_pifr_log.test_id | 7 | Using where |
| 1 | SIMPLE | pifr_client_pifr_log | eq_ref | PRIMARY | PRIMARY | 4 | drupal_qa.pifr_log.client_id | 1 | Using index |
+----+-------------+----------------------+--------+---------------+---------+---------+--------------------------------------+-------+---------------------------------+

I've no idea which purpose the logs save and won't really meddle with them. If they aren#t needed for all time, the pifr_test moduld should have an expiration mechanism.

I've gone ahead and disabled the PIFR demo module in case that was responsible. We deployed it to approximately 20 authenticated users on Friday.

My guess is we need some basic maintenance build in.

Does Drupal.org have a central logging solution yet?

Does the INNER JOIN ever remove rows from the result set? Or is it there simply to gather extra data that is known to be present? If it's the latter, this query is easy to optimize.

no central logging yet, it's on my wishlist.

I've no idea about the purpose of the parts of the query. It is a views query, so it isn't really obvious what the motivation for the parts it.

I believe all these errors are related to an overflow of the tmpfs partition

Triaging