Hi,
1. We have set 150000 ms as network timeout in IgniteConfiguration. Do we need to set a different connection timeout? 2. Even when I utilize Cache Mode as Local, the objects are stored in Server and distribution is what is not happening. Can it not store in Client. 3. How can extract a field values from BinaryObject. Do you have any sample code? Cheers, Mani From: Andrey Mashenkov [mailto:[email protected]] Sent: Wednesday, January 11, 2017 5:18 PM To: [email protected] Subject: Re: Questions on Client Reconnect and Client Cache Hi, 1. It looks like connection timeouts is too low. Do you see any errors in client logs? 2. You can have local cache on client. See CacheConfiguration#cacheMode option [1] 3. You can try recommendation given in [2] thread. [1] http://apacheignite.gridgain.org/docs/cache-modes#local-mode [2] http://apache-ignite-users.70518.x6.nabble.com/Efficient-way-to-get-partial-data-of-a-cache-entry-td9965.html#a9969 On Wed, Jan 11, 2017 at 9:39 AM, <[email protected]<mailto:[email protected]>> wrote: Can someone throw some light and help on below questions From: Lakshminarayanan, Manikandan (Cognizant) Sent: Wednesday, January 11, 2017 8:54 AM To: '[email protected]<mailto:[email protected]>' <[email protected]<mailto:[email protected]>> Subject: Questions on Client Reconnect and Client Cache Hi, Appreciate if anyone can answers below questions 1. In case if Ignite server is restarted, I need to restart the client (web applications). Is there any way client can reconnect to server on server restart. I know when server restarts it allocates a different ID and because of this the current existing connection becomes stale. Is there way to overcome this problem and if so, which version of Ignite supports this feature. Currently I utilize version 1.7 2. 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 properties like cache configuration and it acts only as a front-end to a distributed cache. Is it possible to create client only cache in Ignite 3. If I have a large object to cache, I find Serialization 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 retrieval from Ignite DataGrid. Regards, Mani This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. 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, 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-mail addresses may be monitored. -- С уважением, Машенков Андрей Владимирович Тел. +7-921-932-61-82 Best regards, Andrey V. Mashenkov Cerr: +7-921-932-61-82 This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. 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, 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-mail addresses may be monitored.
