[keycloak-dev] Infinispan error during update in ha configuration

[Мартынов Илья]

Hi Marek,

Ok, I got it, thank you for response!

вт, 2 июля 2019 г., 19:25 Marek Posolda <mposolda at redhat.com>:

> I think you can't mix old and new Keycloak servers in same cluster. And
> rolling upgrade (zero downtime upgrade) is not yet supported. We plan to
> add support for it, but it won't be in a very near future as it will
> likely require quite a lot of work...
>
> In shortcut, it will be recommended to stop all pods with 4.5.0 and then
> start pods with 6.0.1.
>
> Marek
>
>
> On 02/07/2019 16:25, Мартынов Илья wrote:
> > Hello!
> > I have Keycloak 4.5.0.Final deployed in standalone-ha configuration in
> k8s
> > cluster. When I try to update Keycloak to version 6.0.1, the following
> > happens:
> > 1. K8s starts new pod with version 6.0.1
> > 2. Old pod still running, it will be terminated on successfull readiness
> > probe of the new pod
> > 3. New pod discovers old pod via JGroups, cache synchronization started
> > 4. Exception in new pod:
> > 02-07-2019;13:34:29,220 WARN [stateTransferExecutor-thread--p25-t1]
> > org.infinispan.statetransfer.InboundTransferTask ISPN000210: Failed to
> > request state of cache work from node idp-6569c544b
> > -hsd6g, segments {0-255}: org.infinispan.remoting.RemoteException:
> > ISPN000217: Received exception from idp-6569c544b-hsd6g, see cause for
> > remote stack trace
> >          at org.infinispan at 9.4.8.Final
> >
> //org.infinispan.remoting.transport.ResponseCollectors.wrapRemoteException(ResponseCollectors.java:28)
> > ...
> > Caused by: java.io.IOException: Unknown type: 132
> >          at
> >
> org.infinispan.marshall.core.GlobalMarshaller.readNonNullableObject(GlobalMarshaller.java:681)
> >          at
> >
> org.infinispan.marshall.core.GlobalMarshaller.readNullableObject(GlobalMarshaller.java:355)
> >          at
> >
> org.infinispan.marshall.core.BytesObjectInput.readObject(BytesObjectInput.java:40)
> >
> > Looks like this exception blocks further Keycloak startup, because
> nothing
> > happens in logs afterwards. Also, my rest service deployed as JAX-RS bean
> > also doesn't respond, so pod is not treated as alive by Kubernetes.
> > Please help.
> > _______________________________________________
> > keycloak-dev mailing list
> > keycloak-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/keycloak-dev
>
>
>