Hello! You can make it semi-persistent by changing the internal Ignite node type inside Hibernate to client (property clientMode=true) and starting a few stand-alone nodes (one per each VM?)
This way, its client will just connect to the existing cluster with data already there. You can also enable Ignite persistence, but I assume that's not what you want. Regards, -- Ilya Kasnacheev пн, 9 нояб. 2020 г. в 20:05, Bastien Durel <[email protected]>: > Le lundi 09 novembre 2020 à 19:11 +0300, Ilya Kasnacheev a écrit : > > Hello! > > > > Why Hibernate won't use it for reads of that user, I don't know, it's > > outside of scope of Ignite. > > > > Putting 1,000,000 records in 5 minutes sounds reasonable, especially > > since L2 population is optimized for latency, not throughput (as > > opposed to e.g. CacheLoader). > > Hello, > > I'm OK if the L2C make 5 minutes to load (as I said, there will > probably never be such a query in the real application), the real > problem here is that this cache does not persist between Sessions, and > therefore is recreated each time. > > It may be a configuration problem, but reading [1], I cannot find why > > Regards, > > [1] > https://ignite.apache.org/docs/latest/extensions-and-integrations/hibernate-l2-cache > > -- > Bastien Durel > DATA > Intégration des données de l'entreprise, > Systèmes d'information décisionnels. > > [email protected] > tel : +33 (0) 1 57 19 59 28 > fax : +33 (0) 1 57 19 59 73 > 45 avenue Carnot, 94230 CACHAN France > www.data.fr > > >
