on 2018 Mar 13 9:11 PM
Hi,
during deployment of our project we are shutting down all the servers in the cluster and starting them up in parallel. The problem is that the startup is slowed down by cluster messages like
hybrisnode-4: JOIN(hybrisnode-4) sent to hybrisnode-1 timed out (after 3000 ms), on try 10
and the server isn't started if the 10 tentatives are reached (in avg can take 10m). Is there a way to avoid this?
Tried already to set
cluster.ping.load.on.startup=false
but without any success.
Any ideas? Thanks in advance, Regards
Hybris version 6.6.0.2
Request clarification before answering.
Solution is here https://launchpad.support.sap.com/#/notes/2736516
problem relates to JGROUPSPRING table entries, which is not getting deleted on server restart
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I checked the table JGROUPSPING and there were way too many records. After removing all of them, now problem seems disappeared.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, so you're using jdbcping? It may be a 6.6. issue, I would open a support ticket.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Look for problems with the JGROUPS table in the cluster's database if using the stock Hybris Commerce jgroups-tcp config. First the nodes advertise their availability to peers there. Are the nodes listed actually up?
Second make sure your nodes can actually reach each others' JGroups TCP port.
hybrisnode-4$ nc -z hybrisnode-1 "${hybris_jgroups_bind_port}"
If you're doing this in IaaS cloud, make sure all the VMs have network/firewall policy allowing them to talk to their peers on their jgroups address/port.
we are only stopping Hybris process. The point is that configuration did not change but we migrated to version 6.6 from 5.7.
We are using Jgroups via TCP with standard configurations.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How did you configure your jgroups, what clustering method and discovery mechanism you use? Does “shut down” here mean killing the node without gracefully stopping hybris?, typically if you redeploy hybris you don’t need to shut down the server just the hybris process.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.