blocks|key|888132|text|其他服务在同一台机器上吗？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|888133|如果没有，则没有任何重叠(在一组具有虚拟IP的机器上使用Linux，而在另一组计算机上使用MMR+)。|888134|如果有其他服务，那么可能考虑虚拟化或将它们转移到其他机器，因为这将简化网络接口管理(您无法在这两种虚拟IP管理方法之间产生冲突)。|888135|只需确保虚拟主机位于单独的主机上，否则主机的故障将导致您丢失所有的MySQL实例！|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|J|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|K|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|L|8|@]|9|@]|A|$]]]|H|$]]

Are the other services on the same machines?

If not then you don't have any overlap (Linux-HA on one set of machines with a virtual IP, and MMR on another set of machines)

If there are other services then perhaps consider virtualization or moving them to other machines, as this will simplify the network interface management (you don't be able to get clashes between the two virtual-IP management methods).

Just make sure that the virtualized masters are on separate hosts, otherwise a failure of the host machine will cause you to lose all your MySQL instances anyway!

blocks|key|887938|text|我尽可能多地使用Linux工具，尽可能少地使用MySQL组件。尽我所能，我不相信MySQL的东西。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

I use the Linux HA tools for as much as possible, and the MySQL components for as little as possible. I don't trust the MySQL stuff as far as I can throw it.

blocks|key|887984|text|似乎可以为这两种情况分别定义不同的VIP接口。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|887985|我一直无法找到类似配置的参考资料，所以我认为你只需要努力通过和做大量的测试。|887986|然而，在一般情况下，我非常怀疑任何多主复制技术。我会认真考虑是否可以在故障转移配置中使用一个主服务器。|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|H|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|I|8|@]|9|@]|A|$]]]|F|$]]

It seems plausible that you could define seperate VIP interfaces for each of the two. 

I've been unable to find references on similar configurations, so I think you're just gonna have to work your way through and do a lot of testing.

In genereal however, I'm very sceptical of any multi master replication technology. I'd think hard on whether I could make due with a single master in a failover configuration.

blocks|key|888018|text|Linux和MMR单独使用可能会很复杂。如果您主要关心的是交互，那么限制它的最简单的方法就是不同的硬件/网络。如果这是不可能的，每个框的复杂性将增加。因此，最佳实践是尽可能地将虚拟地址和ip地址分开，这样您就可以将Linux和MMR的配置集中在一个接口子集上，而不必担心它们相互干扰。我也会仔细考虑你是否需要主-母复制。它可能非常复杂，复杂容易失败。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|888019|您可能会更好地服务于主从服务器，或者在发生主要故障时降级服务。如果你仍然需要主人/主人，你可能想看看postgres+(尽管mmr选项很多)。我也不愿提及它，但如果我没有提到它，那将是一种疏忽，但根据我的经验，如果MMR很重要，并且无法从体系结构上或通过其他方法解决，您可能希望查看一个商业数据库，比如Oracle或DB2，它们都通过共享存储实现了基于日志的MMR，并且非常可靠。|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|F|8|@]|9|@]|A|$]]]|D|$]]

Linux-HA and MMR individually can be complicated to get working. If your primary concern is interaction the easiest way to limit it is disparate hardware / networking. If that is not possible the complexity per box will increase. So best practice is to split up your virtual addresses and ip addressing as much as possible so that you can focus the configuration of both Linux-HA and MMR on a subset of interfaces and can worry less about them interfering with each other. I would also think hard as to whether you need master-master replication. It can be very complicated, and complexity is prone to failure.

You may be better served with master slave, or degraded service in the event of primary failure. If you still need master/master you may want to look at postgres (although the mmr options are numerous). I also hate to mention it but would be remiss if I didn't, but in my experience if MMR matters and cannot be solved architecturally or through some other means you may want to look at a commercial database such as Oracle or DB2, both of which implement log based MMR via shared storage and are very reliable.

blocks|key|4987840|text|对我们来说很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4987841|然而，每个服务都有一个单独的VIP是至关重要的，虽然理论上你不需要它，但我们发现它只适用于单独的VIP服务，如果没有它，可能会有点奇怪。|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|F|8|@]|9|@]|A|$]]]|D|$]]

It works fine for us.

However it's critical to have a separate VIP per service, although in theory you don't need it we've found it just works with seperate VIP's and can be a bit odd without.

blocks|key|4987944|text|我们有一个可能与您感兴趣的产品集群类似的产品集群：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4987945|MySQL+MMM使两个服务器之间的数据库保持同步。|unordered-list-item|4987946|OCFS2在DRBD+0.8之上以多主模式保持web文件和配置文件在两台服务器之间的同步。|offset|length|4987947|保留区位于web集群前面的冗余防火墙上，它跟踪哪些服务器正在运行，并在它们之间平均分配客户端连接。|4987948|实现和保持运行相当简单，并提供了出色的性能。Keepalived可能会有点微妙，因为它不会将超级用户错误放入syslog中，涉及坏的配置，但是一旦让它正常工作，就会非常可靠。DRBD是在机器之间保持整个文件系统同步的最好的非SAN解决方案，而OCFS2是(在我们的测试中)性能最好的开源集群文件系统，它的设置也非常容易。|4987949|唯一真正需要注意的是，如果用户的连接指向一台服务器，然后切换到另一台服务器，则会丢失Apache+/+PHP会话和状态数据(除非所有这些都存储在数据库中)。不过，这不是什么大问题，因为“保持生命”有一种模式，可以确保相同的客户端up总是连接到相同的后端服务器(假设它们不睡觉)。|entityMap|0|LINK|mutability|MUTABLE|url|http://oss.oracle.com/projects/ocfs2/|1|http://www.drbd.org/|2|http://www.keepalived.org/^0|0|0|0|5|0|6|8|1|0|0|3|2|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|10|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|11|8|@]|9|@$G|12|H|13|1|14]|$G|15|H|16|1|17]]|A|$]]|$1|I|3|J|5|D|7|18|8|@]|9|@$G|19|H|1A|1|1B]]|A|$]]|$1|K|3|L|5|6|7|1C|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1D|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]|V|$5|Q|R|S|A|$T|W]]|X|$5|Q|R|S|A|$T|Y]]]]

We've got a production cluster that may be similar to what you're interested in:

<ul>
<li>MySQL MMM to keep databases in sync between both servers.</li>
<li><a href="http://oss.oracle.com/projects/ocfs2/" rel="nofollow noreferrer">OCFS2</a> on top of <a href="http://www.drbd.org/" rel="nofollow noreferrer">DRBD 0.8</a> in multi-master mode to keep web files and configuration files in sync between both servers.</li>
<li><a href="http://www.keepalived.org/" rel="nofollow noreferrer">Keepalived</a> on redundant firewalls in front of the web cluster, which keeps track of which servers are up and evenly distributes client connections between them.</li>
</ul>

It's reasonably simple to implement and keep running, and provides excellent performance. Keepalived can be a little fiddly because it doesn't put super userful errors into syslog about broken configurations, but once you've got it working it's rock solid. DRBD is about the best non-SAN solution for keeping whole filesystems in sync between machines, and OCFS2 is (in our tests) the best performing open source clustered filesystem, and it's setup is real easy as well.

The only real caveat with this is that if a user's connections are being directed at one server, and then they get switched to the other server, it'll lose Apache / PHP session and state data (unless that's all being stored in the database). This isn't a huge deal though, since keepalived has a mode that'll make sure the same client IPs always connect to the same backend servers (assuming they stay up).

blocks|key|4987670|text|哪个操作系统(Linux)正在使用？通常，当您必须安装Mysql集群/Apache时，我会为我们的客户端设置大量时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4987671|SAN+Box+x|4987672|Node1+Node2|4987673|服务运行|4987674|VIP+Mysql/Apache+LVM/GFS/GFS+2|4987675|我建议您按照下面的链接设置|4987676|http://kbase.redhat.com/faq/docs/DOC-5648|offset|length|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|0|0|0|15|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|Z|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|11|8|@]|9|@$N|12|O|13|1|14]]|A|$]]]|P|$Q|$5|R|S|T|A|$U|M]]]]

Which OS (Linux) are using ?
normally when you have to setup Mysql cluster /Apache i have setup lot of time for our client

| SAN Box |

| |
Node1 Node2

services running

VIP
Mysql/Apache
LVM/GFS/GFS2

and I suggest following link to setup

<a href="http://kbase.redhat.com/faq/docs/DOC-5648" rel="nofollow noreferrer">http://kbase.redhat.com/faq/docs/DOC-5648</a>

I'm interested in using MMR (<a href="http://mysql-mmm.org/" rel="nofollow noreferrer">http://mysql-mmm.org/</a>) for high availability and replication purposes. The problem is, I'm also interested in using Linux-HA for other services, such as Apache. The two overlap when it comes to certain things, such as swapping virtual IP interfaces etc.

Does anyone have a similar setup and have some best practices/solutions for the problem above?

Mixing Multi-Master Replication (MMR) with Linux-HA

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我感兴趣的是将MMR (http://mysql-mmm.org/)用于高可用性和复制目的。问题是，我也对将Linux用于其他服务感兴趣，比如Apache。当涉及到某些事情时，例如交换虚拟IP接口等，这两者是重叠的。是否有人有类似的设置，并对上述问题有一些最佳实践/解决方案？

问将多主复制(MMR)与Linux-HA混合使用
EN

回答 7

Server Fault用户

Server Fault用户

Server Fault用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将多主复制(MMR)与Linux-HA混合使用EN

回答 7

Server Fault用户

Server Fault用户

Server Fault用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将多主复制(MMR)与Linux-HA混合使用
EN