Thank you for your help guys, I was able to get both vdb's running
after realizing that I had unfortunately loaded the config file before
properly editing the database name, and after I corrected the problem in
the xml file, the recovery log thought I was still loading the improper
backends. To correct the issue I cleared the recovery logs on both
controllers, be it that this is a test bed I can do that, and I
proceeded to restart the controllers and reload the fresh xml files.
I see that you guys talk about having multiple JGroups files to help
rid myself of the warn messages I'm assuming between different JGroups
on the same network. Where might I be able to find some documentation
about this and how scalable is this. Once we push to production we plan
on running quite a few vdb's at one time, and by quite a few figure
roughly atleast 10-20 at any given time. Anything I can do to help
minimize latency or cross talk would be greatly appreciated.
Thanks again for your help,
Matt West
In this configuration case what kind of traffic is handle by JGroups ?
I believe it's light or is it the same as between the controller and
the database ?
If i'm right it could be multiplexed on the same JGroups stack as having
multiple JGroups stack is a waste of CPU and the configuration would
be easier.
On 5/11/07, *Emmanuel Cecchet* < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Hi Matt,
You must make sure that each pair of configuration file uses the same
virtual database name and same group name (in the Distribution
element).
A good practice is to use different JGroups configuration files with
different multicast addresses for each virtual database to avoid
traffic
collision between messages of different virtual databases.
If this does not help, feel free to post your configuration files so
that we can help you.
Thanks for your interest in Sequoia,
Emmanuel
> Hey guys, I've got a setup of 2 controllers and 4 backends.
On each
> of my backends which are all MySQL I have a test1 and test2
database.
> When I setup my virtualdatabase files I have called them
db1-test1 and
> db1-test2 and db2-test1 and db2-test2 and so on, all the way up to
> db4-test2. When I load the configuration files for test1 vdb
> everything loads up ok, No Problems. I'm then able to load
db1-test2
> and db2-test2 by loading the test2 xml file, but after that I'm
unable
> to load db3-test2 and db4-test2 because it says I can not use
the same
> backends or they are not compatible. I have checked my xml files
with
> a fine tooth comb and each line has different backend names and
> backend locations.
>
> db1-test1 points to jdbc:mysql://db1:3306/test1
> db1-test2 points to jdbc:mysql://db1:3306/test2
> db2-test1 points to jdbc:mysql://db2:3306/test1
> db2-test2 points to jdbc:mysql://db2:3306/test2
> db3-test1 points to jdbc:mysql://db3:3306/test1
> db3-test2 points to jdbc:mysql://db3:3306/test2
> db4-test1 points to jdbc:mysql://db4:3306/test1
> db4-test2 points to jdbc:mysql://db4:3306/test2
>
> If you need me to post the xml files I will do so, but I was hoping
> someone might have a clue as to why when I load up the second
set of
> test2 database backends it complains about the backends. The error I
> see in the console window is as follows...
>
> Loading of virtual databases configuration file failed (because
of The
> virtual database test2 could not be added to the controller
(because
> of Error while joining group test2
> (org.continuent.sequoia.common.exceptions.ControllerException:
Virtual
> database configuration is not compatible with other controller
> settings.))).
>
> Thanks so much in advance,
>
--
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]
<mailto:[email protected]>
https://forge.continuent.org/mailman/listinfo/sequoia
<https://forge.continuent.org/mailman/listinfo/sequoia>
--
-Tout ce qui n'est pas donné est perdu - Hasari Pal
------------------------------------------------------------------------
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
--
Matthew West
Junior Linux Administrator
Disovery Mining, Inc.
Office: (415)561-6780 x146
Mobile: (415)710-6211
Fax: (415)561-6784
[EMAIL PROTECTED]
www.discoverymining.com
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
