Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id EE0AC200C09 for ; Wed, 11 Jan 2017 04:24:31 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id ECD95160B4B; Wed, 11 Jan 2017 03:24:31 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 1BC79160B3D for ; Wed, 11 Jan 2017 04:24:30 +0100 (CET) Received: (qmail 47655 invoked by uid 500); 11 Jan 2017 03:24:30 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 47645 invoked by uid 99); 11 Jan 2017 03:24:30 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Jan 2017 03:24:30 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id ADE981A047D for ; Wed, 11 Jan 2017 03:24:29 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1 X-Spam-Level: X-Spam-Status: No, score=-1 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, RP_MATCHES_RCVD=-2.999, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id Ka_jc88h6ME7 for ; Wed, 11 Jan 2017 03:24:26 +0000 (UTC) Received: from chnog22.cognizant.com (chnog22.cognizant.com [203.99.199.27]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 4F7215F4A6 for ; Wed, 11 Jan 2017 03:24:25 +0000 (UTC) From: To: Subject: Questions on Client Reconnect and Client Cache Thread-Topic: Questions on Client Reconnect and Client Cache Thread-Index: AdJruOfu/d5D37QNR/iKxG85X/lKow== Date: Wed, 11 Jan 2017 03:23:57 +0000 Message-ID: <1AC7BDDA4E0DCD469EF27024B06CFB9713B27694@CTSINCHNSXMBE.cts.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.155.132.85] Content-Type: multipart/alternative; boundary="_000_1AC7BDDA4E0DCD469EF27024B06CFB9713B27694CTSINCHNSXMBEct_" MIME-Version: 1.0 archived-at: Wed, 11 Jan 2017 03:24:32 -0000 --_000_1AC7BDDA4E0DCD469EF27024B06CFB9713B27694CTSINCHNSXMBEct_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, Appreciate if anyone can answers below questions 1. In case if Ignite server is restarted, I need to restart the clien= t (web applications). Is there any way client can reconnect to server on se= rver restart. I know when server restarts it allocates a different ID and b= ecause of this the current existing connection becomes stale. Is there way = to overcome this problem and if so, which version of Ignite supports this f= eature. Currently I utilize version 1.7 2. Can I have client cache like how Ehcache provides. I don't want cl= ient cache as a front-end to a distributed cache. When I looked at the Near= Cache API, it doesn't have cache name properties like cache configuration = and it acts only as a front-end to a distributed cache. Is it possible to c= reate client only cache in Ignite 3. If I have a large object to cache, I find Serialization and Deseri= alization takes a longer time in Ignite and retrieving from distributed cac= he is slow. Is there any way we can speed up large objects retrieval from I= gnite DataGrid. Regards, Mani This e-mail and any files transmitted with it are for the sole use of the i= ntended recipient(s) and may contain confidential and privileged informatio= n. If you are not the intended recipient(s), please reply to the sender and= destroy all copies of the original message. Any unauthorized review, use, = disclosure, dissemination, forwarding, printing or copying of this email, a= nd/or any action taken in reliance on the contents of this e-mail is strict= ly prohibited and may be unlawful. Where permitted by applicable law, this = e-mail and other e-mail communications sent to and from Cognizant e-mail ad= dresses may be monitored. --_000_1AC7BDDA4E0DCD469EF27024B06CFB9713B27694CTSINCHNSXMBEct_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

Appreciate if anyone can answers below questions

 

1.     &= nbsp; In case if Ignite server is restarted, I need to re= start the client (web applications). Is there any way client can reconnect = to server on server restart. I know when server restarts it allocates a dif= ferent ID and because of this the current existing connection becomes stale. Is there way to overcome this p= roblem and if so, which version of Ignite supports this feature. Currently = I utilize version 1.7

 

2.     &= nbsp; Can I have client cache like how Ehcache provides. = I don’t want client cache as a front–end to a distributed cache= . When I looked at the Near Cache API, it doesn’t have cache name pro= perties like cache configuration and it acts only as a front-end to a distributed cache. Is it possible to create client onl= y cache in Ignite

 

3.     &= nbsp; If I have a large object to cache, I find Serializa= tion and Deserialization takes a longer time in Ignite and retrieving from = distributed cache is slow. Is there any way we can speed up large objects r= etrieval from Ignite DataGrid.

 

 

Regards,

Mani

This e-mail and any files transmitted with it are for the sole use of the i= ntended recipient(s) and may contain confidential and privileged informatio= n. If you are not the intended recipient(s), please reply to the sender and= destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwardi= ng, printing or copying of this email, and/or any action taken in reliance = on the contents of this e-mail is strictly prohibited and may be unlawful. = Where permitted by applicable law, this e-mail and other e-mail communications sent to and from Cognizant e-m= ail addresses may be monitored. --_000_1AC7BDDA4E0DCD469EF27024B06CFB9713B27694CTSINCHNSXMBEct_--