Re: HELLO WORLD GA EXAMPLE

In the terminal where I executed: user@PTFAssaultMachine:~/apache-ignite-fabric-2.6.0-bin/examples$ sudo mvn exec:java -Dexec.mainClass="org.apache.ignite.examples.ml.genetic.helloworld.HelloWorldGAExample" The loop displays this strange recurring output: ] [2018-11-30 02:00:23,494][INFO

Re: HELLO WORLD GA EXAMPLE

I did end up getting a node started by running the following command: user@PTFAssaultMachine:~/apache-ignite-fabric-2.6.0-bin$ bin/ignite.sh /home/user/apache-ignite-fabric-2.6.0-bin/examples/config/example-ignite.xml This started a node.. I then followed the instructions as provided in the

Re: HELLO WORLD GA EXAMPLE

Dear techbysample, there is no example-config.xml the only files that are in tat folder are example-ignite.xml, example-default.xml, example data-regions.xml, and example-chache. Which one of these .xml files should I use? I am running this in a debian-9 virtual machine inside qubes4.0 Linux,

Re: Gridgain Console monitoring question

Hi, Charu. The main reason is https://issues.apache.org/jira/browse/IGNITE-6677 In other words queries history will be collected only for thous queries that were executed with selected "Use selected cache as default schema name" checkbox. Once IGNITE-6677 will be fixed, you will see all

Re: Ignite benchmarking with YCSB

Hi Ilya, I have tried to set the following and rerun the same workload. But this time the performance got degraded from 56k Ops per YCSB to 47k Ops. PFA the thread dump with pairedconnection enabled: ycsb-1: ycsb1_dump1.ycsb1_dump1

Gridgain Console monitoring question

Hi, We are using open source Ignite and have configured the basic web console monitoring. However, we are unable to do the following : - Queries History - Explain plan of the queries. We can see the running queries. The parameter cacheConfiguration.queryDetailMetricsSize has

Re: HELLO WORLD GA EXAMPLE

AlphaMufasaOmega , Hello. How many nodes are running? Did you remember to start at least one standalone Ignite node BEFORE running the HelloWorld GA Example? I suspect from your logs that the node has stopped. That is why Zeppelin cannot connect to Ignite. Type the following to start a

HELLO WORLD GA EXAMPLE

Dear Apache Ignite Community, I was trying to run the Hello World example in Apache ignite Genetic Algorithm codes and I ran into the following error or code stack which seems to be preventing me from seeing the result in zeppelin after following the instructions

Re: ODBC driver build error

Thank you for the reply Igor, After adding legacy_stdio_definitions.lib in the linker's input, I built the ODBC driver successfully. I want to build ODBC driver myself because I want to apply this ticket to Ignite 2.6 because 2.7 is not yet released.

Fair queue polling policy?

Hello, My aim is a queue for load balancing that is described in the documentation : create an "ideally balanced system where every node only takes the number of jobs it can process, and not more."

Re: Speed Expectations for Ignite Queue

To answer my own question: the speed seems to be expected and lays in the same range like e.g. redis+redisson Peter Am 26.11.18 um 16:32 schrieb Peter: > > Hello, > > I'm currently trying Apache Ignite and love the concept. > > I have created a simple example of what I'm trying to achieve >

Re: Geo redundancy support in Ignite?

We use https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/cache/affinity/rendezvous/ClusterNodeAttributeAffinityBackupFilter.java in order to say that the backup nodes cannot be in the same availability zone as the primary node for any given cache. You just

Re: Geo redundancy support in Ignite?

It’s absolutely possible. The difficulty comes not in making it work but in figuring out the failure scenarios and what sensible thing to do in each case. The obvious example: if your inter-site network goes down what happens? You now have two clusters, each that thinks it’s *the* cluster. I

Re: JDBC Streaming

Hi Ilya, Yes - I am using JDBC Client driver to INSERT data into the SQL table. It works correctly (but slow) without setting 'streaming=true'. When I set 'streaming=true' in the connection string, as per the Ignite docs (

Re: Geo redundancy support in Ignite?

Hello. I am a newbie on Ignite. Ingite does not support geo redundancy out of the box. But, looking at the documentation it is not impossible to realize it. Using a mix of multicast and static IO addresses, and good inter-site networking, you could establish a geographically distributed Ignite

Re: (IF NOT EXISTS) in CREATE TABLE statement does not work

Hello! This is a well-known problem: https://issues.apache.org/jira/browse/IGNITE-8060 (and friends) Unfortunately there's no schedule for a fix. Regards, -- Ilya Kasnacheev пн, 26 нояб. 2018 г. в 12:08, Qingping <15075...@qq.com>: > After many tests, I found that if I first set up an

Re: Ignite benchmarking with YCSB

Hello! It is hard to say what is the limiting factor here. Yes there's a lot of threads on YCSB side, but still a single one on Ignite side. And it's sitting on Communication write. Can you try doing the following: supplying custom TcpCommunicationSpi as ignite's communicationSpi with

Re: Ignite benchmarking with YCSB

Hi Ilya, Please find the YCSB side jstack threaddump files along with Ignite side. Please note that this time i have used 80 threads. Number of YCSBs: 2 Threads per YCSB: 80 YCSB-1 ThreadDump files on 2 occassions: ycsb1_load_1.ycsb1_load_1

Re: Speed Expectations for Ignite Queue

Hello! I think that you had too optimistic expectations. LinkedBlockingQueue is a core Java data structure and it is very fast - it just writes a reference to data structure in best case scenario. Meanwhile, Ignite Queue will create several internal temporary objects (such as distributed

Re: Client stucks and doesn't connect

Hello. I use version 2.6.0#20180710-sha1:669feacc and I can not reproduce this issue. I have seen it at least 2 times, and I don't have full log =/ . My cluster has lazy disk so restoration of partition states is too slow. So I think there is race condition between ClientImpl and call of

Re: Client stucks and doesn't connect

Hello. I use version 2.6.0#20180710-sha1:669feacc and I can not reproduce this issue. I have seen it at least 2 times, and I don't have full log =/ . My cluster has lazy disk so restoration of partition states is too slow. So I think there is race condition between ClientImpl and call of

Re: Ignite cluster going down frequently

Hello! It is not clear from this log alone why this node became segmented. Do you have log from other server node in the topology? It was coordinator so maybe it was the one experiencing problems. Regards, -- Ilya Kasnacheev ср, 28 нояб. 2018 г. в 13:56, Hemasundara Rao <

Re: Ignite performance is getting dipped by 50% when run both upserts and query services are run together

Hello! I think you should expect that. When you do more parallel operations, there's more locking and throughput decreases. However, we don't know enough about your specific workload to really understand what's going on. Regards, -- Ilya Kasnacheev вт, 27 нояб. 2018 г. в 16:24, Naveen : >

Re: Use case difference between CacheLoader, CacheWriter and CacheStore?

Hello! CacheStoreAdapter is just a convenience class with some methods pre-implemented. You can use both. Regards, -- Ilya Kasnacheev вт, 27 нояб. 2018 г. в 15:18, the_palakkaran : > Thanks. Should I be using CacheStore or CacheStoreAdapter for my > implementations? > > > > -- > Sent from:

Re: Ignite benchmarking with YCSB

Hello! I can see only one node actually doing any work, out of 6. I can see there's 100 threads on YCSB side, but it doesn't seem that there's actually any parallelism. Can you also do thread dump of YCSB? Regards, -- Ilya Kasnacheev чт, 29 нояб. 2018 г. в 16:20, summasumma : > Hi Ilya, > >

Re: Slow select distinct query on primary key

Hi, I tried the additional index as you suggested, but it did not improve the query time. The query still takes 58-61 seconds. CREATE INDEX PERF_POSITIONS_IDX ON PERF_POSITIONS (ACCOUNT_ID); CREATE INDEX PERF_POSITIONS_IDX2 ON PERF_POSITIONS (ACCOUNT_ID, EFFECTIVE_DATE, FREQUENCY, SOURCE_ID,

Is there any way to speed up delete data or drop table?

Hello. We need to fully sync data from mysql to ignite periodicity.Thus we need to clear data in ignite first.Ignite does not support truncate statement and its drop table statement sometimes takes long time.It's also very slow to delete all data in ignite's tables or caches.Is there any way to

Re: Ignite benchmarking with YCSB

Hi Ilya, Yes i have taken during the workload and not before or after. Reattaching after fresh run now. Can u please check and let me know? load_1.load_1 load_2.load_2

Re: Configuration of ignite

Actual operations contain high write operations and lesser read ones. Okay distributed storage noted. Thank you. On Thu, 29 Nov 2018 at 6:16 PM, Ilya Kasnacheev wrote: > Hello! > > What are actual operations that you want best TPS for? For different > operations the the answer will be

Re: JDBC Streaming

Hello! You can use DML on thick client, too, but it will be slower than Data Streamer approach. Regards, -- Ilya Kasnacheev вт, 27 нояб. 2018 г. в 11:22, joseheitor : > Shouldn't I be able to do this through plain JDBC DML operations? The > documentation for the JDBC Client Driver specifies

Re: Configuration of ignite

Hello! What are actual operations that you want best TPS for? For different operations the the answer will be different. With regards to maxSize you should try to load your data, see how much memory it will take. Note that Apache Ignite will distribute cache between all four nodes by default.

Re: Problems Starting Hello Workd GA example from ignite webstie

Hello! You have to do mvn clean install first. mvn exec:java does not force rebuild process. Regards, -- Ilya Kasnacheev чт, 29 нояб. 2018 г. в 13:32, AlphaMufasaOmega : > Dear Apache Ignite Community, > >I have had lots of problems trying to figure out how to execute the > Hello > World

Configuration of ignite

I am setting up a cluster of 4 nodes. 2 are partitioned and 2 are backups of the respective nodes. The dataset contains 1 million rows of 150 columns having VARCHAR values. What would be the configurations needed for the same? In regards of pagesize, maxsize, checkpointbuffersize. What would be

Re: Geo redundancy support in Ignite?

Hello! Apache Ignite currently assumes that your whole cluster is geographically collocated, including clients (but excluding thin clients). There may be third party solutions on top of Apache Ignite which allow geo-distributed redundancy. Regards, -- Ilya Kasnacheev чт, 29 нояб. 2018 г. в

Re: Ignite benchmarking with YCSB

Hello! I can't see any work happening in your thread dumps. Are you sure that you have collected them during your workload, as opposed to after load is finished (or before it is started)? Regards, -- Ilya Kasnacheev чт, 29 нояб. 2018 г. в 15:11, summasumma : > Hi Ilya, > > I have used jstack

Re: java.lang.ClassCastException: org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl

Hello! If it does not help, can you please provide full startup log including full Exception stack trace? Be sure to start Ignite in verbose mode (-v, without IGNITE_QUIET). Regards, -- Ilya Kasnacheev вт, 20 нояб. 2018 г. в 08:11, userx : > Hi Ilya, > > Thank you for your reponse. > Any

Re: Upgrading from 1.9 .... need help

Hello! You can use Page Eviction which is preferable in 2.x: https://apacheignite.readme.io/docs/evictions As for best practices, I think you should not have more than a few regions and not to fine-tune size of your caches, instead relying on Page Eviction. Regards, -- Ilya Kasnacheev чт, 15

Re: Ignite benchmarking with YCSB

Hi Ilya, I have used jstack to threaddump. PFA the dump files for your reference. These are taken after adding the following 64 Threadpool configuration in Apache Ignite configuration and while the Insert operation was happening with 55k OPS from YCSB: !-- Configure system thread pool.

Geo redundancy support in Ignite?

Hi all, Can anyone please let me know if there is Geo redundancy scenario support in Ignite? Say, if we need a geo-replication of a ignite cluster, what is the best way to do/configure? Any Ignite specific suggestions already available? Can u pls clarify following? 1. Is it possible in ignite

RE: Effective way to pre-load data around 10 TB

Hi, Currently the best option is IgniteCache::preloadPartition method added in https://issues.apache.org/jira/browse/IGNITE-8873. There is a JIRA ticket to allow pre-loading data before the node joins the cluster: https://issues.apache.org/jira/browse/IGNITE-10152. Stan From: Naveen Sent: 29

RE: some cases (IF NOT EXISTS) in the CREATE TABLE statement does notwork

A bug for this is filed: https://issues.apache.org/jira/browse/IGNITE-10414 Stan From: Qingping Sent: 27 ноября 2018 г. 4:26 To: user@ignite.apache.org Subject: some cases (IF NOT EXISTS) in the CREATE TABLE statement does notwork Question=== When testing Ignite 2.6.0 (2018-07-16),

RE: Client stucks and doesn't connect

Hi, The interesting (and disappointing) part is the NPE: java.lang.NullPointerException: null     at org.apache.ignite.spi.discovery.tcp.ClientImpl.sendJoinRequest(ClientImpl.java:666)     at org.apache.ignite.spi.discovery.tcp.ClientImpl.joinTopology(ClientImpl.java:546)     at

Re: Ignite startu is very slow

Hi, This time it is got hung. so I have killed the nodes and restarted again. Please find attached logs on startup. node1.log node2.log As you

Problems Starting Hello Workd GA example from ignite webstie

Dear Apache Ignite Community, I have had lots of problems trying to figure out how to execute the Hello World GA example for genetic algorithms. I get the an error when executing the command: mvn exec:java

RE: Ignite cache.getAll takes a long time

Hi, Start by looking at what’s going on in the cluster when you see these long reads. Collecting a JFR record or a GC log would be nice. Also, do you see that with concurrent reads and writes, i.e. do you have getAll and putAll executing in parallel? Perhaps there is some sort of contention

Re: ODBC driver build error

By the way, you do know that there is a pre-built binary installer in Ignite binary release, right? Or do you want to build ODBC by yourself for some reason? Best Regards, Igor On Thu, Nov 29, 2018 at 12:50 PM Igor Sapego wrote: > This is a known issue of broken backward compatibility of

Re: ODBC driver build error

This is a known issue of broken backward compatibility of MSVC. See [1] for details and solution. [1] - https://apacheignite-sql.readme.io/docs/odbc-driver#section-building-on-windows Best Regards, Igor On Thu, Nov 29, 2018 at 9:22 AM Ray wrote: > Hi Igor, > > Thanks for the reply. > I

Effective way to pre-load data around 10 TB

HI We are using Ignite 2.6. AS we already know, after the cluster restart, every GET call gets data from DISK for the first time and loads into RAM and subsequent calls data will read from RAM only.. First time GET calls are 10 times slower than read from RAM, which we wanted to avoid by

Re: Slow select distinct query on primary key

Hi, There is some issue to use indexes for complex PK, which is already fixed and will be included into 2.8. https://issues.apache.org/jira/browse/IGNITE-8386 As of now to fix your performance issue you can create separate index for ACCOUNT_ID column. чт, 29 нояб. 2018 г. в 02:24, yongjec : >