Bug #40873 Cluster rolling upgrade/downgrade docs don't specify --initial
Submitted: 20 Nov 2008 1:18 Modified: 16 Apr 2012 16:40
Reporter: Mikiya Okuno Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:all OS:Any
Assigned to: MySQL Verification Team CPU Architecture:Any

[20 Nov 2008 1:18] Mikiya Okuno

These pages are missing an important information, which is if we need to specify --initial option to ndbd when doing rolling upgrade/downgrade. Stewert said that --initial option is required between some versions, but not every time. Please clarify when --initial option is required and write it to the reference manual.

I think it is safe to use --initial option everytime when upgrade/downgrade. So, the alternative is to make it default to use --initial option.

How to repeat:

Suggested fix:
[20 Nov 2008 5:44] Jon Stephens
Updated synopsis to state nature of problem.
[3 Dec 2008 9:51] Jon Stephens
Discussed this issue with Jonas. He suggests that the best (and probably only) way to determine this is by testing an online upgrade between every Cluster release and the next higher one. I don't really have the resources to do this in a reasonable length of time - perhaps you can get someone in Support or QA to do so and then supply the results in this bug report.

[3 Dec 2008 10:00] Jon Stephens
BTW, Jonas also pointed out to me that we probably *don't* want to tell people "Just use --initial for all online upgrades" since this can make node restarts quite slow!
[28 May 2009 8:59] Jon Stephens
Reassigning to Mikiya as a reminder that I can't proceed until I have the needed info.
[16 Apr 2012 16:40] Jon Stephens
No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you.