Hi! Unfortunately, support of peer class loading and data streams is limited for thin clients. AFAIK, .Net thin client supports data streamer.
I found that Ignite has a special mode of running client nodes `forceClientToServerConnections` [1]. But this feature is marked as experimental since 2.9 and I don't see any updates there. Actually, I'm not aware about this feature much. I found the feature discussion on dev list [2]. Maybe somebody from the community can say more about this feature. But looks like it can be a solution in your case. [1] https://ignite.apache.org/docs/latest/clustering/running-client-nodes-behind-nat [2] https://www.mail-archive.com/dev@ignite.apache.org/msg44990.html On Mon, Nov 15, 2021 at 12:15 PM MJ <6733...@qq.com> wrote: > That would be peer class loading && data stream . > > Thanks > > ------------------ 原始邮件 ------------------ > *发件人:* "user" <timonin.ma...@gmail.com>; > *发送时间:* 2021年11月15日(星期一) 下午3:59 > *收件人:* "user"<user@ignite.apache.org>; > *主题:* Re: client node connects to server nodes behind NAT > > Hi, I'll touch on a similar topic a little tomorrow on IgniteSummit [1], > you're welcome :) > > But, a thick client is part of topology, and it has to be able to connect > every node in the cluster directly, then thick clients have to be run > within the same kubernetes cluster. Thin clients were designed to eliminate > this problem. > > What features of thick clients do you want to use? > > [1] https://ignite-summit.org/sessions/293596 > > On Mon, Nov 15, 2021 at 3:50 AM MJ <6733...@qq.com> wrote: > >> Hi, >> >> Is that possible for a non-Kubernetes client node connects to server >> nodes within Kubernetes ? >> >> have read below docs seems impossible >> >> https://ignite.apache.org/docs/latest/installation/kubernetes/azure-deployment#connecting-client-nodes >> >> Have tried with thin client outside of Kubernetes - that works fine >> client node(thick client) - always throw exceptions, most likely the >> internal ips bebind NAT cannot be detected from external , is there any >> workaround to implement that non-Kubernetes client node connects to server >> nodes within Kubernetes ? I'd like to utilise the power features of thick >> client. and They can be depoloyed everywhere if there is the way of making >> it. >> >> >> >> Thanks, >> Ma Jun >> >
