srinivasan.manoj at wipro
Jul 1, 2007, 9:26 PM
Post #1 of 1
(3198 views)
Permalink
|
|
FW: Problem when using Wackamole
|
|
Hi,
I am running Wackamole and Spread on a 2 node setup. Both the nodes
are running on Fedora Core 6 OS.
At present I was finally able to obtain the failover case in the
nodes as I alternatively failed the nodes and tried to obtain a Virtual
IP on the other
Currently its taking about 1 minute(or around 45-50 seconds) for the
failover of first node to shift the ownership of the virtual IP to the
second node and also vice versa.
I would like to know if there is any way in which I can quicken this
process .Is there any way where we can use spread as a messanging
mechanism to improve
for my case.
I have enclosed the Conf files for both Wackamole and Spread.
Also will it be possible to do the Failover in a quicker time by
changing the parameters.
Do tell me about this.
Regards
Manoj
Wackamole.conf:
# The Spread daemon we are going to connect to. It should be on the
local box
Spread = 4803 [at] 127
SpreadRetryInterval = 5s
# The group name
Group = wack1
# Named socket for online control
#Control = /var/run/wack.it
# Win32: specify a host:port combination for the control
Control = 127.0.0.1:2413
#PerlUseLib .
#PerlUse example
#RunDynamic funcs:killhup on up
#RunDynamic example::dump_it on up
# Denote the interface we prefer to have
#prefer eth0:10.3.4.5/8
# In most cases, I just don't care. Let wackamole decide.
#Prefer eth5:10.145.167.113/32
Prefer None
# List all the virtual interfaces (ALL of them)
VirtualInterfaces {
# The following two lines have the same effect
# en0:192.168.1.2/24
# Win32: note that you *must* match the netmask with the netmask
# already configured on a given interface, otherwise the IP
address
# won't be added.
# The interface names match those that you'll see under Network
Connections
# in the control panel; you'll probably need to renamed them so
that
# they don't include spaces in their names.
#{ brlan0:10.80.116.41/23 }
# This is how you say 2 or more IPs are to be treated as a
single
# "set" or "virtual interface". If wackamole decides that this
# machine will manage it, you are ensured to get ALL the ips in
the
# set.
# { en1:10.0.0.1/8 en0:192.168.35.64/26 }
eth5:10.145.167.160/32
#eth5:0.0.0.0/26
# Collect and broadcast the IPs in our ARP table every so often
Arp-Cache = 90s
# List who we will notify
# Here the netblock (/24 or /28) can be deceptive. It is NOT a
netmask
# for a single IP. It is how one will describe that they want to
# notify ALL IPs in a segment.
Notify {
eth5:10.145.167.1/32
eth5:10.145.167.0/24 throttle 16
arp-cache
}
balance {
# This field is the maximum number of IP addresses that will
move
# from one wackamole to another during a round of balancing.
AcquisitionsPerRound = all
# Time interval in each balancing round.
interval = 4s
}
# How long it takes us to mature
mature = 2s
spread.conf:
# Blank lines are permitted in this file.
# spread.conf sample file
#
# questions to spread [at] spread
#
#MINIMAL REQUIRED FILE
#
# Spread should work fine on one machine with just the uncommented
# lines below. The rest of the file documents all the options and
# more complex network setups.
#
# This configures one spread daemon running on port 4803 on localhost.
Spread_Segment 10.145.167.255:4803 {
yamuna 10.145.167.113
ganga 10.145.167.114
}
# Spread options
#-----------------------------------------------------------------------
----
#-----------------------------------------------------------------------
----
#Set what internal Spread events are logged to the screen or file
# (see EventLogFile).
# Default setting is to enable PRINT and EXIT events only.
#The PRINT and EXIT types should always be enabled. The names of others
are:
# EXIT PRINT DEBUG DATA_LINK NETWORK PROTOCOL SESSION
# CONFIGURATION MEMBERSHIP FLOW_CONTROL STATUS EVENTS
# GROUPS MEMORY SKIPLIST ALL NONE
# ALL and NONE are special and represent either enabling every type
# or enabling none of them.
# You can also use a "!" sign to negate a type,
# so { ALL !DATA_LINK } means log all events except data_link
ones.
DebugFlags = { PRINT EXIT ALL !DATA_LINK !EVENTS !MEMORY !NETWORK }
#Set whether to log to a file as opposed to stdout/stderr and what
# file to log to.
# Default is to log to stdout.
#
#If option is not set then logging is to stdout.
#If option is set then logging is to the filename specified.
# The filename can include a %h or %H escape that will be replaced at
runtime
# by the hostname of the machine upon which the daemon is running.
# For example "EventLogFile = spreadlog_%h.log" with 2 machines
# running Spread (machine1.mydomain.com and machine2.mydomain.com) will
# cause the daemons to log to "spreadlog_machine1.mydomain.com.log" and
# "spreadlog_machine2.mydomain.com.log" respectively.
#EventLogFile = testlog.out
#Set whether to add a timestamp in front of all logged events or not.
# Default is no timestamps. Default format is "[%a %d %b %Y %H:%M:%S]".
#If option is commented out then no timestamp is added.
#If option is enabled then a timestamp is added with the default format
#If option is enabled and set equal to a string, then that string is
used
# as the format string for the timestamp. The string must be a valid
time
# format string as used by the strftime() function.
#EventTimeStamp
# or
#EventTimeStamp = "[%a %d %b %Y %H:%M:%S]"
#Set whether to allow dangerous monitor commands
# like "partition, flow_control, or kill"
# Default setting is FALSE.
#If option is set to false then only "safe" monitor commands are allowed
# (such as requesting a status update).
#If option is set to true then all monitor commands are enabled.
# THIS IS A SECURTIY RISK IF YOUR NETWORK IS NOT PROTECTED!
#DangerousMonitor = false
#Set handling of SO_REUSEADDR socket option for the daemon's TCP
# listener. This is useful for facilitating quick daemon restarts (OSes
# often hold onto the interface/port combination for a short period of
time
# after daemon shut down).
#
# AUTO - Active when bound to specific interfaces (default).
# ON - Always active, regardless of interface.
# SECURITY RISK FOR ANY OS WHICH ALLOW DOUBLE BINDS BY DIFFERENT
USERS
# OFF - Always off.
#SocketPortReuse = AUTO
#Sets the runtime directory used when the Spread daemon is run as root
# as the directory to chroot to. Defaults to the value of the
# compile-time preprocessor define SP_RUNTIME_DIR, which is generally
# "/var/run/spread".
#RuntimeDir = /var/run/spread
#Sets the unix user that the Spread daemon runs as (when launched as
# the "root" user). Not effective on a Windows system. Defaults to
# the user and group "spread".
#DaemonUser = spread
#DaemonGroup = spread
#Set the list of authentication methods that the daemon will allow
# and those which are required in all cases.
# All of the methods listed in "RequiredAuthMethods" will be checked,
# irregardless of what methods the client chooses.
# Of the methods listed is "AllowedAuthMethods" the client is
# permitted to choose one or more, and all the ones the client chooses
# will also be checked.
#
# To support older clients, if NULL is enabled, then older clients can
# connect without any authentication. Any methods which do not require
# any interaction with the client (such as IP) can also be enabled
# for older clients. If you enable methods that require interaction,
# then essentially all older clients will be locked out.
#
#The current choices are:
# NULL for default, allow anyone authentication
# IP for IP based checks using the spread.access_ip file
#RequiredAuthMethods = " "
#AllowedAuthMethods = "NULL"
#Set the current access control policy.
# This is only needed if you want to establish a customized policy.
# The default policy is to allow any actions by authenticated clients.
#AccessControlPolicy = "PERMIT"
# network description line.
# Spread_Segment <multicast address for subnet> <port> {
# port is optional, if not specified the default 4803 port is used.
#Spread_Segment 127.0.0.255:4803 {
# either a name or IP address. If both are given, than the name is
taken
# as-is, and the IP address is used for that name.
# localhost 127.0.0.1
#}
# repeat for next sub-network
Spread_Segment 129.130.12.255:4803 {
dns-h1 129.130.12.160
dns-h2 129.130.12.161
}
#Spread_Segment x.2.2.255 {
# other1 128.2.2.10
# 128.2.2.11
# other3.my.com
#}
# Spread will feel free to use broadcast messages within a sub-network.
# if you do not want this to happen, you should specify your machines on
# different logical sub-networks.
# IP-Multicast addresses can also be used as the multicast address for
# the logical sub-network as in this example. If IP-multicast is
supported
# by the operating system, then the messages will only be received
# by those machines who are in the group and not by all others in the
same
# sub-network as happens with broadcast addresses
#Spread_Segment 225.0.1.1:3333 {
# mcast1 1.2.3.4
# mcast2 1.2.3.6
#}
# Multi-homed host setup
#
# If you run Spread on hosts with multiple interfaces you may want to
# control which interfaces Spread uses for client connections and for
# the daemon-to-daemon (and monitor control) messages. This can be done
# by adding an extra stanza to each configured machine.
#
#Sample:
#
#Spread_Segment 225.0.1.1 {
# multihomed1 1.2.3.4 {
# D 192.168.0.4
# C 1.2.3.4 }
# multihomed2 1.2.3.5 {
# D 192.168.0.5
# C 1.2.3.5
# C 127.0.0.1 }
# multihomed3 1.2.3.6 {
# 192.168.0.6
# 1.2.3.6 }
#}
# This configuration sets up three multihomed machines into a Spread
segment.
# The first host has a 'main' IP address of 1.2.3.4 and listens for
client
# connections only on that interface. All daemon-to-daemon UDP
multicasts and
# the tokens and any monitor messages must use the 192.168.0.4
interface.
# The second host multihomed2 has a similar setup, except it also
listens for
# client connections on the localhost interface as well as the 1.2.3.5
interface.
# If you make any use of the extra interface stanza ( a { } block ) then
you
must
# explicitly configure ALL interfaces you want as Spread removes all
defaults
when
# you use the explicit notation.
# The third multihomed3 host uses a shorthand form of omitting the D or
C
option and
# just listening for all types of traffic and events on both the
192.168.0 and
1.2.3
# networks. If no letter is listed before the interface address then ALL
types
of
# events are handled on that interface.
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
www.wipro.com
|
