[Pacemaker] IPaddr2 started but "not working"

[Michael Schwartzkopff]

Am Montag, 28. Oktober 2013, 11:15:07 schrieb Francesco Namuri:
> Il 28/10/2013 10.38, Michael Schwartzkopff ha scritto:
> > Am Montag, 28. Oktober 2013, 10:25:47 schrieb Francesco Namuri:
> >> Hi Lars,
> >> 
> >> Il 28/10/2013 09.56, Lars Marowsky-Bree ha scritto:
> >>> On 2013-10-28T09:38:34, Francesco Namuri <f.namuri at credires.it> wrote:
> >>>> Hi,
> >>>> I've a problem with a IPaddr2 resource, it appears to be started
> >>>> correctly and it works for a while, but after it appears "to be
> >>>> hanged",
> >>>> it doesn't work until I send it a restart.
> >>>> Does anyone has experienced similar issue?
> >>> 
> >>> You're running it in cluster-ip mode; why?
> >> 
> >> Is that question related to the cluster-ip parameter?
> >> I removed it from the cluster ip of the WLAN...
> >> 
> >>>> --code--
> >>>> primitive cluster_ip_wlan ocf:heartbeat:IPaddr2 \
> >>>> 
> >>>>         params ip="172.16.15.254" cidr_netmask="32"
> >>>> 
> >>>> clusterip_hash="sourceip-sourceport" \
> >>>> 
> >>>>         op monitor interval="10s" \
> >>>>         meta target-role="Started"
> >>>> 
> >>>> --------
> >>> 
> >>> I'd suggest to drop the "clusterip_hash" parameter, unless you're also
> >>> running it as a clone. (In which case seeing your full configuration
> >>> would be needed.)
> >> 
> >> I put the "clusterip_hash" option, thinking that it could help to avoid
> >> dropping established connections when I switch from one node to the
> >> other.
> >> I followed a howto, but I'm really not sure about that.
> > 
> > No. I will not preserve connections from one node to the other.
> > If you are not sure, do not configure it.
> > If you don't know what it does, do not configure it.
> 
> It's always a good advice :)
> I remove it from all the configuration.
> Is there a method to avoid dropping connection when I switched from a
> node to another?

Generally: No.
Only in very limited cases, when the applications provides a state table sync. 
This is the case i.e. for iptables firewalls and ipvs load balancers.

In some cases the tcp stack can recover the connection and some times the 
applications can recover (FTP, downloads in HTTP, ...) or just retry.

But in most cases the users will have to press "reload" or something 
comparable.

-- 
Mit freundlichen Grüßen,

Michael Schwartzkopff

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 230 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20131028/ea5e3b8f/attachment-0004.sig>