[jboss-jira] [JBoss JIRA] Resolved: (JGRP-1247) Discovery: max_rank prevents physical address from being fetched

Bela Ban (JIRA) jira-events at lists.jboss.org
Wed Oct 20 07:23:55 EDT 2010


     [ https://jira.jboss.org/browse/JGRP-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bela Ban resolved JGRP-1247.
----------------------------

    Resolution: Won't Fix


We can set max_rank=0 and ergonomics=false, then we get the same effect.

Something to think about: in a later release, we might want to send UUIDExt (subclass of UUID) for the first N requests (or M time) after a new member has joined. UUIDExt == UUID + physical addr + logical name. Whenever a UUIDExt is received, we add the physical address and logical name to the cache

> Discovery: max_rank prevents physical address from being fetched
> ----------------------------------------------------------------
>
>                 Key: JGRP-1247
>                 URL: https://jira.jboss.org/browse/JGRP-1247
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>             Fix For: 2.11
>
>
> If we have {A,B,C,D,E,F} and max_rank=3, then we'll only get responses from A, B and C. If a new member G doesn't have E's physical address, a GET_PHYSICAL_ADDRESS sent up from TP to Discovery doesn't fetch E's physical address !
> SOLUTION: GET_PHYSICAL_ADDRESS should include the logical address of the member (E) whose physical address we want. A receiver returns a response if (1) its rank is less than max_rank or (2) the arg to GET_PHYSICAL_ADDRESS is not null and is the local address

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-jira mailing list