Denis, I am going by the latest updated docs. The instructions DO NOT work as described, producing the error above, same as last year.
Of course, this is for thin clients connecting from outside the cluster. Your instructions state: "The sessionAffinity used below is required only if Ignite cluster is deployed in Kubernetes and your applications are outside of it. The property ensures that Ignite thin clients, JDBC/ODBC drivers preserve a connection with a specific Ignite pod. " So, that sounds like we need it. And yet, it does NOT work, giving the error above. Taking that one line out works, but then we lose the ability to "ensure that Ignite thin clients preserve a connection with a specific pod", which sounds important? This is for an Ignite cluster running in a k8s cluster in AWS. --Stan -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
