Re: Ignite does not perform as expected

Sorry for my poor English, I mean only use devId as my index, and I have found the solution in ignite documents. I can force ignite use devId as index according to *USE INDEX* -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite does not perform as expected

What do you mean? Only one index can be used for table for a one query. If you want to filter by 2 fields, you have to create group index. пн, 7 янв. 2019 г. в 17:38, Justin Ji : > Thank for your reply. > > How can I use devId as my index when only one index can be used for one > table > > > > --

Re: Ignite does not perform as expected

Thank for your reply. How can I use devId as my index when only one index can be used for one table -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite does not perform as expected

Thank for your reply. How can I use devId as my index when only one index can be used for one table -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: nodes getting disconnected from cluster

Hi, Can you share logs from all nodes, especially from node qagmscore02/ 10.114.113.53:47500 ? Evgenii пн, 7 янв. 2019 г. в 08:14, Akash Shinde : > Hi, > Someone could please help me on this issue. > > Thanks, > Akash > > On Thu, Jan 3, 2019 at 5:46 PM Akash Shinde wrote: > >> Hi, >> >> I am g

Re: Ignite does not perform as expected

Ignite can use only one index per table, so, you probably need to create a group index: https://apacheignite-sql.readme.io/docs/schema-and-indexes#section-group-indexes Evgenii пн, 7 янв. 2019 г. в 06:47, Justin Ji : > when I run a SQL query with the two indexes, but ignite does not perform as >

Does Ignite message support C++?

I have an ignite cluster that running on Java, all nodes (Java) within the cluster can send and receive Ignite messages. Now, I have to create another client node by C++, I am using Ignite 2.7, but seems that Ignite C++ does not supports Ignite messages, right? -- Sent from: http://apache-ignit

Again Failed to get page IO instance

Hi, we have ran ignite 2.6.0, and have 8 server in our base line topology. After we bounce the severs, our client starts writing update using invoke method, but we get error Caused by: java.lang.IllegalStateException: Item not found: 9 at org.apache.ignite.internal.processors.cache.persis

Re: How to debug network issues in cluster

As an Ignite user, here are my two cents: - if you were never able to get the node to join the cluster, check that there are no firewalls/rules blocking the Ignite ports (telnet might be a quick way to do that) - check that the IPs printed by TcpDiscoverySpi are the correct ones; if you have virtu

Re: JDK 11 support

I can run it in 2.6 by adding these to the JVM arguments: --add-exports=java.base/jdk.internal.misc=ALL-UNNAMED --add-exports=java.base/sun.nio.ch=ALL-UNNAMED I haven't had a chance to try with 2.7 yet, I would have expected it to work without these, though. Is this going to be addressed in 2.8, m

Re: nodes getting disconnected from cluster

Hi, Someone could please help me on this issue. Thanks, Akash On Thu, Jan 3, 2019 at 5:46 PM Akash Shinde wrote: > Hi, > > I am getting " Timed out waiting for message delivery receipt" WARN > message in my logs. > But I am sure that it is not happening because of long GC pause. I have > check

After upgrading 2.7 getting Unexpected error occurred during unmarshalling

Hi, When execute affinity.partition(key), I am getting following exception on Ignite 2.7. Stacktrace: 2019-01-07 21:23:03,093 6699878 [mgmt-#67%springDataNode%] ERROR o.a.i.i.p.task.GridTaskWorker - Error deserializing job response: GridJobExecuteResponse [nodeId=c0c832cb-33b0-4139-b11d-5cafab2

Ignite does not perform as expected

when I run a SQL query with the two indexes, but ignite does not perform as expected, it only uses dpId does not use devId, I explain the SQL: SELECT __Z0.ID AS __C0_0, __Z0.GMTCREATE AS __C0_1, __Z0.GMTMODIFIED AS __C0_2, __Z0.DEVID AS __C0_3, __Z0.DPID AS __C0_4, __Z0.COD

Re: JDK 11 support

I am running Ignite 2.7 on JDK 11 but getting following error - c:\apache-ignite-2.7.0-bin\bin>ignite.bat WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.apache.ignite.internal.util.GridUnsafe$2 (file:/C:/apache-ignite-2.7.0-bin/libs/ignite-c

backup mode

hello. is it posible to change backup from 0 to 1 in existing cache?

Re: Failing to create index on Ignite table column

Hi, Is there any way to check the list of column names on which index has been created for a particular table? Regards, Shravya Nethula. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Failing to create index on Ignite table column

Hi, We are using Ignite 2.7.0 version. Yes this issue is coming up each time I try to create a new table and create indexes on some columns of the table. The creation of indexes code occurs just after the table creation code. The table is successfully created and indexes are created successfully

Re: Do elements with EternalExpiryPolicy in cache ever get evicted?

Hi, Does anyone know the answer to this? Thanks! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: SQL performance very slow compared to KV in pure-in-memory cache?

Thanks Naveen. I am definitely not looking for better performance in SQL than KV store. But just wanted to know if the results im getting in scale of 1:4 performance between SQL and KV store is as expected or not, say a particular operations give 400k ops in KV but same size records with same oper

Re: Ignite Plugin development ...

Hi, in this examples you have either WhiteListNullPlugin or WhiteListAuthenticator @Override public IgnitePlugin plugin() { System.out.println("new plugin"); return new WhiteListNullPlugin(); } @Override public IgnitePlugin plugin() { return ne

Re: Failing to create index on Ignite table column

Hi! It does look very strange because it has null value for the index name, and it looks like it does a "x = map.put( indexname, entry)" in the code and if x is not null (index already exists) you will get that exception, but if the name of the index is null it's a bit strange that the map re