Spam in error log if server run without permission to set nice 0
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.5 |
Invalid
|
Undecided
|
Unassigned | |||
5.6 |
Triaged
|
Medium
|
Unassigned | |||
5.7 |
Invalid
|
Undecided
|
Unassigned |
Bug Description
If server is started in environment where setting nice to 0 is not allowed (e.g. non-root with mysqld niced to priority lower to 0), the error log will have
2014-08-04 15:15:06 28999 [Warning] InnoDB: Setting thread 29686 nice to 0 failed, current nice 10, errno 13
2014-08-04 15:15:06 28999 [Warning] InnoDB: Setting thread 29685 nice to 0 failed, current nice 10, errno 13
2014-08-04 15:15:06 28999 [Note] InnoDB: Percona XtraDB (http://
2014-08-04 15:15:06 28999 [Warning] InnoDB: Setting thread 29687 nice to 0 failed, current nice 10, errno 13
2014-08-04 15:15:06 28999 [Warning] InnoDB: Setting thread 29688 nice to 0 failed, current nice 10, errno 13
These messages are benign and caused by the thread scheduling priority implementation that attempts to nice every worker thread on startup. If no innodb_
A fix would be to add another value to innodb_
tags: | added: xtradb |
This seems to happen only once at the start of the server and as pointed before message are benign so I would prefer to leave it as is and add a documentation note.
Also, in either case we may need to notify user through a warning/note that we have failed to set the priority as requested.
I think current warning framework look good.