I have about a dozen corosync+pacemaker clusters and I am just now getting
around to understanding timeouts.
Most of my corosync.conf files look something like this:
version:2
token: 5000
token_retransmits_before_loss_const: 10
join:
Analyzing the log of zabbix application, I see that the problem of not
being started on node02 is Cuz the PID can not be accessed by 2 hosts.
root@node01:/usr/local/etc/log_zabbix# pcs resource
Master/Slave Set: ZabbixDTClone [ZabbixDT]
Masters: [ node01 node02 ]
Clone Set: dlm-clone [dlm]
I'm getting this error shown below.
Can someone help me?
root@node01:~# pcs status
Cluster name: mycluster
WARNING: corosync and pacemaker node names do not match (IPs used in setup?)
Last updated: Mon Oct 10 01:11:52 2016 Last change: Mon Oct 10 01:04:58
2016 by root via crm_resource on node01
On 09/10/16 11:58 PM, Andrei Borzenkov wrote:
> 10.10.2016 00:42, Eric Robinson пишет:
>> Digimer, thanks for your thoughts. Booth is one of the solutions I
>> looked at, but I don't like it because it is complex and difficult to
>> implement
>
> HA is complex. There is no way around it.
>
>>
10.10.2016 00:42, Eric Robinson пишет:
> Digimer, thanks for your thoughts. Booth is one of the solutions I
> looked at, but I don't like it because it is complex and difficult to
> implement
HA is complex. There is no way around it.
> (and perhaps costly in terms of AWS services or something
>
I could add the Zabbix service to the cluster with the following command;
pcs resource create p_zabbix ocf:heartbeat:zabbixserver params
binary="/usr/local/sbin/zabbix_server"
pid="/usr/local/etc/log_zabbix/zabbix_server.pid" op monitor interval="10s"
timeout="20s" op stop interval="0"
Digimer, thanks for your thoughts. Booth is one of the solutions I looked at,
but I don't like it because it is complex and difficult to implement (and
perhaps costly in terms of AWS services or something similar)). As I read
through your comments, I returned again and again to the feeling that
I faced with the same problem a few years ago - we needed to make a
two-node cluster working in a "split-brain" situation. We were looking at a
resource agent called SFEX which is disk based -
http://www.linux-ha.org/wiki/Sfex_(resource_agent) . At the end we rejected
SFEX because, if I am not
I've been working on a script for preventing split-brain in 2-node clusters and
I would appreciate comments from everyone. If someone already has a solution
like this, let me know!
Most of my database clusters are 2-nodes, with each node in a geographically
separate data center. Our layout
added service with the following line;
pcs resource create ZabbixServer lsb:zabbix_server op monitor interval=30s
when I look at the status;
oot@node01:/usr/local/etc# pcs status
Cluster name: mycluster
WARNING: corosync and pacemaker node names do not match (IPs used in setup?)
Last updated:
I am following the clusterlabs documentation that is for RedHat and making
adjustments to Ubuntu.
node01= 10.10.10.100 (zabbix core)
node02= 10.10.10.200 (zabbix core)
VIP= 10.10.10.250
zabbixweb= 10.10.10.2
zabbixbd= 10.10.10.1
I am having problem in zabbix core connection (node01 and node02)
11 matches
Mail list logo
