4 ms·
I'll just point out that experience with heartbeat from 2001 is rather outdated. That would be similar to comparing 2.4 kernels problems to the most recent 3.7
by mitchty 14y ago
I'll just point out that experience with heartbeat from 2001 is rather outdated.
That would be similar to comparing 2.4 kernels problems to the most recent 3.7 kernel. Likely not an overly useful anecdote.
For the record we use heartbeat at work with no issues such as this.
- onetwothreefour 14y agoWhile I agree with you, I think the anecdote is still useful because it shows that the problems of the present are really problems of the past too. Software quality improves, sure, but you can still learn from the past.
- mitchty 14y agoI'd say its more an implementation issue than software. And that this is a solved issue even 10+ years ago with heartbeat. Our heartbeat links are segregated from the public network with separate network cards/switches. So the specific issue github hit here isn't what we would have encountered. We do have quad nic cards for a reason in the systems we run, this issue github hit is one of the various reasons you don't run heartbeat over the public topology. It will bite you in the ass no matter what cluster software you are running. Unless you also have a disk heartbeat over shared fibre/scsi, or maybe serial but same difference. Depending upon the public network though is a lost cause.