Percona Server moved to https://jira.percona.com/projects/PS

Documentation on crash resistant replication for 5.5 does not mention relay_log_recovery option

Bug #1406482 reported by Valerii Kravchuk on 2014-12-30

6

This bug affects 1 person

Affects

Status

Importance

Assigned to

Milestone

Percona Server moved to https://jira.percona.com/projects/PS

Invalid

Undecided

Unassigned

You need to log in to change this bug's status.

Affecting:	Percona Server moved to https://jira.percona.com/projects/PS
Filed here by:	Valerii Kravchuk
When:	2014-12-30
Completed:	2014-12-30

Target

Distribution
Package	(Find…)
Project	(Find…)

Status	Importance
	Undecided

Assigned to

	Nobody
	Me

Remote Watch

	None, the status of the bug is updated manually.
	None, the status of the bug is updated manually.
	URL:

The information about this bug in Launchpad is automatically pulled daily from the remote bug.

Comment on this change (optional)

Email me about changes to this bug report

5.1

Invalid

Undecided

Unassigned

You need to log in to change this bug's status.

Affecting:	Percona Server moved to https://jira.percona.com/projects/PS 5.1
Filed here by:	Valerii Kravchuk
When:	2014-12-30
Completed:	2014-12-30

Status	Importance
	Undecided

Assigned to

	Nobody
	Me

Remote Watch

	None, the status of the bug is updated manually.
	None, the status of the bug is updated manually.
	URL:

The information about this bug in Launchpad is automatically pulled daily from the remote bug.

Comment on this change (optional)

Email me about changes to this bug report

5.5

Fix Released

High

Hrvoje Matijakovic

You need to log in to change this bug's status.

Affecting:	Percona Server moved to https://jira.percona.com/projects/PS 5.5
Filed here by:	Valerii Kravchuk
When:	2014-12-30
Confirmed:	2014-12-30
Assigned:	2014-12-31
Started work:	2015-01-15
Completed:	2015-01-22

Status	Importance
	High

Assigned to

	Me
	Hrvoje Matijakovic (hrvojem)

Remote Watch

	None, the status of the bug is updated manually.
	None, the status of the bug is updated manually.
	URL:

The information about this bug in Launchpad is automatically pulled daily from the remote bug.

Comment on this change (optional)

Email me about changes to this bug report

5.6

Invalid

Undecided

Unassigned

You need to log in to change this bug's status.

Affecting:	Percona Server moved to https://jira.percona.com/projects/PS 5.6
Filed here by:	Valerii Kravchuk
When:	2014-12-30
Completed:	2014-12-30

Status	Importance
	Undecided

Assigned to

	Nobody
	Me

Remote Watch

	None, the status of the bug is updated manually.
	None, the status of the bug is updated manually.
	URL:

The information about this bug in Launchpad is automatically pulled daily from the remote bug.

Comment on this change (optional)

Email me about changes to this bug report

(?)

Bug Description

Based on numerous tests and checks from https://bugs.launchpad.net/percona-server/+bug/1239958 it seems one has to set --relay_log_recovery option to ON on Percona Server 5.5 for crash resistant replication to really work properly in some cases. Our documentation, http://www.percona.com/doc/percona-server/5.5/reliability/crash_resistant_replication.html, does not mention this though.

Tags: Edit Tag help

Related branches

lp:~hrvojem/percona-server/bug1406482-5.5

Merged into lp:percona-server/5.5 at revision 729

Laurynas Biveinis (community): Approve on 2015-01-22

Valerii Kravchuk (valerii-kravchuk) on 2014-12-30

tags:

added: i41005

Laurynas Biveinis (laurynas-biveinis) on 2014-12-31

tags:

added: crash-resistant-slave-5.5 doc

Shahriyar Rzayev (rzayev-sehriyar) wrote on 2018-01-25:

#1

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3246

Report a bug

This report contains Public information Edit

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers