Hi,
I am accessing the Sequoia controller using an example similar to
SimpleJmxClient.java. What is the necessary parameters and procedure to
replicate a database using the following method call:
proxy.replicateBackend("localhost","localhost3",new HashMap());
Currently it fails.
Thanks,
Jar
[ https://forge.continuent.org/jira/browse/SEQUOIA-819?page=all ]
Stephane Giron resolved SEQUOIA-819:
Assign To: Mathieu Peltier (was: Stephane Giron)
Resolution: Fixed
Fix Version: (was: Sequoia 2.10.2)
(Visible to emicnetworks
Failed to execute request within transaction after killing controller:
Connection lost while executing statementExecuteQuery and automatic reconnect
failed
-
I still have a lot of problems getting Sequoia to
work with Postgres (both PG for Windows and Linux).
- I just start 1 controller with 1 backend and
initialize and enable the backend.
- I use Squirrel SQL to submit some querries by
using the Sequoia driver:
create table a (a varchar(10),
Marc Wick <[EMAIL PROTECTED]> writes:
> The postgres documentation writes :
>
> It is important to know that |CURRENT_TIMESTAMP| and related functions
> return the start time of the current transaction; their values do not
> change during the transaction. This is considered a feature: the
> intent
Jared,
My question is when I replicate an object across the backend databases
how do I guarantee that the Primary Keys created are identical.
Currently the PK values sometimes vary across databases. It is critical
that the PK values are globally the same for all backend databases.
Please help.
"Box, Jared C" <[EMAIL PROTECTED]> writes:
> I am running a Sequoia example using 1 virtual database, 2 controllers,
> with 2 backend databases on each controller. I am using HSQLDB for all
> backends.
>
> My question is when I replicate an object across the backend databases
> how do I guarant
Check PG backup behaviour wrt stored proc languages creation
Key: SEQUOIA-818
URL: https://forge.continuent.org/jira/browse/SEQUOIA-818
Project: Sequoia
Type: Bug
Components: Backup System
Versions:
It would break one of my own applications, for example. I run a random
function each night on my objects to randomize the listing of the
objects on the website. If all objects get the same random value, than I
don't have to run the randomizer at all. The sort order would be the
same every day a
Marc Wick <[EMAIL PROTECTED]> writes:
> be careful with random() as it will be difficult to achieve the same
> semantic, if more than one row is updated. Just replacing it with a
> single random value will break applications relying on every row being
> assigned an other random value.
Errr... sin
Hi Emmanuel
I wonder if this also applies to NOW().
If I do something like 'UPDATE t SET sometime=NOW()' will each row
compute potentially a different NOW() value ?
The postgres documentation writes :
It is important to know that |CURRENT_TIMESTAMP| and related functions
return the start ti
Hi Marc,
You were right:
mysql> create table test (x int);
Query OK, 0 rows affected (0.05 sec)
mysql> insert into test values (1);
Query OK, 1 row affected (0.00 sec)
mysql> insert into test values (2);
Query OK, 1 row affected (0.00 sec)
mysql> insert into test values (3);
Query OK, 1 row af
[ https://forge.continuent.org/jira/browse/SEQUOIA-817?page=all ]
Emmanuel Cecchet resolved SEQUOIA-817:
--
Assign To: Mathieu Peltier (was: Emmanuel Cecchet)
Resolution: Fixed
Command implemented in CVS
To be tested omre extensively (worke
[ https://forge.continuent.org/jira/browse/SEQUOIA-816?page=all ]
Emmanuel Cecchet resolved SEQUOIA-816:
--
Assign To: Jeff Mesnil (was: Emmanuel Cecchet)
Resolution: Fixed
Fixed in CVS HEAD
To be tested
> VDB Configuration's XML generated
Provide a console command to rename an existing dump
Key: SEQUOIA-817
URL: https://forge.continuent.org/jira/browse/SEQUOIA-817
Project: Sequoia
Type: New Feature
Components: Core, CLI Console
Reporter: Emm
VDB Configuration's XML generated by the controller is not valid
Key: SEQUOIA-816
URL: https://forge.continuent.org/jira/browse/SEQUOIA-816
Project: Sequoia
Type: Bug
Components: Configuration Files P
Hi everyone,
we try to use two controllers (RAIDb-0-1 scenario). We cannot enable our
Backend in the console.
I have two Questions:
Is the order in which we start our controllers of any matter?
When I start the controller I got the following warnings:
16:17:32,438 WARN sequoia.controller.r
Hi Emmanuel
If I do the very same thing with postgres I get '0' in every row. (In
postgres random is between 0 and 1)
Then I tried :
db=> update tmp set id = random()*1;
UPDATE 5
db=> select * from tmp;
id
--
4354
837
7679
6874
2543
(5 rows)
Could you also try multiplying the random
Hi Marc,
Do you mean that something like UPDATE t SET x=random() would give a
different value for each row?
Exactly. It will be pretty hard to implement this on the sequoia
level. It would need a stored procedure in every backend that needs to
be called with a seed value to make sure all back
Hi Emmanuel
Do you mean that something like UPDATE t SET x=random() would give a
different value for each row?
Exactly. It will be pretty hard to implement this on the sequoia level.
It would need a stored procedure in every backend that needs to be
called with a seed value to make sure all
Hi Marc,
be careful with random() as it will be difficult to achieve the same
semantic, if more than one row is updated. Just replacing it with a
single random value will break applications relying on every row being
assigned an other random value.
Do you mean that something like UPDATE t SET x
be careful with random() as it will be difficult to achieve the same
semantic, if more than one row is updated. Just replacing it with a
single random value will break applications relying on every row being
assigned an other random value.
Marc
Stephane Giron (JIRA) wrote:
Macro handling (b
I will try to checkout the CVS version from Sequoia to try this. I'll let
you know.
Tnx,
Igor
- Original Message -
From: "Marc Herbert" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, October 18, 2006 10:42 AM
Subject: Re: [Sequoia] Fw: PfPostgreSQL backup. Can't make it work.
> "Igor M
> you may wish to try the "authentication=true" option on the postgresql
> backuper definition in your vdb.xml. This will turn on the
> authentication mode, allowing sequoia to feed the password you provide
> on the CLC into pg_dump. This requires that "expect" be installed on
> your controller hos
Macro handling (bad replacement of macro, supported macros in vdb DTD file)
---
Key: SEQUOIA-815
URL: https://forge.continuent.org/jira/browse/SEQUOIA-815
Project: Sequoia
Type: Bug
Components:
[ https://forge.continuent.org/jira/browse/SEQUOIA-811?page=all ]
Emmanuel Cecchet resolved SEQUOIA-811:
--
Resolution: Fixed
Fix Version: (was: Sequoia 2.10.2)
Implementation has been removed from 2.10 branch
> MySQL Backuper does not
[ https://forge.continuent.org/jira/browse/SEQUOIA-814?page=all ]
Emmanuel Cecchet resolved SEQUOIA-814:
--
Resolution: Fixed
Fix Version: (was: Sequoia 2.10.2)
Implementation has been removed from 2.10 branch
> Provide a tar-based back
[ https://forge.continuent.org/jira/browse/SEQUOIA-814?page=all ]
Emmanuel Cecchet reopened SEQUOIA-814:
--
Implementation has been removed from 2.10 branch
> Provide a tar-based backuper for MySQL
> --
>
>
[ https://forge.continuent.org/jira/browse/SEQUOIA-811?page=all ]
Emmanuel Cecchet reopened SEQUOIA-811:
--
Implementation has been removed from 2.10 branch
> MySQL Backuper does not work with mysqldump v4.1.2 to 4.1.9
>
[ https://forge.continuent.org/jira/browse/SEQUOIA-813?page=all ]
Emmanuel Cecchet reopened SEQUOIA-813:
--
Implementation has been removed from 2.10 branch
> Provide a generic tar-based backuper
>
>
> K
[ https://forge.continuent.org/jira/browse/SEQUOIA-813?page=all ]
Emmanuel Cecchet resolved SEQUOIA-813:
--
Resolution: Fixed
Fix Version: (was: Sequoia 2.10.2)
Implementation has been removed from 2.10 branch
> Provide a generic tar-ba
"Igor Markovic" <[EMAIL PROTECTED]> writes:
Index: src/org/continuent/sequoia/controller/backup/backupers/NativeCommandExec.java
===
RCS file: /cvsroot/sequoia/sequoia/src/org/continuent/sequoia/controller/backup/backupers/NativeComman
Hi all,
We released Sequoia 2.10.1 maintenance release that mainly integrates
an updated version of Appia and Hedera. This fixes bug that were
discovered shortly after the 2.10 release.
Some minor other issues have also been fixed and another 2.10.2
maintenance release might come out this mon
[ https://forge.continuent.org/jira/browse/SEQUOIA-785?page=all ]
Jeff Mesnil closed SEQUOIA-785:
---
Resolution: Fixed
> Merge controller translations
> -
>
> Key: SEQUOIA-785
> URL: https://forge.continuent
[ https://forge.continuent.org/jira/browse/SEQUOIA-785?page=all ]
Jeff Mesnil reopened SEQUOIA-785:
-
Assign To: Jeff Mesnil (was: Mathieu Peltier)
> Merge controller translations
> -
>
> Key: SEQUOIA-785
>
35 matches
Mail list logo
