[ https://forge.continuent.org/jira/browse/HEDERA-43?page=all ]
     
Linas Virbalas resolved HEDERA-43:
----------------------------------

      Assign To: Linas Virbalas  (was: Robert Hodges)
     Resolution: Fixed
    Fix Version: Hedera 2.0

> Duocomm support in channel performance and view change tests
> ------------------------------------------------------------
>
>          Key: HEDERA-43
>          URL: https://forge.continuent.org/jira/browse/HEDERA-43
>      Project: Hedera
>         Type: Sub-task

>     Versions: Hedera 2.0
>     Reporter: Linas Virbalas
>     Assignee: Linas Virbalas
>      Fix For: Hedera 2.0

>
> Original Estimate: 2 days
>         Remaining: 2 days
>
> Duocomm semantics and configuration are a little different from JGroups and 
> Appia. We need to make the Hedera ViewChangeTest and 
> ChannelPerformanceMultiprocessTest to pass with Duocomm. Currently Duocomm 
> supports only 2 members, because of this we need to make at least 2 member 
> tests to pass:
>   ChannelPerformanceMultiprocessTest.testChannelPerformanceMultiprocess1 - 2 
> members
>   ChannelPerformanceMultiprocessTest.testChannelPerformanceMultiprocess2 - 4 
> members
>   ChannelPerformanceMultiprocessTest.testChannelPerformanceMultiprocessLong - 
> 2 members
>   ViewChangeTest.testViewChange() - 2 members
>   ViewChangeTest.testViewChangeSafetyConditions() - 2 members
>   ViewChangeTest.testVirtualSynchrony() - 4 members
> Changes needed:
> 1. Ability to pass a separate config file for every member. Duocomm specifies 
> the binding address with port in it, so we need to specify different 
> addresses for the members. E.g.:
>     -Dproperties=/hedera_duocomm0.properties:/hedera_duocomm1.properties
> 2. Make the ViewChangeTestThread.waitAllMembersToJoin() react to the 
> groupComposition(...) event. We need this because Duocomm sends 
> groupComposition event instead of the joinMember in some cases.
> 3. Wait for a master to join in the testViewChangeSafetyConditions. Duocomm 
> takes its time when a first member joins (not an issue with JGroups and Appia 
> though). We'll add a ViewChangeTestThread.waitSelfToJoin() method for that.

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

_______________________________________________
Hedera mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/hedera

Reply via email to