Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1379162050.1204560650559.JavaMail.jira@brutus>
Date: Mon, 3 Mar 2008 08:10:50 -0800 (PST)
From: "Ole Solberg (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-3162) Create a framework for replication
 tests
In-Reply-To: <9375592.1193755430814.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ole Solberg updated DERBY-3162:
-------------------------------

    Attachment: derby-3162.3-v1.diff.txt
                derby-3162.3-v1.stat.txt

Patch derby-3162.3-v1 for replication test framework.

1. Handle that startMaster now correctly gets "XRE04" while slave is not yet ready after startSlave.

2. Create {user.dir}/[db_master|db_slave] if not existing.

3. Start servers via rt.exec().

4. New ReplicationRun_Full which handles the distributed case with replication state tests
    and optional load on servers.


> Create a framework for replication tests
> ----------------------------------------
>
>                 Key: DERBY-3162
>                 URL: https://issues.apache.org/jira/browse/DERBY-3162
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Test
>    Affects Versions: 10.4.0.0
>            Reporter: Ole Solberg
>            Assignee: Ole Solberg
>            Priority: Minor
>         Attachments: derby-3162.1-v1.diff.txt, derby-3162.2-v2.diff.txt, derby-3162.2-v2.stat.txt, derby-3162.3-v1.diff.txt, derby-3162.3-v1.stat.txt
>
>
> Handle
>  - starting and stopping Derby servers to have the master and slave replication roles,
>  - doing administrative commands like startreplication, startslave, stopreplication, failover,
>  - performing consistency checks on the slave vs. the master,
>  - running load clients against master and slave in the various states of replication,
>  - provoking error situations on master and slave, and network,
>  - ... 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.