When starting up two is servers by setting replica 2, DUPLICATE entry execption is thrown. about kubernetes-is HOT 4 OPEN

@Megala21 @malithie I experienced the same problem a number of times.

A possible solution for this is the introduction of Kubernetes liveness probes [1].

For example, under the WSO2 product Kubernetes resource unification process that began recently, I managed to build up a IS two node cluster in which I've used liveness probes to conduct port scanning (port 9443) to check the liveness of each IS pod as follows:

        livenessProbe:
          exec:
            command:
            - /bin/bash
            - -c
            - nc -z localhost 9443
          initialDelaySeconds: 100
          periodSeconds: 10

If the server startup has failed due to the discussed issue, the liveness probe fails. As a result, it will spawn up a new IS pod after killing the existing unhealthy pod.

[1]: Kubernetes liveness and readiness probes

from kubernetes-is.

During testing it was experienced that the solution suggested in #7 (comment) does not provide the most perfect solution to the discussed issue. It was experienced that the server startup takes place successfully even while the above errors are occurring.

Hence, the current solution that has been adopted is to instruct the user to scale [1] the number of Identity Server instances as desired. By default, the setup is initiated with a single Identity Server instance.

[1]: Instruction to scale the number of nodes

from kubernetes-is.

@malithie, @omindu shall we close this, if this issue has been tested and fixed in latest Identity Server versions?

from kubernetes-is.

Still, we have errors when starting the server parallel.
refer : wso2/product-is#5936

from kubernetes-is.