On Tue, 2018-11-13 at 18:41 +0100, Valentin Vidic wrote:
> On Tue, Nov 13, 2018 at 11:01:46AM -0600, Ken Gaillot wrote:
> > Clone instances have a default stickiness of 1 (instead of the
> > usual 0)
> > so that they aren't needlessly shuffled around nodes every
> > transition.
> > You can temporar
On Tue, Nov 13, 2018 at 11:01:46AM -0600, Ken Gaillot wrote:
> Clone instances have a default stickiness of 1 (instead of the usual 0)
> so that they aren't needlessly shuffled around nodes every transition.
> You can temporarily set an explicit stickiness of 0 to let them
> rebalance, then unset i
On Tue, 2018-11-13 at 17:27 +0100, Valentin Vidic wrote:
> On Tue, Nov 13, 2018 at 05:04:19PM +0100, Valentin Vidic wrote:
> > Also it seems to require multicast, so better check for that too :)
>
> And while the CLUSTERIP resource seems to work for me in a test
> cluster, the following clone defi
On Tue, Nov 13, 2018 at 05:04:19PM +0100, Valentin Vidic wrote:
> Also it seems to require multicast, so better check for that too :)
And while the CLUSTERIP resource seems to work for me in a test
cluster, the following clone definition:
clone cip-clone cip \
meta clone-max=2 clone-nod
On Tue, Nov 13, 2018 at 04:06:34PM +0100, Valentin Vidic wrote:
> Could be some kind of ARP inspection going on in the networking equipment,
> so check switch logs if you have access to that.
Also it seems to require multicast, so better check for that too :)
--
Valentin
On Tue, Nov 13, 2018 at 09:06:56AM -0500, Daniel Ragle wrote:
> Thanks, finally getting back to this. Putting a tshark on both nodes and
> then restarting the VIP-clone resource shows the pings coming through for 12
> seconds, always on node2, then stop. I.E., before/after those 12 seconds
> nothin
On 10/11/2018 5:00 PM, Valentin Vidic wrote:
On Thu, Oct 11, 2018 at 01:25:52PM -0400, Daniel Ragle wrote:
For the 12 second window it *does* work in, it appears as though it works
only on one of the two servers (and always the same one). My twelve seconds
of pings runs continuously then stops
On Thu, Oct 11, 2018 at 01:25:52PM -0400, Daniel Ragle wrote:
> For the 12 second window it *does* work in, it appears as though it works
> only on one of the two servers (and always the same one). My twelve seconds
> of pings runs continuously then stops; while attempts to hit the Web server
> wor
I'm adding a VIP to my active/active two node cluster using IPaddr2.
These are on updated CentOS 7.5 machines.
When I bring up the IP, I'm able to ping it from an external machine for
about 12 seconds and then I get no further responses. This happens each
time I restart the VIP clone.
I can
