[hibernate-issues] [Hibernate-JIRA] Resolved: (OGM-49) A new node is unable to join a running cluster

[Sanne Grinovero (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/OGM-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sanne Grinovero resolved OGM-49.
--------------------------------

    Resolution: Fixed

> A new node is unable to join a running cluster
> ----------------------------------------------
>
>                 Key: OGM-49
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-49
>             Project: Hibernate OGM
>          Issue Type: Bug
>            Reporter: Sanne Grinovero
>            Assignee: Sanne Grinovero
>
> When a new node containing no data is joining a cluster which already owns some persistent entities, state transfer errors are generated and the join fails if the existing caches had not initialized all involved caches (for example if nothing was ever stored in the IDENTIFIERS cache).
> The join can tolerate this errors by changing the configuration to use strictPeerToPeer=false, and we can also make sure that all caches are always initialized at startup.

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