Jeff, The sessionAffinity is needed only if you plan to access Ignite cluster deployed in K8 from an application deployed outside of it. For instance, it will ensure that a remote JDBC session will stick to a specific Ignite pod.
However, if all your applications are deployed in K8 as well then you can freely disregard sessionAffinity parameter. Is this your case? -- Denis On Tue, Sep 11, 2018 at 10:16 AM Jeff Simon <jeffsi...@fico.com> wrote: > Yes if I remove session affinity it works. So my question is does ignite > require sessionAffinity? And to be honest, I'm not really sure what we are > using ignite for since it seems to be a multi-purpose app. I think we are > going to use for caching. So would session affinity be required for > caching? I'm guessing the answer would be 'no, it's not required.' > > Thanks, Jeff > > On 9/10/18, 4:15 PM, "vkulichenko" <valentin.kuliche...@gmail.com> wrote: > > Does it work without specifying sessionAffinity? > > -Val > > > > -- > Sent from: > https://urldefense.proofpoint.com/v2/url?u=http-3A__apache-2Dignite-2Dusers.70518.x6.nabble.com_&d=DwICAg&c=ObqWq9831a7badpzAhIKIA&r=GDHaUsXuW5l_tQf8Lb0qSFuKsPCA5WAkjY2k5nQo7uw&m=nGR_kKy4EMqQjzu9FfD9BViiBYvvkZabdxLvh7lXjYw&s=Z-AZJ1xOOCKZyUNQNOndPrBGu7rnXR0zTXTyOSUwNbM&e= > > > This email and any files transmitted with it are confidential, proprietary > and intended solely for the individual or entity to whom they are > addressed. If you have received this email in error please delete it > immediately. >
