Customized affinity function

Hi, I have following case. I have around 1 subscriptions. Each subscription has data varying from 1 to 10 million. Currently the affinity key is set on subscriptionId. e.g: Subscription1: 2 million rows Subscription2: 10 million rows Subscription3: 50 million rows Subscription5: 30 million

Issue IGNITE-3471

https://issues.apache.org/jira/browse/IGNITE-3471 Can we please have a fix for this issue in ignite 2.5 version? Reason: I am trying to test the distributed transaction support using following piece of code. While debugging the code I observed that code executes on client node first and after

Re: Readonly nodes

That is ok, I don't need Ignite to do authentication. Just prevent data modification. Denis told about node filters, but i didn't get how it is working On 11/04/2018 02:56, vkulichenko wrote: Ignite doesn't have authentication/authorization capabilities at the moment, however there are

Re: Slow invoke call

Hi Sam, What does this byte array represent? You have to array copies in the entry processor, so I'm not surprised it doesn't perform very well. That's also the reason why it gets worse when size of the array is increased. The fact that you're using off-heap also make it worse in this case as it

Re: Readonly nodes

Ignite doesn't have authentication/authorization capabilities at the moment, however there are certain plans for that as far as I know. In the meantime, you can take a look 3rd party vendors like GridGain that have paid offerings for this: https://docs.gridgain.com/docs/security-and-audit -Val

Re: How to query cross-node Cache data with JDBC correlation?

Hi, Unfortunately, I doubt this description would be efficient to understand what's going on. Do you have a reproducer that you can share with us? -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: JMX-MBean Reports OffHeapAllocatedSize as zero

Hi Christoph, Can you try 2.4.0? I know there were some fixes for memory metrics, so there is a big chance you will not reproduce the issue with the latest version. -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Readonly nodes

I use Ignite as a session store and need to allow write access only for authentication services. On 11/04/2018 00:45, Denis Magda wrote: The filter excludes the nodes from the list of those which can store data. That's why those nodes would never receive any requests. Considering your

Re: Readonly nodes

The filter excludes the nodes from the list of those which can store data. That's why those nodes would never receive any requests. Considering your follow-up questions, I guess you are looking for multi-tenancy capabilities. Do you want to prevent some of your applications to update data stored

Re: Ignite Sql query problem using IN clause

There is a suggested workaround in https://apacheignite-sql.readme.io/docs/performance-and-debugging#section-sql-performance-and-usability-considerations, item 2 As a workaround...you can rewrite the query in the following way: select p.name from Person p join table(id bigint = ?) i on p.id =

Re: Readonly nodes

Hi, Denis Thank you for your answer. What effect will filter have? Does it mean that read-only node doesn't have own data copy? Is it like partitioned cache? If so, why is it read-only? On 10/04/2018 02:37, Denis Magda wrote: Hi, Yes, you can tap into NodeFilter interface applying it

JMX-MBean Reports OffHeapAllocatedSize as zero

Hi, I use a partitioned cache with off heap in Ignite 2.3.0. After putting some values I see in JMX MBean org.apache"org.apache.ignite.internal.processors.cache.CacheClusterMetricsMXBeanImpl" some entries with prefix OffHeap. Value OffHeapEntriesCount is the number of stored entries and now

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

Hi Naveen, Unfortunately I'm unable to reproduce that error. Could you please attach simple code/project that fails with specified exception? Thanks! -Dmitry -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Sql query problem using IN clause

Has it been fixed in 2.4 ? Looks like it is not, when I generate the explain plan for a query which has a composite key Here are the queries I ran and explain plan results. When I use IN, it uses the full table scan, otherwise It does look up on primary key explain SELECT * FROM

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

Hi AM using 2.4 My delete statement is failing when I pass multiple keys, table has a composite key with 3 columns. Have mentioned the table structure along with a failed query and successful query and the error I am seeing the Here is the table created Java API CREATE TABLE

Re: Slow invoke call

Sam, >> Why does invoking remote method is taking 50% of time? Is it because of concurrency and entry processor will execute under a lock internally? >> Could you please share a small reproducer project. >> Is there any better way to deal with this usecase? Have you tested with only heap memory?

Re: Ignite cache get operation not working, client application stucks at the initializaiton

In object com.interactcrm.qm.queuegroup.QueueGroup you have the field of type com.interactcrm.qm.dao.ContactDAO and you need to make sure that this field won't be serialized. Evgenii 2018-04-10 12:32 GMT+03:00 Priyanka Shinde : > Hi, > > I have provided the absolute

Re: Ignite cache get operation not working, client application stucks at the initializaiton

Hi, I have provided the absolute path of the log4j.xml and logs were generated in the application logs itself.Attaching the same. C‪lient_logs.txt -- Sent from:

Re: Ignite cache get operation not working, client application stucks at the initializaiton

Hi Evengii, I have provided the Absolute path for log4j.xml and logs are generated.A C‪lient_logs.txt ttaching the same -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Strange node fail

Duplicates http://apache-ignite-users.70518.x6.nabble.com/Strange-node-fail-td21078.html. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Strange node fail

Hi Ray, If your JVM process consumes more memory, then started swapping may cause JVM freeze, and as a consequence, throwing it out from the cluster. Check your free memory, disable swapping, if possible, or increase IgniteConfiguration.failureDetectionTimeout. To check that guess you may use

Re: Regarding Ignite Slack Channel

Hi Rick, If I am not wrong, there is no Apache Ignite channel in Slack. Besides User-list, you can use Gitter [1] or Stackoverflow [2] to contact the community as well. Best Regards, Roman [1] https://gitter.im/apacheignite/ignite [2] https://stackoverflow.com/questions/tagged/ignite -- Sent