Re: client reconnect working?

I tried non-zero values many times and the result is the same. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

client reconnect working?

Hi, We have a bunch of ignite nodes in the client mode (NOT the thin clients), that are connected to a 2 node ignite cluster. These clients stay connected indefinitely unless there is a failure of some sort. So every once in a while, sometime a few hours or even days, the client loses the

updating a composite Key in Ignite SQL Table

Hi, We know, currently, a composite key cannot be updated in a SQL table. What would be useful is if an update to a composite key, does not cause a conflict with other keys, then it should be allowed however, if the update causes a duplicate, an exception should be thrown Could this feature

Re: loading a cache into memory after startup

I don't know if I even want to call an api to warm up memory. I am thinking, we could have a setting like the below in config xml, this is userfriendly and intention of the config file is very clear. Bottomline: if ignite is used more often from disk, then it loses its value from a performance

Re: Ignite client connection from windows machine - UNRELIANCE

serverlogs.serverlogs Attached. There is not much info there, but maybe you can see something here... Also, by the way, if I reboot the ignite cluster (which I don't want to), ignite clients from windows and

Ignite client connection from windows machine - UNRELIANCE

Hi, In our office, we have client nodes started on windows and Linux machines. we see that client nodes on linux always happen to connect to Ignite cluster properly However, once in a while *ALL* windows machines fail to connect Below is the log on of the windows machines. Any clue ?

loading a cache into memory after startup

Hi, After Ignite cluster (w. data, assuming about 50GB of data) starts up we are experiencing significant delays before data is accessible. Understandably, ignite is bringing data from backup on disk into memory based on query. is there a way, where we as much data as possible from backup

Re: apache ignite in client mode - memory leak?

This doesn't look like a ignite memory optimization. A steady consumption of 20MB till it exhausts the memory allocated via -XMX, followed by a GC, is continuously happening. Doesn't feel like you should ignore it, unless ignite has a good reason behind it. Moreover, this is happening on a node,

Re: apache ignite in client mode - memory leak?

>>What happens if you trigger garbage collection? It frees up some amount of memory then continues to increase (as shown in earlier message) Haven't taken GC logs. is there a quick way to take these? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

apache ignite in client mode - memory leak?

Hi, When Ignite is in client mode, it constantly seems to consume 20MB. See the below metric, ignite spews out. Please explain. Metrics for local node (to disable set 'metricsLogFrequency' to 0) ^-- Node [id=dba51c3c, uptime=00:56:00.345] ^-- H/N/C [hosts=5, nodes=6, CPUs=40] ^--

Ignite in client Mode: outofMemory error with TCP discovery

Hi, Whenever, a client loses connection with ignite cluster, it throws out an OutOfMemory error. Can you please see if you can explain this behavior? The ignite client had 1G memory set on XMS and XMX... and a very few clients active. Now it is quite possible that ignite clients lose

Ignite Node failure - null pointer exception

Hi, Can you please look at the log and see if this is a known ignite bug? It is a null pointer exception in tcp discovery. regards mahesh igniteCrashLog.igniteCrashLog -- Sent from:

accessing a file on IGFS via HTTP

is it possible to access a file on IGFS via http interface on the cluster? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

exporting ignite table into CSV file

hi can we use a SQL query to export data from an Ignite table into a CSV file? thanks Mahesh -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

IgniteCache.destroy does not remove its data from work folder

hi, After deleting caches using the IgniteCache.destroy api, the data folder of the cache still remains in work/db... why is this not getting removed? Specifically, I ask because after running ML trainers etc, a new dataset is getting left over in work/db folder This dataset is tagged with a

Re: Ignite SQL : Index on primary Key

But we faced index does not exist exception, when joining with a primary key into another table on Ignite 2.7.0. regards Mahesh -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Ignite SQL : Index on primary Key

looks like a index is not not created automatically on a primary key... Shouldn't it be automatic? faced exceptions while trying to execute join. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: 2.7.0 ML: blas NoClassDefFoundError exception

Hi, My understanding till date is that we need to move ignite-ml FOLDER from optional into libs. anyways, I also moved JARS straight away "libs/optional/ignite-ml/*.jar" into "libs". core1.1.2.jar, which seems to have the BLAS class also exists. I still get the same error.. Caused by:

2.7.0 ML: Random Forest : NodeId exception

Hi, When we tested RandomForest, we get the below exception? What is this exception? What are we missing? ___ Caused by: class org.apache.ignite.IgniteCheckedException: Failed to serialize object: IgniteBiTuple [val1=0, val2=1] at

2.7.0 ML: blas NoClassDefFoundError exception

Hi, How do I need to install BLAS libraries on Server node side? Should I just place then in libs folder? THe below error occurs when I run the test examples. Caused by: java.lang.NoClassDefFoundError: org/netlib/blas/Dnrm2 at com.github.fommil.netlib.F2jBLAS.dnrm2(F2jBLAS.java:121)

ML: 2.8.0-SNAPSHOT - Master Branch - SQLFeatureLabelExtractor class not found

Hi, we moved to master to checkout on the SQLDataSet features Ran the example, DecisionTreeClassificationTrainerSQLTableExample.java However, I get SQLFeatureLabelExtractor class not cound exception. I check on the server that the JARS in ML are resent on the server side libs folder.

Re: IGNITE-3180 : please add support for median, stddev, var in Ignite SQL

SQL. Two usecases - Big, Data, visualizations with databases, and sheets that shows large tables, where is sure wants to get some quick metric Variance and STDDev is should be good... ML side Dataset class already exposes these right ?... We are okay there for now. -- Sent from:

Re: client side for master

Yes. That worked. Thanks. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: client side for master

the pom file in the examples, shows how it works. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

client side for master

Hi, I am want to use master to get some fixes onto on 2.7when I build master, i get someting like apache-ignite-2.8.0-SNAPSHOT-bin What should be the compatible master side? Should I continue working with 2.7 client side. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Default Cache template

It works. it isn't in your documentation though. https://apacheignite.readme.io/docs/cache-template -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: IGNITE-3180 : please add support for median, stddev, var in Ignite SQL

The simple usecase is as follows In big data visualization, for drawing graphs, one needs to know the standard characteristics of a measure column (numeric column) to draw and plan out graphs. ideally, we need to this support in Ignite itself so that client code does not pull large columns

IGNITE-3180 : please add support for median, stddev, var in Ignite SQL

Looks like these are not supported currently, please add them in Ignite 2.8 -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES

On further debug, we realised we set index inline option to 2048..while creating index. This problem (LOCK_RETRIES issue) started only after that. Before, that we didn't face much of a problem with indexes. Also, another notable observation is setting index inline option to 2048 also made the

Re: Default Cache template

Hi, I added the below, in node config.xml file. However, SQL table create from client side keep complaining that "SQLTABLE_TEMPLATE" template is not found. The only way this works is from Java code, when I use the

GridCachePartitionExchangeManager Null pointer exception

We got this null pointer exception and the nodes rebooted. Attached are the logs. GridCachePartitionExchanger.GridCachePartitionExchanger -- Sent from:

Re: failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES

We actually think while building index, the tree is getting corrupted. Increasing LOCK_RETRIES didnt fix it too... Please review the below link as well. Infact, we saw creating index was getting into a infinite loop and throwing out errors at other clients.

processDynamicIndexChange exception at client node while creating index

The client connection through exceptions shown in the log. During this time, we have another program creating index on a column. please review client_error.log -- Sent from:

RE: failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES

Increasing the size of IGNITE_BPLUS_TREE_LOCK_RETRIES makes the issue go away. But the explanation that is occurs due to contention is somewhat not clear. In all cases, in occurred to be when I was creating an index. Feels like it is somehow related to the height of the tree... and this

Re: DatasetFactory.createSimpleDataset with a cache

that would be awesome -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: DatasetFactory.createSimpleDataset with a cache

classification and clustering Importantly, critical for us to ensure, we have all the hooks to write our algorithms from datasets. Will provide more feedback in the next 1-2 months. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: DatasetFactory.createSimpleDataset with a cache

Yes. Yuri. Got it. We will wait for 2.8 release. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: DatasetFactory.createSimpleDataset with a cache

In other words, for ML functions, can I use IgniteBiFunction with Key and Value as *BinaryObject*, and at the same time KEY_TYPE and VALUE_TYPE is not specified while creating the SQL table cache? Unfortunately, in our product, we have data in SQL tables, and from these we intend to create

DatasetFactory.createSimpleDataset with a cache

Hi, I am trying to create a dataset with a SQL table Cache as follows The sql table was created as follows CREATE TABLE Person_Table_Test (id LONG, name VARCHAR(64), cityId DOUBLE, country VARCHAR(64), pinCode LONG, age LONG, date DATE, time TIMESTAMP, PRIMARY KEY (id)) WITH

Re: Creating Dataset classNotFound exception

also, in this function, if tableCache is a sql tableCache, will IgniteBiFunction is correctly executed try { dataSet = DatasetFactory.createSimpleDataset(ignite, tableCache, extractor); } catch (Exception e) { e.printStackTrace(); } -- Sent from:

Re: Creating Dataset classNotFound exception

For the moment, I moved my class to server - libs folder The test program didnt run successfully, but does these errors mean, I am missing something on server side and would that be fatal [03:18:28,156][WARNING][pub-#74][BLAS] Failed to load implementation from:

Re: Creating Dataset classNotFound exception

I have enabled peer class loading all my clients and servers. Should I be pulling IgniteBiFunction into a separate class and try? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Creating Dataset classNotFound exception

Hi I have a very simple program to create a DataSet to see if we can migrate to Ignite ML. Strangely on the server logs, why would I get a CreateMLDataSet Class Not found exception? public class CreateMLDataSet { public static void main(String[] args) throws Exception {

RE: Baselined node rejoining crashes other baseline nodes - Duplicate KeyError

Stan, thanks for the visibility. -1- Over the last year, we move from various versions of ignite 2.4, 2.5 to 2.7. I always keep work folder in tact. -2- Over a period of development, we might have tried to create index a second or many times on the same column on which an index already existed.

RE: failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES

OK. We don't have 1000 users for causing any sort of concurrency related lock ups. So possible explanation is corruption of the tree, below is our scenario -a- We created a table with sql - in the create params KEY_TYPE= ".", VALUE_TYPE="..." are also set. The intention is to retrieve

RE: failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES

how do I set it ? should I boot ignite node (ignite.sh) with the following switch ? java ... -DIGNITE_BPLUS_TREE_LOCK_RETRIES=10 regards Mahesh -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES

On 2.7, we are regularly seeing the below message and then the nodes stop. [16:45:04,759][SEVERE][disco-event-worker-#63][] JVM will be halted immediately due to the failure: [failureCtx=FailureContext [type=CRITICAL_ERROR, err=class o.a.i.IgniteCheckedException: Maximum number of retries 1000

Baselined node rejoining crashes other baseline nodes - Duplicate Key Error

I have two nodes on which we have 3 tables which are partitioned. Index are also built on these tables. For 24 hours caches work fine. The tables are definitely distributed across both the nodes Node 2 reboots due to some issue - goes out of the baseline - comes back and joins the baseline.