ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alper Tekinalp <al...@evam.com>
Subject Re: Finding Key to Node Mapping
Date Fri, 23 Sep 2016 08:04:31 GMT
Hi Val.

We use ignite as client in our GUI app that mostly used by our
clients. When our servers are on amazon it is imposibble to connet
servers because most of the time it is impossible to configure port
forwarding on the router.

Other than that we have issues on waiting time for clients to connect
servers. It takes 30-50 seconds for the client to connect the
server(s). And for a GUI application it is kinda anoying to wait that
much time specially the only thing it does is to connect the servers,
you know it does not load any data etc.

So as it is not possible to know key-to-node mapping without
connecting to cluster, is it possible to speed up the client? As I
stated before we only usekey-to-node mapping info on client side. So
maybe it is meaningful to disable some threads or turn off features

Regards and thanks for your help.

On Thu, Sep 15, 2016 at 3:12 AM, vkulichenko
<valentin.kulichenko@gmail.com> wrote:
> Alper,
> To apply affinity function, a client has to join topology, otherwise it
> doesn't have information about available nodes. You told in one the threads
> that you were able to connect, so I don't see the issue. Am I missing
> something?
> -Val
> --
> View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Finding-Key-to-Node-Mapping-tp7653p7756.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Alper Tekinalp

Software Developer

Evam Stream Analytics

Atatürk Mah.Turgut Özal Bulvarı Gardenya 1 Plaza 42/B K:4 Ataşehir / İSTANBUL

Tlf : +90216 688 45 46 Fax : +90216 688 45 47 Gsm:+90 536 222 76 01


View raw message