我妈和我闺密的舅妈，均于2008年3月查出结肠癌，并马上都在同一家三甲医院做了手术。她俩病情相似，都是结肠癌，手术时都处于无转移阶段（B型），就是所谓中期。我妈60岁，她舅妈53岁。

术后我妈做了4个化疗，8月做了肠回纳手术后，又做了2个化疗。做化疗但坚持用中医固本配合，每天进食大量她给自己配备的武器：灵芝孢子粉、松花粉、蜂胶、固元膏、淮山药芡实薏米粥等一系列她认为有用的东西，时不时躺在床上做做气功，心态坦然。我给妈妈买了很多中西医的专业书籍，她躺在医院等待愈合期间大量阅读，受益匪浅，多次发现并纠正医护中的错误、研究医嘱并思考医生开出的治疗方案是否适合自己；还比对每次化验指标，根据指标进行调整。医院现在肿瘤患者很多，医疗配套和医护队伍都跟不上这不断增加的庞大的病患，随时出现的情况让你匪夷所思，防不胜防。（补充：医生给我妈开出12个化疗的方案——据说是国家根据这一期的患者给出的标准方案，各地都遵照此方案进行，我妈只坚持完成了6个。）

闺密舅妈很年青很坚强，在家人的照顾下，完全按照西医大夫交代的配合治疗，做完医生规定的10个化疗疗程。但遗憾的是，在不间断做第10个化疗的时候，已经开始肝肺转移。闺密舅妈虽不用中医（后期用了一段，但随着转移和新化疗的开始又停止了），但参加了气功班，还常去抗癌协会参加活动啥的。

我妈本周在301做完新一轮检查，CT下来体内无复发，血相指标正常。我说她的成绩单上又贴了2朵小红花。 闺密舅妈，近期疼痛难忍，上周入院，医生指示，马上转院到肿瘤医院，并开始做第11个化疗，每晚疼得睡不着觉。家人手足无措。

不想评论中西医（我个人认为中西医都有各自的作用，关键看你怎么用）。只是说，如果未来家人遇到如是大病，当家属的或者是病患本身，一定要有自己的判断和选择，毕竟，身体放出的信号只有自己最知道。衷心希望闺密舅妈能够好转。

Percona presented two talks at PHP Quebec last week - one on A Tour of MySQL High Availability, and another on Performance Tuning MySQL. There was a great reaction to showcasing some of the quick-wins that can be found by using the Percona patches. Unfortunately, the one thing that I forgot to mention in the slides is that the patches are Open Source and free to use.

Entry posted by morgan | 2 comments

Add to: | | | |

Henry Robinson has created an excellent series of articles on consensus protocols. We already covered his 2 Phase Commit article and he also has a 3 Phase Commit article showing how to handle 2PC under single node failures.

But that is not enough! 3PC works well under node failures, but fails for network failures. So another consensus mechanism is needed that handles both network and node failures. And that's Paxos.

Paxos correctly handles both types of failures, but it does this by becoming inaccessible if too many components fail. This is the "liveness" property of protocols. Paxos waits until the faults are fixed. Read queries can be handled,
but updates will be blocked until the protocol thinks it can make forward progress.

The liveness of Paxos is primarily dependent on network stability. In a distributed heterogeneous environment you are at risk of losing the ability to make updates. Users hate that.

So when companies like Amazon do the seemingly insane thing of creating eventually consistent databases, it should be a little easier to understand now. Partitioning is required for scalability. Partitioning brings up these nasty consensus issues. Not being able to write under partition failures is unacceptable. Therefor create a system that can always write and work on consistency when all the downed partitions/networks are repaired.

read more