FLORIAN'S BLOG

Know how they say that you don’t know you’re doing something right until someone starts imitating you? Well, this is a great time for us. Someone evidently took a good long read of our hastexo High Availability Expert class agenda, and made this.It’s wonderful for us to see that it’s such an inspiration to others (even the acronym!), and we hope to see more folks doing this in the future. PERFORMANCE TUNING DRBD SETUPS Start your optimization efforts without DRBD, and when you’ve found your best setup, add DRBD to the mix. Secondly, ensure controlled experimentation. Performance tuning is boring and tedious work when done right, so don’t expect to be having a lot of fun. Do record your experimental setups in a reproducible fashion.

FLORIAN'S BLOG

After last year’s talk in Brisbane, where I greatly enjoyed co-presenting with Tim Serong, I have the privilege of returning to Australia for this year’s linux.conf.au in Ballarat, Victoria.. This time I have a brief talk opening up the High Availability and Distributed Storage miniconf on Monday, January 16, and a tutorial entitled High Availability Sprint in the morning on Thursday INTERNAL METADATA, AND WHY WE RECOMMEND IT Internal metadata, and why we recommend it. One of the things that repeatedly seem to puzzle users about the DRBD is the question of whether to use internal or external metadata. Remember, DRBD sets aside a small area on a local disk (on every cluster node) where it keeps the Activity Log, the quick-sync bitmap, data generation UUIDs,

and a few

CHECKING YOUR SECONDARY’S INTEGRITY Suppose you run into the following situation: you've suffered the effects of a nasty bug hidden somewhere deep inside your network stack. Say your NIC screwed up checksum offloading, or some network driver caused a kernel panic. Either way, you have reason to believe that some portion of the data you sent over that wire DRBD LIMITATIONS (OR ARE THEY?) I've recently received one database admin's personal list of DRBD's perceived limitations. While I'm certainly the last person to say that DRBD is limitation-free (hey, it's software), I'd like to address these specifically -- because really, in my humble opinion, most of them aren't limitations at all. The Secondary host sits idle, that's

wasted investment.

ON DRBD CONNECTION TIMEOUTS DRBD sends these “pings” in a configurable interval, specified by the ping-int configuration option and defaulting to 10 seconds. DRBD “pings” time out within the time specified as ping-timeout, which by default is 0.5 seconds. So: while I/O is being issued DUAL-PRIMARY DRBD, ISCSI, AND MULTIPATH: DON’T DO THAT Excuse that deliberately Google-optimized blunt and inelegant title, folks, but this is getting old. If you run dual-Primary DRBD, and then export an iSCSI target from both nodes, and then you want to to do dm-multipath or somesuch for what you think constitutes failover, don't do that. There. Bold and italics. Really and truly, don't. DRBD AND MYSQL: JUST SAY YES DRBD partition corruption means failover node would be unusable (disadvantage of shared storage) and failback could destroy original master too. If the filesystem that sits on top of DRBD gets corrupted, it will be equally corrupted on the peer node after failover. DRBD is a block device; it is agnostic of layers above it. WHEN NOT TO USE DRBD This is a good article and makes a lot of sense I have used DRBD with LAMP stacks and mysql very effectivly for some fairly large scale projects,with scheduled mysql db hot copies from a slave,running hourly and a remote location for DR and of course we use RSYNC the static stuff as well.

FLORIAN'S BLOG

Know how they say that you don’t know you’re doing something right until someone starts imitating you? Well, this is a great time for us. Someone evidently took a good long read of our hastexo High Availability Expert class agenda, and made this.It’s wonderful for us to see that it’s such an inspiration to others (even the acronym!), and we hope to see more folks doing this in the future. PERFORMANCE TUNING DRBD SETUPS Start your optimization efforts without DRBD, and when you’ve found your best setup, add DRBD to the mix. Secondly, ensure controlled experimentation. Performance tuning is boring and tedious work when done right, so don’t expect to be having a lot of fun. Do record your experimental setups in a reproducible fashion.

FLORIAN'S BLOG

After last year’s talk in Brisbane, where I greatly enjoyed co-presenting with Tim Serong, I have the privilege of returning to Australia for this year’s linux.conf.au in Ballarat, Victoria.. This time I have a brief talk opening up the High Availability and Distributed Storage miniconf on Monday, January 16, and a tutorial entitled High Availability Sprint in the morning on Thursday INTERNAL METADATA, AND WHY WE RECOMMEND IT Internal metadata, and why we recommend it. One of the things that repeatedly seem to puzzle users about the DRBD is the question of whether to use internal or external metadata. Remember, DRBD sets aside a small area on a local disk (on every cluster node) where it keeps the Activity Log, the quick-sync bitmap, data generation UUIDs,

and a few

CHECKING YOUR SECONDARY’S INTEGRITY Suppose you run into the following situation: you've suffered the effects of a nasty bug hidden somewhere deep inside your network stack. Say your NIC screwed up checksum offloading, or some network driver caused a kernel panic. Either way, you have reason to believe that some portion of the data you sent over that wire DRBD LIMITATIONS (OR ARE THEY?) I've recently received one database admin's personal list of DRBD's perceived limitations. While I'm certainly the last person to say that DRBD is limitation-free (hey, it's software), I'd like to address these specifically -- because really, in my humble opinion, most of them aren't limitations at all. The Secondary host sits idle, that's

wasted investment.

ON DRBD CONNECTION TIMEOUTS DRBD sends these “pings” in a configurable interval, specified by the ping-int configuration option and defaulting to 10 seconds. DRBD “pings” time out within the time specified as ping-timeout, which by default is 0.5 seconds. So: while I/O is being issued DUAL-PRIMARY DRBD, ISCSI, AND MULTIPATH: DON’T DO THAT Excuse that deliberately Google-optimized blunt and inelegant title, folks, but this is getting old. If you run dual-Primary DRBD, and then export an iSCSI target from both nodes, and then you want to to do dm-multipath or somesuch for what you think constitutes failover, don't do that. There. Bold and italics. Really and truly, don't. DRBD AND MYSQL: JUST SAY YES DRBD partition corruption means failover node would be unusable (disadvantage of shared storage) and failback could destroy original master too. If the filesystem that sits on top of DRBD gets corrupted, it will be equally corrupted on the peer node after failover. DRBD is a block device; it is agnostic of layers above it. WHEN NOT TO USE DRBD This is a good article and makes a lot of sense I have used DRBD with LAMP stacks and mysql very effectivly for some fairly large scale projects,with scheduled mysql db hot copies from a slave,running hourly and a remote location for DR and of course we use RSYNC the static stuff as well.

FLORIAN'S BLOG

Know how they say that you don’t know you’re doing something right until someone starts imitating you? Well, this is a great time for us. Someone evidently took a good long read of our hastexo High Availability Expert class agenda, and made this.It’s wonderful for us to see that it’s such an inspiration to others (even the acronym!), and we hope to see more folks doing this in the future. MYSQL SCALE-OUT WITH REPLICATION AND PACEMAKER It seems that the MySQL Conference selection committee didn't seem to like the talk (and tutorial) I submitted about integrating MySQL Replication with the Pacemaker cluster stack, enabling full MySQL scale-out in an environment you previously knew only for its synchronous-replication High Availability features. But -- fear not, my fellow HA geeks! -- we are “ALTERNATIVES” TO DRBD Compare this to DRBD: no need for a SAN, so you can use it to operate a fully shared-nothing cluster. No firmware licensing cost. No need for expensive infrastructure as everything can replicate over regular IP networks. Role switch in a matter of seconds. Tight integration with both Pacemaker and Red Hat Cluster Suite . HEARTBEAT 3.0.2 RELEASED After a long release hiatus, an elaborate project re-organization, and with a new primary project sponsor, the Heartbeat cluster messaging layer saw its 3.0.2 release earlier today. Heartbeat 3.0.2 is the first official Heartbeat release since 2.1.3, released over 2 years ago. There have been a number of intermediate releases in the interim,

including some

HOW TO DEAL WITH KERNEL PANICS AND OOPSES IN HA CLUSTERS Let's face it. Software is never perfect. Even the most reliable of systems do produce kernel panics and oopses. It shouldn't happen, but it does. As an admin responsible for the operation of a high availability cluster, you can keep your cluster service up and running on a healthy node -- even if one of HIGH-AVAILABILITY VIRTUALIZATION WITH XEN AND DRBD Please note: if you are interested in a full-fledged, complete HA virtualization solution delivered as one fixed-bid service package, check out the product information for DRBD Virtualization Enterprise Cluster on our corporate web site. For the German speakers among you, Hans-Joachim Baader has written an interesting howto on leveraging DRBD, Xen, and Heartbeat to make WHY DRBD WON’T LET YOU MOUNT THE SECONDARY The filesystem is now grossly inconsistent until it is remounted. So even if DRBD would allow read-only mounts on the Secondary, all that Secondary would serve you would be garbage. That’s why it’s disallowed. If you do want access to the device from both nodes, use DRBD 8 in allow-two-primaries mode. No-one forces you to actually

build a

MYSQL/PACEMAKER SCALEOUT WEBINAR RECORDING AVAILABLE Yesterday's webcast is now available for playback. If you want a PDF of the slides, please leave a note on our web site. Update, July 19, 2010: We have switched our webinar service provider. The webinar recordings are still available, albeit under a different URL, see this

page for details.

LINBIT ANNOUNCES STEWARDSHIP FOR HEARTBEAT CODE BASE LINBIT announces stewardship for Heartbeat code base. Here is an announcement we made earlier today on the linux-ha and linux-ha-dev mailing lists. This is to announce that LINBIT, with the kind permission from the Linux-HA project board, will act as the “steward” of the Heartbeat cluster messaging layer code base, from

this point forward.

IN CASE YOU HAVEN’T NOTICED, WE NO LONGER MANAGE CLUSTERS While Yves presents a valid approach for managing NDB with Pacemaker and the anything Linux-HA resource agent (a generic wrapper for any daemon based application), the XML configuration shown is likely to have people running away screaming. This is how we had to do things back in the Heartbeat 2 days, which meant that as a cluster admin you would permanently run around with a

FLORIAN'S BLOG

Know how they say that you don’t know you’re doing something right until someone starts imitating you? Well, this is a great time for us. Someone evidently took a good long read of our hastexo High Availability Expert class agenda, and made this.It’s wonderful for us to see that it’s such an inspiration to others (even the acronym!), and we hope to see more folks doing this in the future. PERFORMANCE TUNING DRBD SETUPS Start your optimization efforts without DRBD, and when you’ve found your best setup, add DRBD to the mix. Secondly, ensure controlled experimentation. Performance tuning is boring and tedious work when done right, so don’t expect to be having a lot of fun. Do record your experimental setups in a reproducible fashion.

FLORIAN'S BLOG

After last year’s talk in Brisbane, where I greatly enjoyed co-presenting with Tim Serong, I have the privilege of returning to Australia for this year’s linux.conf.au in Ballarat, Victoria.. This time I have a brief talk opening up the High Availability and Distributed Storage miniconf on Monday, January 16, and a tutorial entitled High Availability Sprint in the morning on Thursday INTERNAL METADATA, AND WHY WE RECOMMEND IT Internal metadata, and why we recommend it. One of the things that repeatedly seem to puzzle users about the DRBD is the question of whether to use internal or external metadata. Remember, DRBD sets aside a small area on a local disk (on every cluster node) where it keeps the Activity Log, the quick-sync bitmap, data generation UUIDs,

and a few

CHECKING YOUR SECONDARY’S INTEGRITY Suppose you run into the following situation: you've suffered the effects of a nasty bug hidden somewhere deep inside your network stack. Say your NIC screwed up checksum offloading, or some network driver caused a kernel panic. Either way, you have reason to believe that some portion of the data you sent over that wire DRBD LIMITATIONS (OR ARE THEY?) I've recently received one database admin's personal list of DRBD's perceived limitations. While I'm certainly the last person to say that DRBD is limitation-free (hey, it's software), I'd like to address these specifically -- because really, in my humble opinion, most of them aren't limitations at all. The Secondary host sits idle, that's

wasted investment.

ON DRBD CONNECTION TIMEOUTS DRBD sends these “pings” in a configurable interval, specified by the ping-int configuration option and defaulting to 10 seconds. DRBD “pings” time out within the time specified as ping-timeout, which by default is 0.5 seconds. So: while I/O is being issued DUAL-PRIMARY DRBD, ISCSI, AND MULTIPATH: DON’T DO THAT Excuse that deliberately Google-optimized blunt and inelegant title, folks, but this is getting old. If you run dual-Primary DRBD, and then export an iSCSI target from both nodes, and then you want to to do dm-multipath or somesuch for what you think constitutes failover, don't do that. There. Bold and italics. Really and truly, don't. DRBD AND MYSQL: JUST SAY YES DRBD partition corruption means failover node would be unusable (disadvantage of shared storage) and failback could destroy original master too. If the filesystem that sits on top of DRBD gets corrupted, it will be equally corrupted on the peer node after failover. DRBD is a block device; it is agnostic of layers above it. WHEN NOT TO USE DRBD This is a good article and makes a lot of sense I have used DRBD with LAMP stacks and mysql very effectivly for some fairly large scale projects,with scheduled mysql db hot copies from a slave,running hourly and a remote location for DR and of course we use RSYNC the static stuff as well.

FLORIAN'S BLOG

Know how they say that you don’t know you’re doing something right until someone starts imitating you? Well, this is a great time for us. Someone evidently took a good long read of our hastexo High Availability Expert class agenda, and made this.It’s wonderful for us to see that it’s such an inspiration to others (even the acronym!), and we hope to see more folks doing this in the future. PERFORMANCE TUNING DRBD SETUPS Start your optimization efforts without DRBD, and when you’ve found your best setup, add DRBD to the mix. Secondly, ensure controlled experimentation. Performance tuning is boring and tedious work when done right, so don’t expect to be having a lot of fun. Do record your experimental setups in a reproducible fashion.

FLORIAN'S BLOG

After last year’s talk in Brisbane, where I greatly enjoyed co-presenting with Tim Serong, I have the privilege of returning to Australia for this year’s linux.conf.au in Ballarat, Victoria.. This time I have a brief talk opening up the High Availability and Distributed Storage miniconf on Monday, January 16, and a tutorial entitled High Availability Sprint in the morning on Thursday INTERNAL METADATA, AND WHY WE RECOMMEND IT Internal metadata, and why we recommend it. One of the things that repeatedly seem to puzzle users about the DRBD is the question of whether to use internal or external metadata. Remember, DRBD sets aside a small area on a local disk (on every cluster node) where it keeps the Activity Log, the quick-sync bitmap, data generation UUIDs,

and a few

CHECKING YOUR SECONDARY’S INTEGRITY Suppose you run into the following situation: you've suffered the effects of a nasty bug hidden somewhere deep inside your network stack. Say your NIC screwed up checksum offloading, or some network driver caused a kernel panic. Either way, you have reason to believe that some portion of the data you sent over that wire DRBD LIMITATIONS (OR ARE THEY?) I've recently received one database admin's personal list of DRBD's perceived limitations. While I'm certainly the last person to say that DRBD is limitation-free (hey, it's software), I'd like to address these specifically -- because really, in my humble opinion, most of them aren't limitations at all. The Secondary host sits idle, that's

wasted investment.

ON DRBD CONNECTION TIMEOUTS DRBD sends these “pings” in a configurable interval, specified by the ping-int configuration option and defaulting to 10 seconds. DRBD “pings” time out within the time specified as ping-timeout, which by default is 0.5 seconds. So: while I/O is being issued DUAL-PRIMARY DRBD, ISCSI, AND MULTIPATH: DON’T DO THAT Excuse that deliberately Google-optimized blunt and inelegant title, folks, but this is getting old. If you run dual-Primary DRBD, and then export an iSCSI target from both nodes, and then you want to to do dm-multipath or somesuch for what you think constitutes failover, don't do that. There. Bold and italics. Really and truly, don't. DRBD AND MYSQL: JUST SAY YES DRBD partition corruption means failover node would be unusable (disadvantage of shared storage) and failback could destroy original master too. If the filesystem that sits on top of DRBD gets corrupted, it will be equally corrupted on the peer node after failover. DRBD is a block device; it is agnostic of layers above it. WHEN NOT TO USE DRBD This is a good article and makes a lot of sense I have used DRBD with LAMP stacks and mysql very effectivly for some fairly large scale projects,with scheduled mysql db hot copies from a slave,running hourly and a remote location for DR and of course we use RSYNC the static stuff as well.

FLORIAN'S BLOG

Know how they say that you don’t know you’re doing something right until someone starts imitating you? Well, this is a great time for us. Someone evidently took a good long read of our hastexo High Availability Expert class agenda, and made this.It’s wonderful for us to see that it’s such an inspiration to others (even the acronym!), and we hope to see more folks doing this in the future. MYSQL SCALE-OUT WITH REPLICATION AND PACEMAKER It seems that the MySQL Conference selection committee didn't seem to like the talk (and tutorial) I submitted about integrating MySQL Replication with the Pacemaker cluster stack, enabling full MySQL scale-out in an environment you previously knew only for its synchronous-replication High Availability features. But -- fear not, my fellow HA geeks! -- we are “ALTERNATIVES” TO DRBD Compare this to DRBD: no need for a SAN, so you can use it to operate a fully shared-nothing cluster. No firmware licensing cost. No need for expensive infrastructure as everything can replicate over regular IP networks. Role switch in a matter of seconds. Tight integration with both Pacemaker and Red Hat Cluster Suite . HEARTBEAT 3.0.2 RELEASED After a long release hiatus, an elaborate project re-organization, and with a new primary project sponsor, the Heartbeat cluster messaging layer saw its 3.0.2 release earlier today. Heartbeat 3.0.2 is the first official Heartbeat release since 2.1.3, released over 2 years ago. There have been a number of intermediate releases in the interim,

including some

HOW TO DEAL WITH KERNEL PANICS AND OOPSES IN HA CLUSTERS Let's face it. Software is never perfect. Even the most reliable of systems do produce kernel panics and oopses. It shouldn't happen, but it does. As an admin responsible for the operation of a high availability cluster, you can keep your cluster service up and running on a healthy node -- even if one of HIGH-AVAILABILITY VIRTUALIZATION WITH XEN AND DRBD Please note: if you are interested in a full-fledged, complete HA virtualization solution delivered as one fixed-bid service package, check out the product information for DRBD Virtualization Enterprise Cluster on our corporate web site. For the German speakers among you, Hans-Joachim Baader has written an interesting howto on leveraging DRBD, Xen, and Heartbeat to make WHY DRBD WON’T LET YOU MOUNT THE SECONDARY The filesystem is now grossly inconsistent until it is remounted. So even if DRBD would allow read-only mounts on the Secondary, all that Secondary would serve you would be garbage. That’s why it’s disallowed. If you do want access to the device from both nodes, use DRBD 8 in allow-two-primaries mode. No-one forces you to actually

build a

MYSQL/PACEMAKER SCALEOUT WEBINAR RECORDING AVAILABLE Yesterday's webcast is now available for playback. If you want a PDF of the slides, please leave a note on our web site. Update, July 19, 2010: We have switched our webinar service provider. The webinar recordings are still available, albeit under a different URL, see this

page for details.

LINBIT ANNOUNCES STEWARDSHIP FOR HEARTBEAT CODE BASE LINBIT announces stewardship for Heartbeat code base. Here is an announcement we made earlier today on the linux-ha and linux-ha-dev mailing lists. This is to announce that LINBIT, with the kind permission from the Linux-HA project board, will act as the “steward” of the Heartbeat cluster messaging layer code base, from

this point forward.

IN CASE YOU HAVEN’T NOTICED, WE NO LONGER MANAGE CLUSTERS While Yves presents a valid approach for managing NDB with Pacemaker and the anything Linux-HA resource agent (a generic wrapper for any daemon based application), the XML configuration shown is likely to have people running away screaming. This is how we had to do things back in the Heartbeat 2 days, which meant that as a cluster admin you would permanently run around with a

FLORIAN'S BLOG

Know how they say that you don’t know you’re doing something right until someone starts imitating you? Well, this is a great time for us. Someone evidently took a good long read of our hastexo High Availability Expert class agenda, and made this.It’s wonderful for us to see that it’s such an inspiration to others (even the acronym!), and we hope to see more folks doing this in the future.

FLORIAN'S BLOG

After last year’s talk in Brisbane, where I greatly enjoyed co-presenting with Tim Serong, I have the privilege of returning to Australia for this year’s linux.conf.au in Ballarat, Victoria.. This time I have a brief talk opening up the High Availability and Distributed Storage miniconf on Monday, January 16, and a tutorial entitled High Availability Sprint in the morning on Thursday TRAINING | FLORIAN'S BLOG | PAGE 2 Posts about Training written by Florian Haas. After our hugely successful summer class in Silicon Valley, we have set up a survey to help us determine the location of our Q4 DRBD Total course in the United States. So let us know where you would like to see the next incarnation of the industry’s premier Linux High Availability

training!

RANDOM THOUGHTS

If you follow Slashdot, KernelTrap, et al., and if you’re a software developer who uses a source code management system, you’ve probably come across this video.It features Linus talking to Google engineers about git.. If, like me, you’re not a software developer, you probably haven’t seen it. But if, also like me, you’re interested in what presentation techniques good speakers use MYSQL | FLORIAN'S BLOG | PAGE 6 Today we announced (German press release, English press release) a partner deal with Dolphin Interconnect Solutions, makers of the Dolphin Express highspeed interconnect technology. Like DRBD, Dolphin Express and Dolphin SuperSockets are well established within the MySQL customer base — the latter as a low-latency interconnect for MySQL Cluster.As part of the deal, DRBD will soon be INTERNAL METADATA, AND WHY WE RECOMMEND IT Internal metadata, and why we recommend it. One of the things that repeatedly seem to puzzle users about the DRBD is the question of whether to use internal or external metadata. Remember, DRBD sets aside a small area on a local disk (on every cluster node) where it keeps the Activity Log, the quick-sync bitmap, data generation UUIDs,

and a few

FLORIAN'S BLOG

Know how they say that you don’t know you’re doing something right until someone starts imitating you? Well, this is a great time for us. Someone evidently took a good long read of our hastexo High Availability Expert class agenda, and made this.It’s wonderful for us to see that it’s such an inspiration to others (even the acronym!), and we hope to see more folks doing this in the future.

FLORIAN'S BLOG

After last year’s talk in Brisbane, where I greatly enjoyed co-presenting with Tim Serong, I have the privilege of returning to Australia for this year’s linux.conf.au in Ballarat, Victoria.. This time I have a brief talk opening up the High Availability and Distributed Storage miniconf on Monday, January 16, and a tutorial entitled High Availability Sprint in the morning on Thursday TRAINING | FLORIAN'S BLOG | PAGE 2 Posts about Training written by Florian Haas. After our hugely successful summer class in Silicon Valley, we have set up a survey to help us determine the location of our Q4 DRBD Total course in the United States. So let us know where you would like to see the next incarnation of the industry’s premier Linux High Availability

training!

RANDOM THOUGHTS

If you follow Slashdot, KernelTrap, et al., and if you’re a software developer who uses a source code management system, you’ve probably come across this video.It features Linus talking to Google engineers about git.. If, like me, you’re not a software developer, you probably haven’t seen it. But if, also like me, you’re interested in what presentation techniques good speakers use INTERNAL METADATA, AND WHY WE RECOMMEND IT One of the things that repeatedly seem to puzzle users about the DRBD is the question of whether to use internal or external metadata.Remember, DRBD sets aside a small area on a local disk (on every cluster node) where it keeps the Activity Log, the quick-sync bitmap, data generation UUIDs, and a few other bits and pieces for local housekeeping.. The specific aspect that is to be discussed MYSQL | FLORIAN'S BLOG | PAGE 6 Today we announced (German press release, English press release) a partner deal with Dolphin Interconnect Solutions, makers of the Dolphin Express highspeed interconnect technology. Like DRBD, Dolphin Express and Dolphin SuperSockets are well established within the MySQL customer base — the latter as a low-latency interconnect for MySQL Cluster.As part of the deal, DRBD will soon be CHECKING YOUR SECONDARY’S INTEGRITY Suppose you run into the following situation: you've suffered the effects of a nasty bug hidden somewhere deep inside your network stack. Say your NIC screwed up checksum offloading, or some network driver caused a kernel panic. Either way, you have reason to believe that some portion of the data you sent over that wire DRBD AND MYSQL: JUST SAY YES I recently came across this blog post with the catchy title of “DRBD and MySQL: Just Say No”.Now while I have absolutely no issue with people not liking DRBD or finding that it doesn’t fit their needs, I couldn’t help but notice that the post recycles some persistent myths about DRBD, which could use some correction.. I’ve tried to reply using a blog comment, but alas it seems I was WHEN NOT TO USE DRBD Now you may not believe me, but there actually are situations when DRBD is not the right choice for meeting your storage needs. Since I've been asked to compile some of these and present them here, let's take a look. Don't use DRBD when All or most of your data is static. Front-end web servers ON DRBD CONNECTION TIMEOUTS Here is a question recently seen on drbd-user:. I cannot get the timeout parameter in to work (I set it up as in all the examples I saw). I set it low (say 1 second), kill the remote box IO commences after 10 seconds (as the other parameters state).

ABOUT THIS BLOG

Following my transition to hastexo, I have started to use the hastexo web site as my primary means of blogging.Please take a look at my new blog location and update your feed readers.I have no intentions to take this WordPress blog down, so old posts will remain preserved here for reference purposes.

FLORIAN'S BLOG

Linux, High Availability, and other stuff of interest. Following my transition to hastexo, I have started to use the hastexo web site as my primary means of blogging.Please take a look at my new blog location and update your feed readers.I have no intentions to take this WordPress blog down, so old posts will remain preserved here for

reference purposes.

PACEMAKER – PAGE 3 Martin Loschwitz, the longest-serving Debian Developer in our ranks, will present a walk-through of going from Linux clustering on Debian lenny (with Heartbeat 2.1.3, shudder) to squeeze (with Heartbeat 3 and Pacemaker).In this webinar you will learn everything you need to know about a painless migration to the new Linux cluster stack. This webinar will be held on Monday, June 7, at 1400 UTC. DRBD LIMITATIONS (OR ARE THEY?) I've recently received one database admin's personal list of DRBD's perceived limitations. While I'm certainly the last person to say that DRBD is limitation-free (hey, it's software), I'd like to address these specifically -- because really, in my humble opinion, most of them aren't limitations at all. The Secondary host sits idle, that's

wasted investment.

“ALTERNATIVES” TO DRBD This entry was posted on Wednesday, September 16th, 2009 at 8:59 and is filed under Pacemaker, Technical.You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.. Post navigation GOT DRBD? GOT DOLPHIN? COMBINE ’EM! Today we announced (German press release, English press release) a partner deal with Dolphin Interconnect Solutions, makers of the Dolphin Express highspeed interconnect technology. Like DRBD, Dolphin Express and Dolphin SuperSockets are well established within the MySQL customer base -- the latter as a low-latency interconnect for MySQL

Cluster.

LAST MINUTE DISCOUNT NOW AVAILABLE FOR HIGH AVAILABILITY We have exactly one seat still left open in our hastexo High Availability Expert class coming up in Berlin next week. So if you want to learn about GFS2, OCFS2, advanced Pacemaker, GlusterFS and Ceph in one of Europe’s most beautiful cities, now is your chance!. And, we have a Last Minute discount available so you can get in for cheap! You’ll just have to be really, really fast before ASTERISK HIGH AVAILABILITY COMING TO THE PACEMAKER CLUSTER The Pacemaker based Linux cluster stack is gaining a freshly supported service: the Asterisk open-source PBX. hastexo's Martin Loschwitz has contributed a resource agent for the popular telephony stack. I've merged and committed the ocf:heartbeat:asterisk resource agent to the upstream repository this morning, and it's going to ship with the next release of the resource-agents IN CASE YOU HAVEN’T NOTICED, WE NO LONGER MANAGE CLUSTERS While Yves presents a valid approach for managing NDB with Pacemaker and the anything Linux-HA resource agent (a generic wrapper for any daemon based application), the XML configuration shown is likely to have people running away screaming. This is how we had to do things back in the Heartbeat 2 days, which meant that as a cluster admin you would permanently run around with a A FEW SEATS STILL LEFT FOR DRBD PERFORMANCE TUNING WEBINAR For those of you interested in getting maximum performance out of your DRBD-based HA clusters, I am hosting a webinar on the subject on Wednesday, 8/27 at 1800 UTC (2pm Eastern, 11am Pacific). The webinar is offered free of charge and it's already pretty tight in terms of attendance, the event being limited to a

FLORIAN'S BLOG

Linux, High Availability, and other stuff of interest

* Home

* About me

* About this blog

IMITATION IS THE SINCEREST FORM OF FLATTERY

May 29, 2012

Know how they say that you don’t know you’re doing something right until someone starts imitating you? Well, this is a great time for us. Someone evidently took a good long read of our hastexo High

Availability Expert

class

agenda, and made this

.

It’s wonderful for us to see that it’s such an inspiration to others (even the acronym!), and we hope to see more folks doing this

in the future.

Meanwhile, I should say this since I haven’t yet mentioned it here on my blog: there’s an new feature to our own HHAX class that we’ve added to our upcoming class in Berlin

,

and that is the booth arbitration daemon and ticket

manager.

Read more…

Leave a Comment »

| Uncategorized

| Permalink

Posted by Florian Haas ------------------------- 4 EXTRA SEATS AVAILABLE IN CLOUD BOOTCAMP IN WELLINGTON!

May 21, 2012

Our Cloud Bootcamp for OpenStack™

in

Wellington next month just got 4 extra seats! If you’re in New Zealand, Australia, or the Pacific region, and want to learn about OpenStack, now is your chance!

Read more…

Leave a Comment »

| Uncategorized

| Permalink

Posted by Florian Haas ------------------------- RETURNING TO PARIS FOR OPENSTACK IN ACTION 2: PRODUCTION READY

May 10, 2012

This month, I’m thrilled to go to Paris to talk about highly-available OpenStack. The event I’m speaking at is OPENSTACK IN ACTION 2: PRODUCTION READY

, and it’s

being organized by French hosting & cloud services provider eNovance

.

Read more…

Leave a Comment »

| Uncategorized

| Permalink

Posted by Florian Haas ------------------------- OUR FIRST CLOUD BOOTCAMP IS NOW SOLD OUT

May 8, 2012

Less than two weeks after it’s been announced

,

our inaugural Cloud Bootcamp for OpenStack

™ in

Wellington, New Zealand is now SOLD OUT. Our friends at Catalyst IT have put up a wait list , and we’re currently working on tacking on extra days to fill the excess demand.

This will be fun.

Read more…

Leave a Comment »

| Uncategorized

| Permalink

Posted by Florian Haas ------------------------- AN EXCITING DAY FOR THE CEPH COMMUNITY

May 3, 2012

Today, as you’ve probably noticed if you’re following the development of the Ceph

stack, something

mighty cool has been happening. The ceph.com web site received a major makeover with a slick new design, and the people behind Ceph haveannounced the launch of a brand new company

to

drive the Ceph stack, Inktank .

Read more…

Leave a Comment »

| Uncategorized

| Permalink

Posted by Florian Haas ------------------------- MORE DETAILS ON OSCON 2012, AND YOUR CHANCE TO GET IN CHEAPER!

May 1, 2012

A few more details on my speaking slot at this year’s OSCON, titled _Highly Available Cloud: OpenStack Integration with

Pacemaker._

Read more…

Leave a Comment »

| Uncategorized

| Permalink

Posted by Florian Haas ------------------------- COMING TO NEW ZEALAND!

April 25, 2012

hastexo is offering Cloud Bootcamp for OpenStack™

in

Wellington. Another fine example of the global OpenStack community at

work.

Read more…

Leave a Comment »

| Uncategorized

| Permalink

Posted by Florian Haas -------------------------

� Previous Entries

*

PLEASE UPDATE YOUR BOOKMARKS! Following my transition to hastexo , I have started to use the hastexo web site as my primary means of blogging. Please take a look at my new blog location and update your feed

readers . I have no

intentions to take this WordPress blog down, so old posts will remain preserved here for reference purposes.

*

NEW

* Imitation is the sincerest form of flattery * 4 extra seats available in Cloud Bootcamp in Wellington! * Returning to Paris for OpenStack in Action 2: Production Ready * Our first Cloud Bootcamp is now Sold Out * An exciting day for the Ceph community

*

POPULAR

* DRBD != fsck != DIX * DRBD limitations (or are they?) * When not to use DRBD * Asterisk High Availability coming to the Pacemaker cluster stack * Imitation is the sincerest form of flattery

*

BLOGROLL

* Planet HA

* drbd.org

* DRBD on Wikipedia

* My GitHub repos

* My Xing Page

* My LinkedIn Page

*

Search

Blog at WordPress.com.

Florian's blog

Blog at WordPress.com.

Post to

Cancel

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use. To find out more, including how to control cookies, see here: Cookie

Policy

* Follow

*

* Florian's blog

* Customize

* Follow

* Sign up

* Log in

* Report this content * Manage subscriptions

* Collapse this bar