[jira] Commented: (DERBY-3632) Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.

["Dag H. Wanvik (JIRA)" <ji...@apache.org>]

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

Dag H. Wanvik commented on DERBY-3632:
--------------------------------------

Looks like this change will make the test more stable. 

Just a question.. currently the test sleeps for only 200 milliseconds before trying to see if fail-over occurred (loops max 100 times, i.e. 20 seconds). Is it expected that failover will take so long here? 
If the expectation is in the order of several seconds, why is the sleep increment that small (200ms) ?

If this is all as expected, +1 to commit.


> 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.