Vladimir, I agree with you, StatefulSet is not related here.
> it's not a strict rule to communicate only directly with a pod > running a node with a primary partition Yes, if a node with a primary partition is not known or can't be contacted, we fail over to a default (random) node (afaik this is how Java, C++ and .NET thin clients are implemented) On Thu, Aug 13, 2020 at 12:44 PM Vladimir Pligin <vova199...@yandex.ru> wrote: > Hi guys, > > Maybe I'm missing something but I don't undestand how StatefulSet relates > to > the described functionality. > StatefulSet is more about persistence. Correct me if I'm wrong but my > current understanding is that we don't need to have any explicit state for > a > thin client connection. I'd like this thing to be simple: if I'm working > with a pod and it fails then I just go to another one and try my request > again. The corner case is the best-effort affinity. As far as I can it's > not > a strict rule to communicate only directly with a pod running a node with a > primary partition. It's ok to fail-over in this case and communicate with > any pod. Am I right? > > > > -- > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ >
