<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">2018-03-01 17:25 GMT+01:00 Tristan Tarrant <span dir="ltr"><<a href="mailto:ttarrant@redhat.com" target="_blank">ttarrant@redhat.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Why not just prestart caches ?<br>
<span class=""><br></span></blockquote><div><br></div><div>How can you do that? Will it work for caches created after the node has started?<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
On 3/1/18 5:14 PM, Thomas SEGISMONT wrote:<br>
><br>
> 2018-03-01 16:36 GMT+01:00 Tristan Tarrant <<a href="mailto:ttarrant@redhat.com">ttarrant@redhat.com</a><br>
</span>> <mailto:<a href="mailto:ttarrant@redhat.com">ttarrant@redhat.com</a>>>:<br>
<div><div class="h5">><br>
> You need to use the brand new CacheAdmin API:<br>
><br>
> <a href="http://infinispan.org/docs/stable/user_guide/user_guide.html#obtaining_caches" rel="noreferrer" target="_blank">http://infinispan.org/docs/<wbr>stable/user_guide/user_guide.<wbr>html#obtaining_caches</a><br>
> <<a href="http://infinispan.org/docs/stable/user_guide/user_guide.html#obtaining_caches" rel="noreferrer" target="_blank">http://infinispan.org/docs/<wbr>stable/user_guide/user_guide.<wbr>html#obtaining_caches</a>><br>
><br>
><br>
> I'll look into that for Vert.x 3.6 which will be based on Infinispan 9.2.<br>
><br>
> Is there any way to achieve these goals with 9.1.x?<br>
><br>
><br>
><br>
><br>
> Tristan<br>
><br>
> On 3/1/18 4:30 PM, Thomas SEGISMONT wrote:<br>
> > Hi,<br>
> ><br>
> > This email follows up on my testing of the Infinispan Cluster Manager<br>
> > for Vert.x on Kubernetes.<br>
> ><br>
> > In one of the tests, we want to make sure that, after a rolling<br>
> update<br>
> > of the application, the data submitted to Vert.x' AsyncMap is still<br>
> > present. And I found that when the underlying cache is predefined in<br>
> > infinispan.xml, the data is present, otherwise it's not.<br>
> ><br>
> > I pushed a simple reproducer on GitHub:<br>
> > <a href="https://github.com/tsegismont/cachedataloss" rel="noreferrer" target="_blank">https://github.com/tsegismont/<wbr>cachedataloss</a><br>
> <<a href="https://github.com/tsegismont/cachedataloss" rel="noreferrer" target="_blank">https://github.com/<wbr>tsegismont/cachedataloss</a>><br>
> ><br>
> > The code does this:<br>
> > - a first node is started, and creates data<br>
> > - new nodes are started, but they don't invoke cacheManager.getCache<br>
> > - the initial member is killed<br>
> > - a "testing" member is started, printing out the data in the console<br>
> ><br>
> > Here are my findings.<br>
> ><br>
> > 1/ Even when caches are declared in infinispan.xml, the data is lost<br>
> > after the initial member goes away.<br>
> ><br>
> > A little digging showed that the caches are really distributed only<br>
> > after you invoke cacheManager.getCache<br>
> ><br>
> > 2/ Checking cluster status "starts" triggers distribution<br>
> ><br>
> > I was wondering why the behavior was not the same as with my Vert.x<br>
> > testing on Openshift. And then realized the only difference was the<br>
> > cluster readiness check, which reads the cluster health. So I updated<br>
> > the reproducer code to add such a check (still without invoking<br>
> > cacheManager.getCache). Then the caches defined in infinispan.xml<br>
> have<br>
> > their data distributed.<br>
> ><br>
> > So,<br>
> ><br>
> > 1/ How can I make sure caches are distributed on all nodes, even<br>
> if some<br>
> > nodes never try to get a reference with cacheManager.getCache, or<br>
> don't<br>
> > check cluster health?<br>
> > 2/ Are we doing something wrong with our way to declare the default<br>
> > configuration for caches [1][2]?<br>
> ><br>
> > Thanks,<br>
> > Thomas<br>
> ><br>
> > [1]<br>
> ><br>
> <a href="https://github.com/tsegismont/cachedataloss/blob/master/src/main/resources/infinispan.xml#L10" rel="noreferrer" target="_blank">https://github.com/tsegismont/<wbr>cachedataloss/blob/master/src/<wbr>main/resources/infinispan.xml#<wbr>L10</a><br>
> <<a href="https://github.com/tsegismont/cachedataloss/blob/master/src/main/resources/infinispan.xml#L10" rel="noreferrer" target="_blank">https://github.com/<wbr>tsegismont/cachedataloss/blob/<wbr>master/src/main/resources/<wbr>infinispan.xml#L10</a>><br>
> > [2]<br>
> ><br>
> <a href="https://github.com/tsegismont/cachedataloss/blob/master/src/main/resources/infinispan.xml#L22" rel="noreferrer" target="_blank">https://github.com/tsegismont/<wbr>cachedataloss/blob/master/src/<wbr>main/resources/infinispan.xml#<wbr>L22</a><br>
> <<a href="https://github.com/tsegismont/cachedataloss/blob/master/src/main/resources/infinispan.xml#L22" rel="noreferrer" target="_blank">https://github.com/<wbr>tsegismont/cachedataloss/blob/<wbr>master/src/main/resources/<wbr>infinispan.xml#L22</a>><br>
> ><br>
> > ______________________________<wbr>_________________<br>
> > infinispan-dev mailing list<br>
> > <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
</div></div>> <mailto:<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.<wbr>jboss.org</a>><br>
> > <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/infinispan-<wbr>dev</a><br>
<span class="">> <<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/infinispan-<wbr>dev</a>><br>
> ><br>
><br>
> --<br>
> Tristan Tarrant<br>
> Infinispan Lead and Data Grid Architect<br>
> JBoss, a division of Red Hat<br>
> ______________________________<wbr>_________________<br>
> infinispan-dev mailing list<br>
</span>> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a> <mailto:<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.<wbr>jboss.org</a>><br>
> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/infinispan-<wbr>dev</a><br>
> <<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/infinispan-<wbr>dev</a>><br>
<div class="HOEnZb"><div class="h5">><br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> infinispan-dev mailing list<br>
> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/infinispan-<wbr>dev</a><br>
><br>
<br>
--<br>
Tristan Tarrant<br>
Infinispan Lead and Data Grid Architect<br>
JBoss, a division of Red Hat<br>
______________________________<wbr>_________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/infinispan-<wbr>dev</a><br>
</div></div></blockquote></div><br></div></div>