Skip to content
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.

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

BZ 1281733 -- Add section "Troubleshooting" to the MySQL chapter #1701

Merged
merged 1 commit into from Mar 17, 2016

Conversation

tnguyen-rh
Copy link

This is for BZ 1281733.

@mnagy
PTAL. You can also comment on the BZ.

MySQL configuration variable `innodb_use_native_aio`
to have value `0`.

1. Increase the `aio-max-nr` kernel resource.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I would mention that this is a per-node solution right here. "If you want to fix this, run this on your node".

@mnagy
Copy link

mnagy commented Mar 8, 2016

This is very good, at least technical-wise. Just a nit, LGTM

@tnguyen-rh
Copy link
Author

@bfallonf @tpoitras @ahardin-rh @adellape PTAL when you get a chance.

On subsequent deployments, this arranges for the
MySQL configuration variable `innodb_use_native_aio`
to have value `0`.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/ `MYSQL_AIO`/ `*MYSQL_AIO*`
s/ `innodb_use_native_aio`/ `*innodb_use_native_aio*`

(because they are configuration parameters/environment variables)

@ahardin-rh
Copy link
Contributor

Just one nit. LGTM! 👌

@tnguyen-rh
Copy link
Author

@ahardin-rh Thanks. I've modified the markup as you suggested.

@tnguyen-rh tnguyen-rh removed the peer-review-in-progress Signifies that the peer review team is reviewing this PR label Mar 15, 2016

.Explanation
MySQL's storage engine was unable to use of the kernel's
AIO (Asynchronous I/O) facilities due to resource limits.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think there's a typo in the above sentence. Should it be:

"MySQL's storage engine was unable to use the kernel's..."? Or "...make use of the kernel's..."?

@bfallonf
Copy link

Just the one typo, I think. Otherwise, LGTM!

@tnguyen-rh
Copy link
Author

@bfallonf
Good catch, thanks.

@tnguyen-rh
Copy link
Author

[rev_history]
|link:../using_images/db_images/mysql.html[MySQL Image]
|Added a link:../using_images/db_images/mysql.html#troubleshooting[Troubleshooting] section.
%

@tnguyen-rh tnguyen-rh added this to the Next Release milestone Mar 17, 2016
tnguyen-rh added a commit that referenced this pull request Mar 17, 2016
BZ 1281733 -- Add section "Troubleshooting" to the MySQL chapter
@tnguyen-rh tnguyen-rh merged commit 2b7677a into openshift:master Mar 17, 2016
@tnguyen-rh tnguyen-rh deleted the bz1281733 branch March 17, 2016 20:02
@tnguyen-rh tnguyen-rh modified the milestones: Next Release, Published - 2016-03-21 Mar 21, 2016
@tnguyen-rh tnguyen-rh removed this from the Next Release milestone Mar 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants