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

Config gaps are also captured by tests in same folder. As for queues, I'm no expert, but I think all Ignite data structures use cache underneath, and any cache can be configured to enable persistence. On Tue, Dec 5, 2017 at 2:53 AM, Raymond Wilson wrote: > I was reading into this a little more

Re: Re: Re: Re:Poor performance select query with jdbc thin mode

Lucky, I looks strange, that client driver works slower than thin. Normally it should work just like cache.query() + network overhead. Maybe you included connection time into your evaluation? Or something else? You should compare query execution time, when connection is already established and all

Re:Re: index about jdbc thin mode

afedotov, As you say ,you removed JPA related annotations. How to removed? I try as your suggestion, I found if I build a new entity class and use cache.query() ,it will take the index, but still not take the index with JDBC thin mode. What did I miss? Thanks.

Re:Re: Re: Re:Poor performance select query with jdbc thin mode

Denis, This query just only retrieve 2 records. As I say in the first message, cache.query() took less time. Another thing,I did a statistics. When I enable enforceJoinOrder option, there are just few queries can become faster , but more than 1000 queries become slower.

Re: "HandshakeException: Remote node ID is not as expected" occurs when tested with 1000 clients

I go to the machine where cannot be connected (cc3a7x2183), and found the following exception message java.lang.IllegalArgumentException: Cache is not configured: ignite-sys-cache at org.apache.ignite.internal.processors.cache.GridCacheProcessor.jcache(GridCacheProcessor.java:3423)

Re: Semaphore Stuck when no acquirers to assign permit

>From what i found, it looks like the DataStructuresProcessor EventListener get invoked after the dsMap has been cleared which prevents the onNodeRemoved from being invoked. I created a pull request which will invoke the onNodeRemove from the stop method. Also added my test to the data structure te

Re:Re: index about jdbc thin mode

well, I use jdbc thin mode. It's ok with cache.query(); But It did not work with JDBC thin mode. Thanks.

Re: Register Contentious query quit slow

Denis， I can understand the meta data need to be updated when the CQ has initial query(IQ) or remote filter(RF). But my understading is only the object within IQ and RF need to be updated and the stuff in Local listeners does not. In my case, the logic in IQ and RF is simple string compare

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

I was reading into this a little more to see if queues are persistent. It appears they are not? https://issues.apache.org/jira/browse/IGNITE-2389 Thanks, Raymond. *From:* Alexey Popov [mailto:tank2.a...@gmail.com] *Sent:* Saturday, December 2, 2017 4:49 AM *To:* user@ignite.apache.org *Cc

[WEBINAR]: Meeting the Challenges of Fast Data in Healthcare with In-Memory Technologies

Please join me for a webinar on Wednesday, 6 December 2017 @ 11:00 am PT. https://ignite.apache.org/events.html#meeting-challenges-fast-data-in-healthcare-in-memory-technologies Thank you.

using JDBC with Ignite cluster, configured with persistent storage

Hi, I'm trying to use JDBC connection to run SQL on cluster, configured with Persistent storage. Persistent storage means what I have to make cluster active before I can do any DDL (or even request list of tables?) below is the output of sqlline, I'm trying to use, : 0: jdbc:ignite:thin://10.238.

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

Pavel, I took a look at the test; thanks! I don’t think this captures the configuration gaps between spring config and C# config, correct? Thanks, Raymond. *From:* Pavel Tupitsyn [mailto:ptupit...@apache.org] *Sent:* Tuesday, December 5, 2017 5:46 AM *To:* user@ignite.apache.org *Cc:*

Re: Student Blog about Apache Ignite & Questions how to efficiently handle data

Apparently I messed up the Blog link, here's the proper one: https://streambench.wordpress.com/category/apache-ignite/ Best Regards Sven -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: ignite.compute(ClusterGroup) is broken??

Hi Denis, Thank you for responding. >>> Can you provide a short summary of what you are trying to achieve? The problem is this. Ignite begins sending compute traffic to a Node (i.e. ComputeJobs), before that Node is truly ready to take traffic. Basically, as soon as Ignite starts and is balanc

Re: Caused by: class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to find SQL table for type: UserAppInfo

You did not set CacheConfiguration#indexedTypes property. See documentation for more details: https://apacheignite.readme.io/docs/cache-queries#query-configuration-by-annotations -Val On Sat, Dec 2, 2017 at 12:24 AM, kcheng.mvp wrote: > by the way, here is my maven dependency. > > the unit test

Re: ignite.compute(ClusterGroup) is broken??

Chris, I lost track of our discussion, because this part of your system seems to be too overarchitectured. Can you provide a short summary of what you are trying to achieve? The main thing that I don't understand is why you need a *map* method? This method is supposed to be used as a part of a ma

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

Raymond, There is no document. We keep track of missing stuff with tests. I've just added that for root level APIs, see MissingMembers: https://github.com/apache/ignite/blob/master/modules/platforms/dotnet/Apache.Ignite.Core.Tests/ApiParity/IgniteParityTest.cs#L39 Pavel On Sun, Dec 3, 2017 at 11

Re: Ignite cache partition size

Hello! * 8192 partitions have been tried with success, as far as I know. I think you can give it a shot, see where it gets you. It might slow down partition exchange a bit, but it should not hang just from increased amount of information (as opposed to stuck operations) * Yes,they need to have th

Re: Ignite .NET - Delete statement

Hi Jérôme, Could you please send me a full reproducer? And could you please clarify which version of Ignite is used? Thanks, Mike. 2017-12-04 12:38 GMT+03:00 jerpic : > Hello, I try to delete some records according to the DELETE statement (see > below). Unfortunately, I got every time an except

Student Blog about Apache Ignite & Questions how to efficiently handle data

Hello! I noticed that this community is pretty active, so there might be some people that are interested in this: For a university project, we're trying to compare different stream processing engines. I decided to use Apache Ignite. Since our professorship hasn't really worked with most of those

Re: Semaphore Stuck when no acquirers to assign permit

Hi Tim! Yes, it looks as bug. Thank you for investigation! Feel free to contribute. ;) On Fri, Dec 1, 2017 at 8:39 PM, Timay wrote: > Hey all, > > We experienced an issue when trying to establish a semaphore after a single > instanced client node goes down hard (kill -9). Which afterwards we ca

Re: Issues with multiple kafka connectors, questions regarding ignite caches

I think I figured it out now: Using the same worker for three different topics might be nonsense either way, at least in my case - All three topics require different converters, therefor I'll need three different connectors. To start multiple instances of connect-standalone, I need to specify the

Re: Ignite poor performance

Also, for indexes of String type you can increase inline size: https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/QueryIndex.html#setInlineSize(int) the default is 10, you can increase it to 32 or 64, it depends on your data, so you can experiment with different values and ch

Re: Index performance

So, then share benchmarks code Evgenii 2017-12-04 18:14 GMT+03:00 Ali : > I would recommend using the default value for this property - 1. But, if > you want to run a few of long queries, it could be increased. > > > Doesn’t help > > I have already tried to execute test with configurations: > >

Re: Index performance

> I would recommend using the default value for this property - 1. But, if you > want to run a few of long queries, it could be increased. Doesn’t help I have already tried to execute test with configurations: 1 request queryParalellism = 1 100 concurrent request queryParalellism = 1 1 request

Re: Ignite poor performance

Hi Sasha, it's definitely can work faster: 1. add index for DEST_NE_NAME: https://apacheignite.readme.io/docs/cache-queries#section-query-configuration-by-annotations 2. enable query parallelism: https://apacheignite-sql.readme.io/docs/performance-and-debugging#query-parallelism Thanks, Mike.

Re: index about jdbc thin mode

Hi, Just to clarify, the same result I have while running using the thin JDBC driver. Class.forName("org.apache.ignite.IgniteJdbcThinDriver"); try ( Connection conn = DriverManager.getConnection("jdbc:ignite:thin://localhost:10800"); PreparedStatement pre

Re: Index performance

Hi, Please share benchmarks code, it's hard to understand why you can't load CPU for 100% without your code. But I see one thing, that definitely could lead to performance problems - you've set - this could lead to a lot of context switching since every query could be executed in 48 threads. I'

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 requi

Re: index about jdbc thin mode

Hi, Not sure, what's wrong with your code. Either IX_T_BD_StatusFid or IX_T_BD_CUSTOMER should have been taken. I removed JPA related annotations and checked your code, it gave me the following plan: [[SELECT __Z0.FID AS __C0_0, __Z0.FNUMBER AS __C0_1 FROM "customerCache".CUSTOMERIGNITEIN

Ignite poor performance

Hi, I Working on big POC for telecom industry solution I have loaded to ignite 5,000,000 objects/rows (I loaded it in the client side Please find the code below) In the metric the used of heap looks too small (for 5M rows) is it normal utilization? [04-12-2017 13:10:27][INFO ][grid-timeout-wo

Index performance

Hi! I found poor sql index performance and CPU utilisation in ignite 2.3 version when try to benchmark cluster for performance. Cluster configuration: 6 x 2 E5-2600v2 256GB 10GB link 1 x 4 E7 node (edge) from which tests are running Ignite config

Re: "HandshakeException: Remote node ID is not as expected" occurs when tested with 1000 clients

Hi, What happened here: other node tried to connect to the node via address cc3a7x2183.nhnsystem.com/10.112.96.139:5 and were not succeeded. After it node tried to connect via other address, that was resolved by a node at a start - 127.0.0.1:5. Of course, as these 2 nodes on the separate m

Re: Can the cache key and affinity key be different

Hi, To collocate A and B with C you need to introduce custom key classes for A and B that will include @AffinityKeyMapped annotation on a C's ID field. An example of how to implement such a key could be found here https://apacheignite.readme.io/docs/affinity-collocation#section-collocate-data-with

Re: Number of open file handles keeps on increasing on Ignite node on adding a new cache

Hi Denis, After putting all the caches in single cache group, I dont have issue of too many open file handles. Ignite is putting all the caches in the single persistence folder and now bin files count is static even with 200 caches but each single bin file size is getting increased. Though I hav

Re: Index not getting created

Hi, I see only that "cache not found" at the server.log. Something is wrong. Is it possible to provide a test as the standalone java class or standalone GitHub project so that I can run it and reproduce the problem? On 30.11.2017 20:34, Naveen Kumar wrote: Hi Here is the node logs captured w

RE: Obtaining metadata about items in the cache

Thanks Alexey. This would certainly reduce the IO, but does still require all the data to be read. My use case is not really a production one: I want to iterate all items in the cache to determine if the page size for persistency was suitable. Reading all the data is not too painful, but a me

Re: query operator in local node

Hi, IgniteQuery#setLocal(true) will make the query to execute only on local node. Use IgniteCompute#affinityCall / affinityRun to send a job that would execute your local query to specific node. For example, this will execute a local query on a node where "myKey" is stored: compute.*affinityRun*

Re: Obtaining metadata about items in the cache

Hi Raymond, I do not think Ignite supports iterating other metadata but you could minimise IO by: - collocated processing (analyse entries locally without sending them over the network) - working with binary object representation directly (without serialisation/deserialisation) You c

Re: class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to find SQL table for type:

Hi, make sure you registered key and values types with the SQL engine using CacheConfiguration#setIndexedTypes(keyClass, UserAppInfo.class)

Ignite .NET - Delete statement

Hello,I try to delete some records according to the DELETE statement (see below). Unfortunately, I got every time an exception (see the attached file). Exception.txt Do you have an idea about the origin of this issue ?Here

Locking rows within Ignite Transactions

Hi I'm using Ignite Transactions(Ignite Version 2.1.0 and *TransactionConcurrency.PESSIMISTIC,TransactionIsolation.REPEATABLE_READ*") and after starting a transaction I need to lock certain rows. According to Ignite 2.1.0 Documentation *"Explicit locks are not transactional and cannot not be use

Re: Java's DelayQueue as distributed data structure?

Hi Slava, I've filed the feature request in JIRA (https://issues.apache.org/jira/browse/IGNITE-7098) Thanks again, Teun Hoogendoorn -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

index about jdbc thin mode

Hi, I got a strange thing. I execute a query with JDBC thin mode. But the performance and explain is very strange. The SQL is : SELECT FID,FNUMBER FROM "customerCache".CustomerIgniteInfo WHERE FUSEDSTATUS = 3 and explain is: SELECT __Z0.FID AS __C0_0, __Z0.F

"HandshakeException: Remote node ID is not as expected" occurs when tested with 1000 clients

I setup one ignite server node, and registered one service instance. And then, I call the service function from 1000 tasks(threads) distributed on 100 different machines (spark app). The problem is that tcp connections between ignite server and clients are unstable. At the early stage of this job,