Percona Toolkit moved to https://jira.percona.com/projects/PT

Merge lp:~percona-toolkit-dev/percona-toolkit/update-relay-log-space-limit-docs-fix-bug-949154 into lp:percona-toolkit/2.0

  1. update-relay-log-space-limit-docs-fix-bug-949154
  2. Merge into 2.0
Proposed by Daniel Nichter
Status: Merged
Merged at revision: 219
Proposed branch: lp:~percona-toolkit-dev/percona-toolkit/update-relay-log-space-limit-docs-fix-bug-949154
Merge into: lp:percona-toolkit/2.0
Diff against target: 16 lines (+5/-2)
1 file modified
bin/pt-variable-advisor (+5/-2)
To merge this branch: bzr merge lp:~percona-toolkit-dev/percona-toolkit/update-relay-log-space-limit-docs-fix-bug-949154
Reviewer Review Type Date Requested Status
Daniel Nichter Approve
Review via email: mp+99454@code.launchpad.net
To post a comment you must log in.
Revision history for this message
Daniel Nichter (daniel-nichter) :
review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'bin/pt-variable-advisor'
2--- bin/pt-variable-advisor 2012-03-07 23:41:54 +0000
3+++ bin/pt-variable-advisor 2012-03-27 00:04:21 +0000
4@@ -3452,8 +3452,11 @@
5
6 severity: warn
7
8-Setting relay_log_space_limit is relatively rare, and could cause
9-an increased risk of previously unknown bugs in replication.
10+Setting relay_log_space_limit can cause replicas to stop fetching binary logs
11+from their master immediately. This could increase the risk that your data will
12+be lost if the master crashes. If the replicas have encountered a limit on relay
13+log space, then it is possible that the latest transactions exist only on the
14+master and no replica has retrieved them.
15
16 =item slave_net_timeout
17

Subscribers

People subscribed via source and target branches