<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 14, 2016 at 10:54 AM, Tristan Tarrant <span dir="ltr"><<a href="mailto:ttarrant@redhat.com" target="_blank">ttarrant@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">>> - new nodes joining the cluster (and therefore with a possibly outdated<br>
>> configuration) would receive the configuration of caches already running<br>
>> in the cluster and applying them locally<br>
>><br>
><br>
> How does this happen?<br>
<br>
</span>Again, via the cluster transport.<br>
<span class=""></span></blockquote></div><br><br></div><div class="gmail_extra">How can his be? Isn't the cache configuration managed by mgmt configuration.<br></div><div class="gmail_extra">so as such would always be "latest" or does cache change its own configuration independently?<br></div></div>