[ https://issues.jboss.org/browse/ISPN-5515?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-5515: --------------------------------------- I think these are really tricky ideas which should be discussed on the mailing list, I noticed this JIRA by pure luck and find it concerning that such decisions are made without any wider discussion. What I find most tricky: - it's possible the new starting node starts while "thinking it's first", but then actually merge with a running cluster. The cluster detection protocols aren't foolproof, and you're relying on timeouts to be configured safely (when are they ever?). - it's unrealistic to push such a requirement to "admin's responsibility" especially but not least because node restarts might not be under their control - even with this design, the majority of cachestores are cleared so there is an assumption that "data loss is fine" for the user: so why even bother trying to keep a small portion of it at risk of consistency trouble? - this design seems to favour something else above correctness, and I'm not sure what "something else" you're aiming at.. why work hard to not wipe a single cachestore? I agree with you that this is an improvement over the current state, but I don't see why you would implement tricky code to provide a tricky solution when all what's needed is remove the preloading option from configuration. You'll be done in much less work and get a better reliable solution. Unless I'm missing the important reason to load this data? -- This message was sent by Atlassian JIRA (v6.3.15#6346)