Re: MySQL grant use?
Am 24. Jul, 2010 schwätzte Alex Dean so: moin moin, I think you should consider replicating to multiple slaves. 1 is for backup, and is totally read-only. That's my goal. First I need to get all of the DBen going to at least one slave and make sure we've backing up everything that needs to be backed up. http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html#sysvar_read_only This is per DB? If db1 is a slave DB, I can set it as read-only, but keep db2, which is a local DB, as read-write? Another slave, for reporting, can have more relaxed rules. If people want to mess with the data there, no harm. If they screw it up too horribly, restore a backup onto the reporting database and continue as before. You need to get I still want the replicated parts to be read-only. Yes, I want reporting environments seperate from production slaves. them to script any changes they're making, so they're easy to re-apply after you restore the testing database. (If there are certain columns they add, or aggregating tables they find useful, they should be able to run 1 script to re-create them. This removes the we can't restore, it'll ruin all my custom work! complaint.) Great idea. This will be the hardest to push through, but I think we can do it. Plan to periodically take a backup from your live database, and use that re-init your slaves. MySQL replication is quite good, but I still have seen some odd situations where replication can mess up. Since a full live diff of the 2 servers (which would check all data and verify you're in sync) isn't really feasible, I think it's safest to take backups from the prod server on a somewhat-infrequent basis. I'll have to think about this one. I see your point and agree with it. I might instead tackle it via audits. I like audits for the potential of catching slow corruption. Might do both :). ciao, der.hans -- # http://www.LuftHans.com/Classeshttp://www.TwoGeekTechs.com/ # Director of Engineering, FonWallet Transaction Solutions, Inc. # Fairy Tale, n.: A horror story to prepare children for the newspapers.--- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: MySQL grant use?
Am 24. Jul, 2010 schwätzte Bryan O'Neal so: I agree with Alex but this just follows logical design of separation. You dev, qa, prod, ha, and dr environments should be separated and used for those set purposes. Unfortunately I also know that if this most elementary step has not been take it is usually due to a lack of required resources not simple oversight. But even if you do that should not replace the monitoring scripts or, as you mentioned, the commitment to repeatable and documented automated operations. Yeah, monitoring and auditing are going in everywhere. We're also automating everything on the sysadmin side. Getting dev to do that is more complex, but will be happening. BTW Alex if all you want to do is verify you are in sync you can do a checksum on the tables in both servers. If they are in sync the checksums will match - again, great automated monitoring check. What verifying myisam and innodb copies of the same data are exactly the same? Actually, I want something that will diff them and apply the diff to the innodb side. I'm needing to convert a very busy production myisam table that is somewhat humongous to innodb and the conversion takes longer than the maintenance windows. For testing, I did a cp of the data files, copied them to a different machine and did the conversion. I now need to quickly determine what's missing and copy it over. If rows don't change, then it's just a matter of select * from orig where index_id ( select max(index_id) from copy ). Not sure what to do if rows get changed. ciao, der.hans -- # http://www.LuftHans.com/Classeshttp://www.TwoGeekTechs.com/ # Director of Engineering, FonWallet Transaction Solutions, Inc. # Science is magic explained. - der.hans--- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: MySQL grant use?
Am 24. Jul, 2010 schwätzte Bryan O'Neal so: Sadly Number of physical boxes is usually not the issue with resource bottle neck; it is that you are always running close to capacity and can not convince anyone to purchase more equipment because things are running fine. Double the number of fsyncs on a box and then you get a Luckily, we can get equipment if we need it, within reason. This will be especially so if I can reduce the number of boxen required for our product :). complaint that everything runs too slow and it must have been something you did so undo it :( With checksum - I am more then willing to admit I have not done any production MySQL work in a while but I remember that it could be done live. Also indicated in the manual. Ah, I was thinking you meant a checksum on the files, I will have to investigate the internal checksum. Would be great to be able to use it for auditing. Indeed, checksums in the logs with monitoring might be able to handle the detecting corruption issues Alex brought up. ciao, der.hans -- # http://www.LuftHans.com/Classeshttp://www.TwoGeekTechs.com/ # Director of Engineering, FonWallet Transaction Solutions, Inc. # When you are tired of choosing the lesser of two evils, # Vote Cthulhu for President!--- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: UK Government says, Dump Microsoft
Am 23. Jul, 2010 schwätzte keith smith so: It is great the Government is using some open source / free software. And they also released some into the public domain is great. I would also offer a word of caution - make sure any software the government released is free from any type of reporting code or a back door. The same as code from anyone else :). With Free Software we can do that type of validation. Proprietary software customers are depending on the company putting customer priorities higher than company priorities. ciao, der.hans -- # http://www.LuftHans.com/Classeshttp://www.TwoGeekTechs.com/ # Director of Engineering, FonWallet Transaction Solutions, Inc. # As we enjoy great Advantages from the # Inventions of others we should be glad of an # Opportunity to serve others by any Invention of ours, # and this we should do freely and generously. # -- Benjamin Franklin (1706-1790), on his refusal to patent his inventions.--- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: MySQL grant use?
replication is not always perfect in MySQL - Innodb is less pron to error but it still happens. Do your best to kill myisam. What verifying myisam and innodb copies of the same data are exactly the same? Actually, I want something that will diff them and apply the diff to the innodb side. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: MySQL grant use?
Read only I believe is a server wide var, but again, I am not certain. Replication should also be server wide , ie. no replication rules, including which databases should be considered for replication. Just recently learned what kind of problems it can cause otherwise. On Sun, Jul 25, 2010 at 12:56 AM, der.hans pl...@lufthans.com wrote: Am 24. Jul, 2010 schwätzte Alex Dean so: moin moin, I think you should consider replicating to multiple slaves. 1 is for backup, and is totally read-only. That's my goal. First I need to get all of the DBen going to at least one slave and make sure we've backing up everything that needs to be backed up. http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html#sysvar_read_only This is per DB? If db1 is a slave DB, I can set it as read-only, but keep db2, which is a local DB, as read-write? Another slave, for reporting, can have more relaxed rules. If people want to mess with the data there, no harm. If they screw it up too horribly, restore a backup onto the reporting database and continue as before. You need to get I still want the replicated parts to be read-only. Yes, I want reporting environments seperate from production slaves. them to script any changes they're making, so they're easy to re-apply after you restore the testing database. (If there are certain columns they add, or aggregating tables they find useful, they should be able to run 1 script to re-create them. This removes the we can't restore, it'll ruin all my custom work! complaint.) Great idea. This will be the hardest to push through, but I think we can do it. Plan to periodically take a backup from your live database, and use that re-init your slaves. MySQL replication is quite good, but I still have seen some odd situations where replication can mess up. Since a full live diff of the 2 servers (which would check all data and verify you're in sync) isn't really feasible, I think it's safest to take backups from the prod server on a somewhat-infrequent basis. I'll have to think about this one. I see your point and agree with it. I might instead tackle it via audits. I like audits for the potential of catching slow corruption. Might do both :). ciao, der.hans -- # http://www.LuftHans.com/Classes http://www.TwoGeekTechs.com/ # Director of Engineering, FonWallet Transaction Solutions, Inc. # Fairy Tale, n.: A horror story to prepare children for the newspapers. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
ABLEconf mtg Sunday night
moin moin, we're having an ABLEconf planning meeting Sunday night at 20:00 in the #ABLEconf IRC channel on Freenode. www.ABLEconf.com ciao, der.hans -- # http://www.LuftHans.com/Classeshttp://www.TwoGeekTechs.com/ # Director of Engineering, FonWallet Transaction Solutions, Inc. # so now the US army is sacrificing goats -- Alice Cooper, 15Sep2004 --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Saw this off Slashdot - 200 Linux machine
http://www.extremetech.com/article2/0,2845,2366841,00.asp It's not bad really for just a desktop to get online and type with. -- A mouse trap, placed on top of your alarm clock, will prevent you from rolling over and going back to sleep after you hit the snooze button. Stephen --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: MySQL grant use?
On Jul 25, 2010, at 3:03 AM, der.hans wrote: I'm needing to convert a very busy production myisam table that is somewhat humongous to innodb and the conversion takes longer than the maintenance windows. If you have a slave which is capable of becoming a production server, you can convert the slave to innodb. Let the conversion process take as long as it needs. Master is stil myisam, and slave is now innodb. Then during maintainence window, you take down the master and bind its IPs to the slave. Now you master is innodb. Needs testing, of course, but I believe this would work just fine. If you then set up the old master as a slave to the new master, you'll be able to switch back to using myisam on your master (as a saftey net). alex --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: MySQL grant use?
On 7/25/10 3:46 PM, Alex Dean wrote: On Jul 25, 2010, at 3:03 AM, der.hans wrote: I'm needing to convert a very busy production myisam table that is somewhat humongous to innodb and the conversion takes longer than the maintenance windows. If you have a slave which is capable of becoming a production server, you can convert the slave to innodb. Let the conversion process take as long as it needs. Master is stil myisam, and slave is now innodb. Then during maintainence window, you take down the master and bind its IPs to the slave. Now you master is innodb. Needs testing, of course, but I believe this would work just fine. If you then set up the old master as a slave to the new master, you'll be able to switch back to using myisam on your master (as a saftey net). There is a program in OpenBSd that can help with this. its called carp. you have 2 machines running, one the primary and the other the backup. if the main fails, carp kicks in and take possession if the relevant ip addresses (as far as your network is concerned, you never lost connectivity). I am not sure of they have a similar command in linux, but its worth checking on. this in combination with a live running backup of mysql would mean that you don't have to worry about manually changing ip's on the other box, it would be done automatically. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
