Re: client reconnect working?

[mahesh76private]

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?

[mahesh76private]

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 connection and attempts to reconnect. If this reconnect is not
proper, then we continuously see an attempt by this client to reconnect
indefinitely. See serverlogs file (attached)

Is ignite client reconnect working properly? If the client fails to
reconnect after a few attempts for whatever reason, I would expect the
client to fail after a few attempts and not bother the ignite cluster.
However, this does not happen. The reconnection keeps going on forever. 
If I reboot the client, then the client successfully connects again, which
means reconnection is not successful. 


I also attaching server logs and server node config and client node config
for more information. 

logs-config-2.zip
  





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

updating a composite Key in Ignite SQL Table

[mahesh76private]

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 be supported in future?

regards






--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: loading a cache into memory after startup

[mahesh76private]

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 standpoint
So, this option (warmupOnStart)  seems mandatory.  








 **







--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite client connection from windows machine - UNRELIANCE

[mahesh76private]

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 Linux will start connecting without a
problem. 
Right now, we have only clients from linux connecting fine and clients on
windows fail. 

regards
Mahesh



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Ignite client connection from windows machine - UNRELIANCE

[mahesh76private]

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 ?


[15:05:34,795][INFO][main][IgniteKernal] Config URL: n/a
[15:05:34,813][INFO][main][IgniteKernal] IgniteConfiguration
[igniteInstanceName=null, pubPoolSize=8, svcPoolSize=7, callbackPoolSize=8,
stripedPoolSize=8, sysPoolSize=8, mgmtPoolSize=4, igfsPoolSize=8,
dataStreamerPoolSize=8, utilityCachePoolSize=8,
utilityCacheKeepAliveTime=6, p2pPoolSize=2, qryPoolSize=8,
igniteHome=C:\Users\mahes\Desktop\apache\apache-ignite-2.7.0-bin\apache-ignite-2.7.0-bin,
igniteWorkDir=C:\Users\mahes\Desktop\apache\apache-ignite-2.7.0-bin\apache-ignite-2.7.0-bin\work,
mbeanSrv=com.sun.jmx.mbeanserver.JmxMBeanServer@769e7ee8,
nodeId=7d9f28d2-69db-49b5-9c20-219523108114, marsh=BinaryMarshaller [],
marshLocJobs=false, daemon=false, p2pEnabled=true, netTimeout=1,
sndRetryDelay=1000, sndRetryCnt=3, metricsHistSize=1,
metricsUpdateFreq=2000, metricsExpTime=9223372036854775807,
discoSpi=TcpDiscoverySpi [addrRslvr=null, sockTimeout=5, ackTimeout=0,
marsh=null, reconCnt=10, reconDelay=2000, maxAckTimeout=60,
forceSrvMode=false, clientReconnectDisabled=false, internalLsnr=null],
segPlc=STOP, segResolveAttempts=2, waitForSegOnStart=true,
allResolversPassReq=true, segChkFreq=1, commSpi=TcpCommunicationSpi
[connectGate=null,
connPlc=org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$FirstConnectionPolicy@1fa121e2,
enableForcibleNodeKill=false, enableTroubleshootingLog=false,
locAddr=192.168.1.156, locHost=null, locPort=47100, locPortRange=100,
shmemPort=-1, directBuf=true, directSndBuf=false, idleConnTimeout=60,
connTimeout=5000, maxConnTimeout=60, reconCnt=10, sockSndBuf=32768,
sockRcvBuf=32768, msgQueueLimit=0, slowClientQueueLimit=0, nioSrvr=null,
shmemSrv=null, usePairedConnections=false, connectionsPerNode=1,
tcpNoDelay=true, filterReachableAddresses=false, ackSndThreshold=32,
unackedMsgsBufSize=0, sockWriteTimeout=4, boundTcpPort=-1,
boundTcpShmemPort=-1, selectorsCnt=1, selectorSpins=0, addrRslvr=null,
ctxInitLatch=java.util.concurrent.CountDownLatch@7eac9008[Count = 1],
stopping=false],
evtSpi=org.apache.ignite.spi.eventstorage.NoopEventStorageSpi@4116aac9,
colSpi=NoopCollisionSpi [], deploySpi=LocalDeploymentSpi [],
indexingSpi=org.apache.ignite.spi.indexing.noop.NoopIndexingSpi@15de0b3c,
addrRslvr=null,
encryptionSpi=org.apache.ignite.spi.encryption.noop.NoopEncryptionSpi@489115ef,
clientMode=true, rebalanceThreadPoolSize=1, txCfg=TransactionConfiguration
[txSerEnabled=false, dfltIsolation=REPEATABLE_READ,
dfltConcurrency=PESSIMISTIC, dfltTxTimeout=0,
txTimeoutOnPartitionMapExchange=0, pessimisticTxLogSize=0,
pessimisticTxLogLinger=1, tmLookupClsName=null, txManagerFactory=null,
useJtaSync=false], cacheSanityCheckEnabled=true, discoStartupDelay=6,
deployMode=SHARED, p2pMissedCacheSize=100, locHost=null,
timeSrvPortBase=31100, timeSrvPortRange=100, failureDetectionTimeout=1,
sysWorkerBlockedTimeout=360, clientFailureDetectionTimeout=3,
metricsLogFreq=6, hadoopCfg=null, connectorCfg=ConnectorConfiguration
[jettyPath=null, host=null, port=11211, noDelay=true, directBuf=false,
sndBufSize=32768, rcvBufSize=32768, idleQryCurTimeout=60,
idleQryCurCheckFreq=6, sndQueueLimit=0, selectorCnt=4, idleTimeout=7000,
sslEnabled=false, sslClientAuth=false, sslCtxFactory=null, sslFactory=null,
portRange=100, threadPoolSize=8, msgInterceptor=null], odbcCfg=null,
warmupClos=null, atomicCfg=AtomicConfiguration [seqReserveSize=1000,
cacheMode=PARTITIONED, backups=1, aff=null, grpName=null], classLdr=null,
sslCtxFactory=null, platformCfg=null, binaryCfg=null, memCfg=null,
pstCfg=null, dsCfg=null, activeOnStart=true, autoActivation=true,
longQryWarnTimeout=3000, sqlConnCfg=null,
cliConnCfg=ClientConnectorConfiguration [host=null, port=10800,
portRange=100, sockSndBufSize=0, sockRcvBufSize=0, tcpNoDelay=true,
maxOpenCursorsPerConn=128, threadPoolSize=8, idleTimeout=0,
jdbcEnabled=true, odbcEnabled=true, thinCliEnabled=true, sslEnabled=false,
useIgniteSslCtxFactory=true, sslClientAuth=false, sslCtxFactory=null],
mvccVacuumThreadCnt=2, mvccVacuumFreq=5000, authEnabled=false,
failureHnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
super=AbstractFailureHandler [ignoredFailureTypes=[]]],
commFailureRslvr=null]
[15:05:34,819][INFO][main][IgniteKernal] Daemon mode: off
[15:05:34,819][INFO][main][IgniteKernal] OS: Windows 10 10.0 amd64
[15:05:34,819][INFO][main][IgniteKernal] OS user: mahes
[15:05:34,826][INFO][main][IgniteKernal] PID: 10608
[15:05:34,826][INFO][main][IgniteKernal] Language runtime: Java Platform API
Specification ver. 1.8
[15:05:34,826][INFO][main][IgniteKernal] VM information: Java(TM) SE Runtime
Environment 1.8.0_191-b12 Oracle Corporation Java HotSpot(TM) 64-Bit 

loading a cache into memory after startup

[mahesh76private]

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 (disk) into
memory (allocated in config XML, see below) at one shot after a cluster
start up?

*






*

Right now, data seems to come into memory based on queries. So when we have
large tables with say 12 million records, some of the queries wait for about
3-4 minutes...

regards







--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: apache ignite in client mode - memory leak?

[mahesh76private]

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, configured as a client. 

I will take GC logs

regards
mahesh







--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: apache ignite in client mode - memory leak?

[mahesh76private]

>>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?

[mahesh76private]

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]
^-- CPU [cur=0.23%, avg=0.65%, GC=0%]
^-- PageMemory [pages=0]
^-- Heap [used=*1755MB*, free=57.14%, comm=1824MB]
^-- Off-heap [used=0MB, free=-1%, comm=0MB]
^-- Outbound messages queue [size=0]
^-- Public thread pool [active=0, idle=0, qSize=0]
^-- System thread pool [active=0, idle=0, qSize=0]
2019-05-23 15:22:06.886  INFO 33 --- [eout-worker-#23]
org.apache.ignite.internal.IgniteKernal  : 
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
^-- Node [id=dba51c3c, uptime=00:57:00.348]
^-- H/N/C [hosts=5, nodes=6, CPUs=40]
^-- CPU [cur=0.27%, avg=0.64%, GC=0%]
^-- PageMemory [pages=0]
^-- Heap [used=*1774MB*, free=56.68%, comm=1824MB]
^-- Off-heap [used=0MB, free=-1%, comm=0MB]
^-- Outbound messages queue [size=0]
^-- Public thread pool [active=0, idle=0, qSize=0]
^-- System thread pool [active=0, idle=0, qSize=0]
2019-05-23 15:23:07.019  INFO 33 --- [eout-worker-#23]
org.apache.ignite.internal.IgniteKernal  : 
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
^-- Node [id=dba51c3c, uptime=00:58:00.350]
^-- H/N/C [hosts=5, nodes=6, CPUs=40]
^-- CPU [cur=0.23%, avg=0.63%, GC=0%]
^-- PageMemory [pages=0]
^-- Heap [used=*1793MB*, free=56.21%, comm=1824MB]
^-- Off-heap [used=0MB, free=-1%, comm=0MB]
^-- Outbound messages queue [size=0]
^-- Public thread pool [active=0, idle=0, qSize=0]
^-- System thread pool [active=0, idle=0, qSize=0]




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Ignite in client Mode: outofMemory error with TCP discovery

[mahesh76private]

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 connection with ignite 
cluster frequently.

Any insights into the issue will be deeply appreciated.




15-05-2019 15:30:35.024 [jvm-pause-detector-worker] WARN
 org.apache.ignite.internal.IgniteKernal.warning - Possible too long
JVM pause: 5063 milliseconds.
15-05-2019 15:30:38.958 [jvm-pause-detector-worker] WARN
 org.apache.ignite.internal.IgniteKernal.warning - Possible too long
JVM pause: 3664 milliseconds.
15-05-2019 15:30:42.783 [jvm-pause-detector-worker] WARN
 org.apache.ignite.internal.IgniteKernal.warning - Possible too long
JVM pause: 3666 milliseconds.
15-05-2019 15:30:46.522 [jvm-pause-detector-worker] WARN
 org.apache.ignite.internal.IgniteKernal.warning - Possible too long
JVM pause: 3630 milliseconds.
15-05-2019 15:30:50.163 [exchange-worker-#38] WARN 
org.apache.ignite.internal.diagnostic.warning - Failed to wait for partition
map exchange [topVer=AffinityTopologyVersion [topVer=751, minorTopVer=1],
node=604f46ce-3693-404c-b180-29b2b6dcf8ed]. Consider changing
TransactionConfiguration.txTimeoutOnPartitionMapSynchronization to non
default value to avoid this message. Dumping pending objects that might be
the cause: 
15-05-2019 15:30:50.163 [jvm-pause-detector-worker] WARN
 org.apache.ignite.internal.IgniteKernal.warning - Possible too long
JVM pause: 3591 milliseconds.
15-05-2019 15:30:50.163 [exchange-worker-#38] WARN 
org.apache.ignite.internal.diagnostic.warning - Ready affinity version:
AffinityTopologyVersion [topVer=751, minorTopVer=0]
15-05-2019 15:30:57.519 [jvm-pause-detector-worker] WARN
 org.apache.ignite.internal.IgniteKernal.warning - Possible too long
JVM pause: 3648 milliseconds.
15-05-2019 15:31:04.762 [jvm-pause-detector-worker] WARN
 org.apache.ignite.internal.IgniteKernal.warning - Possible too long
JVM pause: 7242 milliseconds.
15-05-2019 15:31:31.284 [jvm-pause-detector-worker] WARN
 org.apache.ignite.internal.IgniteKernal.warning - Possible too long
JVM pause: 22505 milliseconds.
15-05-2019 15:31:38.924 [jvm-pause-detector-worker] WARN
 org.apache.ignite.internal.IgniteKernal.warning - Possible too long
JVM pause: 11482 milliseconds.
15-05-2019 15:31:47.483 [grid-timeout-worker-#23] INFO
 org.apache.ignite.internal.IgniteKernal.info - 
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
^-- Node [id=604f46ce, uptime=05:40:44.720]
^-- H/N/C [hosts=7, nodes=7, CPUs=56]
^-- CPU [cur=100%, avg=0.63%, GC=30.2%]
^-- PageMemory [pages=0]
^-- Heap [used=2025MB, free=1.08%, comm=2048MB]
^-- Off-heap [used=0MB, free=-1%, comm=0MB]
^-- Outbound messages queue [size=0]
^-- Public thread pool [active=0, idle=0, qSize=0]
^-- System thread pool [active=1, idle=0, qSize=0]
15-05-2019 15:31:54.864 [tcp-client-disco-sock-writer-#2]
ERROR
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.error - Failed to send
message: null
java.io.IOException: Failed to get acknowledge for message:
TcpDiscoveryClientMetricsUpdateMessage [super=TcpDiscoveryAbstractMessage
[sndNodeId=null, id=1fe38eaba61-604f46ce-3693-404c-b180-29b2b6dcf8ed,
verifierNodeId=null, topVer=0, pendingIdx=0, failedNodes=null,
isClient=true]]
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$SocketWriter.body(ClientImpl.java:1398)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
Exception: java.lang.OutOfMemoryError thrown from the
UncaughtExceptionHandler in thread "TcpDiscoverySpi.timer"
Exception: java.lang.OutOfMemoryError thrown from the
UncaughtExceptionHandler in thread "ajp-nio-8009-ClientPoller-1"
Exception: java.lang.OutOfMemoryError thrown from the
UncaughtExceptionHandler in thread "Catalina-utility-1"
Exception: java.lang.OutOfMemoryError thrown from the
UncaughtExceptionHandler in thread "http-nio-8080-ClientPoller-1"
Exception: java.lang.OutOfMemoryError thrown from the
UncaughtExceptionHandler in thread "AsyncFileHandlerWriter-1259475182"
Exception: java.lang.OutOfMemoryError thrown from the
UncaughtExceptionHandler in thread "jvm-pause-detector-worker"
Exception: java.lang.OutOfMemoryError thrown from the
UncaughtExceptionHandler in thread "grid-nio-worker-tcp-comm-2-#26"
Exception: java.lang.OutOfMemoryError thrown from the
UncaughtExceptionHandler in thread "ajp-nio-8009-ClientPoller-0"
Exception: java.lang.OutOfMemoryError thrown from the
UncaughtExceptionHandler in thread "grid-nio-worker-client-listener-1-#30"
Exception: 

Ignite Node failure - null pointer exception

[mahesh76private]

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: http://apache-ignite-users.70518.x6.nabble.com/

accessing a file on IGFS via HTTP

[mahesh76private]

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

[mahesh76private]

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

[mahesh76private]

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 random UUID tag and so with every run creates
a new dataset. 
Sort of clutters up work/db folder. 

regards
Mahesh




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite SQL : Index on primary Key

[mahesh76private]

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

[mahesh76private]

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

[mahesh76private]

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: java.lang.NoClassDefFoundError: org/netlib/blas/Dnrm2
at com.github.fommil.netlib.F2jBLAS.dnrm2(F2jBLAS.java:121)
at
org.apache.ignite.ml.math.isolve.lsqr.LSQROnHeap.lambda$bnorm$7b55d622$1(LSQROnHeap.java:53)
at
org.apache.ignite.ml.dataset.Dataset.lambda$computeWithCtx$96d91738$1(Dataset.java:143)
at
org.apache.ignite.ml.dataset.impl.cache.CacheBasedDataset.lambda$computeWithCtx$62946a87$1(CacheBasedDataset.java:112)
at
org.apache.ignite.ml.dataset.impl.cache.util.ComputeUtils.lambda$affinityCallWithRetries$b46c4136$1(ComputeUtils.java:90)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1855)
at
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:568)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6816)
at
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:562)
... 11 more



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

2.7.0 ML: Random Forest : NodeId exception

[mahesh76private]

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
org.apache.ignite.internal.marshaller.optimized.OptimizedMarshaller.marshal0(OptimizedMarshaller.java:207)
at
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:58)
at
org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:10222)
at
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:196)
... 99 more
Caused by: java.io.IOException: Externalizable class doesn't have default
constructor: class org.apache.ignite.ml.tree.randomforest.data.NodeId
at
org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.(OptimizedClassDescriptor.java:408)
at
org.apache.ignite.internal.marshaller.optimized.OptimizedMarshallerUtils.classDescriptor(OptimizedMarshallerUtils.java:210)
at
org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(OptimizedObjectOutputStream.java:201)
at
org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObjectOverride(OptimizedObjectOutputStream.java:159)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344)
at
org.apache.ignite.internal.marshaller.optimized.OptimizedMarshaller.marshal0(OptimizedMarshaller.java:202)
... 102 more
Caused by: java.lang.NoSuchMethodException:
org.apache.ignite.ml.tree.randomforest.data.NodeId.()
at java.lang.Class.getConstructor0(Class.java:3082)
at java.lang.Class.getDeclaredConstructor(Class.java:2178)
at
org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.(OptimizedClassDescriptor.java:403)
... 107 more




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

2.7.0 ML: blas NoClassDefFoundError exception

[mahesh76private]

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)
at
org.apache.ignite.ml.math.isolve.lsqr.LSQROnHeap.lambda$bnorm$7b55d622$1(LSQROnHeap.java:53)
at
org.apache.ignite.ml.dataset.Dataset.lambda$computeWithCtx$96d91738$1(Dataset.java:143)
at
org.apache.ignite.ml.dataset.impl.cache.CacheBasedDataset.lambda$computeWithCtx$62946a87$1(CacheBasedDataset.java:112)
at
org.apache.ignite.ml.dataset.impl.cache.util.ComputeUtils.lambda$affinityCallWithRetries$b46c4136$1(ComputeUtils.java:90)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1855)
at
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:568)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6816)
at
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:562)
... 11 more



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

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

[mahesh76private]

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. 
The JAR has SQLFeatureLabelExtractor class in libs folder.

Any clue why this would still happen?







--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

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

[mahesh76private]

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: http://apache-ignite-users.70518.x6.nabble.com/

Re: client side for master

[mahesh76private]

Yes. That worked. Thanks.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: client side for master

[mahesh76private]

the pom file in the examples, shows how it works. 



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

client side for master

[mahesh76private]

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

[mahesh76private]

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

[mahesh76private]

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 (running in millions) to calculate the metric such as
var, std, median, etc





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

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

[mahesh76private]

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

[mahesh76private]

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 index huge, ran into 100s of Gig...

Anyway, we are not using this option anymore Frankly, it seems a
internal detail of ignite, and not sure why this is given as an option to
configure for users. 



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Default Cache template

[mahesh76private]

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
CacheConfiguration.addCacheConfiguration and register the template with the
cluster. 

My need is to set the template in node config xml and ensure it
automatically resisters the template and there should be no need to
explicitly set it. 

Please let me know, if I am doing something wrong.






--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

GridCachePartitionExchangeManager Null pointer exception

[mahesh76private]

We got this null pointer exception and the nodes rebooted. 

Attached are the logs. 
GridCachePartitionExchanger.GridCachePartitionExchanger

  





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES

[mahesh76private]

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. 


http://apache-ignite-users.70518.x6.nabble.com/processDynamicIndexChange-exception-at-client-node-while-creating-index-td26770.html

My suspicion is this issue happens only when table is partitioned, no
affinity keys, and definitely spread across multiple nodes. 

Please review the logs





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

processDynamicIndexChange exception at client node while creating index

[mahesh76private]

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: http://apache-ignite-users.70518.x6.nabble.com/

RE: failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES

[mahesh76private]

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 variable seems to
limit the height. 




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: DatasetFactory.createSimpleDataset with a cache

[mahesh76private]

that would be awesome




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: DatasetFactory.createSimpleDataset with a cache

[mahesh76private]

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

[mahesh76private]

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

[mahesh76private]

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 datasets and develop some ML functions with it. These SQL
tables are generated dynamically by users.





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

DatasetFactory.createSimpleDataset with a cache

[mahesh76private]

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 "template=SQLTABLE_CACHE_TEMPLATE , backups=2"

The dataset is created as follows
PersonTable type

 try {
  dataSet = DatasetFactory.createSimpleDataset(ignite, personTable, new
TableFeatureExtractor(features));
} catch (Exception e) {
  e.printStackTrace();
}

TableFeatureExtractor is as follows

public class TableFeatureExtractor implements IgniteBiFunction {

  @Override
  public Vector apply(BinaryObject k, BinaryObject v) {
  }
}


The dataset seems to be created from logs, but all its operations always
return null.

Quesiton: is this model of creating a dataset supported in Ignite 2.7?

regards
Mahesh




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Creating Dataset classNotFound exception

[mahesh76private]

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: http://apache-ignite-users.70518.x6.nabble.com/

Re: Creating Dataset classNotFound exception

[mahesh76private]

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:
com.github.fommil.netlib.NativeSystemBLAS
[03:18:28,156][WARNING][pub-#74][BLAS] Failed to load implementation from:
com.github.fommil.netlib.NativeRefBLAS



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Creating Dataset classNotFound exception

[mahesh76private]

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

[mahesh76private]

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 {

CacheConfiguration cacheCfg = new CacheConfiguration(tableName);
IgniteCache tableCache =
ignite.getOrCreateCache(cacheCfg).withKeepBinary();

IgniteBiFunction featureExtractor =
new IgniteBiFunction() {
  @Override
  public Vector apply(BinaryObject key, BinaryObject value) {
Integer val  = (Integer)value.field("quantity");
Vector vector = VectorUtils.of(val);
return vector;
  }
};

SimpleDataset dataSet = null;
try {
  dataSet = DatasetFactory.createSimpleDataset(ignite, tableCache,
featureExtractor);
} catch (Exception e) {
  e.printStackTrace();
}


// Calculation of the mean value.
double[] mean = dataSet.mean();
System.out.println("Mean \n\t" + Arrays.toString(mean));

// Calculation of the standard deviation.
double[] std = dataSet.std();
System.out.println("Standard deviation \n\t" + Arrays.toString(std));

// Calculation of the covariance matrix.
double[][] cov = dataSet.cov();
System.out.println("Covariance matrix ");
for (double[] row : cov)
  System.out.println("\t" + Arrays.toString(row));

// Calculation of the correlation matrix.
double[][] corr = dataSet.corr();
System.out.println("Correlation matrix ");
for (double[] row : corr) System.out.println("\t" +
Arrays.toString(row));
  }
}




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

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

[mahesh76private]

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. Now,
could that cause a confusion at ignite level, especially in a multi-node
scenario? Was something out of sync? Was a check missing?
-3-
Over a period of time, we dropped the table several times and recreated the
table several times and indexes. Was something stable left out in work
folder. We always used 2 or more nodes. 
-4-
Over a period of time, we saw issues with index creation as well. My
colleague posted another strange behaviour with index creation. See the
issue here,
http://apache-ignite-users.70518.x6.nabble.com/Failing-to-create-index-on-Ignite-table-column-td26252.html#a26258
Summary is if we don't give index names the ignite gives exceptions.
 

Something seems to be wrong with Ignite index handling in multi-node
environment. 

Regarding your point 2 (jira), absolutely, makes sense not to crash the node
on this exception. We have about 100GB data (tables) on ignite and the only
work around right now seems to be 

Boot node 1. Keep its work folder. 
Boot node 2 after removing its work folder

This scenario though works, gives the cluster a down-time of about 1-2 hours
and this is not acceptable for our customers. 



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES

[mahesh76private]

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 data inserted into SQL table via Key/Value API
for some ML code using ignite framework. 

-b-
Once the table is created, we created an index on primary key column. 
Question: is creating an index column on primary key required? Internally, I
assume you would create an index.

-c-
we started inserting rows into table via SQL insert. 

In this scenario, we got the LOCK_RETRIES  issue

Hope this gives you some clue as to why the issue occurred? Can you please
address the question in b)

regards
Mahesh
.




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES

[mahesh76private]

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

[mahesh76private]

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 reached for Put operation (the tree may be corrupted).
Increase IGNITE_BPLUS_TREE_LOCK_RETRIES system property if you regularly see
this message (current value is 1000).]]


Can you please through some light on what this error is?





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Baselined node rejoining crashes other baseline nodes - Duplicate Key Error

[mahesh76private]

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.  Other baseline nodes crash and in the logs we see
duplicate Key error

[10:38:35,437][INFO]tcp-disco-srvr-#2[TcpDiscoverySpi] TCP discovery
accepted incoming connection [rmtAddr=/192.168.1.7, rmtPort=45102]
[10:38:35,437][INFO]tcp-disco-srvr-#2[TcpDiscoverySpi] TCP discovery
spawning a new thread for connection [rmtAddr=/192.168.1.7, rmtPort=45102]
[10:38:35,437][INFO]tcp-disco-sock-reader-#12[TcpDiscoverySpi] Started
serving remote node connection [rmtAddr=/192.168.1.7:45102, rmtPort=45102]
[10:38:35,451][INFO]tcp-disco-sock-reader-#12[TcpDiscoverySpi] Finished
serving remote node connection [rmtAddr=/192.168.1.7:45102, rmtPort=45102
[10:38:35,457][SEVERE]tcp-disco-msg-worker-#3[TcpDiscoverySpi]
TcpDiscoverSpi's message worker thread failed abnormally. Stopping the node
in order to prevent cluster wide instability.
*java.lang.IllegalStateException: Duplicate key
at org.apache.ignite.cache.QueryEntity.checkIndexes(QueryEntity.java:223)
at org.apache.ignite.cache.QueryEntity.makePatch(QueryEntity.java:174)*


Logs and confurations are attached here 
https://issues.apache.org/jira/browse/IGNITE-8728
 
please offer any suggestions 



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/