Re: Ignite Cluster issues with larger latency between nodes

equently no processing going through. > > Is there any benchmarking done for Ignite or documents available which > say, for a stable ignite cluster the latency between nodes cannot be > x ms? > > However, if this is indeed our application issue then I would like to > understand how to troubleshoot or get around this issue. > > Thanks > Victor > -- Regards, Sumit Deshinge

Re: Crash recover for Ignite persistence cluster (lost partitions case)

не предназначено > Вам, использование, копирование, распространение информации, содержащейся в > настоящем сообщении, а также осуществление любых действий на основе этой > информации, строго запрещено. Если Вы получили это сообщение по ошибке, > пожалуйста, сообщите об этом отправителю по электронной почте и удалите это > сообщение. > *CONFIDENTIALITY NOTICE:* This email and any files attached to it are > confidential. If you are not the intended recipient you are notified that > using, copying, distributing or taking any action in reliance on the > contents of this information is strictly prohibited. If you have received > this email in error please notify the sender and delete this email. > -- Regards, Sumit Deshinge

How to enable ignite compress capability

) at org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.write(FilePageStoreManager.java:634) -- Regards, Sumit Deshinge

Re: Thin client cache operations takes longer and longer for subsequent retries to throw exception when server down

ngRetries, reconnectThrottlingPeriod > > To fail fast, set reconnectThrottlingPeriod to 0 and retryLimit to 1. > > [1] > https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/ClientConfiguration.html > > On Fri, Jul 8, 2022 at 4:46 PM Sumit Deshinge > wrote: > >&g

Re: Cache directory full path on disk

llo Sumit > > You can simply clean up with a scheduled cronjob does executes rmdir, if > the directory is not empty rmdir will not proceed. > > Cheers > Gianluca > > On Fri, 8 Jul 2022 at 15:38, Sumit Deshinge > wrote: > >> Any pointers here? >> >&

Re: Thin client cache operations takes longer and longer for subsequent retries to throw exception when server down

Correction in subject On Fri, Jul 8, 2022 at 7:12 PM Sumit Deshinge wrote: > Hi, > > I have ignite thin clients connecting to ignite server. > When server node is down, ClientCache operations like get, exists takes > incremental times to throw clientconnectiontimeout exception.

Thin client cache operations takes longer and longer when server down

setting/property do I need to change in order to reduce this time? Basically I want these client cache operations to fai fast during subsequent retries. -- Regards, Sumit Deshinge

Re: Cache directory full path on disk

Any pointers here? On Wed, Jun 29, 2022 at 12:55 PM Sumit Deshinge wrote: > After cache.destroy operation is performed, it clears all the cache data, > but directory for that cache exists with empty data. > I am creating many caches for specific workflow and destroy them, same > kee

Re: Cache directory full path on disk

and that count goes on increasing. So I want to cleanup them. On Tue, Jun 28, 2022 at 6:38 PM Stephen Darlington < stephen.darling...@gridgain.com> wrote: > What are you trying to achieve? > > On 28 Jun 2022, at 13:14, Sumit Deshinge wrote: > > How do I get a full cache

Cache directory full path on disk

, Sumit Deshinge

Re: Unable to remove cache key entries after Ignite server restart

te.apache.org/docs/latest/tools/control-script#verifying-partition-checksums > > On Thu, 5 May 2022 at 12:24, Sumit Deshinge > wrote: > > > > Has anyone faced such an issue earlier? Any pointers are much > appreciated. > > > > On Thu, Apr 28, 2022 at

Re: Unable to remove cache key entries after Ignite server restart

Has anyone faced such an issue earlier? Any pointers are much appreciated. On Thu, Apr 28, 2022 at 10:20 PM Sumit Deshinge wrote: > Note that this is not happening with all the data set but only for cache > entries which were written into ignite before server restart and tried to > b

Re: Unable to remove cache key entries after Ignite server restart

Note that this is not happening with all the data set but only for cache entries which were written into ignite before server restart and tried to be deleted after restart. On Thu, Apr 28, 2022 at 10:18 PM Sumit Deshinge wrote: > Hi, > > I am using ignite with native persistence enab

Unable to remove cache key entries after Ignite server restart

of checkpoint. Will restore memory state and finish checkpoint on node start. - Started cache in recovery mode - Finished recovery for cache Any idea or configuration that needs to be done during such case ? -- Regards, Sumit Deshinge

Re: Ever increasing Disk space for a cache in ignite storage directory

ation please. > > This thread might help you(comments) > > > https://stackoverflow.com/questions/48951091/ignite-how-eviction-expiry-and-rebalancing-work-with-external-cachestore > > On Tue, Feb 22, 2022, 08:27 Sumit Deshinge > wrote: > >> Hi, >> >> We are u

Ever increasing Disk space for a cache in ignite storage directory

to avoid such problems? -- Regards, Sumit Deshinge

Re: Server cache reads less number of entries than number of entries put by client cache

t; > On Thu, Feb 3, 2022 at 7:53 PM Sumit Deshinge > wrote: > >> Yes, that I am sure, because the keys are generated using ignite uuid, >> which internally is based on hostname, and all the clients are hosted on >> machines with unique hostnames. >> >>

Too many open cursors issue after cache partition loss exceptions

this situation ? -- Regards, Sumit Deshinge

Re: Server cache reads less number of entries than number of entries put by client cache

you do 5000 puts but some keys are the same, the result will be > less than 5000 entries. > > On Wed, Feb 2, 2022 at 12:27 PM Sumit Deshinge > wrote: > >> No, cache does not have entries. Somehow the number of entries returned >> are less than the number of entries put by al

Re: Server cache reads less number of entries than number of entries put by client cache

Feb 2, 2022 at 10:38 AM Sumit Deshinge < > sumit.deshi...@broadcom.com> wrote: > >> Hi Pavel, >> >> I am trying to remove the data from one cache (on which I am iterating) >> to another cache in transaction. >> When the iterator says no further elements, I

Re: Server cache reads less number of entries than number of entries put by client cache

, data is removed from the cache > > Sumit, as I understand, you read data while you also remove it, so it is > not clear what the expectation is. > > On Wed, Feb 2, 2022 at 10:28 AM Sumit Deshinge > wrote: > >> Thank you Surinder and Pavel. I will give this approach a try

Re: Server cache reads less number of entries than number of entries put by client cache

Just an idea, please correct if I am wrong >> >> On Fri, Jan 28, 2022 at 3:49 PM Sumit Deshinge >> wrote: >> >>> Hi, >>> >>> We are running apache ignite 2.11 with cache configuration FULL_SYNC and >>> REPLICATED mode. >>&g

Server cache reads less number of entries than number of entries put by client cache

transaction with serializable isolation level, then this issue is not observed*. What could be the possible problem in this use case with pessimistic concurrency and repeatable_read isolation level? This is particularly important as this configuration is resulting in data loss. -- Regards, Sumit Deshinge

Re: Ignite Cache operations get stuck when multiple thin clients try to perform CRUD operations in parallel with partition map exchange

gt; On 3 Nov 2021, at 11:59, Sumit Deshinge > wrote: > > Hi Ilya, > > I have tried to run this with both ignite 2.10 and 2.11 > There are 24 thin clients on different VMs which are trying to perform > *CRUD* operations on the *same AND/OR different caches* parallelly. &g

Re: Ignite Cache operations get stuck when multiple thin clients try to perform CRUD operations in parallel with partition map exchange

masks=local=1|owner=0|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=1|near_local=0|removed=0|read=0, > > prevVer=null, nextVer=null], GridCacheMvccCandidate > > [nodeId=2735bef0-7404-41e3-843f-7043490c9d84, ver=GridCacheVersion > > [topVer=247332659, order=163585270522

Ignite Cache operations get stuck when multiple thin clients try to perform CRUD operations in parallel with partition map exchange

94ab-d246944ed4a9, timeout=0, startTime=1635858659324, duration=20140, label=null]] at org.apache.ignite.internal.util.IgniteUtils$11.apply(IgniteUtils.java:974) at org.apache.ignite.internal.util.IgniteUtils$11.apply(IgniteUtils.java:972) ... 16 more -- Sumit Deshinge R Engineer |