db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ole Solberg (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3632) Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.
Date Fri, 30 May 2008 07:57:45 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601039#action_12601039
] 

Ole Solberg commented on DERBY-3632:
------------------------------------

"Normally" failover does not take that long. But I have seen cases, with other load on the
test host, when both startmaster and failover can take time.

It would be good to see if this change do make the test more stable.


> Replication tests must ensure stable replication state has been reached before attempting
further connection or new replication commands.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3632
>                 URL: https://issues.apache.org/jira/browse/DERBY-3632
>             Project: Derby
>          Issue Type: Bug
>          Components: Replication, Test
>    Affects Versions: 10.4.1.4, 10.5.0.0
>         Environment: All
>            Reporter: Ole Solberg
>            Assignee: Ole Solberg
>            Priority: Minor
>         Attachments: derby-3632_p1.diff.txt, derby-3632_p1.stat.txt
>
>
> When executing replication commands (startslave, startmaster, stopmaster, stopslave,
failover) tests must make sure that correct replication state has been reached before attempting
further connection to the master and slave databases.
> This causes intermittent errors in replication tests.

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


Mime
View raw message