Hi,
The test I do is :
Create to controllers (with RAIDb-1). Each controller load virtualdatabase
with one backend. Each backend is in a peer. I work with mysql engine.
few times later I stop the one of my MySQL service and let the controller
and his backend running.
This is the message I've got:
=============== one: exception ===============================
2009-01-28 12:17:58,265 ERROR sequoia.controller.recoverylog Failed to log
begin for transaction 562949953421403
com.mysql.jdbc.CommunicationsException: Communications link failure
Last packet sent to the server was 0 ms ago.
at
com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1070)
at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2103)
at com.mysql.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:718)
at com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:298)
at
com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:282)
at
org.continuent.sequoia.controller.connection.DriverManager.getConnectionForDriver(DriverManager.java:266)
at
org.continuent.sequoia.controller.connection.DriverManager.getConnection(DriverManager.java:168)
at
org.continuent.sequoia.controller.recoverylog.RecoveryLogConnectionManager.connect(RecoveryLogConnectionManager.java:82)
at
org.continuent.sequoia.controller.recoverylog.RecoveryLogConnectionManager.validateConnection(RecoveryLogConnectionManager.java:153)
at
org.continuent.sequoia.controller.recoverylog.RecoveryLogConnectionManager.getLogPreparedStatement(RecoveryLogConnectionManager.java:177)
at
org.continuent.sequoia.controller.recoverylog.events.LogRequestEvent.execute(LogRequestEvent.java:77)
at
org.continuent.sequoia.controller.recoverylog.LoggerThread.run(LoggerThread.java:678)
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:520)
at java.net.Socket.connect(Socket.java:470)
at java.net.Socket.<init>(Socket.java:367)
at java.net.Socket.<init>(Socket.java:209)
at
com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:253)
at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:280)
at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2026)
... 10 more
..............................
=============== two: good act or feedback !!!
=================================
2009-01-28 12:18:00,500 ERROR controller.RequestManager.db Request update
task set CDATE=?, ... failed on all local backends but succeeded on other
controllers. Disabling all local backends.
Let me give your a schema please:
controller1 (bkd) controller2 (bkd)
| |
| |
| |
MySQL service(started) MySQL service (stopped)
But in my First Test, last week, I done this
controller
/\
/ \
/ \
/ \
db1(run) db2 (stop)
Have here a connection time out and wait too long to excute request to the
running database (db1).
Thanks again.
On Tue, Jan 27, 2009 at 6:00 PM, <[email protected]
> wrote:
> Send Sequoia mailing list submissions to
> [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://forge.continuent.org/mailman/listinfo/sequoia
> or, via email, send a message with subject or body 'help' to
> [email protected]
>
> You can reach the person managing the list at
> [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Sequoia digest..."
>
>
> Today's Topics:
>
> 1. Re: [ SEQUOIA ] Backend and database instance (Emmanuel Cecchet)
> 2. Re: Replicate multiple databases for one node (MySQL)
> (Emmanuel Cecchet)
> 3. Critical issue for single controller configurations
> (Emmanuel Cecchet)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 26 Jan 2009 20:33:04 -0500
> From: Emmanuel Cecchet <[email protected]>
> Subject: Re: [Sequoia] [ SEQUOIA ] Backend and database instance
> To: Sequoia general mailing list <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi,
>
> I am not sure I get any of this but if a database backend crashes,
> assuming that it is not the last one in the cluster and you have other
> backends available, Sequoia will do the following (also assuming that
> you have RAIDb-1):
> - SELECT statement are retried on another node
> - writes are executed in parallel on all backends and the result is
> returned from the remaining backends
> - the failed backend is automatically disabled.
>
> When you restart the database instance, you have to follow the procedure
> that I sent you in the previous email (basically restore backend +
> enable) and the backend will be automatically resynchronized.
>
> Hope this helps,
> Emmanuel
> >
> >
> > What happens if the database crash while SEQUOIA (or corresponding
> > backend node) still running?
> >
> > And continue to receive request from client?
> >
> > I test this without disable any backend node. I let them all in enable
> > state.
> > Why I do that? Database crash's unpredictable.
> > So I have Exceptions in the controller trace and this action has an
> > effect on all my application.
> > Then when I restart the database instance (eg MySQL) there is no
> > action like recovery failure on the database.
> > And I thought that maybe it (sequoia) is not planned for this.
> >
> > I prefer to ask before drawing a conclusion.
> >
> > Thanks for your advices.
> >
> > --
> > Bakary,
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Sequoia mailing list
> > [email protected]
> > https://forge.continuent.org/mailman/listinfo/sequoia
>
>
> --
> Emmanuel Cecchet
> FTO @ Frog Thinker
> Open Source Development & Consulting
> --
> Web: http://www.frogthinker.org
> email: [email protected]
> Skype: emmanuel_cecchet
>
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 26 Jan 2009 20:35:04 -0500
> From: Emmanuel Cecchet <[email protected]>
> Subject: Re: [Sequoia] Replicate multiple databases for one node
> (MySQL)
> To: Sequoia general mailing list <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi Patrik,
> > Is it possible to replicate multiple databases, i.e. the whole RDBMS? I'm
> > thinking of replicating all databses of a MySQL DB engine.
> >
> Sequoia does not automatically replicate all databases of a MySQL
> engine, but you can write a virtual database file for each database and
> load them all in the same controller. Sequoia does not support
> cross-database queries, so you will not be able to do something like
> SELECT * FROM db1.t1, db2.t2.
>
> Thanks for your interest in Sequoia,
> Emmanuel
>
> --
> Emmanuel Cecchet
> FTO @ Frog Thinker
> Open Source Development & Consulting
> --
> Web: http://www.frogthinker.org
> email: [email protected]
> Skype: emmanuel_cecchet
>
>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 27 Jan 2009 11:45:27 -0500
> From: Emmanuel Cecchet <[email protected]>
> Subject: [Sequoia] Critical issue for single controller configurations
> To: Sequoia general mailing list <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi all,
>
> I recently fixed a critical issue in Sequoia 2.10.10 that appears on all
> systems using a single controller. The details can be found at
> https://forge.continuent.org/jira/browse/SEQUOIA-1141.
> I strongly encourage anyone in production to apply this patch. There is
> no official build that currently includes that patch.
>
> Thanks for your attention,
> Emmanuel
>
> --
> Emmanuel Cecchet
> FTO @ Frog Thinker
> Open Source Development & Consulting
> --
> Web: http://www.frogthinker.org
> email: [email protected]
> Skype: emmanuel_cecchet
>
>
>
> ------------------------------
>
> _______________________________________________
> Sequoia mailing list
> [email protected]
> https://forge.continuent.org/mailman/listinfo/sequoia
>
> End of Sequoia Digest, Vol 41, Issue 28
> ***************************************
>
--
Bakary,
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
