Skip to content

PXC-4796 [DOCS] - Document SST Post-processing Timeout in Large Insta… #292

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
patrickbirch wants to merge 1 commit into
base: 8.4
Choose a base branch
from
Open

PXC-4796 [DOCS] - Document SST Post-processing Timeout in Large Insta… #292

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions docs/xtrabackup-sst.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -318,6 +318,24 @@ An example of setting the option:
sst-idle-timeout=0
```

### post-processing-timeout

| Parameter | Description |
| -------------- | ------------------ |
| Default: | 300 |
| Unit: | seconds |

The maximum time the State Snapshot Transfer (SST) procedure waits for the newly provisioned MySQL instance to complete its shutdown or startup. During shutdown, the procedure waits until the process is no longer alive or the Process ID (PID) cleanup completes. During startup, the procedure waits until the procedure successfully connects to the MySQL server.

The `wsrep_sst_common.sh` script reads this variable from the configuration file to set the timeout value. For more information about when to increase this value, see [Troubleshoot](#troubleshoot).

An example of setting the option:

```{.text .no-copy}
[sst]
post-processing-timeout=600
```

### tmpdir

| Parameter | Description |
Expand Down Expand Up @@ -458,3 +476,9 @@ the size of the InnoDB memory buffer will be used:
[mysqld]
innodb_buffer_pool_size=24M
```

## Troubleshoot

| Problem | Possible Cause | Solution |
|---------|---------------|----------|
| SST procedure aborts during post-processing phase | The post-processing phase takes more than 300 seconds to complete. The timeout occurs on systems with Non-Uniform Memory Access (NUMA) architecture when you have large InnoDB Buffer Pools and the `innodb_numa_interleave` variable is enabled. When `innodb_numa_interleave` is active, the memory initialization process for the large InnoDB Buffer Pool can be significantly slower, leading to the MySQL instance taking more than the default 300 seconds to become responsive. The SST script, which monitors the instance start-up and shut down, times out and aborts the entire procedure. When the timeout is reached, the SST procedure stops and the joining node cannot join the cluster. | Set a higher value for [`post-processing-timeout`](#post-processing-timeout) in the `[sst]` section of your configuration file. You can also disable the `innodb_numa_interleave` variable if you do not need it. |
Loading