[jboss-jira] [JBoss JIRA] (JGRP-1541) PDC: persist discovery responses

[Bela Ban (JIRA)]

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

Bela Ban updated JGRP-1541:
---------------------------

    Summary: PDC: persist discovery responses  (was: Discovery: persist discovery responses)

    
> PDC: persist discovery responses
> --------------------------------
>
>                 Key: JGRP-1541
>                 URL: https://issues.jboss.org/browse/JGRP-1541
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>             Fix For: 3.3
>
>
> When we use TCPPING.initial_hosts=A, and have nodes A, B and C, then the following can happen:
> - A is started. The view is {A}
> - B is started, finds A and joins the cluster. The view is {A,B}
> - C is started, finds A and joins the cluster. The view is now {A,B,C}
> - A is killed. The view is now {B,C}
> - C is restarted
> --> C won't find A therefore cannot ask B to join it (C doesn't know about B)
> SOLUTION:
> - If every member persisted its discovery results on disk, C would still know about A and B, and could therefore discover B
> - This could be implemented directly in TCPPING, or as a generic, separate, protocol (possibly useful for other discovery protocols such as S3_PING, TCPGOSSIP (when the GossipRouter is down) as well)
> - The disk cache would have to include an expiry mechanism, so that the file doesn't grow forever, and also stale results aren't returned forever
> - This mechanism would not work though if C came up the first time (no file on disk yet) and A wasn't running.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira