It appears that your application attempts to join the cluster as a peer member. During a rolling upgrade, only peers running an older version are not allowed to join the cluster. Can you upgrade the application node after restarting the locator with the new geode version?
Anthony > On Oct 20, 2017, at 9:09 AM, George Wilder <[email protected]> wrote: > > I have deployed a java application configured as a peer-to-peer Apache Geode > v1.1.1 cache. I also have an Apache Geode v1.1.1 locator. Both application > and locator, when running, connect to one another with no issue. > I stop both application and locator, then replace the locator with an updated > Apache Geode v1.2.1 locator. When I restart the application(v1.1.1) and the > locator(v1.2.1), the locator performs a version check and rejects the > connection attempt made by the application: > > INFO o.a.g.d.i.m.g.Services : received join request from > 172.17.0.13(12):32768(version:GEODE 1.1.0) > WARN o.a.g.d.i.m.g.Services : detected an attempt to start a peer using > an older version of the product 172.17.0.13(12):32768(version:GEODE 1.1.0) > DEBUG o.a.g.d.i.m.g.Services : sending via JGroups: > [JoinResponseMessage(null; ; Rejecting the attempt of a member using an older > version of the product to join the distributed system)] recipients: > [172.17.0.13(12):32768(version:GEODE 1.1.0)] > > Is this expected? >
