Hi Xavier,
Unfortunately, after some tests I encountered a strange behaviour.
I have two database DB1 and DB2.
I stop the database DB2, DB2 is always enabled because sequoia cannot
know that I stopped the second DB.
I execute some read requests.
The first one is sent to the de db1 ==> OK
The second one is sent to the db2 ==> KO (I just stopped the db).
But the result of my query is null :(
It is like my second request was not redirected to the valid DB1 ?
Did you already encounter this ?
I don't know which database you use but Sequoia relies on the database
JDBC driver to throw an SQLException when the database is down. If your
database driver returns a null ResultSet instead, it might be returned
back to the application.
In your scenario, we should execute on DB2, fail and automatically retry
on DB1 and return the result.
Could you look in your full_cluster.log file if you can see any error
message?
Thanks for your feedback,
Emmanuel
--
Emmanuel Cecchet
Chief Scientific Officer, Continuent
Blog: http://emanux.blogspot.com/
Open source: http://www.continuent.org
Corporate: http://www.continuent.com
Skype: emmanuel_cecchet
Cell: +33 687 342 685
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
