[infinispan-issues] [JBoss JIRA] Commented: (ISPN-791) On node startup, ensure all peers have compatible configurations

[Galder Zamarreño (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619367#comment-12619367 ] 

Galder Zamarreño commented on ISPN-791:
---------------------------------------

As Mircea said in ISPN-1270, we could pass the hash around and if conflict, request and compare the actual XML or configuration objects to give clues to the user on what's diverging.

> On node startup, ensure all peers have compatible configurations
> ----------------------------------------------------------------
>
>                 Key: ISPN-791
>                 URL: https://issues.jboss.org/browse/ISPN-791
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Configuration
>    Affects Versions: 4.1.0.Final
>            Reporter: Manik Surtani
>            Assignee: Vladimir Blagojevic
>             Fix For: 5.1.0.BETA1, 5.1.0.FINAL
>
>
> This is to prevent caches that are supposed to be symmetric/identical from being misconfigured.  Some elements are allowed to be unique, of course, such as bind addresses in JGroups as well as node names, server hints, certain props passed to cache stores, etc.
> A simple test could be a hash (MD5 or SHA1?) of the config XML (or a serial form of the generated Configuration bean) which is exchanged as a part of the join method.  On failure of the hash check, the entire object could be checked, and if that fails as well, an appropriate ConfigurationException could be thrown.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira