Common Corosync Configuration

为什么80%的码农都做不了架构师？>>>   

# Please read the corosync.conf.5 manual page
compatibility: whitetank

# Totem SRP/RRP protocol configuration
totem {
	# the version field should always be set to 2
	version: 2

	# the secauth field maybe be set to on to use security and reduced
	# network performance, or off for higher performance operation
	# disable encryption
	secauth: off

	# the threads field maybe be set to 0 to not use threaded sending,
	# or to  some value greater than 1, usually equal to the number of 
	# processors in the system - 1. Send operations will be threaded
	# across multiple processors when this is configured. If set to 0,
	# no threads will be userd by Totem.
	# How many threads to use for encryption/decryption.
	threads: 0

	# how long before declaring a token lost (ms)
	token: 5000

	# how many token retransmits before forming a new configuration
	token_retransmits_before_loss_const: 10

	# how long to wait for join messages in the membership protocol (ms)
	join: 1000

	# how long to wait for consensus to be achieved before starting a new
	# round of membership configuration (ms)
	consensus: 6000

	# this directive controls the virtual synchrony filter type used to 
	# identify a primary component. The default is ykd, can also be set
	# none.
	# turn off the virtual synchrony filter
	vsftype: none

	# number of messages that may be sent by one processor on receipt of
	# the token.
	max_messages: 20

	# stagger sending the node join messages by 1..send_join ms
	send_join: 45

	# limit generated nodeids to 31-bits (positive signed integers)
	clear_node_high_bit: yes

	# optionally assign a fixed node id (integer)
	# nodeid: 1234

	# The interface  directive specifies a totem interface to bind to.
	# Multiple interface directives may be used, in which case a redundant
	# ring mode of operation will be used by Totem.
	interface {
		# The ringnumber is the ring number used for this ring and 
		# should be set to 0 and increasing upwards for the interface
		# directives on each node on the same network.
		ringnumber: 0

		# The bindnetaddr is the network address to bind to. For the 
		# purpose of sharing configuration files across the cluser,
		# openais uses network interface netmask to mask only the addr-
		# ess bits that are used for routing the network. The pseudocode
		# used to determine if the interface should be bound to is:
		#	for all interfaces in system
		#		if bindnetaddr == iface.addr & iface.netmask
		#			bind to interface
		# This can cause confusion if netmask or bindnetaddr are not 
		# set properly.
		# bindnetaddr: 192.168.1.1
		bindnetaddr: 172.16.82.100

		# This is the multicase address used by corosync executive.
		# The default should work for most networks, but the network
		# administrator should be queried about a multicase address 
		# to use. Avoid 224.x.x.x because this is a "config" multicast
		# address. This may also be an IPv6 address.
		# If IPv6 address is used, the nodeid field must be specified.
		mcastaddr: 226.94.1.1

		# This specifies the UDP port number. It is possible to use the
		# same multicast address on a network with the corosync services
		# configured for different UDP ports. Please note corosync uses
		# two UDP ports mcastprot(for mcast receives) and mcastprot-1(
		# for mcast sends). If you have multiple clusters on the same 
		# network using the same mcastaddr please configure the mcast-
		# ports with a gap.
		mcastport: 5405

		# the Time To Live(TTL). If you run your cluster on a routed 
		# network then te default of "1" will be too small. This option
		# provides a way to increase this up to 255. The valid range is
		# 0..255. Note that it's only valid on multicast transprot types
		ttl: 1
	}
}

# Within the logging directive, there are several configuration options 
# which are all optional.
logging {
	# This specifies that file and line should be printed.The default is off.
	fileline: off

	# This specifies that the code function name should be printed.
	# The default is off.
	# function_name: off

	#################################################################
	# The following options are valid both for top level logging 
	# directive and they can be overriden in logger_subsys entries.
	#################################################################

	# These specify the destination of logging output. Any combination of
	# these options may be specifies. Valid options are yes and no.
	# The default is syslog and stderr.
	to_stderr: no
	to_logfile: yes
	to_syslog: yes

	# If the to_logfile directive is set to yes, this option specifies the
	# pathname of the log file. No default.
	logfile: /var/log/cluster/corosync.log

	# This specifies the logfile priority for this particular subsystem.
	# Ignored if debug is on. Possible values are: alert, crit, debug(
	# same as debug=on), emerg, err, info, notice, warning.
	# The default is info.
	# logfile_priority: info

	# This specifies the syslog facility type that will be used for any
	# messages sent to syslog. options are daemon, local0, local1, local2
	# local3, local4, local5, local6 & local7.
	# The default is daemon.
	syslog_facility: daemon

	# This is specifies the syslog level for this particular sybsystem.
	# Ignored if debug is on. Possible values are: altert, crit, debug(
	# same as debug=on), emerg, err, info, notice, warning.
	# The default is info.
	# syslog_priority: info

	# This specifies whether debug output is logged for 
	# this partcicular logger.
	debug: off

	# This specifies that a timestamp is placed on all log messages.
	# The default is off.
	timestamp: on

	# Within the logging directive, logger_subsys directives are optional.
	# Within the logger_subsys sub-directive, all of the above logging
	# configuration options are valid and can be used to overriden the 
	# default settings. The subsys entry, described below, is mandatory to
	# identify the subsystem.
	logger_subsys {
		# This specifies the subsystem identity (name) for which logging
		# is specified. This is the name used by a service in the 
		# log_init() call. E.g. 'CKPT'. This directive is required.
		subsys: AMF
		debug: off
	}
}

amf {
	mode: disabled
}

Sample Corosync.conf for a two-node cluster

转载于:https://my.oschina.net/qihh/blog/59199