Re: [Maria-discuss] jdbc failure after restart

2016-11-23 Thread Diego Dupin
Only SHOW and SET query are allowed on non primary nodes. If this is those kind of query you want to run, you always can correct directly to this specific node. Not sure it works with MySQL connector, (maybe with old version like 5.1.30, but since then, evolution of connector use different "select"

Re: [Maria-discuss] jdbc failure after restart

2016-11-23 Thread l vic
That makes sense, thanks... My question, howerver: what do i need to do so that my jdbc client could periodically run query on remaining node even if wsrep_ready=OFF? On Tue, Nov 22, 2016 at 7:21 PM, Diego Dupin wrote: > Hi, > > As documented here (https://mariadb.com/kb/en/mariadb/mariadb-galer

Re: [Maria-discuss] jdbc failure after restart

2016-11-22 Thread Diego Dupin
Hi, As documented here ( https://mariadb.com/kb/en/mariadb/mariadb-galera-cluster-known-limitations/) : > >- A command may fail with ER_UNKNOWN_COM_ERROR producing 'WSREP has >not yet prepared node for application use' (or 'Unknown command' in older >versions) error message. It happen

[Maria-discuss] jdbc failure after restart

2016-11-22 Thread l vic
i have the following jdbc exception in my jdbc client for the node 1 after another node (node2) is removed: om.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: WSREP has not yet prepared node for application use at sun.reflect.GeneratedConstructorAccessor9.newInstance(Unknown So