Re: NullPointerException in GridCacheTtlManager.expire

Thank you for the information! What are the worst consequences if I hit that bug? Entries not being evicted? Is my tx committed if the error is striking on commit or do I need to redo the work that was done in the tx? On 12. Apr 2018, at 14:30, Andrey Mashenkov

Re: Primary and Backups caches questions.

Hi Mauricio, 1. This is correct. 2. Queries return the actual data, therefore you see every entry only once. The fact that there are backups is internal and is not related to query results. And actually, I don't think the check you're doing is valid because different queries are not in sync with

Re: SQL Transactional Support for Commit and rollback operation.

Hi Rizal, It will be served hot to your doors soon. Please stay tuned ;) -- Denis On Wed, Apr 11, 2018 at 6:21 PM, rizal123 wrote: > Dear Ignite Masters, > > Yes, i also need this features. I hope it will be release soon. I hope.. :) > > I have to pending my project

Primary and Backups caches questions.

Hi All. I have the following scenario. My cluster has 12 nodes. I have one PARTITIONED cache named Documents and the type is also the number of backups of this cache is 1. My questions are the following: 1. Having my number of backups equals to 1, this means that any entry will

Re: NullPointerException in GridCacheTtlManager.expire

Hi Dome, It is known issue and there is a ticket for this [1] you can track. It is hard to be reproduced due to a race. Seems, GridCacheUtils.unwindEvicts() should check if context has been started. [1] https://issues.apache.org/jira/browse/IGNITE-7972 On Thu, Apr 12, 2018 at 2:39 PM,

Re: FsyncModeFileWriteAheadLogManager cannot be cast to FileWriteAheadLogManager ERROR

Hi, This is a bug that has already been fixed in https://issues.apache.org/jira/browse/IGNITE-7865. As a workaround, you can change WALMode value from FSYNC to any other mode, or start Ignite with JVM property -DIGNITE_WAL_FSYNC_WITH_DEDICATED_WORKER=true. On Thu, Apr 12, 2018 at 2:18 PM, NO

Re: NullPointerException in GridCacheTtlManager.expire

Hi Dome, Could you please attach full logs? Thanks! -Dmitry -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: FsyncModeFileWriteAheadLogManager cannot be cast to FileWriteAheadLogManager ERROR

Hello! It looks like this problem fix have been scheduled for 2.5: https://issues.apache.org/jira/browse/IGNITE-7865 I would recommend using walMode of LOG_ONLY for now, or adding a system property -DIGNITE_WAL_FSYNC_WITH_DEDICATED_WORKER=true. Your mileage may vary, but to me, LOG_ONLY looks

FsyncModeFileWriteAheadLogManager cannot be cast to FileWriteAheadLogManager ERROR

Hi AM using 2.4 When I stop a node, other nodes will have an error log as follows =LOG== [2018-04-12T19:03:39,767][ERROR][sys-#317][GridCacheIoManager] Failed processing message [senderId=b541279a-78fb-4ab0-a9b2-a50f8f36823d,

Re: Delete SQL is failing with IN clause for a table which has composite key

Hi, The problem is already fixed [1]. Fix will be available in AI 2.5. [1] https://issues.apache.org/jira/browse/IGNITE-8147 On Wed, Apr 11, 2018 at 9:21 AM, Naveen wrote: > Hi > > These are the queries I have used, which I was getting the error every time > I