mysql hardware refresh + version upgradeHow to upgrade MySQL to newer version on existing databaseWhich...
"Marked down as someone wanting to sell shares." What does that mean?
Travelling in US for more than 90 days
Reason why a kingside attack is not justified
What is this high flying aircraft over Pennsylvania?
What is it called when someone votes for an option that's not their first choice?
Error in master's thesis, I do not know what to do
What do the positive and negative (+/-) transmit and receive pins mean on Ethernet cables?
Comic-book: Kids find a dead female superhero in the woods
Derivative of an interpolated function
Do people actually use the word "kaputt" in conversation?
Exposing a company lying about themselves in a tightly knit industry (videogames) : Is my career at risk on the long run?
Are hand made posters acceptable in Academia?
Capacitor electron flow
Why didn’t Eve recognize the little cockroach as a living organism?
Relations between homogeneous polynomials
What should be the ideal length of sentences in a blog post for ease of reading?
I keep switching characters, how do I stop?
Did I make a mistake by ccing email to boss to others?
Mortal danger in mid-grade literature
How would a solely written language work mechanically
python displays `n` instead of breaking a line
Taking my research idea outside my paid job
Strange behavior in TikZ draw command
Is divisi notation needed for brass or woodwind in an orchestra?
mysql hardware refresh + version upgrade
How to upgrade MySQL to newer version on existing databaseWhich first: upgrade mysql version or convert storage engine?Scaling Percona datacenters: setup and replicationSoftware/Hardware UpgradeSteps to upgrade MySQL from version 5.0 to version 5.5MySQL 5.7 upgradeShould I run mysql_upgrade after minor version upgrade via RPM?MySQL Upgrade queryPostgres minor version upgradeHow to upgrade a MySQL database using numbered scripts based on a version field
currently I am running MySQL 5.0.80 on windows server 2003 (x64), 64gb memory, I have a master and 2 slaves. It's a large 400 gb Database. I am setting up all new hardware (SAN + dedicated MySQL servers with 256 gb memory running windows server 2008 r2. I need to come up with a good plan for moving everything over while minimizing downtime. Is it absolute truth that you cannot go from 5.0 to 5.6 even when using mysqldump to move the data? I was originally hoping to run mysqldump during off hours from master (don't fully trust the slaves data integrity), then make master available to users again while I source the sql files into a new 5.6 server and use it as a slave for a day or so until I knew all was well, then promote to master. Not sure that is feasible because of the jump in versions as well as the replicating (temporarily) from 5.0 to 5.6. Does anyone have suggestions as to a work plan for moving the master and two slaves onto new hardware with a version upgrade? Every time i dump the data it will take 5+ hours and sourcing it in even longer so I am trying to be smart about this since my organization is so sensitive to downtime. thank you.
mysql migration upgrade
asked Aug 12 '14 at 18:43
jasonjason
292
bumped to the homepage by Community♦ 4 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
currently I am running MySQL 5.0.80 on windows server 2003 (x64), 64gb memory, I have a master and 2 slaves. It's a large 400 gb Database. I am setting up all new hardware (SAN + dedicated MySQL servers with 256 gb memory running windows server 2008 r2. I need to come up with a good plan for moving everything over while minimizing downtime. Is it absolute truth that you cannot go from 5.0 to 5.6 even when using mysqldump to move the data? I was originally hoping to run mysqldump during off hours from master (don't fully trust the slaves data integrity), then make master available to users again while I source the sql files into a new 5.6 server and use it as a slave for a day or so until I knew all was well, then promote to master. Not sure that is feasible because of the jump in versions as well as the replicating (temporarily) from 5.0 to 5.6. Does anyone have suggestions as to a work plan for moving the master and two slaves onto new hardware with a version upgrade? Every time i dump the data it will take 5+ hours and sourcing it in even longer so I am trying to be smart about this since my organization is so sensitive to downtime. thank you.
mysql migration upgrade
asked Aug 12 '14 at 18:43
jasonjason
292
bumped to the homepage by Community♦ 4 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
5.0 -> 5.6 is a big change. I would upgrade slaves first, made sure they're in sync with the master (pt-table-checksum) let it run for awhile and then do promotion. You need to be able to switch back in case the app doesn't work well with 5.6
– akuzminsky
Aug 12 '14 at 19:11
and by 'upgrade slaves' you mean install a fresh 5.6, dump and import data and make it a slave to the 5.0 master?
– jason
Aug 12 '14 at 19:25
add a comment |
currently I am running MySQL 5.0.80 on windows server 2003 (x64), 64gb memory, I have a master and 2 slaves. It's a large 400 gb Database. I am setting up all new hardware (SAN + dedicated MySQL servers with 256 gb memory running windows server 2008 r2. I need to come up with a good plan for moving everything over while minimizing downtime. Is it absolute truth that you cannot go from 5.0 to 5.6 even when using mysqldump to move the data? I was originally hoping to run mysqldump during off hours from master (don't fully trust the slaves data integrity), then make master available to users again while I source the sql files into a new 5.6 server and use it as a slave for a day or so until I knew all was well, then promote to master. Not sure that is feasible because of the jump in versions as well as the replicating (temporarily) from 5.0 to 5.6. Does anyone have suggestions as to a work plan for moving the master and two slaves onto new hardware with a version upgrade? Every time i dump the data it will take 5+ hours and sourcing it in even longer so I am trying to be smart about this since my organization is so sensitive to downtime. thank you.
mysql migration upgrade
asked Aug 12 '14 at 18:43
jasonjason
292
currently I am running MySQL 5.0.80 on windows server 2003 (x64), 64gb memory, I have a master and 2 slaves. It's a large 400 gb Database. I am setting up all new hardware (SAN + dedicated MySQL servers with 256 gb memory running windows server 2008 r2. I need to come up with a good plan for moving everything over while minimizing downtime. Is it absolute truth that you cannot go from 5.0 to 5.6 even when using mysqldump to move the data? I was originally hoping to run mysqldump during off hours from master (don't fully trust the slaves data integrity), then make master available to users again while I source the sql files into a new 5.6 server and use it as a slave for a day or so until I knew all was well, then promote to master. Not sure that is feasible because of the jump in versions as well as the replicating (temporarily) from 5.0 to 5.6. Does anyone have suggestions as to a work plan for moving the master and two slaves onto new hardware with a version upgrade? Every time i dump the data it will take 5+ hours and sourcing it in even longer so I am trying to be smart about this since my organization is so sensitive to downtime. thank you.
mysql migration upgrade
mysql migration upgrade
asked Aug 12 '14 at 18:43
jasonjason
292
asked Aug 12 '14 at 18:43
jasonjason
292
asked Aug 12 '14 at 18:43
jasonjason
292
asked Aug 12 '14 at 18:43
jasonjason
292
asked Aug 12 '14 at 18:43
jasonjason
292
292
bumped to the homepage by Community♦ 4 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 4 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
5.0 -> 5.6 is a big change. I would upgrade slaves first, made sure they're in sync with the master (pt-table-checksum) let it run for awhile and then do promotion. You need to be able to switch back in case the app doesn't work well with 5.6
– akuzminsky
Aug 12 '14 at 19:11
and by 'upgrade slaves' you mean install a fresh 5.6, dump and import data and make it a slave to the 5.0 master?
– jason
Aug 12 '14 at 19:25
add a comment |
5.0 -> 5.6 is a big change. I would upgrade slaves first, made sure they're in sync with the master (pt-table-checksum) let it run for awhile and then do promotion. You need to be able to switch back in case the app doesn't work well with 5.6
– akuzminsky
Aug 12 '14 at 19:11
and by 'upgrade slaves' you mean install a fresh 5.6, dump and import data and make it a slave to the 5.0 master?
– jason
Aug 12 '14 at 19:25
5.0 -> 5.6 is a big change. I would upgrade slaves first, made sure they're in sync with the master (pt-table-checksum) let it run for awhile and then do promotion. You need to be able to switch back in case the app doesn't work well with 5.6
– akuzminsky
Aug 12 '14 at 19:11
5.0 -> 5.6 is a big change. I would upgrade slaves first, made sure they're in sync with the master (pt-table-checksum) let it run for awhile and then do promotion. You need to be able to switch back in case the app doesn't work well with 5.6
– akuzminsky
Aug 12 '14 at 19:11
and by 'upgrade slaves' you mean install a fresh 5.6, dump and import data and make it a slave to the 5.0 master?
– jason
Aug 12 '14 at 19:25
and by 'upgrade slaves' you mean install a fresh 5.6, dump and import data and make it a slave to the 5.0 master?
– jason
Aug 12 '14 at 19:25
add a comment |
1 Answer
1
active
oldest
votes
I think your plan is largely sound, and is how I handled a similar upgarde (albeit 5.0 > 5.5). What I did was to take a Dump from the Master in the quiet hours like you said, and then set up a new Slave on one of the new 2008r2 boxes.
This allows you time to 'play' with the new 5.6 database so you can tweak the config, and make sure the data replicates correctly.
Bearing in mind that as akuzminsky mentioned 5.0 > 5.6 is a big change, and a lot of things will have changed (binlog_format and GTID to name two of the big ones), and various settings will have been deprecated, or removed entireley.
In this way you get to keep the original Master and two slaves in production use, whilst you get up to speed with the 5.6 database. You can also repeat the process with a fresh install and different settings if things don't quite work as planned.
Once you are happy with the new slave, then you can set up two additional 5.6 slaves connected to the new 5.6 database giving you a new 5.6 system (master and two slaves), allowing you to do more checks.
Finally, once you are completely happy with the new 5.6 system, you can then simply move your application(s) to look at the new master and slaves at a convenient time.
Also, a bit of advice from someone that's been there, keep an eye on your error logs on the new servers. The later versions are more sensitive to errors, and I suddenly found my error logs filling up very quickly, requiring a bit of time to re-write some of the queries in our applications to make them 'replication safe'.
answered Aug 13 '14 at 8:03
IGGtIGGt
9971026
thank you, your summary makes me feel better about my plan. What about MySQL's documentation indicating you have to follow the path 5.0=>5.1=>5.5=>5.6 ?? That seems safe but very time and resource intensive. It sounds like guys by and large are are not doing that. Does using mySqlDump to move the data negate that warning?
– jason
Aug 13 '14 at 13:12
also do I have reason to be concerned about the interem time I will be replicating from 5.0 to 5.6?
– jason
Aug 13 '14 at 13:15
I think the 5.0=>5.1=>5.5=>5.6 they mention is if you were upgrading your server in place, rather than creating a completely new instance of it. As far as I know MySQLDump should work OK, it's going the other way (5.6 > 5.5 or less) that can be problematic. Also remember to run mysql-upgrade if you include the MySQL tables, as there are structural changes in these.
– IGGt
Aug 13 '14 at 13:58
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f73802%2fmysql-hardware-refresh-version-upgrade%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I think your plan is largely sound, and is how I handled a similar upgarde (albeit 5.0 > 5.5). What I did was to take a Dump from the Master in the quiet hours like you said, and then set up a new Slave on one of the new 2008r2 boxes.
This allows you time to 'play' with the new 5.6 database so you can tweak the config, and make sure the data replicates correctly.
Bearing in mind that as akuzminsky mentioned 5.0 > 5.6 is a big change, and a lot of things will have changed (binlog_format and GTID to name two of the big ones), and various settings will have been deprecated, or removed entireley.
In this way you get to keep the original Master and two slaves in production use, whilst you get up to speed with the 5.6 database. You can also repeat the process with a fresh install and different settings if things don't quite work as planned.
Once you are happy with the new slave, then you can set up two additional 5.6 slaves connected to the new 5.6 database giving you a new 5.6 system (master and two slaves), allowing you to do more checks.
Finally, once you are completely happy with the new 5.6 system, you can then simply move your application(s) to look at the new master and slaves at a convenient time.
Also, a bit of advice from someone that's been there, keep an eye on your error logs on the new servers. The later versions are more sensitive to errors, and I suddenly found my error logs filling up very quickly, requiring a bit of time to re-write some of the queries in our applications to make them 'replication safe'.
answered Aug 13 '14 at 8:03
IGGtIGGt
9971026
thank you, your summary makes me feel better about my plan. What about MySQL's documentation indicating you have to follow the path 5.0=>5.1=>5.5=>5.6 ?? That seems safe but very time and resource intensive. It sounds like guys by and large are are not doing that. Does using mySqlDump to move the data negate that warning?
– jason
Aug 13 '14 at 13:12
also do I have reason to be concerned about the interem time I will be replicating from 5.0 to 5.6?
– jason
Aug 13 '14 at 13:15
I think the 5.0=>5.1=>5.5=>5.6 they mention is if you were upgrading your server in place, rather than creating a completely new instance of it. As far as I know MySQLDump should work OK, it's going the other way (5.6 > 5.5 or less) that can be problematic. Also remember to run mysql-upgrade if you include the MySQL tables, as there are structural changes in these.
– IGGt
Aug 13 '14 at 13:58
add a comment |
I think your plan is largely sound, and is how I handled a similar upgarde (albeit 5.0 > 5.5). What I did was to take a Dump from the Master in the quiet hours like you said, and then set up a new Slave on one of the new 2008r2 boxes.
This allows you time to 'play' with the new 5.6 database so you can tweak the config, and make sure the data replicates correctly.
Bearing in mind that as akuzminsky mentioned 5.0 > 5.6 is a big change, and a lot of things will have changed (binlog_format and GTID to name two of the big ones), and various settings will have been deprecated, or removed entireley.
In this way you get to keep the original Master and two slaves in production use, whilst you get up to speed with the 5.6 database. You can also repeat the process with a fresh install and different settings if things don't quite work as planned.
Once you are happy with the new slave, then you can set up two additional 5.6 slaves connected to the new 5.6 database giving you a new 5.6 system (master and two slaves), allowing you to do more checks.
Finally, once you are completely happy with the new 5.6 system, you can then simply move your application(s) to look at the new master and slaves at a convenient time.
Also, a bit of advice from someone that's been there, keep an eye on your error logs on the new servers. The later versions are more sensitive to errors, and I suddenly found my error logs filling up very quickly, requiring a bit of time to re-write some of the queries in our applications to make them 'replication safe'.
answered Aug 13 '14 at 8:03
IGGtIGGt
9971026
thank you, your summary makes me feel better about my plan. What about MySQL's documentation indicating you have to follow the path 5.0=>5.1=>5.5=>5.6 ?? That seems safe but very time and resource intensive. It sounds like guys by and large are are not doing that. Does using mySqlDump to move the data negate that warning?
– jason
Aug 13 '14 at 13:12
also do I have reason to be concerned about the interem time I will be replicating from 5.0 to 5.6?
– jason
Aug 13 '14 at 13:15
I think the 5.0=>5.1=>5.5=>5.6 they mention is if you were upgrading your server in place, rather than creating a completely new instance of it. As far as I know MySQLDump should work OK, it's going the other way (5.6 > 5.5 or less) that can be problematic. Also remember to run mysql-upgrade if you include the MySQL tables, as there are structural changes in these.
– IGGt
Aug 13 '14 at 13:58
add a comment |
I think your plan is largely sound, and is how I handled a similar upgarde (albeit 5.0 > 5.5). What I did was to take a Dump from the Master in the quiet hours like you said, and then set up a new Slave on one of the new 2008r2 boxes.
This allows you time to 'play' with the new 5.6 database so you can tweak the config, and make sure the data replicates correctly.
Bearing in mind that as akuzminsky mentioned 5.0 > 5.6 is a big change, and a lot of things will have changed (binlog_format and GTID to name two of the big ones), and various settings will have been deprecated, or removed entireley.
In this way you get to keep the original Master and two slaves in production use, whilst you get up to speed with the 5.6 database. You can also repeat the process with a fresh install and different settings if things don't quite work as planned.
Once you are happy with the new slave, then you can set up two additional 5.6 slaves connected to the new 5.6 database giving you a new 5.6 system (master and two slaves), allowing you to do more checks.
Finally, once you are completely happy with the new 5.6 system, you can then simply move your application(s) to look at the new master and slaves at a convenient time.
Also, a bit of advice from someone that's been there, keep an eye on your error logs on the new servers. The later versions are more sensitive to errors, and I suddenly found my error logs filling up very quickly, requiring a bit of time to re-write some of the queries in our applications to make them 'replication safe'.
answered Aug 13 '14 at 8:03
IGGtIGGt
9971026
I think your plan is largely sound, and is how I handled a similar upgarde (albeit 5.0 > 5.5). What I did was to take a Dump from the Master in the quiet hours like you said, and then set up a new Slave on one of the new 2008r2 boxes.
This allows you time to 'play' with the new 5.6 database so you can tweak the config, and make sure the data replicates correctly.
Bearing in mind that as akuzminsky mentioned 5.0 > 5.6 is a big change, and a lot of things will have changed (binlog_format and GTID to name two of the big ones), and various settings will have been deprecated, or removed entireley.
In this way you get to keep the original Master and two slaves in production use, whilst you get up to speed with the 5.6 database. You can also repeat the process with a fresh install and different settings if things don't quite work as planned.
Once you are happy with the new slave, then you can set up two additional 5.6 slaves connected to the new 5.6 database giving you a new 5.6 system (master and two slaves), allowing you to do more checks.
Finally, once you are completely happy with the new 5.6 system, you can then simply move your application(s) to look at the new master and slaves at a convenient time.
Also, a bit of advice from someone that's been there, keep an eye on your error logs on the new servers. The later versions are more sensitive to errors, and I suddenly found my error logs filling up very quickly, requiring a bit of time to re-write some of the queries in our applications to make them 'replication safe'.
answered Aug 13 '14 at 8:03
IGGtIGGt
9971026
answered Aug 13 '14 at 8:03
IGGtIGGt
9971026
answered Aug 13 '14 at 8:03
IGGtIGGt
9971026
answered Aug 13 '14 at 8:03
IGGtIGGt
9971026
9971026
thank you, your summary makes me feel better about my plan. What about MySQL's documentation indicating you have to follow the path 5.0=>5.1=>5.5=>5.6 ?? That seems safe but very time and resource intensive. It sounds like guys by and large are are not doing that. Does using mySqlDump to move the data negate that warning?
– jason
Aug 13 '14 at 13:12
also do I have reason to be concerned about the interem time I will be replicating from 5.0 to 5.6?
– jason
Aug 13 '14 at 13:15
I think the 5.0=>5.1=>5.5=>5.6 they mention is if you were upgrading your server in place, rather than creating a completely new instance of it. As far as I know MySQLDump should work OK, it's going the other way (5.6 > 5.5 or less) that can be problematic. Also remember to run mysql-upgrade if you include the MySQL tables, as there are structural changes in these.
– IGGt
Aug 13 '14 at 13:58
add a comment |
thank you, your summary makes me feel better about my plan. What about MySQL's documentation indicating you have to follow the path 5.0=>5.1=>5.5=>5.6 ?? That seems safe but very time and resource intensive. It sounds like guys by and large are are not doing that. Does using mySqlDump to move the data negate that warning?
– jason
Aug 13 '14 at 13:12
also do I have reason to be concerned about the interem time I will be replicating from 5.0 to 5.6?
– jason
Aug 13 '14 at 13:15
I think the 5.0=>5.1=>5.5=>5.6 they mention is if you were upgrading your server in place, rather than creating a completely new instance of it. As far as I know MySQLDump should work OK, it's going the other way (5.6 > 5.5 or less) that can be problematic. Also remember to run mysql-upgrade if you include the MySQL tables, as there are structural changes in these.
– IGGt
Aug 13 '14 at 13:58
thank you, your summary makes me feel better about my plan. What about MySQL's documentation indicating you have to follow the path 5.0=>5.1=>5.5=>5.6 ?? That seems safe but very time and resource intensive. It sounds like guys by and large are are not doing that. Does using mySqlDump to move the data negate that warning?
– jason
Aug 13 '14 at 13:12
thank you, your summary makes me feel better about my plan. What about MySQL's documentation indicating you have to follow the path 5.0=>5.1=>5.5=>5.6 ?? That seems safe but very time and resource intensive. It sounds like guys by and large are are not doing that. Does using mySqlDump to move the data negate that warning?
– jason
Aug 13 '14 at 13:12
also do I have reason to be concerned about the interem time I will be replicating from 5.0 to 5.6?
– jason
Aug 13 '14 at 13:15
also do I have reason to be concerned about the interem time I will be replicating from 5.0 to 5.6?
– jason
Aug 13 '14 at 13:15
I think the 5.0=>5.1=>5.5=>5.6 they mention is if you were upgrading your server in place, rather than creating a completely new instance of it. As far as I know MySQLDump should work OK, it's going the other way (5.6 > 5.5 or less) that can be problematic. Also remember to run mysql-upgrade if you include the MySQL tables, as there are structural changes in these.
– IGGt
Aug 13 '14 at 13:58
I think the 5.0=>5.1=>5.5=>5.6 they mention is if you were upgrading your server in place, rather than creating a completely new instance of it. As far as I know MySQLDump should work OK, it's going the other way (5.6 > 5.5 or less) that can be problematic. Also remember to run mysql-upgrade if you include the MySQL tables, as there are structural changes in these.
– IGGt
Aug 13 '14 at 13:58
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f73802%2fmysql-hardware-refresh-version-upgrade%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
5.0 -> 5.6 is a big change. I would upgrade slaves first, made sure they're in sync with the master (pt-table-checksum) let it run for awhile and then do promotion. You need to be able to switch back in case the app doesn't work well with 5.6
– akuzminsky
Aug 12 '14 at 19:11
and by 'upgrade slaves' you mean install a fresh 5.6, dump and import data and make it a slave to the 5.0 master?
– jason
Aug 12 '14 at 19:25