Re: Native persistence - No space left on device error

Keep an eye on the storage usage metrics to avoid such incidents proactively in production: https://www.gridgain.com/docs/tutorials/management-monitoring/ignite-storage-monitoring#track-disk-storage-size - Denis On Wed, Nov 18, 2020 at 7:41 AM Ilya Kasnacheev wrote: > Hello! > > When you run

Re: Nodes failed to join the cluster after restarting

Hi, I attach the log from the only working node while two others are restarted. There is no error message other than the "failed to join" message. I do not see any clue in the log. I cannot reproduce this issue either. That's why I am asking about the code. Maybe you know certain suspicious

Apache Ignite Clientside NearCache and Serverside Eviction blocking cluster

Hi All, We have recently enabled Eviction on Ignite server nodes. We were using ignite nearcache for ignite client nodes. Due to nearcache, the server side cache-entries are not getting evicted. Eventually this leads to off-cache full, and "Too many attempts to evict data page" error and ignite

Re: Javamelody starting an Apache Ignite server node!

Hello! Have you seen https://github.com/javamelody/javamelody/issues/858 ? Regards, -- Ilya Kasnacheev ср, 18 нояб. 2020 г. в 22:14, David Tinker : > https://github.com/javamelody/javamelody/issues/962 > > "I am using the Apache Ignite thin client ( >

Javamelody starting an Apache Ignite server node!

https://github.com/javamelody/javamelody/issues/962 "I am using the Apache Ignite thin client ( https://ignite.apache.org/docs/latest/thin-clients/java-thin-client). Somehow after my app has been running for a few minutes an Ignite server node suddenly starts up! This happens on a "javamelody"

RE: Failed to prepare update plan error while inserting data, when select is used aong with insert

Hi Alexandar, Sorry my bad. I just realized that the primary key is missed while inserting. Thanks for your response and help Thanks. Harinath -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Failed to prepare update plan error while inserting data, when select is used aong with insert

Hi, That’s odd, could you please share the logs with  the error?   From: harinathSent: Wednesday, November 18, 2020 6:52 PMTo: user@ignite.apache.orgSubject: RE: Failed to prepare update plan error while inserting data, when select is used aong with insert Hi Alexandar, I have tried without

Re: C# SQL API on key-value entries in cache error

Hello, The correct query would be "SELECT AssociateID FROM Associate", because Ignite infers table name from the class name, and column names from property names. You can override table name with QueryEntity.TableName property, and column names with QuerySqlFieldAttribute.Name property. On Wed,

RE: Failed to prepare update plan error while inserting data, when select is used aong with insert

Hi Alexandar, I have tried without parentheses, still i see the same error Thanks, Harinath -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Native persistence - No space left on device error

Hello! When you run out of disk space, the Ignite node will stop functioning normally, and your underlying PDS storage may become corrupted as well. Thus it is recommended to avoid running out of disk space. This is not in any means a normal mode of operation of Apache Ignite. Regards, -- Ilya

C# SQL API on key-value entries in cache error

Hello, I ran into some errors trying to use Apache Ignite's SQL API, specifically the @QueryAnnotation and executing a query . Right now, I start a

Native persistence - No space left on device error

What is the expected behavior of native persistence when there is no more space on disk? I'm getting this error when I reach the max size of the mounted volume (storage, not wal): *class org.apache.ignite.IgniteCheckedException: No space left on device* I assumed, that when there is no more

Re: not in, not exists sql result is not correct

Hello! This looks like a query where the result is only correct if the data in orders and accounts are collocated. If they are not, you may check it by setting distributedJoins=true connection property and re-running the query. Please see

RE: Failed to prepare update plan error while inserting data, when select is used aong with insert

Hi,  Seems like there is a syntax error and Apache Ignite failed to produce an execution plan Could you try to run it without the parentheses? Like: INSERT INTO desttable (name, lastname, age) SELECT name, lastname, age from srctable  From: Alexandr ShapkinSent: Wednesday, November 18, 2020 5:10

RE: Failed to prepare update plan error while inserting data, when select is used aong with insert

Hi, Seems like there is a syntax error. From: harinathSent: Wednesday, November 18, 2020 10:28 AMTo: user@ignite.apache.orgSubject: Failed to prepare update plan error while inserting data, when select is used aong with insert Hi, Using ignite thick client, i'm trying to copy data from one

Re: Java VM Parameters setting through cpp api

Yes, it is possible. See [1] [1] - https://ignite.apache.org/releases/latest/cppdoc/structignite_1_1IgniteConfiguration.html#ad7f632214a786dfdf8dc6f5824749e8a Best Regards, Igor On Wed, Nov 18, 2020 at 3:18 PM Wolfgang Meyerle < wolfgang.meye...@googlemail.com> wrote: > Hi, > > Is it possible

Java VM Parameters setting through cpp api

Hi, Is it possible somehow to define specific Java VM Parameters through the cpp interfacte or the xml configuration files. I'm facing serious sys-stripe timeouts and one recommendation of Ignite is to switch to IPv4 only. Unfortunately this is an Java VM Parameter which I do not seem to

Re: What is considered high IO wait and partition exchange fiallure?

Hello John, Can you share the full log and cluster configuration? For instance, the cluster may fail the node due to unresponsive socket request if this node had long GC pauses due to high load. > Does this mean this node was also the master? Not sure I've got your question. Do you mean the