Hi Rakitha,
One recommendation--the Sequoia 3.0 line has a number of experimental
features and is not very stable. All work related to commercial
products is going on in the Sequoia 2.10 branch. You may want to
switch to this for greater stability. We just posted a build 2.10.9
that you can use if you are looking for binaries.
Cheers, Robert
Robert Hodges, CTO, Continuent, Inc.
Email: [EMAIL PROTECTED]
Mobile: +1-510-501-3728 Skype: hodgesrm
On Aug 6, 2007, at 12:45 PM, Rakitha Suranga (JIRA) wrote:
[ https://forge.continuent.org/jira/browse/SEQUOIA-965?
page=comments#action_14022 ]
Rakitha Suranga commented on SEQUOIA-965:
-----------------------------------------
Hi Marc,
Yes I'm more sure about JBoss does not connect directly to
backend1, since when we enable both backends and insert one recode
using application, recode is saved in both databases. Actually
issue is coming when recovering after down 1 backend.
Ex:
If backend2 is down (disabled), what I'm going to do is restore
last backup (backend1 backup) to the backend2 and enable backend2.
Mean time I'm expecting, database modifications (insert & updates)
which happened while down (disabled) backend2, are saving
(recovering) to the backend2.
Is this sense incorrect?
If it is incorrect, please explain me how it is going. Otherwise I
have an issue with recovering data.
Thanks.
Recovery Issue with Sequoia-3.0-beta2
-------------------------------------
Key: SEQUOIA-965
URL: https://forge.continuent.org/jira/browse/SEQUOIA-965
Project: Sequoia
Type: Task
Components: Recovery Log
Versions: Sequoia 3.0 beta3
Environment: operating system-linux redhat, databse -PostgreSQL
8.0.3, Jboss4/Hibernate application.
Reporter: Rakitha Suranga
Priority: Blocker
Original Estimate: 2 days, 5 hours, 30 minutes
Remaining: 2 days, 5 hours, 30 minutes
I'm using one controller with sequoia-3.0-beta2 and two backends
(backend1 & backend2) running with PostgreSQL 8.0.3. We are
testing following environments with Jboss4/Hibernate application.
This environment was configured with RAIDb-1, like Sequoia User's
Guide.
My test script makes the following steps:
1. initialize backend1
2. backup backend1
3. enable backend1
4. insert one record using application (only backends1 enable)
5. restore backup to the backend2
6. enable backend2(sequoia recover using last know checkpoint)
But after recovery, backend2 doesn't have the new record, and
looking for controller's log hasn't errors.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the
administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia