4:32 p.m.
On node startup, ensure all peers have compatible configurations
----------------------------------------------------------------
Key: ISPN-791
URL: https://jira.jboss.org/browse/ISPN-791
Project: Infinispan
Issue Type: Feature Request
Components: Configuration
Affects Versions: 4.1.0.Final
Reporter: Manik Surtani
Assignee: Manik Surtani
Fix For: 5.0.0.BETA1, 5.0.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
3:13 p.m.
New subject: [JBoss JIRA] Assigned: (ISPN-791) On node startup, ensure all peers have compatible configurations
[
https://jira.jboss.org/browse/ISPN-791?page=com.atlassian.jira.plugin.sys...
]
Vladimir Blagojevic reassigned ISPN-791:
----------------------------------------
Assignee: Vladimir Blagojevic (was: Manik Surtani)
On node startup, ensure all peers have compatible configurations
----------------------------------------------------------------
Key: ISPN-791
URL: https://jira.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.0.0.BETA1, 5.0.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
7:39 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-791) On node startup, ensure all peers have compatible configurations
[
https://issues.jboss.org/browse/ISPN-791?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño updated ISPN-791:
----------------------------------
Fix Version/s: 5.0.0.BETA2
(was: 5.0.0.BETA1)
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.0.0.BETA2, 5.0.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
5:38 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-791) On node startup, ensure all peers have compatible configurations
[
https://issues.jboss.org/browse/ISPN-791?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño updated ISPN-791:
----------------------------------
Fix Version/s: 5.0.0.CR1
(was: 5.0.0.BETA2)
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.0.0.CR1, 5.0.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
10:36 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-791) On node startup, ensure all peers have compatible configurations
[
https://issues.jboss.org/browse/ISPN-791?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño updated ISPN-791:
----------------------------------
Fix Version/s: 5.0.0.CR2
(was: 5.0.0.CR1)
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.0.0.CR2, 5.0.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
6:59 p.m.
New subject: [JBoss JIRA] Updated: (ISPN-791) On node startup, ensure all peers have compatible configurations
[
https://issues.jboss.org/browse/ISPN-791?page=com.atlassian.jira.plugin.s...
]
Manik Surtani updated ISPN-791:
-------------------------------
Fix Version/s: 5.0.0.CR3
(was: 5.0.0.CR2)
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.0.0.CR3, 5.0.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
10:51 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-791) On node startup, ensure all peers have compatible configurations
[
https://issues.jboss.org/browse/ISPN-791?page=com.atlassian.jira.plugin.s...
]
Vladimir Blagojevic updated ISPN-791:
-------------------------------------
Fix Version/s: 5.1.0.BETA1
5.1.0.Final
(was: 5.0.0.FINAL)
(was: 5.0.0.CR3)
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
9:22 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-791) On node startup, ensure all peers have compatible configurations
[
https://issues.jboss.org/browse/ISPN-791?page=com.atlassian.jira.plugin.s...
]
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
10:16 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-791) On node startup, ensure all peers have compatible configurations
[
https://issues.jboss.org/browse/ISPN-791?page=com.atlassian.jira.plugin.s...
]
Michal Linhard commented on ISPN-791:
-------------------------------------
Let's keep in mind that configuration XML isn't the only way of configuring
Infinispan, so the hash shouldn't be a hash of the XML string, but of something that
represents the instantiated Configuration bean.
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
11:23 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-791) On node startup, ensure all peers have compatible configurations
[
https://issues.jboss.org/browse/ISPN-791?page=com.atlassian.jira.plugin.s...
]
Manik Surtani updated ISPN-791:
-------------------------------
Fix Version/s: 5.2.0.FINAL
(was: 5.1.0.BETA1)
(was: 5.1.0.FINAL)
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.2.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
10:01 p.m.
New subject: [JBoss JIRA] (ISPN-791) On node startup, ensure all peers have compatible configurations
[
https://issues.jboss.org/browse/ISPN-791?page=com.atlassian.jira.plugin.s...
]
Mircea Markus updated ISPN-791:
-------------------------------
Fix Version/s: 6.0.0.Final
(was: 5.2.0.Final)
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: 6.0.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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4192
days inactive
4900
days old
infinispan-issues@lists.jboss.org
10 comments
5 participants
participants (5)
-
Galder Zamarreño (JIRA) -
Manik Surtani (JIRA)
-
Michal Linhard (JIRA)
-
Mircea Markus (JIRA)
-
Vladimir Blagojevic (JIRA)