Hi Arun, I hope this issue is related to recoverylog, Please try to drop the recoverylog tables and recreate it and try to start the controller again. Please let me know is you fixed this issue in any other way.
Thank You, Suresh N On 8/23/07, [EMAIL PROTECTED] <[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. Error: > org.continuent.sequoia.common.exceptions.VirtualDatabaseException: > NOT STARTING VDB (Arun Prasad) > 2. Using non-replicated write-only db's with Sequoia? > (Jason Rosenberg) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 23 Aug 2007 19:29:22 +0530 > From: Arun Prasad <[EMAIL PROTECTED]> > Subject: [Sequoia] Error: > org.continuent.sequoia.common.exceptions.VirtualDatabaseException: NOT > STARTING VDB > To: [email protected] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > After configuring controller.xml , virtualdatabase.xml tried > starting controller.sh but it threw > an error: > > /*19:11:40,262 ERROR controller.xml.DatabasesParser The virtual database myDB > could not be added to the controller > (because of Error while joining group myDB > (org.continuent.sequoia.common.exceptions.VirtualDatabaseException: NOT > STARTING VDB (not the last man down).)) > java.lang.Exception: Error while joining group myDB > (org.continuent.sequoia.common.exceptions.VirtualDatabaseException: NOT > STARTING VDB (not the last man down).) > > > */ > > Configured two postgres databases in RAIDb-1 model. > > Thanks in advance. > > Regards, > Arun > /* > > */ > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://forge.continuent.org/pipermail/sequoia/attachments/20070823/12ea1ba4/attachment-0001.html > > ------------------------------ > > Message: 2 > Date: Thu, 23 Aug 2007 11:09:21 -0400 > From: Jason Rosenberg <[EMAIL PROTECTED]> > Subject: [Sequoia] Using non-replicated write-only db's with Sequoia? > To: <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > > We have a deployment that has a cluster of write-only database, which have > identical schemas, but which are not replicated for mutual consistency. A > backend process then aggregates the data for off-line processing (think of > these db¹s as loggers). > > So, I¹d like to be able to load-balance write requests to these db¹s the > same as for read-only db requests. Can this be efficiently done with > Sequoia? So far in looking at the manuals, I haven¹t seen that this has > been documented...It seems that write queries are always broadcast in some > way to all db¹s, or a partial subset, etc.... > > Also, how well does it map to using built-in connection pools within tomcat, > for example? Or would we only make non-pooled connections to the Sequoia > controller? > > Thanks, > > Jason > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://forge.continuent.org/pipermail/sequoia/attachments/20070823/862d960c/attachment-0001.html > > ------------------------------ > > _______________________________________________ > Sequoia mailing list > [email protected] > https://forge.continuent.org/mailman/listinfo/sequoia > > End of Sequoia Digest, Vol 24, Issue 22 > *************************************** > _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
