Re:Re: Re: Re: Re: Re: Re: Re: Re:Poor performance select query with jdbc thin mode

Denis, Thanks very much! All data are related ,and there are about 60G data in the heap. And if I add other business module ,the data also are related.We can not split them. So If data is collocated, then a single node is enough. But it's not high availability. At

Re: Web Console on Kubernetes Cluster

Andrey, Do you think you can put together “Kubernetes Deployment” section for web console? https://issues.apache.org/jira/browse/IGNITE-7131 — Denis > On Dec 5, 2017, at 4:04 PM, lukaszbyjos wrote: > > O, thanks.

Re: Did the default page size change between Ignite 2.2 and 2.3

Only by looking into a documentation of a specific Ignite version or your configs if the property is overridden. — Denis > On Dec 2, 2017, at 7:53 PM, Raymond Wilson wrote: > > BTW, is there a way of determining what the page size of a persistent store > is before

Re: Ignite in docker (Native Persistence)

Nick, As one of Ignite docker maintainers, could you please investigate one how to map Ignite persistence to docker volumes: https://docs.docker.com/engine/admin/volumes/volumes/#use-a-read-only-volume and update

Re: Rest API not working for GET

Did you create the SQL table using CREATE TABLE command? If it’s so then a cache name won’t be equal to “Person” by default. Pass “Person” as a cache name directly via CACHE_NAME parameter of CREATE TABLE as explained here: https://apacheignite-sql.readme.io/docs/create-table — Denis > On Dec

Re: Index not getting created

This issue got fixed after clean restart of the cluster and creating the caches again. I could create the index. Do we have any option to set the affinity mapping for the cache which is already created and holding data. Thanks Naveen -- Sent from:

Re: ClassNotFoundException when using IgniteHadoopIgfsSecondaryFileSystem

Hi, Thanks for your answer. I have both libs/ignite-core and libs/ignite-hadoop/ignite-hadoop, and also the jar for the other hadoop file system, in the list of jars visible on the java.class.path section that is returned by the config command of the Ignite Visor. Is the order of the jars

Re: How IGFS URIs work

Hi again, I'm using the following ipcEndpointConfiguration in all nodes running ignite Then from a node that is not running ignite I can do `hadoop fs -ls

Re: How IGFS URIs work

That is right - you cannot use SHMEM connection type if you have no local Ignite. SHMEM means "shared memory" and requires local Ignite. Change IGFS endpoint type to TCP (below replace __HOST__ and __PORT__ with IP and port of any host running Ignite):

Re: How IGFS URIs work

But if I do that from a compute node that doesn't have ignite, then I fail to connect to the IGFS cluster: [hadoop@ip-10-0-0-242 ~]$ hadoop fs -ls igfs://igfs@/ ls: Failed to communicate with IGFS: Failed to connect to IGFS [endpoint=igfs://igfs@, attempts=[[type=SHMEM, port=10500,

Re: Error running ignite in YARN

Hello Juan! Thank you for the hints! With this, I was able to run Ignite on YARN with your configuration and my patch. The patch from IGNITE-7080 was already merged to master by N. Tikhonov, so it will be included in the next versions. Note that there are still usability issues. I would be glad

Re: DataStreamer vs CacheStoreAdapter

Hi, If you plan to stream into data from single JVM then the better way use only one instance of DataStreamer. Sure, if you're going to start different 10 JVMs than you'll use 10 instance of DataStreamer. By default DataStreamer won't overwrite existing entries in a cache. You can change this

Re: Re: Re: Re: Re: Re: Re: Re: Re:Poor performance select query with jdbc thin mode

Lucky, Please provide explain and timing for the same query, executed on a single node. Denis ср, 6 дек. 2017 г. в 16:27, Lucky : > well,3 node took about double time of single node. >

Re:Re: Re: Re: Re: Re: Re: Re: Re:Poor performance select query with jdbc thin mode

well,3 node took about double time of single node.

Re: Multi Data center replication issue

Hello! Apache Ignite does not have this functionality and community does not relate with it product. You need to ask this questions to company that provided this features. On Wed, Dec 6, 2017 at 3:00 PM, bits1983_25 wrote: > Iam doing a POC on multi data center

Multi Data center replication issue

Iam doing a POC on multi data center replication feature of Gridgain. I'm able to execute successfully the sample example packaged in the gridgain distribution. But when I tried to replicate multiple caches (around 150 caches), I could see only 16 caches eligible for replication through VISOR UI.

Re: JDBC ResultSet get columns with table alias

After upgrading to the latest ignite version, I am able to access using column name. Thanks -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: How IGFS URIs work

You do not need to specify the "host" part of the Hadoop URI at all if you do not want to limit processing to that specific host. Just specify "igfs://myIgfs@/" and Hadoop will load-balance the load for you across all IGFS nodes.

Re: ClassNotFoundException when using IgniteHadoopIgfsSecondaryFileSystem

Hi, I do not see any other reasons for a "class not found" exception but the class is not on the CLASSPATH. Can you make sure "ignite-core-xxx.jar" and "ignite-hadoop-xxx.jar" are on the hadoop's CLASSPATH.

Re: How to do 'stream processing' and more questions of a Ignite newbie

Hi, What you described sounds like an Event Processing architecture, which includes never-ending stream of input data, limited time window, analysis of data within the time window and taking an action if necessary. Ignite supports Event Processing architecture with the following components:

Re: Re: Re: Re: Re: Re: Re: Re:Poor performance select query with jdbc thin mode

Lucky, You can find information about distributed joins tuning here: https://apacheignite-sql.readme.io/docs/distributed-joins It contains explanation of how distributed joins work, and why it's important to keep data collocated. Denis ср, 6 дек. 2017 г. в 13:06, Denis Mekhanikov

Re: Re: Re: Re: Re: Re: Re: Re:Poor performance select query with jdbc thin mode

Looks like you ran this query on a cluster with more than one node, so you get performance drop because of distributed joins. Let's tune performance on a single node first. You can expect queries with joins to operate fast only if data is collocated. Otherwise latency will suffer from network

Re:Re: Re: Re: Re: Re: Re: Re:Poor performance select query with jdbc thin mode

explain : SELECT T0__Z0.FID AS __C0_0, T0__Z0.FCUSTOMERGROUPSTANDARDID AS __C0_1, T0__Z0.FCUSTOMERGROUPID AS __C0_2, T0__Z0.FCUSTOMERID AS __C0_3, T0__Z0.FCUSTOMERGROUPFULLNAME AS __C0_4 FROM "csspGroupStandardCache".CSSPGROUPSTANDARD T1__Z1 /*

Re: Re: Re: Re: Re: Re: Re:Poor performance select query with jdbc thin mode

Lucky, Well, at least we figured out, that JDBC drivers and IgniteCache#query don't have that huge difference, that you told us about :) Could you show result of *EXPLAIN *for this query? Did you configure any indexes? Denis ср, 6 дек. 2017 г. в 4:05, Lucky : > No, the