解决Mogrel cluster周期性挂掉的问题

背景:centos5+nginx+mongrel cluster+mysql
最近经常发现白天还好好的,每天早上一天就挂掉了,去官方网站看看,发生这个现象有多个原因,其中一个是长时间没有连接mysql导致的
我按照网站上的说法加上这么一句ActiveRecord::Base.verification_timeout = 14400
还是老样子,于是我采用另一种方式,更换mysql驱动
1)
yum install mysql-devel
2)
[root@test201 tracker]# gem install mysql -- --with-mysql-include=/usr/include/mysql --with-mysql-lib=/usr/lib/mysql
Bulk updating Gem source index for: http://gems.rubyforge.org/
Building native extensions.This could take a while...
Successfully installed mysql-2.7
1 gem installed
经过几天的跟踪发现一切正常了
阅读更多

虚拟环境下SQL Cluster 资源挂掉

03-31

SQL 2008R2 两个节点, active/active, Windows 2008 R2 SP1, 每个节点32core cpu, 128 GIB 内存。rnrn两周前P2V, 从phsyical machine转到vsphere VMware上,硬件指标无变化,as-as的P2V。现在的问题是,随机的发生SQL instance Virtual IP failed. 导致active node A 上的数据库实例重起,并没有发生故障转移。重新启动时间在1分钟之内,所有客户端连接全部断掉。 幸运的是很快cluster自恢复,数据库实例恢复后,用户开始连接。rnrn事件发生在是上周3一次,工作时间4pm, 上周5一次,工作时间10am, 今早一次,工作时间11:50 am. rnrn[b]Cluster Event :[/b] rn[b]1077:[/b] Health check for IP interface 'IP address 10.xxx.xxx.xxx) failed (status is '1117').rn[b]1127:[/b] Cluster network interface 'xxxxxx' for cluster node 'xxxxxx' on network 'CLuster Network 1' failed. rn[b]1129:[/b] Cluster network 'Cluster Network 1' is partitioned. Some attached failover cluster nodes cannot communicate with each other over the network. THe failover cluster was not able to determine th location of the failure.rn[b]1126:[/b] Cluster network interface 'xxxxx' for cluster node 'xxxx' on network 'Custer Network 1' is unreachable by at least one other cluster node attached to the networkrnrnSQL错误日至除了实例重起的信息和audit login failure信息外没有其他特别的Errorrnrn初步怀疑 Network Adapter 的问题,但是不是很确定。 现在把P2V后E1000的网卡转变成VMXNET3类型,并且扩大buffer,从512变成8192。 等待明日的网卡配置变更。参考VMWare 的最佳实践: Large packet loss at the guest OS level on the VMXNET3 vNIC in ESXi 5.x / 4.x ([url=http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2039495][/url])rnrn汇总问题: 大家有没有遇到过类似VMWare环境的错误,可能的错误在哪里?

没有更多推荐了,返回首页