You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Use Percona Monitoring and Management (PMM) Advisors
2
2
3
-
[Percona Monitoring and Management (PMM)](https://www.percona.com/software/database-tools/percona-monitoring-and-management) provides several categories of Advisors. Each Advisor contains a set of automated checks. These checks investigate your database settings for a specific range of possible issues.
3
+
[Percona Monitoring and Management (PMM)](https://www.percona.com/software/database-
4
+
tools/percona-monitoring-and-management) provides several categories of Advisors.
5
+
Each Advisor contains a set of automated checks. These checks investigate your
6
+
database settings for a specific range of possible issues.
4
7
5
-
[The Percona Platform](https://www.percona.com/software/percona-platform) hosts the Advisors.
8
+
The PMM Server automatically downloads the Advisors if the `Advisors` and
9
+
`Telemetry` options are enabled in `Configuration > Settings > Advanced Settings`.
10
+
Both options are enabled by default.
6
11
7
-
The PMM Server automatically downloads the Advisors if the `Advisors` and `Telemetry` options are enabled in `Configuration > Settings > Advanced Settings`. Both options are enabled by default.
12
+
!!! note "Need Additional Guidance?"
13
+
If you encounter complex advisor recommendations or require expert
When a server subsystem tries to access a corrupted table,
4
-
the server may crash.
5
-
If this outcome is not desirable when a corrupted table is encountered,
6
-
set the new system innodb_corrupt_table_action variable
7
-
to a value which allows the ongoing operation to continue
4
+
the server may crash. If this outcome is not desirable when a corrupted
5
+
table is encountered, set the new system innodb_corrupt_table_action
6
+
variable to a value which allows the ongoing operation to continue
8
7
without crashing the server.
9
8
10
9
The server error log registers attempts to access corrupted table pages.
11
10
12
11
### Interacting with the innodb_force_recovery variable
13
12
14
-
The innodb_corrupt_table_action variable
15
-
may work in conjunction with the innodb_force_recovery variable
16
-
which considerably reduces
17
-
the effect of *InnoDB* subsystems
18
-
running in the background.
13
+
The innodb_corrupt_table_action variable may work in conjunction with
14
+
the innodb_force_recovery variable which considerably reduces the effect
15
+
of *InnoDB* subsystems running in the background.
19
16
20
-
If the innodb_force_recovery option is <4, corrupted pages are lost and the server may continue to run due to the innodb_corrupt_table_action variable having a non-default value.
17
+
If the innodb_force_recovery option is <4, corrupted pages are lost and
18
+
the server may continue to run due to the innodb_corrupt_table_action
19
+
variable having a non-default value.
21
20
22
-
For more information about the innodb_force_recovery variable, see [Forcing InnoDB Recovery] from the MySQL Reference Manual.
21
+
!!! warning "Complex Database Recovery Scenarios"
22
+
Navigating table corruption and recovery can be challenging.
expert guidance for complex database recovery and optimization
25
+
strategies.
23
26
24
-
This feature adds a system variable.
27
+
For more information about the innodb_force_recovery variable, see
28
+
[Forcing InnoDB Recovery] from the MySQL Reference Manual.
25
29
30
+
This feature adds a system variable.
26
31
27
32
## System variables
28
33
@@ -38,10 +43,19 @@ This feature adds a system variable.
38
43
| Default | assert |
39
44
| Range | assert, warn, salvage |
40
45
41
-
* Enabling `innodb_file_per_table` and using the `assert` value creates an assertion failure which causes *XtraDB* to intentionally crash the server. This action is expected when detecting corrupted data in a single-table tablespace.
46
+
* Enabling `innodb_file_per_table` and using the `assert` value creates
47
+
an assertion failure which causes *XtraDB* to intentionally crash the
48
+
server. This action is expected when detecting corrupted data in a
49
+
single-table tablespace.
42
50
43
-
* Enabling `innodb_file_per_table` and using the `warn` value causes *XtraDB* to pass the table corruption as `corrupt table` instead of crashing the server. Detecting the file as corrupt also disables the file I/O for that data file, except for the deletion operation.
51
+
* Enabling `innodb_file_per_table` and using the `warn` value causes
52
+
*XtraDB* to pass the table corruption as `corrupt table` instead of
53
+
crashing the server. Detecting the file as corrupt also disables the
54
+
file I/O for that data file, except for the deletion operation.
44
55
45
-
* Enabling `innodb_file_per_table` and using the `salvage` value causes *XtraDB* to allow read access to the corrupted tablespace but ignores any corrupted pages.
56
+
* Enabling `innodb_file_per_table` and using the `salvage` value causes
57
+
*XtraDB* to allow read access to the corrupted tablespace but ignores
Developers use the stack trace in the debug process, either an interactive investigation or during the post-mortem. No configuration is required to generate a stack trace.
3
+
Developers use the stack trace in the debug process, either an interactive
4
+
investigation or during the post-mortem. No configuration is required to
| Prints binary BuildID | The Strip utility removes unneeded sections and debugging information to reduce the size. This method is standard with containers where the size of the image is essential. The BuildID lets you resolve the stack trace when the Strip utility removes the binary symbols table. |
11
-
| Print the server version information | The version information establishes the starting point for analysis. Some applications, such as MySQL, only print this information to a log on startup, and when the crash occurs, the size of the log may be large, rotated, or truncated. |
Copy file name to clipboardExpand all lines: docs/thread-based-profiling.md
+18-3Lines changed: 18 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,22 @@
1
1
# Thread based profiling
2
2
3
-
Percona Server for MySQL now uses thread based profiling by default, instead of process based profiling. This was implemented because with process based profiling, threads on the server, other than the one being profiled, can affect the profiling information.
3
+
Percona Server for MySQL now uses thread based profiling by default,
4
+
instead of process based profiling. This was implemented because with
5
+
process based profiling, threads on the server, other than the one being
6
+
profiled, can affect the profiling information.
4
7
5
-
Thread based profiling is using the information provided by the kernel [getrusage](https://kernel.org/doc/man-pages/online/pages/man2/getrusage.2.html) function. Since the 2.6.26 kernel version, thread based resource usage is available with the **RUSAGE_THREAD**. This means that the thread based profiling will be used if you’re running the 2.6.26 kernel or newer, or if the **RUSAGE_THREAD** has been ported back.
8
+
Thread based profiling is using the information provided by the kernel
0 commit comments