Hello folks,
Due to a trademark issue with MySQL AB, I had to rename the project, mysql-ha is now called highbase.
As part of the change, I've migrated the site to Geeklog, in order to make it easier for me to maintain it and communicate with my users.
Therefore, this blog is now out of purpose and will be deprecated :)
Be sure to stay tuned by checking the new site here.
Thanks for all the downloads, today I've released beta-0.8 and if you send me more
bug reports I expect to get a release candidate real soon.
Kind regards,
Fernando.
Thursday, November 15, 2007
Saturday, September 01, 2007
beta-0-8 or rc-1 comming soon
After a long hiatus, I've commited to svn the last bug fixes to important issues.
I'm doing some more testing this weekend, and depending on these results, I'll be releasing
beta-08 or rc-1 next week.
In the meantime, you can view the current tree here, and if you can do your own testing
you'll be more than welcome (the Installation Guide is updated on svn already, in ODT
format, the PDF and HTML will be available with the release.
Stay tuned..
I'm doing some more testing this weekend, and depending on these results, I'll be releasing
beta-08 or rc-1 next week.
In the meantime, you can view the current tree here, and if you can do your own testing
you'll be more than welcome (the Installation Guide is updated on svn already, in ODT
format, the PDF and HTML will be available with the release.
Stay tuned..
Thursday, July 05, 2007
I'm reunited with my notebook
After almost a month of suffering through tech support, I have my notebook back.
Expect a new release next week.
In the past days, I've been working in a minimal PHP framework based on the dispatch page described by the PHP Security Consortium, called Zazen
Zazen is MVC taken to the minimum expression, and oriented towards security. It includes functions to obtain user provided variables after filtering them through perl compatible regular expressions.
Zazen is also the first project on which I'm using bazaar for version control. It's great and I'm really happy.
I expect to have a web site and a sourceforge project page ready by this weekend.
A copy of the bazaar repository might be available earlier.
Stay tuned!
Expect a new release next week.
In the past days, I've been working in a minimal PHP framework based on the dispatch page described by the PHP Security Consortium, called Zazen
Zazen is MVC taken to the minimum expression, and oriented towards security. It includes functions to obtain user provided variables after filtering them through perl compatible regular expressions.
Zazen is also the first project on which I'm using bazaar for version control. It's great and I'm really happy.
I expect to have a web site and a sourceforge project page ready by this weekend.
A copy of the bazaar repository might be available earlier.
Stay tuned!
Monday, June 18, 2007
why HP/Compaq's support is FUBAR
My notebook's keyboard/touchpad died last week. Actually, it died on jun 7.
It's a Presario V2617LA, and GNU/Linux runs quite smoothly on it, as I've stated here previously.
That wouldn't be much of an issue on itself. Notebooks have hardware issues from time to time, and I tend to be a little rough on my keyboards, since I learned to type on a mechanical typing machine.
However, when I called the regional support from HP for the warranty (the machine is less than 1 year old), I had to suffer patiently for about 15 minutes of dumb questions until the tech support guy finally asked:
TS: So, Is windows able to boot, or does the machine hung at the very begining?
Me: The machine has GNU/Linux, but it boots perfectly. It's the keyboard and the touch pad that don't work
TS: Oh, so you installed Linux and the keyboard stopped working?
Me: No, I installed GNU/Linux the day I bought the computer and everything worked fine until today.
TS: Can you give me two minutes
(puts me on hold)
TS: I'm sorry sir, but we can't provide you with support if you have Linux. If you reinstall the version of Windows XP or Vista that
Me: The machine came with Windows XP
TS: .. um, the version that came with the computer, then when can give you support. We can send you the DVDs with ..
Me: I made a set of rescue DVDs before installing GNU/Linux.
TS: um, ok
Me: But if I install the rescue DVDs, I'll loose all the information that I currently have on my system
TS: Yes
That's basically their response.
In order to make use of my warranty, I'd have to plug in an external keyboard/mouse, make a backup of all my data, install the rescue DVDs, and once they've figured out that the keyboard and touch pad STILL DON'T F*****G work under windows, they'll replace it, and I'll have to reinstall GNU/Linux from scratch and restore my backups.
I have lots of work to do, so instead, o screwed the warranty, and decided to do the job as if the warranty had expired.
Only that I had the LOUSY idea to go to the official representative of HP/Compaq in Uruguay in order to keep the warranty (it's still useless to me, but just in case I sell the computer).
The machine's been there for 12 days and still no news.
But the overall behavior is typical HP (or at least typical HP LA, perhaps they're better in the US?):
All I know is this:
The computer is good. I've had good experiences with HP/Compaq in the past, with their hardware, that is. However, if you want to use GNU/Linux, go someplace else, or assume that you don't have a warranty.
I'm thinking about buying a Dell next time.
This is obviously delaying my development.
I'm going to have surgery tomorrow again, so between this and the computer issue, don't expect any svn activity for a few more days...
It's a Presario V2617LA, and GNU/Linux runs quite smoothly on it, as I've stated here previously.
That wouldn't be much of an issue on itself. Notebooks have hardware issues from time to time, and I tend to be a little rough on my keyboards, since I learned to type on a mechanical typing machine.
However, when I called the regional support from HP for the warranty (the machine is less than 1 year old), I had to suffer patiently for about 15 minutes of dumb questions until the tech support guy finally asked:
TS: So, Is windows able to boot, or does the machine hung at the very begining?
Me: The machine has GNU/Linux, but it boots perfectly. It's the keyboard and the touch pad that don't work
TS: Oh, so you installed Linux and the keyboard stopped working?
Me: No, I installed GNU/Linux the day I bought the computer and everything worked fine until today.
TS: Can you give me two minutes
(puts me on hold)
TS: I'm sorry sir, but we can't provide you with support if you have Linux. If you reinstall the version of Windows XP or Vista that
Me: The machine came with Windows XP
TS: .. um, the version that came with the computer, then when can give you support. We can send you the DVDs with ..
Me: I made a set of rescue DVDs before installing GNU/Linux.
TS: um, ok
Me: But if I install the rescue DVDs, I'll loose all the information that I currently have on my system
TS: Yes
That's basically their response.
In order to make use of my warranty, I'd have to plug in an external keyboard/mouse, make a backup of all my data, install the rescue DVDs, and once they've figured out that the keyboard and touch pad STILL DON'T F*****G work under windows, they'll replace it, and I'll have to reinstall GNU/Linux from scratch and restore my backups.
I have lots of work to do, so instead, o screwed the warranty, and decided to do the job as if the warranty had expired.
Only that I had the LOUSY idea to go to the official representative of HP/Compaq in Uruguay in order to keep the warranty (it's still useless to me, but just in case I sell the computer).
The machine's been there for 12 days and still no news.
But the overall behavior is typical HP (or at least typical HP LA, perhaps they're better in the US?):
- the day I leave the computer, the guy that receives it says I should call on monday
- on monday, someone tells me it's a mistake, I should call on wednesday
- on wednesday, someone tells me they need the power chord to do more tests.
- today, they tell me they need the password to do more tests. 'Oh, so is the keyboard at least partially working?' The phone operator doesn't know. All they know is that the technician gets a login prompt and he asked for a password.
All I know is this:
The computer is good. I've had good experiences with HP/Compaq in the past, with their hardware, that is. However, if you want to use GNU/Linux, go someplace else, or assume that you don't have a warranty.
I'm thinking about buying a Dell next time.
This is obviously delaying my development.
I'm going to have surgery tomorrow again, so between this and the computer issue, don't expect any svn activity for a few more days...
Friday, May 18, 2007
beta-0.7: another round of fixes
Yeah yeah, monday never came :)
But here's another release, with a few bugfixes, the result of both internal and external testing.
Briefly:
And that's it. No rc-1 on sight, not until we get rid of these bugs.
While I wait, I'm working on a sister tool to monitor MySQL servers and check the status variables, according to the information found on the manual. I have a working version that I've used in-house in
java, but I want to release something in python, perl, or some other language that poses no barrier of adoption for the user (I don't want people to have to install anything in order to run this).
I'll keep you posted.
But here's another release, with a few bugfixes, the result of both internal and external testing.
Briefly:
- MASTER_NODE was wrongly referenced in a few places instead of CLUSTER_IP, resulting in some error conditions not being detected. This is now fixed.
- The path to some programs wasn't portable across distributions. I added some code to compat.sh (which's purpose is precisely to contain all distribution specific code) and aparently this is a step in the right direction, but I'm waiting for feedback from the user.
And that's it. No rc-1 on sight, not until we get rid of these bugs.
While I wait, I'm working on a sister tool to monitor MySQL servers and check the status variables, according to the information found on the manual. I have a working version that I've used in-house in
java, but I want to release something in python, perl, or some other language that poses no barrier of adoption for the user (I don't want people to have to install anything in order to run this).
I'll keep you posted.
Friday, March 23, 2007
mysql-ha-erl trunk, rc-1 on monday
I've imported the new erlang tree into svn.
You can check it out at:
https://svn.sourceforge.net/svnroot/mysql-ha/trunk/mysql-ha-erl/
It's still at an early stage, but the slave routine is outlined and the skeleton works fine.
You can test it on just one node if you start two erlang shells with the proper -name parameters.
This tree uses an extended /etc/mysql-ha.conf file. I'll be documenting all this during the next few weeks.
In the meantime, I'll be releasing rc-1 on monday, with an updated Installation Guide.
Happy Spawning!
You can check it out at:
https://svn.sourceforge.net/svnroot/mysql-ha/trunk/mysql-ha-erl/
It's still at an early stage, but the slave routine is outlined and the skeleton works fine.
You can test it on just one node if you start two erlang shells with the proper -name parameters.
This tree uses an extended /etc/mysql-ha.conf file. I'll be documenting all this during the next few weeks.
In the meantime, I'll be releasing rc-1 on monday, with an updated Installation Guide.
Happy Spawning!
Saturday, March 10, 2007
an erlang fork and rc-1 comming soon
Hello all,
I'm back from my break, and while rc-1 isn't ready yet, it's really close now, I promise :)
I'm also working on a complete rewrite of the cluster in erlang. My original goal was to have a concrete project to do to learn the language, but now I've seen the light, and I honestly believe the erlang version will be better.
There's no svn trunk for this yet, I'll probably import it before the weekend is over so any interested party can take a peek. At the current rate, I expect a first release of beta quality by the end of march, with no need for ssh or ping, amongst other advantages of using erlang!
Back to the current almost stable tree, I expect to release rc-1 by thursday or friday, and after that, I'll work a bit again on the installer package, upgrade all the docs, etc.
As usual, any testing is welcome. We're now running on Fedora Core, CentOS (and that should mean RHEL, WhiteBox and Scientific) and we're almost there with Ubuntu and Debian.
After all the docs are up to date with rc-1, I'll just wait for any remaining bugs to show up and keep improving distro support (I have my eye on the BSDs too).
Regads,
I'm back from my break, and while rc-1 isn't ready yet, it's really close now, I promise :)
I'm also working on a complete rewrite of the cluster in erlang. My original goal was to have a concrete project to do to learn the language, but now I've seen the light, and I honestly believe the erlang version will be better.
There's no svn trunk for this yet, I'll probably import it before the weekend is over so any interested party can take a peek. At the current rate, I expect a first release of beta quality by the end of march, with no need for ssh or ping, amongst other advantages of using erlang!
Back to the current almost stable tree, I expect to release rc-1 by thursday or friday, and after that, I'll work a bit again on the installer package, upgrade all the docs, etc.
As usual, any testing is welcome. We're now running on Fedora Core, CentOS (and that should mean RHEL, WhiteBox and Scientific) and we're almost there with Ubuntu and Debian.
After all the docs are up to date with rc-1, I'll just wait for any remaining bugs to show up and keep improving distro support (I have my eye on the BSDs too).
Regads,
Friday, February 09, 2007
summer break
The project is entering a slow month right now.
I recently had a small procedure done to my back, and once I'm fully recovered, I expect to take a couple
of weeks off.
However, I will continue to work on the cluster, with no new features, just heavy testing, hoping to
come back with a release candidate by the end of the month.
Wish me luck :)
I recently had a small procedure done to my back, and once I'm fully recovered, I expect to take a couple
of weeks off.
However, I will continue to work on the cluster, with no new features, just heavy testing, hoping to
come back with a release candidate by the end of the month.
Wish me luck :)
Wednesday, January 17, 2007
beta-0.6.8 : thresholds up to microseconds!
beta-0.6.8 is out today.
This includes a fix for the startup procedure after a hard fail (the bug being that we couldn't start the
ssh-agent properly due to a conflict with the previous socket), and a major change in the thresholds system.
The cluster now supports thresholds in seconds (as up until now), milliseconds and microseconds (reliablilty depends on hardware, man usleep for more info).
I've changed all invocations to the sleep function for usleep, except in the main loops, and I'm giving admins the chance to express THRESHOLDS in seconds (no units), milliseconds (ms) and
microseconds (us) in /etc/mysql-ha.
The variables affected are:
MONITOR_CHK_THRESHOLD
MYSQL_KILL_WAIT
MYSQL_RESTART_WAIT
SIG_KILL_WAIT
This will be updated in the Installation Guide tomorrow.
I believe this gives administrators much more control over the cluster and takeover/recover time, though it needs proper documentation in the Guide, because if the values are too low for your environment (bad network, loaded server) you can have a false positive. Still, I've taken some good measures to prevent a false positive failover/takeover from happening.
Please go grab this, and happy clustering!
This includes a fix for the startup procedure after a hard fail (the bug being that we couldn't start the
ssh-agent properly due to a conflict with the previous socket), and a major change in the thresholds system.
The cluster now supports thresholds in seconds (as up until now), milliseconds and microseconds (reliablilty depends on hardware, man usleep for more info).
I've changed all invocations to the sleep function for usleep, except in the main loops, and I'm giving admins the chance to express THRESHOLDS in seconds (no units), milliseconds (ms) and
microseconds (us) in /etc/mysql-ha.
The variables affected are:
MONITOR_CHK_THRESHOLD
MYSQL_KILL_WAIT
MYSQL_RESTART_WAIT
SIG_KILL_WAIT
This will be updated in the Installation Guide tomorrow.
I believe this gives administrators much more control over the cluster and takeover/recover time, though it needs proper documentation in the Guide, because if the values are too low for your environment (bad network, loaded server) you can have a false positive. Still, I've taken some good measures to prevent a false positive failover/takeover from happening.
Please go grab this, and happy clustering!
Subscribe to:
Posts (Atom)