Re: Ignite Cluster Error

2018-01-02 Thread Usman Waheed
Yes Sir, that exception is from my code that has caused ignite2 (second ignite node) to go offline :) Investigating now ... -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Cluster Error

2018-01-02 Thread Denis Mekhanikov
Usman, This exception is thrown from your code, so you will have to deal with it yourself :) I would also recommend you to reset all timeouts to default values. They seem to be too high. As Ignite suggests you in log, failure detection will work faster, if you don't assign such big values to time

Re: Ignite Cluster Error

2018-01-02 Thread Usman Waheed
Hi Denis, I saw the following error message in the logs on one of my ignite nodes (ml-ignite1.mobilink.osa): 02/01/2018 10:39:12 WARN [tcp-disco-msg-worker-#2%jazz-prod-triggers-anum%] TcpDiscoverySpi: Local node has detected failed nodes and started cluster-wide procedure. To speed up failure d

Re: Ignite Cluster Error

2018-01-02 Thread Usman Waheed
Hi Denis, I did not see any other errors but let me dig more and will share. Best Regards, Usman -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Cluster Error

2018-01-02 Thread Denis Mekhanikov
Hi Usman! "Timeout has occurred", printed by *GridTimeoutProcessor*, is an internal debug message, which tells you, that some scheduled task is getting executed. It's not an error. And you shouldn't be worried about "connection refused" exceptions on the node startup. They are thrown for all reje

Re: Ignite Cluster Error

2018-01-01 Thread Usman Waheed
For the connection refused error in the logs we have set ipFinder property to: 10.145.1.14:4750

Re: Ignite Cluster Error

2018-01-01 Thread Usman Waheed
Logs from 2 node ignite cluster attached. ​ node1.tar ​​ node2.tar ​ On Fri, Dec 29, 2017 at 1:10 PM, Usman Waheed wrote:

Re: Ignite Cluster Error

2017-12-29 Thread Usman Waheed
Thanks Evgenii , will get back to this thread. On Fri, Dec 29, 2017 at 1:09 PM, Evgenii Zhuravlev wrote: > Please provide logs from all nodes with -DIGNITE_QUIET=false for > investigation > > Evgenii > > 2017-12-29 11:03 GMT+03:00 Usman Waheed : > >> Correction at my end, we increased the timeou

Re: Ignite Cluster Error

2017-12-29 Thread Evgenii Zhuravlev
Please provide logs from all nodes with -DIGNITE_QUIET=false for investigation Evgenii 2017-12-29 11:03 GMT+03:00 Usman Waheed : > Correction at my end, we increased the timeout's to see if it helps to > resolve our problem but no luck. > So we can set it back to the default settings. > > I am a

Re: Ignite Cluster Error

2017-12-29 Thread Usman Waheed
Correction at my end, we increased the timeout's to see if it helps to resolve our problem but no luck. So we can set it back to the default settings. I am also pasting some more settings: While searching for a resolution, i stumbled upon: https://issues.apache.org/jira/browse/IGNITE-6555 which i

Re: Ignite Cluster Error

2017-12-28 Thread Evgenii Zhuravlev
Hi, Why did you set so big timeouts? Why don't default timeouts work for you? Evgenii 2017-12-29 10:35 GMT+03:00 Usman Waheed : > Hi, > > We have deployed apache ignite fabric 2.3 > > We get the below error when trying to run on more than 1 node. > > GridTimeoutProcessor: Timeout has occurred:

Ignite Cluster Error

2017-12-28 Thread Usman Waheed
Hi, We have deployed apache ignite fabric 2.3 We get the below error when trying to run on more than 1 node. GridTimeoutProcessor: Timeout has occurred: CancelableTask [id=970ee7b2061-c1565aa4-510c-4046-9ebb-46efd861b4df, endTime=1512558510454, period=5000, cancel=false, task=org.apache.ignite.

Re: “Failed to communicate with Ignite cluster" error when using JDBC Thin driver

2017-12-26 Thread dkarachentsev
Hi, It's hard to say why it happens. I'm not familiar with mybatis and actually don't know if it shares jdbc connection between threads. It would be great if you could provide some reproducible example that will help to debug the issue. Thanks! -Dmitry -- Sent from: http://apache-ignite-users.

Re: “Failed to communicate with Ignite cluster" error when using JDBC Thin driver

2017-12-22 Thread gunman524
We are using mybatis to manage connection, is that matters? BTW, I check the code in JdbcThinTcpIo method sendRequest JdbcResponse sendRequest(JdbcRequest req) throws IOException { int cap = guessCapacity(req); BinaryWriterExImpl writer = new BinaryWriterExImpl(null, new Binary

Re: “Failed to communicate with Ignite cluster" error when using JDBC Thin driver

2017-12-21 Thread dkarachentsev
Is there any case that you're using Connection in more than one thread? It's not thread safe for now. Thanks! -Dmitry -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: “Failed to communicate with Ignite cluster" error when using JDBC Thin driver

2017-12-20 Thread gunman524
It could not be a version issue, the thin driver and cluster version are exactly same. It can happened on any query but can not be reproduce 100%, it only happened "some times". In Log, I found "Caused by: java.io.IOException: Failed to read incoming message (not enough data). " Firstly I gu

Re: “Failed to communicate with Ignite cluster" error when using JDBC Thin driver

2017-12-20 Thread dkarachentsev
Hi, Is it possible that version of thin driver is different from version of cluster nodes? Does it happen on concrete queries or it could be on any one? Thanks! -Dmitry -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

“Failed to communicate with Ignite cluster" error when using JDBC Thin driver

2017-12-20 Thread gunman524
Hi guys, When I use ignite jdbc thin driver connect Ignite cluster, sometimes will meet the errors below. Do you have any idea what cause this error? many thanks! org.springframework.dao.DataAccessResourceFailureException: ### Error updating database. Cause: java.sql.SQLException: Failed to c