This content has been marked as final. Show 1 reply
FYI, with no change in code a machine reboot has cleared the problem, which just makes me worry more since
this is (will be) all about rolling upgrade changes in production when we deploy the new members, and machine
restarts are not an option there.
If the new nodes come up and can't see what's in the replicated cache, that's a big problem.
If it's going to be a problem, I need to know so I can try to work around it.
It was consistently a problem for me for two days, and went away when I rebooted this morning.
Also FYI, each time I would reproduce the problem the last two days, I'd be starting clusters
from scratch for testing. So I'd start the old software, get things running, data populated, etc,
then start the new member that needed to see the replicated cache entries of the existing cluster,
and they would be missing.
Can't reproduce it today after the reboot though.
Yes, guilty of losing clarity by trying to add clarity by being redundant, apologies.