jp$

Hey Bela So the issue seems to have been resolved. Its under testing for now. I just wanted to clarify a few more nuances about our setup which other's might find useful and I want to see if there's a better configuration than what I have currently I did not mention this earlier by in my setup we have big physical machines on which we are running multiple JVM's each of which runs our application. Should that require a specific change to get better throughput? My current configuration is as mentioned...

Thanks a lot - I'll test this configurations out and keep you posted.

Hello - We are using a commerce platform which internally uses jgroups for its clustering needs. We have had an ongoing issue where in nodes get out of the cluster, we have not been able to establish a cause for the same however the hypothesis which we have is that whenever the CPU utilization on the nodes spikes it causes nodes to step out of the cluster and they do not join back in. We are running JGroups 3.4 and considering a bunch of options 1. Upgrading to Jgroups 3.6 however this being vendor...

The warning's which we get are [m2017-09-20 20:03:09,127 WARN [Incoming-2,CNC-dr,node-608] [] () [org.jgroups.protocols.pbcast.NAKACK2] JGRP000011: node-608: dropped message 6640 from non-member node-216 (view=[node-317|11220] (86) [node-317, node-600, node-601, node-602, node-603, node-605, node-604, node-606, node-608, node-607, node-609, node-611, node-613, node-614, node-610, node-615, node-612, node-616, node-500, node-501 ...]) (received 25 identical messages from node-216 in the last 63706...

Hello - We are using a commerce platform which internally uses jgroups for its clustering needs. We have had an ongoing issue where in nodes get out of the cluster, we have not been able to establish a cause for the same however the hypothesis which we have is that whenever the CPU utilization on the nodes spikes it causes nodes to step out of the cluster and they do not join back in. We are running JGroups 3.1 and considering a bunch of options 1. Upgrading to Jgroups 3.6 however this being vendor...