Hi Shai,
Thanks a lot for this feedback. There is certainly a problem with the
JVM for Solaris.
My guess is that this probably comes from the network stack
implementation and how TCP_NODELAY can be implemented on that platform
(hence the longer recovery time).
Could you try another JVM on Solaris to see if you notice any improvement?
What is the exact vendor and version number of your Solaris JVM?
Thanks for the feedback,
Emmanuel
Ok
So I went and tried the same setup with a difference:
original setup:
1 controller on solaris 10 (sparc), with 2 linux mysqld backends.
now:
1 controller on linux with 2 linux mysqld backends
I tested and I didn't have the problem of the controller hanging..
and controller keeps getting connections while backing up/enabling a
backend + enabling the backend doesnt take too long like with a
solaris controller...
it seems to hang right after a backup is finished and it try to
re-enable backed up backend
what could be the solaris problem ?
(I use same java 1.4.2 for the controller and 1.5.0 for myositis on
both OSs)
Thanks
On Tue, May 13, 2008 at 12:42 PM, Shai Weinstein
<[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:
hello
On Tue, May 13, 2008 at 1:12 AM, Emmanuel Cecchet
<[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:
Hi Shai,
it was not disabled before the backup.. also no errors was
displayed during or after backup
Did you see a message saying that the backup was completed?
What was the backup state when you tried to enable it?
this from the log when i start the backup:
http://pastesite.com/794
the backend was automatically enabled but during this time (~3
minutes) the vdb was not accesible by any client (its not in
production so only 1 client..)
on Myosotis i set the persistent connections option to false
I don't know what else to try , maybe the mysql connector is not
ok ? i'm using the latest stable one from mysql.com
<http://mysql.com> version 5.1.6
there are no any errors, only this warning:
12:26:46,970 WARN DatabaseBackend.myDB.one Default connection
manager undefined in backend configuration, setting to a
VariablePoolConnectionManager
I dont think I use persistent connections - here is my
config (in a paste site):
http://paste.lisp.org/display/60634
The config looks good.
The persistent connection option is set on the driver side so
I can't tell from the virtual database config file.
I have not played with persistent connections for a long time,
so there might be a bug that induces the behavior you indicate
but this looks strange since we can log open/close persistent
connection events. So it should not block anything even while
enabling a new backend. Try to see if it changes anything when
persistent connection are enabled or disabled. You might need
help from the Myosotis mailing list if you don't find the
option there.
Note though that your connection pool size is only 50 per
backend so you can't have more than 50 client connections.
After 50 connections new clients will be blocking no matter
what is the state of your backends.
Which version of Sequoia are you using?
2.10.10
This is good.
Keep us posted with your progress,
Emmanuel
--
Emmanuel Cecchet
FTO @ Frog Thinker Open Source Development & Consulting
--
Web: http://www.frogthinker.org
email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Skype: emmanuel_cecchet
--
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
