Leander,
Hmm, we've been seeing all kinds of weird behavior and/or bugs
in Sequoia in combination with JDK 1.6, The problems appear to
be mostly XML related, although this is based on my subjective
observations. At one point during failover testing, I ran into a
situation where it was impossible to re-add a controller to a RAIDb-1
cluster, because Sequoia thought that the vdb config files on
the two controllers were different, which was positively not the
case, because the config files had not changed since I removed
the controller from the cluster:
========================
2007-03-15 00:13:12,928 ERROR controller.xml.DatabasesParser The
virtual database sequoiadb could not be added to the controller
(because of Error while joining group sequoiadb
(org.continuent.sequoia.common.
exceptions.ControllerException: Virtual database configuration is not
compatible with other controller settings.))
java.lang.Exception: Error while joining group sequoiadb
(org.continuent.sequoia.common.exceptions.ControllerException: Virtual
database configuration is not compatible with other controller settings.)
The other controller should print the explicit message saying what is
incompatible in the configuration. Could you retrieve that message?
Also, I had criticial issues while restoring dumps to a backend,
because Sequoia was unable to drop the database first:
========================
...
2007-03-14 23:38:52,100 DEBUG
backup.backupers.NativeCommandOutputThread Thread-7: dropdb: database
removal failed: ERROR: database "sequoiadb" is being accessed by
other users
Which version of PostgreSQL are you using?
Are you sure that you did not have a client directly connected to the
PostgreSQL backend?
As you can see, the backend database cannot be dropped because
there are client connections to it, but these connections are from
Sequoia. However, I could not find a way to prevent Sequoia from
starting connections to the database. I was able to cirumvent this by
killing the postgresql processes from the command line, but then the
restore of the recovery log would fail after restoring the SQL dump.
Basically, we had been running around in circles like this for days,
where solving one issue introduced another and seeing unpredictable
and erratic behavior until we switched to JDK 1.5, after which all these
issues basically went away. I would like to ask this question again: is
JDK 1.6 even supported for Sequoia? If not, then _please_ add this
information to the website and documentation, with a big fat warning
sign next to it, so other users will not have to experience the madness
we did...
As far as I know, JDK 1.6 has not been tested, so we should certainly
update the documentation to mention this.
Just to make sure that the problem is due to the runtime, you are using
a binary version provided on Continuent.org and not a version that you
recompiled with JDK 1.6, is that correct ?
Thanks again 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
