Re: Node requires maintenance, non-empty set of maintainance tasks is found - node is not coming up

In the end, one option might be to replace the faulty machine with a brand > new one. > In cloud environments this is actually quite cheap and easy to do. > > Cheers > Gianluca > > On Wed, 29 May 2024 at 08:43, Naveen Kumar > wrote: > >> Hello All >> >

Node requires maintenance, non-empty set of maintainance tasks is found - node is not coming up

Hello All We are using Ignite 2.13.0 After a cluster restart, one of the node is not coming up and in node logs are seeing this error - Node requires maintenance, non-empty set of maintainance tasks is found - node is not coming up we are getting errors like time out is reached before computati

Re: BinaryObjectException

wrote: > Hello! > > Most probably it's related to ticket [1] that is fixed in 2.9 release. > > [1]: https://issues.apache.org/jira/browse/IGNITE-13192 > > пн, 22 нояб. 2021 г. в 03:11, Naveen Kumar : > >> Hi All >> >> We are using 2.8.1 >>

BinaryObjectException

Hi All We are using 2.8.1 At times, we do get this BinaryObjectException while calling GETs thru thin client, we dont see any errors or exceptions on node logs, this only be seen on the cline tside. what could be the potential reason for this Attached the exact error message Thanks -- Thank

Re: Re[2]: apache ignite 2.10.0 heap starvation

heap dump generation does not seems to be working. whenever I tried to generate the heap dump, node is going down, bit strange, what else we could analyze On Tue, Oct 12, 2021 at 7:35 PM Zhenya Stanilovsky wrote: > hi, highly likely the problem in your code - cpu usage grow synchronously > with

Re: apache ignite 2.10.0 heap starvation

Good to hear from you , I have had the same issue for quite a long time and am still looking for a fix. What do you think has exactly resolved the heap starvation issue, is it the GC related configuration or the threadpool configuration. ? Default thread pool is the number of the cores of the ser

Re: apache ignite 2.10.0 heap starvation

Just to add what Ibrahim mentioned, I also have a similar issue but I am using 2.8.1 and we do have a good number of Insert/merge statements getting executed. We do get warnings for some of the MERGE statements, like "*The search row by explicit key isn't supported. The primary key is always used t

Re: Partition states validation has filed for group: CUSTOMER_KV

Any pointers or clues on this issue. If it the issue with the source cluster or something to do with the target cluster ? Does the clean restart of the source cluster help here in any way, inconsistent partitions becoming consistent etc ? Thanks On Wed, Sep 8, 2021 at 12:12 PM Naveen Kumar

BinaryObjectException: Unsupported protocol version

Hi All We are using Ignite 2.8.1 and using the thin clients majorly. Facing a strange issues for last couple of days, all PUTs are working fine, but GETs are failing with a reason : BinaryObjectException: Unsupported protocol version. After the node restart, GETs started working fine, and dont se

subscribe

Please subscribe me -- Thanks & Regards, Naveen Bandaru

Re: SQL and backing cache question

This works, I could query the data. If we dont have POJOs and use binary objects to read and write, how can make rest API work. If I understand correctly, Java classes should be on classpath of the ignite node to work rest API. How can we make rest API work?? Also, instead of reading field by fiel

Re: SQL and backing cache question

I do have the same question. When we execute the DDL statement for creating the table thru SQLLINE with the value_type as some.package.MWorkPlan, does it create the java class with this name and load it into JVM. OR we need to create some.package.MWorkPlan class and refer while creating the table

Re: Data lose in query

Exactly, I have faced the same problem and posted this question to the forum, not yet got any response. Thanks On 12-Dec-2017 1:48 PM, "Ahmad Al-Masry" wrote: > Hi; > I added @AffinityKeyMapped to the fields in the model generated by web > console. > But I also noticed that when I load the data

Re: Cache store class not found exception

Please make sure class is on the server Ignite's CLASSPATH. OR You can just deploy the JAR to $IGNITE_HOME/libs/user direcgtory This should resolve On Mon, Dec 11, 2017 at 8:52 PM, Mikael wrote: > Hi! > > I have a cache in a server node that is using a custom cache store for a > JDBC database,

Re: Index not getting created

Hi Here is the node logs captured with -v option. [22:56:41,291][SEVERE][client-connector-#618%IgnitePOC%][JdbcRequestHandler] Failed to execute SQL query [reqId=0, req=JdbcQueryExecuteRequest [schemaName=PUBLIC, pageSize=1024, maxRows=0, sqlQry=CREATE INDEX idx_customer_accountId ON "Customer"

Re: Enabling REST api for a apache client node

My understanding with some other in-memory product is We have seeders and leeches, seeders are the one hold data and leeches are the one which are exposed to the clients, responsible for processing the incoming requests. Basis idea was to offload the connection/disconnection activities from the se

Index not getting created

AM using 2.3 What could be the issue with below create index command. : jdbc:ignite:thin://127.0.0.1> select * from "Customer".CUSTOMER where ACCOUNT_ID_LIST ='A10001'; ++++---