Server created remotely, C# client not able to connect to cluster with IP address

classic Classic list List threaded Threaded
7 messages Options
abd abd
Reply | Threaded
Open this post in threaded view
|

Server created remotely, C# client not able to connect to cluster with IP address

This post was updated on .
CONTENTS DELETED
The author has deleted this message.
akorensh akorensh
Reply | Threaded
Open this post in threaded view
|

Re: Server created remotely, C# client not able to connect to cluster with IP address

This post was updated on .
Hi,
  Looks like you either did not set the thin client ip correctly, there
is a network issue
  preventing the C# thin client from connecting, or the server itself has
not started or is not responding.

  message:  because connected host has failed to respond.
171.159.66.12:10800
   The server would need to be started on 171.159.66.12 in this case.
  The discovery section in the server just tells the server where to find other nodes.
    Check that the clientconnector is up and running at port 10800:
  see:
https://ignite.apache.org/docs/latest/thin-clients/getting-started-with-thin-clients#configuring-thin-client-connector


  Make sure that the Server has started and that you are able to connect to
it via other thin clients.
  Try using sqlline:   https://ignite.apache.org/docs/latest/tools/sqlline


  There is also the possibility that the default timeout is not enough for
your use case:
https://ignite.apache.org/releases/2.9.0/javadoc/org/apache/ignite/configuration/ClientConnectorConfiguration.html#setHandshakeTimeout-long-

  see this example for a simple C# client:
https://github.com/apache/ignite/blob/master/modules/platforms/dotnet/examples/Apache.Ignite.Examples/ThinClient/ThinClientPutGetExample.cs

  doc: https://ignite.apache.org/docs/latest/thin-clients/dotnet-thin-client

Thanks, Alex



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
akorensh akorensh
Reply | Threaded
Open this post in threaded view
|

Re: Server created remotely, C# client not able to connect to cluster with IP address

In reply to this post by abd
  message:  because connected host has failed to respond. 171.159.66.12:10800

  Ignite would need to be started on 171.159.66.12 in this case.
  The discovery section in tells the server where to find other nodes.

  see : https://ignite.apache.org/docs/latest/clustering/tcp-ip-discovery

  Check that the ip of the server you've started ignite from is
171.159.66.12
  Make sure that this ip is reachable from your client node.
 
  You might need to set the localhost manually.
 
https://ignite.apache.org/docs/latest/clustering/network-configuration#discovery



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
abd abd
Reply | Threaded
Open this post in threaded view
|

Re: Server created remotely, C# client not able to connect to cluster with IP address

This post was updated on .
CONTENTS DELETED
The author has deleted this message.
akorensh akorensh
Reply | Threaded
Open this post in threaded view
|

Re: Server created remotely, C# client not able to connect to cluster with IP address

To see that an IP is reachable from the client node, try using telnet <IP>
<PORT> from the client host.
In your case the port should be 10800 and the IP is the one you are starting
the server from.

The discovery section tells Ignite where to find other nodes needed to form
a cluster. If there is a node on 171.159.66.12 that needs to be in the
cluster then include it in the discovery section.

If the cluster consists of only one server, you can leave the discovery
section blank.

Read through this section:
https://ignite.apache.org/docs/latest/clustering/tcp-ip-discovery




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
abd abd
Reply | Threaded
Open this post in threaded view
|

Re: Server created remotely, C# client not able to connect to cluster with IP address

CONTENTS DELETED
The author has deleted this message.
akorensh akorensh
Reply | Threaded
Open this post in threaded view
|

Re: Server created remotely, C# client not able to connect to cluster with IP address