Hi, 1. It's mostly OK, but expiry policy should be set on the main cache and it will be inherited by the near cache Please refer to this documentation section <https://apacheignite.readme.io/v2.1/docs/near-caches#section-configuration> 2. It's not possible out of the box, but you could do some test runs and gather statistics that could give you some hints on the appropriate values for eviction and expiration policies to achieve the wanted behavior or, at least, get closer to it. 3. You can use for example IgniteCache#localEntries or IgniteCache#size with CachePeekMode#NEAR parameter. As well take a look at metrics <https://apacheignite.readme.io/v2.1/docs/cache-metrics> 4. You could have a separate cache for a predefined subset of keys and enable a near cache for it 5. In general, yes.
Kind regards, Alex. On Tue, Aug 29, 2017 at 7:53 AM, hiten [via Apache Ignite Users] < [email protected]> wrote: > Point 5. According to documentation "utilizing Ignite with affinity > colocation, near caches should not be used". > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > http://apache-ignite-users.70518.x6.nabble.com/We-want- > to-configure-near-cache-on-client-so-that-we-can-handle- > high-TPS-items-and-avoid-network-calr-tp16463p16470.html > To start a new topic under Apache Ignite Users, email > [email protected] > To unsubscribe from Apache Ignite Users, click here > <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=1&code=YWxleGFuZGVyLmZlZG90b2ZmQGdtYWlsLmNvbXwxfC0xMzYxNTU0NTg=> > . > NAML > <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/We-want-to-configure-near-cache-on-client-so-that-we-can-handle-high-TPS-items-and-avoid-network-calr-tp16463p16516.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
