Re: .Net ICacheEntryFilter

Hi, Can you share a simple reproducer project for [InstanceResource] within ICacheEntryFilter? I can't find unit tests for that case in Apache Ignite source code. > but the field _ignite is null and we have no access to cache to get it. That sounds like a bug that should be fixed. Thanks,

Re: Logging using Log4Net

Igg.zip -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Logging using Log4Net

Hi, Hm, actually, you've got several log4net misconfigurations in your solution. Everything was fine with Ignite config itself ). Please see updated minified solution attached. Just "build a solution" and it will restore all required packages. The following log4net misconfigurations fixed: 1.

Re: Logging using Log4Net

Hi, There could be several issues. Unfortunately, you just provided some config snippets. First of all, please add to your appender RollingLogFileAppender config. Then, please ensure that your log4net configuration section is actually used. It is better to have a separate file log4net.config

Re: Remote client

Hi, Does your remote client has public IP? Please note that client node should be accessible for TCP incoming connections from a server node, i.e. the server node should be able to connect to client IP as well. Your client IP is 192.168.8.132. And your server node is not able to connect it. So

Re: IgniteOutOfMemoryException when using putAll instead of put

Hi Larry, I checked the code. The issue is specific to your test data. You have relatively large initial entries (4.7 Kbytes) with the same index length (it is a just String). Please note that the index can't fit into the single page (4K). The rest of entries during .get() (from Store) are

Re: IgniteOutOfMemoryException when using putAll instead of put

Hi Larry, I am without my PC for a while. I will check the file you attached later this week. Thanks, Alexey -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Apache Ignite best practice

Hi Sergey, There could not be an exact answer to your question. It depends mostly on your use-case. 1. first of all, you should look at CPU/mem/network usage 2. and then you should check SQL debugging guide, starting from EXPLAIN for your query. Please see [1] for details. 3. you could enable

Re: No user-defined default MemoryPolicy found

I checked the code Actually, you can ignore this warning ("WARNING: No user-defined default MemoryPolicy found; system default of 1GB size will be used."). Apache Ignite applies your defaultMemoryPolicySize Or you can change your config to avoid such warning:

Re: Use SQL to query IgniteRDD with scala at Zeppelin

Hi, Please note that REST protocol puts keys as String. So you have 3 Integer keys and 1 String key in a cache. That is the reason for your results. You can find details in topic [1] [1] http://apache-ignite-users.70518.x6.nabble.com/Rest-API-PUT-command-syntax-tc19158.html Thank you, Alexey

RE: failed to find sql table for type:

Hi, Do you still have this issue? Can you share your code? Ignite.NET solution has a QueryExample.cs, you can use it as a reference code. Thank you, Alexey From: kenn_thomp...@qat.com Sent: Wednesday, January 10, 2018 5:56 PM To: user@ignite.apache.org Subject: failed to find sql table for

Re: off heap memory usage

Hi Colin, You should use TotalAllocatedPages if you have persistence disabled. There is an know issue with PhysicalMemoryPages: https://issues.apache.org/jira/browse/IGNITE-6963 Thank you, Alexey -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: IgniteOutOfMemoryException when using putAll instead of put

Hi, You are right, "evicts=0" is related to cache evictions for on-heap caching [1]. It should be always 0 for you. I tried your case (with the same configs as you) and page evictions work fine with cache store enabled and indexed types. It seems that you have some misconfiguration. What are

RE: No user-defined default MemoryPolicy found

Hi, Please have a look at topic below to get an estimation of memory usage: http://apache-ignite-users.70518.x6.nabble.com/off-heap-memory-usage-tc19282.html I will check the warning later, it looks strange to me. Thanks, Alexey -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: No user-defined default MemoryPolicy found

ok. I see you are at 2.1. (migrating from 2.1 to 2.3) -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: No user-defined default MemoryPolicy found

Hi, I see the same message with 2.1 release. 2.3 does not have it. I will check 2.1 source code later. Do you use 2.1 release? Thanks, Alexey -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: IgniteOutOfMemoryException when using putAll instead of put

Hi, You are right, cache.putAll() can't evict the entries from the batch it is working on, and you can get Ignite OOME. This is expected behavior because putAll get locks for all provided entry keys. That is critical: 1) for transactional caches and 2) any caches backed up by 3-rd party

Re: ClassCastException using cache and continuous query

Hi Diego, It seems that your error is related to different class Loaders being used. I don't have an idea why this happens but please try to clean your "work" directory in Ignite home (IGNITE_HOME) after 1.8 -> 2.3 upgrade or set up a new IGNITE_HOME. Please share you node configs and

Re: Creating multiple Ignite grids on same machine

Hi Raymond, In your case you should configure: 1. different TcpDiscoverySpi local ports 2. different ports for TcpDiscoveryVmIpFinder (Vm = Static for .NET). You should not use a default ipFinder. 3. different TcpCommunicationSpi local ports Please see sample Java xml-configs as a reference

RE: Why does Ignite de-allocate memory regions ONLY during shutdown?

Hi John, Could you please re-phrase you question. What issue are you trying to solve? Probably, you should address your question directly to dev-list. Anyway, you can read about memory region architecture at [1] and [2]. Hope it helps. [1]

Re: dotnet thin client - multiple hosts?

Hi Colin, There is a ticket for this improvement. https://issues.apache.org/jira/browse/IGNITE-7282 Thank you, Alexey -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Apache Ignite & unixODBC and truncating text

Hi Bagsiur, It is some mono lib error below, not a user-code. Can you share a simple code reproducer? Just to see the order of actions in your code. Thank you, Alexey From: bagsiur Sent: Tuesday, January 9, 2018 10:36 AM To: user@ignite.apache.org Subject: Re: Apache Ignite & unixODBC and

Re: How to make full use of network bandwidth?

Hi Michael, Did you try non-default parameters for 1) socketSendBuffer and socketReceiveBuffer [1] in JDBC connection string? 2) socketSendBufferSize and socketReceiveBufferSize [2] in Ignite server node configuration for SqlConnectorConfiguration? Please change them to 128k and make a try.

Re: off heap memory usage

Hi Colin, Unfortunately, you can't get the exact off-heap size. There are several tickets here https://issues.apache.org/jira/browse/IGNITE-6814 https://issues.apache.org/jira/browse/IGNITE-5583 http://apache-ignite-users.70518.x6.nabble.com/Cache-size-in-Memory-td17226.html You are using

Re: java.lang.IllegalStateException: Cache has been closed:

Hi Raj, IgniteCache implements AutoCloseable interface. [1] You can't access it once IgniteCache.close() is called (implicitly via try-with-resource or explicitly). [1] https://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceClose.html Thanks, Alexey -- Sent from:

Re: Apache Ignite & unixODBC and truncating text

Hi Bagsuir, What Ignite version are you using? Could you please share a reproducible example of the issue you have? Or can you try the C# example attached (VS 2017)? Thank you, Alexey odbcvarchar.cs -- Sent from:

Re: Adresses of client's nodes in configuration file

Hi Alex, You are right. You just need IP addresses/hosts of server nodes in the configuration file. Thank you, Alexey -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Error of start with multiple data regions

Sorry. Please ignore my response ). I just misread you message. Thank you, Alexey From: Alexey Popov Sent: 26 декабря 2017 г. 12:05 To: user@ignite.apache.org Subject: Re: Error of start with multiple data regions Hi, Apache Ignite does not have this functionality out of the box

Re: Error of start with multiple data regions

Hi, Apache Ignite does not have this functionality out of the box and the community could not help with your question. You should ask this question directly to the company who provides a multiple data regions solution. Thank you, Alexey -- Sent from:

Re: Memory foot print of the ignite nThe background cache eviction process was unable to free [10] percent of the cache for Context

Naveen, I am not sure I understand you correctly. Ignite off-heap usage is a part of your VIRT "top" output. You can add DATA column to "top" output to better visualize memory usage of pure on-heap+off-heap data only. Please run Ignite with different memory settings and see the memory

Re: Memory foot print of the ignite nThe background cache eviction process was unable to free [10] percent of the cache for Context

Hi Naveen, Off-heap memory "Off-heap size" works strangely. There are several tickets here https://issues.apache.org/jira/browse/IGNITE-6814 https://issues.apache.org/jira/browse/IGNITE-5583 http://apache-ignite-users.70518.x6.nabble.com/Cache-size-in-Memory-td17226.html You can get an

Re: Redis problem with values > 8kb

Thanks, Wolfram. Good to know you have not blocked by this issue. Anyway, the issue is identified and will be fixed in the next release. Thanks, Alexey -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Redis problem with values > 8kb

Hi Wolfram, I reproduced the issue at my env and created a ticket https://issues.apache.org/jira/browse/IGNITE-7153. Unfortunately, I did not find any workaround with Redis client you use. Thank you, Alexey -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Locking rows within Ignite Transactions

Hi, Please note that cache.get(N) does not lock all "rows" inside a transaction. It just locks "row" with N key. Actually, you should not lock data that is not involved in the transaction. That is why the explicit lock is prohibited. It should be done out of transaction scope. If your case

RE: Does the Ignite C# client support distributed queues?

Hi Raymond, You are right, distributed queues require changes at Ignite core. https://issues.apache.org/jira/browse/IGNITE-2701 It was created almost 1 year ago. Please vote for this feature. As far as I know there is no plan/schedule for it. Thank you, Alexey From: Raymond Wilson Sent:

Re: Retrieving keys very slow from a partitioned, no backup, no replicated cache

Hi Anand, Ignite will collect a batch of updates for multiple operations if you enable write-behind. So, it will be done for entry.setvalue() within Cache.invoke for your case. And then Ignite will make a writeall() call for the batch. If your own CacheStore implementation does not override

Re: Redis problem with values > 8kb

Wolfram, The buffer size is hardcoded now, but it could be made configurable if it the real issue. Can you share a simple PHP sample? I think Java Unit tests may miss some important details you have with PHP. I wonder if I can test & find the missing part of the puzzle ). Thanks, Alexey --

Re: Redis problem with values > 8kb

Hi Wolfram, I just run unit tests for Redis with 10k string. They passed without errors. Can you share a reproducible example? Actually, the issue happens inside java.nio.HeapByteBuffer. What jdk/jre version do you use? BTW, this buffer size is set to 8k and it should be re-used in your case.

Re: Indexes on custom objects

Hi Daniels, Actually, you can have & use indexes for single (1 to 1 relation) nested objects. You can't have indexes for nested collections. "Indexes for nested *collections* and in particular for *maps* are not supported.". I wonder why Examples does not have that. Please see how it could be

Re: Cache queries - Failed to run map query remotely

1. I am not sure that "ORDER BY" works the way you expect ). Very probably it sorts by some object hash instead casting it to the specific derived type. 2. I don't think you can do it directly. But there are two workaround options here: a) keep Object as is, create a new String field just for

Re: Ignite 2.3.0 Console logging handler is not configured error in start-up

Hi Sumanta, Please have a look at https://issues.apache.org/jira/browse/IGNITE-6828 This error message comes from Spring framework (org.springframework.data:spring-data-commons). It is not Ignite message and does not affect Ignite logging, so you can just ignore it. To avoid such message you

Re: AW: NullPointer in GridAffinityAssignment.initPrimaryBackupMaps

Lukas, You are right, IGNITE_HOME could not be a problem in embedded mode. Do you have any specific Affinity Function parameters in Cache configuration? Thanks, Alexey -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Prohibit "Node is out of topology"

Hi Lukas, Several "Finished serving remote node connection" shows that the node was cut off the cluster (some socket issues) Please enable DEBUG level for logs to see more details about possible reasons (socket errors, malformed messages, etc) Thanks, Alexey -- Sent from:

Re: NullPointer in GridAffinityAssignment.initPrimaryBackupMaps

Hi Lukas, It seems that a new node is just misconfigured and it can't correctly assign partitions by Affinity Function. Please set a valid IGNITE_HOME and verify that Affinity Function [1] matches the cluster config 2017-11-11 06:10:34:973 + [main] INFO

Re: Error serialising arrays using Ignite 2.2 C# client

Hi Raymond, You are right. True multidimensional arrays are not supported now in binary serialized (C#). Jugged arrays work fine. So, you can use them or just one-dimensional array with 2D-index calculation. Anyway, I opened a ticket: https://issues.apache.org/jira/browse/IGNITE-6896 You can

RE: Node failed to startup due to deadlock

Ups, there is a some issue with text formatted below. It should be just a replace  cache2.lock("fake"); with  Lock lock = ignite0.reentrantLock("fake", true, false, true); where ignite0 is a "final" copy for a new Thread  final Ignite ignite0 = ignite; Thank you, A

RE: Node failed to startup due to deadlock

Hi Naresh, I still don't have a clear understanding of your case. Very probably you just need a Cache Store with Read-Through enabled. Please have a look at [1] and Cache Store examples. As for code provided - you can have a workaround here until

RE: write behind performance impacting main thread. Write behindbuffer is never full

Hi Larry, BTW, there is an open improvement https://issues.apache.org/jira/browse/IGNITE-5003 for the issue you faced. Thanks, Alexey -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Node failed to startup due to deadlock

Hi Naresh, Unfortunately I don’t see any attachment, please send them again. Can you clarify your node startup activity. 1) How do you lock the caches? IgniteCache.lock() or IgniteCache.lockAll() locks only a one or batch of cache entries, not the whole Cache. 2) Do you really need some locks

RE: write behind performance impacting main thread. Write behindbuffer is never full

lp. Larry  On Fri, Nov 3, 2017 at 12:11 PM, Alexey Popov <tank2.a...@gmail.com> wrote: Hi, Can you share your cache store implementation? It could be several reasons for possible performance degradation in write-behind mode. Ignite can start flushing your cache values in main() thread if cacheSize

RE: Node failed to startup due to deadlock

Hi Naresh, I see deadlocks with 1. com.rover.core.dao.model.admin.AdminPreferenceTable (2 locks) 2. com.rover.core.dao.model.product.assembly.AssemblyUpi2BomTable (2 locks) 3. com.rover.core.dao.model.product.assembly.AssemblyBomUpi2PackageTable, 4.

Re: write behind performance impacting main thread. Write behind buffer is never full

Hi, Can you share your cache store implementation? It could be several reasons for possible performance degradation in write-behind mode. Ignite can start flushing your cache values in main() thread if cacheSize becomes greater than 1,5 x setWriteBehindFlushSize. It is a common case but it does

RE: Node failed to startup due to deadlock

Rajeev, I see “WARNING: Failed to wait for partition release future” section in your logs. It includes “WARNING: Pending explicit locks:” with 7 cache locks (GridCacheExplicitLockSpan) GridCacheExplicitLockSpan details don’t have specific information about cache operation but they have

Re: Node failed to startup due to deadlock

Hi Rajeev, All Ignite callbacks are processed in (=called from) internal Ignite thread pools. The generic rule here is to avoid direct Ignite calls from such callbacks. So, it is better to do all your things in separate threads (use ExecutorService for instance). You should pass all work to your

Re: Failed to create string representation of binary object.

Ankit, That looks very strange. Your class does not have registrationInfoResponse field which is mentioned in the error. Please confirm that node with id="b2df236f-4fba-4794-b0e4-4e040581ba9d" is a part of your load testing cluster. Do you have peerClassLoadingEnabled=true at your configs?

Re: Node failed to startup due to deadlock

Naresh, Rajeev I've looked through the logs. Node2 is stuck because it is waiting for Node1 (id=96eea214-a2e3-4e0a-b8c6-7fdf3f29727c) partition map exchange response. So it looks like the real deadlock is at Node1 (id=96eea214-a2e3-4e0a-b8c6-7fdf3f29727c) Can you also send node1 logs and thread

Re: Failed to create string representation of binary object.

Hi Ankit, I see two lines in the exception below: "Failed to read field: registrationInfoResponse " "com.partygaming.services.mds.userprofile.api.UserRegistrationInfoResponse" It seems that UserRegistrationInfoResponse.registrationInfoResponse becomes null / incorrect during your test and it

Re: Deadlock on Node Remove and Add

Hi, Is it the same issue http://apache-ignite-users.70518.x6.nabble.com/Node-failed-to-startup-due-to-deadlock-tc17839.html? Can you try the build from a master branch? Thanks, Alexey -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Node failed to startup due to deadlock

Hi Naresh, Can you share your log from Node 2 and configuration file? The issue is related to Cache PartitionExchange procedure during node startup. Very probably this issue is already fixed on master branch. Thank you in advance, Alexey -- Sent from:

Re: Retrieving keys very slow from a partitioned, no backup, no replicated cache

Hi Anand, Can you share your CacheStore implementation? Do you use CacheStoreAdapter<>? Very probably you don't have your own "CacheStore.writeAll()" implementation that is used for batches. And the default one is used (it just sequentially calls "CacheStore.write()" for all entries in a batch).

Re: Retrieving keys very slow from a partitioned, no backup, no replicated cache

Hi Anand, >In regards to your comment on cache will not get updated using invoke. How >do I ensure that the new computed value gets stored in the cache. >The first goal is to iterate through the cache and update a specific data >field in the cache in the fastest way possible. >The second goal

Re: Retrieving keys very slow from a partitioned, no backup, no replicated cache

Hi Anand, 1. Actually, you should broadcast your logic to all nodes via Ignite.compute() Please see the sample below: Collection res = ignite.compute().broadcast( new IgniteCallable() { /** Auto-inject ignite instance. */