Re: ignite visor not workin in case ignite is started from a tomcat

Hi Alexey Thanks, we found the issue. We were not giving port in config xml through which we were connecting ignitevisor Thanks -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/ignite-visor-not-workin-in-case-ignite-is-started-from-a-tomcat-tp16043p16045.html

ignite visor not workin in case ignite is started from a tomcat

Hi All We have a web application deployed in tomcat, from which we are starting ignite server It seems in this scenario ignite visor is not able to detect ignite instance. In case we start ignite from a java class(not through tomcat), ignite visor is able to connect to ignite and give cache

Re: I am not able to read mxbean values of ignite

mxbean in MBeaninfo of a particluar cache is coming as false, because of which logstash jmx plugin is not able to get data. I am also facing the same problem we have used cacheCfg.setStatisticsEnabled(true); cacheCfg.setManagementEnabled(true); Attributes values are coming in jconsole but

most of the dat in mbeans in empty

Hi All I am trying to monitor mbeans through jconsole. I have ste setStatisticsEnabled(true) In jconsole I can see only some entries for all caches like key size and off heap counts (see image) Why the rest of data is not available ?

Re: sql query in case of cluster group

Hi Andrey, we are not using query timeout, because we want to get partial results, in case 1 node is slow, but other nodes are faster. So, we are using cluster groups. Yes, just checked. If we don't use queryParallelism, then the query works well.. :) Kindly create a jira if you have same

Re: sql query in case of cluster group

We are using cluster groups to run query on each nodes of the cluster so that we can set the timeout on each query. We are running local queries and in TestIgniteCallable we have given List> res = cache.query(qry.setArgs().setLocal(true)).getAll(); What are we missing ? -- View this

Re: sql query in case of cluster group

Hi Andrew It seems to be an order by issue. We have created a test project in github https://github.com/neerajbhatt/testIgnite If we use PutItems to put some records in a partitioned cache(TESTCACHE) args[0]=number of records, and then Get the items by GetItemsWithClusterGroup args[0] = query

Re: sql query in case of cluster group

Hi Andrew Thanks for your inputs now we are not getting duplicate records as we are now using different cache and ignite objects for each compute. But for queries which have order by (sort by) clause we are getting exactly same result from all cluster groups(nodes). It looks in case of order by

Re: sql query in case of cluster group

Any update ?, Also we have data as back up as one. In case of back ups can we get duplicate result as we might be getting result from both master and slave -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/sql-query-in-case-of-cluster-group-tp14884p14903.html Sent

Re: sql query in case of cluster group

--code is as below --all caches are partitioned --args[0] is type of query, args[1] is number of queries, args[2] is ip of cluster group (each node is a separate cluster group. group name is 'i-' --we are trying with different args[2] (cluster groups) and we are getting duplicate result. Web

sql query in case of cluster group

Hello All We have a requirement to set time out for each node so that we can get a partial result , in case of a time out from a particular node. To solve this we have created a cluster group for each node and run compute ClusterGroup cg = cluster.forAttribute("ROLE", group);

Re: wrong data from cluster nodes while using left join

Any update ? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/wrong-data-from-cluster-nodes-while-using-left-join-tp14782p14865.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

wrong data from cluster nodes while using left join

Hi All We have created cluster groups for each node of a cluster (so that we can give time out for each node (cluster group), in case query fails in a node we can get a partial result ) We have couple of partitioned caches (with backup as 1) and we are sending a query with left join id is

Re: query performance degrade when adding a filter criteria (order by)

Also field a in A_CACHE.Rank (r) is indexed -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/query-performance-degrade-when-adding-a-filter-criteria-order-by-tp14624p14625.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

query performance degrade when adding a filter criteria (order by)

Hi All Our below query is working fine SELECT r.uniqueSkuId FROM A_CACHE.Rank as r, B_CACHE.Item as T WHERE T.id = r.id AND T.b=? AND T.c=? AND T.d=? order by r.rank desc limit 3 but when we add additional criteria (r.a=?) as below the time increase from 10 ms to ~500 ms SELECT

Re: slow performance when using order by clause

Hi Andrew Thanks a ton, by chaging order the performance increased signifacantly to about 10 ms Thanks -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/slow-performance-when-using-order-by-clause-tp14389p14573.html Sent from the Apache Ignite Users mailing

Re: slow performance when using order by clause

explain plan without order by FROM ITEMCACHE.ITEM T__Z0 /* ITEMCACHE.ITEM_RATING_IDX: RATING = ?1 */ /* WHERE (T__Z0.RATING = ?1) AND ((T__Z0.DOWNLOADS = ?3) AND (T__Z0.REVIEWS = ?2)) */ INNER JOIN IGPCACHE.RANK R__Z1 /* IGPCACHE.RANK_UNIQUESKUID_IDX: UNIQUESKUID

ignitevisor (2.0) shows zero objects in off heap

We are using ignite 2.0 and ignite visor is showing all objects in heap. As per ignite documentation here all objects be default are in off heap odes for: ITEMCACHE(@c2)

off heap and jvm tuning

Hello All As per my understanding by default ignite 2.0 keeps all objects in off heap by default We have kept java heap as 8 GB for all machines in cluster 1. When we add or remove a node (Partitioned cached, with backup one) we see that heap usage in one machine of cluster accordingly decreased

using ignite web console

I am trying to install ignite web console in one of our servers (linux)as given in https://apacheignite-tools.readme.io/v1.9/docs/build-and-deploy We will be accessing the web console from different windows machine browser Do we need server ip address while building front end or back end as we

Can sql query read from back up partion instead of primary partition

Hi All We are looking to scale our sql query read operation, can we read from backup partitions instead of primary partitions ? There is something called "mode", and setting "readFromBackup". They seem to work for cache operations. Is there similar concept for SQL queries. Thanks -- View

setting query timeout and getting partial result instead of exception.

Hi All We have a cache which is to be partitioned across nodes. Currently all the SQL queries are executed on all nodes by default. However, if a node is slow, all the queries will be slow. So, is there a way to set the timeout on the SQL queries, so that even though a few nodes are slow and

SqlFieldsQuery setTimeout

Hello All While querying to ignite cluster we can set a timeout SqlFieldsQuery.setTimeout Suppose in a 5 node cluster set up if one node timed out we will get result from other 4 nodes or the query will fail altogether ? Ideally we want that maximum result from all the nodes should come, if