Re: OFFHEAP_TIERED and memory fragmentation

Hi Val, fair enough :-) However, in the source-code it looks like "Flexible and precise per-cache memory limit" is supported already. At least each GridUnsafeMemory instance (in each GridCacheContext) receives the value from CacheConfiguration.getOffHeapMaxMemory). I haven't debugged it, but the

Re: Ignite cluster will be jammed for long-running queries

IGNITE-4105 is a must ticket for Apache Ignite 2.0. On Wed, Jan 25, 2017 at 8:58 AM, ght230 wrote: > Yes, some queries will be long running, they are unavoidable. > > Query slow is acceptable, but the cluster jammed is a bit of trouble. > > I will be grateful if IGNITE-4105 can

Re: insert/update/delete issue in Version 1.8

Please double check this documentation section https://apacheignite.readme.io/docs/dml#advanced-configuration If you have your custom key with multiple fields then key’s fields must be separated from value’s fields at the

insert/update/delete issue in Version 1.8

dear experts: I got exception - "Caused by: java.lang.IllegalStateException: Ownership flag not set for binary property. Have you set 'keyFields' property of QueryEntity in programmatic or XML configuration? " when my code is following link of "https://apacheignite.readme.io/docs/jdbc-driver;.

Asynchronous jobs (not the scheduling)

Hi all, I'm wondering if it's possible not to block the job executor's thread when I wait for some async event. somethingLike: ``` ignite.compute().run(() -> someServiceRefSomehow.doSomethingAsync()); ``` where ``` interface SomeService { CompletableFuture doSomethingAsync(); } ``` Or

Re: Asynchronous jobs (not the scheduling)

Sergei, Vlad, I think you also might be interested in compute continuations since the result of async execution may be sufficient for the job itself. Please see ComputeFibonacciContinuationExample under ignite/examples. --Yakov

Re: Asynchronous jobs (not the scheduling)

Hi Sergei, Why do you not use "ignite.compute().withAsync()"? On Wed, Jan 25, 2017 at 2:04 PM, Sergei Egorov wrote: > Hi all, > > I'm wondering if it's possible not to block the job executor's thread when > I wait for some async event. > > somethingLike: > > ``` >

Re: insert/update/delete issue in Version 1.8

Hi, Please show your configuration file (at least the section with QueryEntities) or how you configure your cache programmatically. - Alex 2017-01-25 15:21 GMT+03:00 minisoft_rm : > dear experts: > I got exception - "Caused by: java.lang.IllegalStateException: Ownership

Re: Cache stopped

Hi Alexandr, ignite stop is not actual node failure in this case. isn't it ? how node singleton helps in this case ? Am i missing anything? is there any way to intercept cache start and stop ? Thanks. On 16 December 2016 at 15:51, Alexandr Kuramshin wrote: > Hi Anil, >

Re: Kafka as a Persistent Store

You can implement the CacheStore interface to provide integration with any kind of storage: https://apacheignite.readme.io/docs/persistent-store There is no Kafka based implementation out of the box. -Val -- View this message in context:

Re: Text query

Hi, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send empty email to user-subscr...@ignite.apache.org and follow simple instructions in the reply. avpdiver wrote > Is there possibility to use my custom

Re: eagerTtl

Hi Sam, According to code, there is actually a thread per node not per cache. Do you observe different behavior? Also I didn't find anything about "thread per cache" in JavaDoc. Can you please show where you read this? -Val -- View this message in context:

Re: Cache stopped

Anil, Take a look at lifecycle beans: https://apacheignite.readme.io/docs/ignite-life-cycle -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cache-stopped-tp9503p10253.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

backup to swap

HI, Is there any way to push backup copy to swap file in ignite ? thanks. Thanks.

Re: Getting previous value in cache immediately after performing an unlock

Hi, Your test is incorrect. This lines are not synchronized and can be reordered with each other and with the validation that happens in another thread: simpleCacheValidationWithLock.setIndex(i - 1); simpleCacheValidationWithLock.setValueToValidate(valueCounter); After I moved them into the

eagerTtl

Hi I was going through JAVADoc and came across CacheConfiguration property eagerTtl. Came across one of the post which says eagerTtl=true spans a thread per cache. We are not using ExpiryPolicy on any of the caches, we have almost 100 different cache. To keep memory and thread footprint down,