state transfer with UPGRADE

[Eoin Mooney]

Hi all,

Using UPGRADE protocol with jgroups 5.2 from:

• https://github.com/jgroups-extras/upgrade-common
• https://github.com/jgroups-extras/upgrade-jgroups

It seems the asynchronous nature of the UPGRADE protocol leads to a race-condition in JChannel.connect(), where it is possible that canFetchState is evaluated before a view is installed installed. When this happens, getState() is not called within JChannel.connect()

About 5-6 years ago, I noticed this same behavior (with a previous implementation of the protocol to support rolling upgrades - named RELAY3 at the time): https://groups.google.com/u/1/g/jgroups-dev/c/V_qtFDNQPwo/m/3UOwkUkoAwAJ

... but I completely missed the request to create a ticket at the time

I guess I'm wondering if this behavior is still considered broken? Should I raise an issue to track it?

Thanks in advance,

/Eoin

[Bela Ban]

To be honest, I haven't worked on the upgrade-xxx projects over the last years. I started the jgraas/jgraas/common projects, which IMO is the simpler approach, but also haven't had much time to work on them.

If you want to submit a PR I'd be happy to apply it, but I'm afraid I won't have time to look into this.
Cheers,

--
You received this message because you are subscribed to the Google Groups "jgroups-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jgroups-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/jgroups-dev/71441969-b465-455d-92d4-4f7aed5a7ba3n%40googlegroups.com.

-- 
Bela Ban | http://www.jgroups.org