That's right. This IEP has been only implemented for C++ thin for now.
Best Regards,
Igor
On Fri, Apr 26, 2019 at 2:05 PM kcheng.mvp wrote:
> Hi Igor,
>
> I just checked the jiras and found this IPE has not been implemented for
> *java thin client* yet ?
>
>
>
>
>
Hi Igor,
I just checked the jiras and found this IPE has not been implemented for
*java thin client* yet ?
https://issues.apache.org/jira/issues/?jql=project%20%3D%20Ignite%20AND%20labels%20IN%20(iep-23)%20ORDER%20BY%20status%20%20%20%20%20%20%20
--
Sent from:
Thank your information very much!
Thanks,
Ken Cheng
On Fri, Apr 26, 2019 at 12:32 AM Igor Sapego wrote:
> The point of "Best effort" is that we do not guarantee every requested
> to be routed to the optimal node, we only apply our best effort to make
> this happen.
>
> No, cluster will NOT
The point of "Best effort" is that we do not guarantee every requested
to be routed to the optimal node, we only apply our best effort to make
this happen.
No, cluster will NOT return a address list to the client upon handshake
because.
1. It may be not secure to connect to nodes, which user did
I am still on the design phrase of go thin client. once it's ready I will
share the link. thanks.
Thanks,
Ken Cheng
On Thu, Apr 25, 2019 at 10:02 PM Igor Sapego wrote:
> Hello,
>
> Are you developing a Go thin client? Can you share a link?
>
> There is already one go client I'm aware of [1],
Not sure my understanding is correct or not.
There is the case when a new node join a cluster, if it's just as your said
then some key can not get directly from *the new added node*
I suppose it would work as below.
1: 5 node cluster(a,b,c,d,e)
2: even I just set two nodes/endpoints in the
with IEP-23
there is a change
1. Tries to establish connection to hosts, which is not yet connected.
This is required as changes of the topology may be caused by the new node
joining the cluster.
Thanks,
Ken Cheng
On Thu, Apr 25, 2019 at 10:02 PM Igor Sapego wrote:
> Hello,
>
>
Hello,
Are you developing a Go thin client? Can you share a link?
There is already one go client I'm aware of [1], is yours related somehow?
As for your question, thin client is given list of IPs and ports by a user.
During the start,
or in background thin client tries to establish connection
Thank your information very much!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>From the document
https://apacheignite.readme.io/docs/java-thin-client-initialization-and-configuration
knows that ignite **thin** client mode failover is achieved by specified
multiple hosts(endpoints).
But I know there is a new feature called IEP-23: Best Effort Affinity for
thin clie
10 matches
Mail list logo
