MySQL Forums :: NDB clusters :: Data Node/Mgmt Node in NDBCluster disconnect make error code 157 returned in Java Persistence application


Advanced Search

Re: Data Node/Mgmt Node in NDBCluster disconnect make error code 157 returned in Java Persistence application
Posted by: Mikael Ronström ()
Date: December 01, 2016 11:01AM

Transaction failure at node failure is normal.
Simply retry transaction again and it should work.

Node failures introduce a lot of problematic situations that
are hard to solve without aborting transaction. So transaction
failures at node crashes is normal and application should be
designed to handle it with normal retries. There is a number
of other situations also in databases that can lead to temporary
errors such as deadlocks, various timeouts. So it is always a
good idea to handle temporary errors from transactions.

Options: ReplyQuote


Subject Views Written By Posted
Data Node/Mgmt Node in NDBCluster disconnect make error code 157 returned in Java Persistence application 471 Support HK 11/24/2016 12:42AM
Re: Data Node/Mgmt Node in NDBCluster disconnect make error code 157 returned in Java Persistence application 178 Mikael Ronström 12/01/2016 11:01AM
Re: Data Node/Mgmt Node in NDBCluster disconnect make error code 157 returned in Java Persistence application 170 Support HK 12/06/2016 02:55AM
Re: Data Node/Mgmt Node in NDBCluster disconnect make error code 157 returned in Java Persistence application 168 Jon Stephens 12/06/2016 03:15AM
Re: Data Node/Mgmt Node in NDBCluster disconnect make error code 157 returned in Java Persistence application 176 Support HK 12/06/2016 04:45AM
Re: Data Node/Mgmt Node in NDBCluster disconnect make error code 157 returned in Java Persistence application 173 Mikael Ronström 12/13/2016 08:01AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.