ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Kuznetsov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-11837) Thin client fails to connect to the cluster if one node is down
Date Tue, 14 May 2019 11:32:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-11837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Pavel Kuznetsov updated IGNITE-11837:
-------------------------------------
    Description: 
According to java doc: 

in org.apache.ignite.Ignition

{code:java}

/**
 * Initializes new instance of \{@link IgniteClient}.
 * <p>
 * Server connection will be lazily initialized when first required.
 *
 * @param cfg Thin client configuration.
 * @return Successfully opened thin client connection.
 */
 public static IgniteClient startClient(ClientConfiguration cfg)

 \{code}

 

{code}

but that seems wrong as I get exception:

Exception in thread "main" org.apache.ignite.client.ClientConnectionException: Ignite cluster
is unavailable
 at org.apache.ignite.internal.client.thin.TcpClientChannel.<init>(TcpClientChannel.java:114)
 at org.apache.ignite.internal.client.thin.TcpIgniteClient.lambda$new$0(TcpIgniteClient.java:79)
 at org.apache.ignite.internal.client.thin.ReliableChannel.<init>(ReliableChannel.java:84)
 at org.apache.ignite.internal.client.thin.TcpIgniteClient.<init>(TcpIgniteClient.java:86)
 at org.apache.ignite.internal.client.thin.TcpIgniteClient.start(TcpIgniteClient.java:205)
 Caused by: java.net.ConnectException: Connection refused: connect
 at java.net.DualStackPlainSocketImpl.connect0(Native Method)
 at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:79)
 at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
 at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
 at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
 at java.net.Socket.connect(Socket.java:589)
 at java.net.Socket.connect(Socket.java:538)
 at java.net.Socket.<init>(Socket.java:434)
 at java.net.Socket.<init>(Socket.java:211)
 at org.apache.ignite.internal.client.thin.TcpClientChannel.createSocket(TcpClientChannel.java:216)
 at org.apache.ignite.internal.client.thin.TcpClientChannel.<init>(TcpClientChannel.java:108)at
org.apache.ignite.Ignition.startClient(Ignition.java:586)

 \{code}

 

 

  was:
According to java doc: 

in org.apache.ignite.Ignition

 

/**
 * Initializes new instance of \{@link IgniteClient}.
 * <p>
 * Server connection will be lazily initialized when first required.
 *
 * @param cfg Thin client configuration.
 * @return Successfully opened thin client connection.
 */
public static IgniteClient startClient(ClientConfiguration cfg)

 

but that seems wrong as I get exception:

Exception in thread "main" org.apache.ignite.client.ClientConnectionException: Ignite cluster
is unavailable
 at org.apache.ignite.internal.client.thin.TcpClientChannel.<init>(TcpClientChannel.java:114)
 at org.apache.ignite.internal.client.thin.TcpIgniteClient.lambda$new$0(TcpIgniteClient.java:79)
 at org.apache.ignite.internal.client.thin.ReliableChannel.<init>(ReliableChannel.java:84)
 at org.apache.ignite.internal.client.thin.TcpIgniteClient.<init>(TcpIgniteClient.java:86)
 at org.apache.ignite.internal.client.thin.TcpIgniteClient.start(TcpIgniteClient.java:205)
 Caused by: java.net.ConnectException: Connection refused: connect
 at java.net.DualStackPlainSocketImpl.connect0(Native Method)
 at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:79)
 at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
 at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
 at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
 at java.net.Socket.connect(Socket.java:589)
 at java.net.Socket.connect(Socket.java:538)
 at java.net.Socket.<init>(Socket.java:434)
 at java.net.Socket.<init>(Socket.java:211)
 at org.apache.ignite.internal.client.thin.TcpClientChannel.createSocket(TcpClientChannel.java:216)
 at org.apache.ignite.internal.client.thin.TcpClientChannel.<init>(TcpClientChannel.java:108)at
org.apache.ignite.Ignition.startClient(Ignition.java:586)

 

 

 


> Thin client fails to connect to the cluster if one node is down
> ---------------------------------------------------------------
>
>                 Key: IGNITE-11837
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11837
>             Project: Ignite
>          Issue Type: Bug
>          Components: thin client
>    Affects Versions: 2.7
>            Reporter: Nikola Arnaudov
>            Assignee: Pavel Kuznetsov
>            Priority: Major
>              Labels: javadoc
>
> According to java doc: 
> in org.apache.ignite.Ignition
> {code:java}
> /**
>  * Initializes new instance of \{@link IgniteClient}.
>  * <p>
>  * Server connection will be lazily initialized when first required.
>  *
>  * @param cfg Thin client configuration.
>  * @return Successfully opened thin client connection.
>  */
>  public static IgniteClient startClient(ClientConfiguration cfg)
>  \{code}
>  
> {code}
> but that seems wrong as I get exception:
> Exception in thread "main" org.apache.ignite.client.ClientConnectionException: Ignite
cluster is unavailable
>  at org.apache.ignite.internal.client.thin.TcpClientChannel.<init>(TcpClientChannel.java:114)
>  at org.apache.ignite.internal.client.thin.TcpIgniteClient.lambda$new$0(TcpIgniteClient.java:79)
>  at org.apache.ignite.internal.client.thin.ReliableChannel.<init>(ReliableChannel.java:84)
>  at org.apache.ignite.internal.client.thin.TcpIgniteClient.<init>(TcpIgniteClient.java:86)
>  at org.apache.ignite.internal.client.thin.TcpIgniteClient.start(TcpIgniteClient.java:205)
>  Caused by: java.net.ConnectException: Connection refused: connect
>  at java.net.DualStackPlainSocketImpl.connect0(Native Method)
>  at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:79)
>  at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
>  at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
>  at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
>  at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
>  at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
>  at java.net.Socket.connect(Socket.java:589)
>  at java.net.Socket.connect(Socket.java:538)
>  at java.net.Socket.<init>(Socket.java:434)
>  at java.net.Socket.<init>(Socket.java:211)
>  at org.apache.ignite.internal.client.thin.TcpClientChannel.createSocket(TcpClientChannel.java:216)
>  at org.apache.ignite.internal.client.thin.TcpClientChannel.<init>(TcpClientChannel.java:108)at
org.apache.ignite.Ignition.startClient(Ignition.java:586)
>  \{code}
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message