You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by ozgurnevres <oz...@gmail.com> on 2017/04/03 09:30:14 UTC
A question about cluster configuration (Are there any way to make
client connection faster?)
The ignite configuration in my app.config (and web.config) is like below:
<discoverySpi type="TcpDiscoverySpi">
<localPort>48500</localPort>
<ipFinder type="TcpDiscoveryStaticIpFinder">
<endpoints>
<string>192.168.1.100:48500</string>
</endpoints>
</ipFinder>
</discoverySpi>
<communicationSpi type="TcpCommunicationSpi">
<localPort>48100</localPort>
</communicationSpi>
With that configuration, a client on the same network (on a different
computer) connects around 10-12 seconds.
If I use an IP block like 192.168.1.100:48500..48520 it takes even more
time.
Are there any way to make this faster? What is the best practice?
Thanks
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/A-question-about-cluster-configuration-Are-there-any-way-to-make-client-connection-faster-tp11655.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: A question about cluster configuration (Are there any way to
make client connection faster?)
Posted by afedotov <al...@gmail.com>.
Hi,
Specifying a port range leads to more ports to be scanned and checked, so
the delay is bigger. But the whole time highly depends on many factors:
cache config, network latencies, system load on nodes etc.
Kind regards,
Alex
3 апр. 2017 г. 9:08 PM пользователь "vdpyatkov [via Apache Ignite Users]" <
ml-node+s70518n11681h45@n6.nabble.com> написал:
Hi,
If you are use port range, than this can consume more time, because
Discovery SPI try to connect to by all port in range.
But If you are specified single port, connection should be fast.
Why are you think that delay occur on discovery phase?
------------------------------
If you reply to this email, your message will be added to the discussion
below:
http://apache-ignite-users.70518.x6.nabble.com/A-question-about-cluster-
configuration-Are-there-any-way-to-make-client-connection-
faster-tp11655p11681.html
To start a new topic under Apache Ignite Users, email
ml-node+s70518n1h65@n6.nabble.com
To unsubscribe from Apache Ignite Users, click here
<http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=1&code=YWxleGFuZGVyLmZlZG90b2ZmQGdtYWlsLmNvbXwxfC0xMzYxNTU0NTg=>
.
NAML
<http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/A-question-about-cluster-configuration-Are-there-any-way-to-make-client-connection-faster-tp11655p11693.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: A question about cluster configuration (Are there any way to
make client connection faster?)
Posted by vdpyatkov <vl...@gmail.com>.
Hi
If you are use port range, than this can consume more time, because
Discovery SPI try to connect to by all port in range.
But If you are specified single port, connection should be fast.
Why are you think that delay occur on discovery phase?
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/A-question-about-cluster-configuration-Are-there-any-way-to-make-client-connection-faster-tp11655p11681.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.