2007-05-31 05:09:45 +04:00
#!/bin/sh
2013-04-03 07:44:08 +04:00
# This must run as root as CTDB tool commands need to access CTDB socket
[ $(id -u) -eq 0 ] || exec sudo "$0" "$@"
2007-06-01 14:54:26 +04:00
# this script needs to be installed so that statd points to it with the -H
2007-06-02 13:45:06 +04:00
# command line argument. The easiest way to do that is to put something like this in
# /etc/sysconfig/nfs:
# STATD_HOSTNAME="myhostname -H /etc/ctdb/statd-callout"
2013-01-03 08:33:10 +04:00
[ -n "$CTDB_BASE" ] || \
export CTDB_BASE=$(cd -P $(dirname "$0") ; echo "$PWD")
2007-09-14 08:14:03 +04:00
. $CTDB_BASE/functions
2013-11-08 09:41:11 +04:00
# Overwrite this so we get some logging
die ()
{
script_log "statd-callout" "$@"
exit 1
}
2009-11-09 17:06:59 +03:00
loadconfig ctdb
2007-06-03 16:07:07 +04:00
loadconfig nfs
2007-05-31 05:09:45 +04:00
2013-11-08 09:41:11 +04:00
[ -n "$NFS_HOSTNAME" ] || \
die "NFS_HOSTNAME is not configured. statd-callout failed"
# A handy newline
nl="
"
2007-09-07 02:52:56 +04:00
2015-02-13 12:55:43 +03:00
ctdb_setup_service_state_dir "statd-callout"
cd "$service_state_dir" || \
die "Failed to change directory to \"${service_state_dir}\""
2007-05-31 05:09:45 +04:00
case "$1" in
2015-02-13 12:55:43 +03:00
# Keep a single file to keep track of the last "add-client" or
# "del-client'. These get pushed to ctdb.tdb during "update",
# which will generally be run once each "monitor" cycle. In this
# way we avoid scalability problems with flood of persistent
# transactions after a "notify" when all the clients re-take their
# locks.
2013-11-08 09:41:11 +04:00
add-client)
# statd does not tell us to which IP the client connected so
# we must add it to all the IPs that we serve
cip="$2"
2015-04-18 15:00:49 +03:00
ctdb_get_pnn
2013-11-08 09:41:11 +04:00
date=$(date '+%s')
2014-11-20 06:32:46 +03:00
ctdb ip -X |
2015-02-13 12:55:43 +03:00
tail -n +2 |
while IFS="|" read x sip node x ; do
[ "$node" = "$pnn" ] || continue # not us
key="statd-state@${sip}@${cip}"
echo "\"${key}\" \"${date}\"" >"$key"
done
2007-05-31 05:09:45 +04:00
;;
2015-02-13 12:55:43 +03:00
del-client)
2013-11-08 09:41:11 +04:00
# statd does not tell us from which IP the client disconnected
# so we must add it to all the IPs that we serve
cip="$2"
2015-04-18 15:00:49 +03:00
ctdb_get_pnn
2014-11-20 06:32:46 +03:00
ctdb ip -X |
2015-02-13 12:55:43 +03:00
tail -n +2 |
while IFS="|" read x sip node x ; do
[ "$node" = "$pnn" ] || continue # not us
key="statd-state@${sip}@${cip}"
echo "\"${key}\" \"\"" >"$key"
done
2007-05-31 05:09:45 +04:00
;;
2015-02-13 12:55:43 +03:00
update)
files=$(echo statd-state@*)
if [ "$files" = "statd-state@*" ] ; then
# No files!
exit 0
fi
# Filter out lines for any IP addresses that are not currently
# hosted public IP addresses.
2015-04-18 15:00:49 +03:00
ctdb_get_pnn
2015-02-13 12:55:43 +03:00
ctdb_ips=$(ctdb ip | tail -n +2)
sed_expr=$(echo "$ctdb_ips" |
awk -v pnn=$pnn 'pnn == $2 { \
ip = $1; gsub(/\./, "\\.", ip); \
printf "/statd-state@%s@/p\n", ip }')
if cat $files | sed -n "$sed_expr" | ctdb ptrans "ctdb.tdb" ; then
rm $files
fi
;;
2013-11-08 09:41:11 +04:00
notify)
2007-09-07 02:52:56 +04:00
# we must restart the lockmanager (on all nodes) so that we get
2015-07-27 00:02:57 +03:00
# a clusterwide grace period (so other clients don't take out
2007-09-07 02:52:56 +04:00
# conflicting locks through other nodes before all locks have been
# reclaimed)
# we need these settings to make sure that no tcp connections survive
# across a very fast failover/failback
2007-10-22 04:18:38 +04:00
#echo 10 > /proc/sys/net/ipv4/tcp_fin_timeout
2007-10-21 00:42:33 +04:00
#echo 0 > /proc/sys/net/ipv4/tcp_max_tw_buckets
#echo 0 > /proc/sys/net/ipv4/tcp_max_orphans
2007-09-07 02:52:56 +04:00
2015-07-27 00:02:57 +03:00
# Delete the notification list for statd, we don't want it to
2010-08-30 12:13:28 +04:00
# ping any clients
2007-09-07 02:52:56 +04:00
rm -f /var/lib/nfs/statd/sm/*
rm -f /var/lib/nfs/statd/sm.bak/*
2007-09-07 06:14:53 +04:00
2007-09-07 02:52:56 +04:00
# we must keep a monotonically increasing state variable for the entire
# cluster so state always increases when ip addresses fail from one
# node to another
2010-08-30 12:13:28 +04:00
# We use epoch and hope the nodes are close enough in clock.
# Even numbers mean service is shut down, odd numbers mean
# service is started.
2013-11-08 09:41:11 +04:00
state_even=$(( $(date '+%s') / 2 * 2))
2007-09-07 02:52:56 +04:00
2015-06-24 14:36:14 +03:00
# We must also let some time pass between stopping and
# restarting the lock manager. Otherwise there is a window
# where the lock manager will respond "strangely" immediately
# after restarting it, which causes clients to fail to reclaim
# their locks.
2015-07-01 11:32:35 +03:00
"$CTDB_NFS_CALLOUT" "stop" "nlockmgr" >/dev/null 2>&1
sleep 2
"$CTDB_NFS_CALLOUT" "start" "nlockmgr" >/dev/null 2>&1
2007-09-07 02:52:56 +04:00
# we now need to send out additional statd notifications to ensure
# that clients understand that the lockmanager has restarted.
# we have three cases:
# 1, clients that ignore the ip address the stat notification came from
# and ONLY care about the 'name' in the notify packet.
# these clients ONLY work with lock failover IFF that name
# can be resolved into an ipaddress that matches the one used
# to mount the share. (==linux clients)
# This is handled when starting lockmanager above, but those
# packets are sent from the "wrong" ip address, something linux
# clients are ok with, buth other clients will barf at.
# 2, Some clients only accept statd packets IFF they come from the
# 'correct' ip address.
# 2a,Send out the notification using the 'correct' ip address and also
# specify the 'correct' hostname in the statd packet.
# Some clients require both the correct source address and also the
# correct name. (these clients also ONLY work if the ip addresses
# used to map the share can be resolved into the name returned in
# the notify packet.)
# 2b,Other clients require that the source ip address of the notify
# packet matches the ip address used to take out the lock.
# I.e. that the correct source address is used.
# These clients also require that the statd notify packet contains
# the name as the ip address used when the lock was taken out.
#
# Both 2a and 2b are commonly used in lockmanagers since they maximize
# probability that the client will accept the statd notify packet and
# not just ignore it.
2010-08-30 12:13:28 +04:00
# For all IPs we serve, collect info and push to the config database
2015-04-18 15:00:49 +03:00
ctdb_get_pnn
2013-11-08 09:41:11 +04:00
# Construct a sed expression to take catdb output and produce pairs of:
# server-IP client-IP
# but only for the server-IPs that are hosted on this node.
2015-10-20 04:38:38 +03:00
ctdb_all_ips=$(ctdb ip all | tail -n +2)
2015-02-13 12:55:43 +03:00
sed_expr=$(echo "$ctdb_all_ips" |
2014-12-19 06:19:32 +03:00
awk -v pnn=$pnn 'pnn == $2 { \
2015-02-26 07:34:51 +03:00
ip = $1; gsub(/\./, "\\.", ip); \
2014-12-19 06:19:32 +03:00
printf "s/^key.*=.*statd-state@\\(%s\\)@\\([^\"]*\\).*/\\1 \\2/p\n", ip }')
2013-11-08 09:41:11 +04:00
statd_state=$(ctdb catdb ctdb.tdb | sed -n "$sed_expr" | sort)
2013-11-19 08:40:08 +04:00
[ -n "$statd_state" ] || exit 0
2013-11-08 09:41:11 +04:00
2016-02-12 02:12:13 +03:00
smnotify="${CTDB_HELPER_BINDIR}/smnotify"
2015-02-13 12:55:43 +03:00
prev=""
echo "$statd_state" | {
# This all needs to be in the same command group at the
# end of the pipe so it doesn't get lost when the loop
# completes.
items=""
while read sip cip ; do
# Collect item to delete from the DB
key="statd-state@${sip}@${cip}"
item="\"${key}\" \"\""
items="${items}${items:+${nl}}${item}"
2013-11-08 09:41:11 +04:00
2015-02-13 12:55:43 +03:00
# NOTE: Consider optimising smnotify to read all the
# data from stdin and then run it in the background.
# Reset stateval for each serverip
[ "$sip" = "$prev" ] || stateval="$state_even"
# Send notifies for server shutdown
2016-02-12 02:12:13 +03:00
"$smnotify" --client=$cip --ip=$sip --server=$sip --stateval=$stateval
"$smnotify" --client=$cip --ip=$sip --server=$NFS_HOSTNAME --stateval=$stateval
2015-02-13 12:55:43 +03:00
# Send notifies for server startup
stateval=$(($stateval + 1))
2016-02-12 02:12:13 +03:00
"$smnotify" --client=$cip --ip=$sip --server=$sip --stateval=$stateval
"$smnotify" --client=$cip --ip=$sip --server=$NFS_HOSTNAME --stateval=$stateval
2015-02-13 12:55:43 +03:00
done
2013-11-08 09:41:11 +04:00
2015-02-13 12:55:43 +03:00
echo "$items" | ctdb ptrans "ctdb.tdb"
}
# Remove any stale touch files (i.e. for IPs not currently
# hosted on this node and created since the last "update").
# There's nothing else we can do with them at this stage.
echo "$ctdb_all_ips" |
awk -v pnn=$pnn 'pnn != $2 { print $1 }' |
while read sip ; do
rm -f "statd-state@${sip}@"*
done
2007-05-31 05:09:45 +04:00
;;
esac