Denis, No ideas here. I think, it is not possible right now from pure C++.
Best Regards, Igor On Sat, Sep 14, 2019 at 1:02 AM Denis Magda <dma...@apache.org> wrote: > Igor, > > Any idea how to start a cache dynamically from C++ thick client passing > near cache settings? > > Don't see how we can do it know unless you start a special Java app that > starts the caches with required settings and dies. > > - > Denis > > > On Fri, Sep 13, 2019 at 2:34 PM Oleg Popov <o.po...@livelace.ru> wrote: > >> As I wrote before - I create caches dynamically and cannot declare cache >> configuration in client.xml because cache doesn't exist yet. >> >> ------------------------------ >> *From: *"Denis Magda" <dma...@apache.org> >> *To: *"user" <user@ignite.apache.org> >> *Sent: *Friday, September 13, 2019 10:50:16 PM >> *Subject: *Re: [cpp] Setup a near cache on client and server nodes >> >> Oleg, >> You need to add the near cache settings to Ignite client configuration >> explicitly. Please try out the code snippets from this documentation page: >> https://apacheignite.readme.io/docs/near-caches >> >> - >> Denis >> >> >> On Fri, Sep 13, 2019 at 12:36 PM Oleg Popov <o.po...@livelace.ru> wrote: >> >>> I use thick client. I don't have any records with caches configurations >>> in my client XML file (I create caches dynamically through REST requests >>> and caches templates). >>> >>> I don't know where I should place a near cache configuration on a >>> client. Should I explicitly declare a cache configuration and put a near >>> cache configuration into it ? >>> >>> Could you share a working settings (data node, client node) of a near >>> cache ? >>> >>> ------------------------------ >>> *From: *"Denis Magda" <dma...@apache.org> >>> *To: *"user" <user@ignite.apache.org> >>> *Sent: *Friday, September 13, 2019 8:46:06 PM >>> *Subject: *Re: [cpp] Setup a near cache on client and server nodes >>> >>> Hello Oleg, >>> Just to confirm, do you use C++ thin or thick (regular) client? If you >>> have inserted this property into the configuration on the client side then >>> it should work. Something might have failed on the visor end. >>> >>> Btw, do you see any performance difference after turning on/off the near >>> cache? >>> >>> - >>> Denis >>> >>> >>> On Thu, Sep 12, 2019 at 12:30 AM Oleg Popov <o.po...@livelace.ru> wrote: >>> >>>> Hello. >>>> >>>> Configuration: >>>> >>>> 1. N1 и N2 - data nodes (in different k8s clusters). >>>> 2. C1 - client node (outside of k8s clusters; c++ client node). >>>> 3. All caches are replicated. Caches create through REST/caches >>>> templates. >>>> >>>> Need: >>>> >>>> 1. C1 has to have a near cache for better performance. >>>> >>>> Question: >>>> >>>> 1. How to enable and use a near cache on client and data nodes ? >>>> 2. Is there any support NearConfiguration in C++ ? >>>> >>>> I have already tried to add: >>>> >>>> <property name="nearConfiguration"> >>>> >>>> <bean class="org.apache.ignite.configuration.NearCacheConfiguration"> >>>> <property name="nearEvictionPolicy"> >>>> <bean >>>> class="org.apache.ignite.cache.eviction.lru.LruEvictionPolicy"> >>>> <property name="maxSize" value="1000000"/> >>>> </bean> >>>> </property> >>>> </bean> >>>> </property> >>>> >>>> to a cache template, but ignitevisor shows that near cache is disabled >>>> ("off" state). >>>> >>>> >>>> С уважением, Попов О.В. / Best regards, Popov V Oleg >>>> >>> >>
