Bug #77273 should thread/sql/compress_gtid_table be a BACKGROUND thread?
Submitted: 8 Jun 2015 14:04 Modified: 19 Jun 2015 6:17
Reporter: Shane Bester (Platinum Quality Contributor) Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Replication Severity:S4 (Feature request)
Version:5.7.7, 5.7.8 OS:Any
Assigned to: CPU Architecture:Any
Triage: Needs Triage: D5 (Feature request)

[8 Jun 2015 14:04] Shane Bester
Description:
mysql> select * from performance_schema.threads where name like '%gtid%'\G
*************************** 1. row ***************************
          THREAD_ID: 24
               NAME: thread/sql/compress_gtid_table
               TYPE: FOREGROUND
     PROCESSLIST_ID: 1
   PROCESSLIST_USER: NULL
   PROCESSLIST_HOST: NULL
     PROCESSLIST_DB: NULL
PROCESSLIST_COMMAND: Daemon
   PROCESSLIST_TIME: 41
  PROCESSLIST_STATE: Suspending
   PROCESSLIST_INFO: NULL
   PARENT_THREAD_ID: 1
               ROLE: NULL
       INSTRUMENTED: YES
1 row in set (0.00 sec)

mysql> select * from information_schema.processlist;
+----+------+------+------+---------+------+-----------+----------------------------------------------+
| ID | USER | HOST | DB   | COMMAND | TIME | STATE     | INFO                                         |
+----+------+------+------+---------+------+-----------+----------------------------------------------+
|  2 | root |      | test | Query   |    0 | executing | select * from information_schema.processlist |
+----+------+------+------+---------+------+-----------+----------------------------------------------+
1 row in set (0.00 sec)

How to repeat:
https://dev.mysql.com/doc/refman/5.7/en/threads-table.html

"The thread type, either FOREGROUND or BACKGROUND. User connection threads are foreground threads. Threads associated with internal server activity are background threads."

Suggested fix:
In my understanding BACKGROUND would be better for the gtid compress thread.
[19 Jun 2015 6:17] Umesh Shastry
Hello Shane,

Thank you for the report.

Thanks,
Umesh