Re: [infinispan-dev] Configuration hash
Hmmmmm, we gotta think about this. There might be situations where configurations are not
identical due to valid reasons, i.e. Each cache is configured with a local FS write behind
store but each node points to a diff location within the system. That's a valid
configuration. However, it doesn't make sense to have a node with REPL_SYNC and the
other with DIST_SYNC.
The easiest solution would be to use a WARN message unless you want to start figuring out
which combination of configurations are compatible and which not, and forbid cluster
formation accordingly.
On Nov 15, 2010, at 8:39 PM, Elias Ross wrote:
This is a good idea. At the very least, it should WARN in the log
that
such an attempt was made.
On Mon, Nov 15, 2010 at 10:58 AM, Vladimir Blagojevic
<vblagoje(a)redhat.com> wrote:
> Some Infinispan users are configuring certain nodes with one
> configuration and other nodes with another. Should we calculate a
> configuration hash and allow cluster joins for nodes that have the same
> hash only? Should reduce the noise as the user base continues to expand....
>
> Cheers,
> Vladimir
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache