Re: Sudden node failure on Ignite v2.7.5

2019-07-15 Thread ihalilaltun
Hi Pavel, Thanks for you reply. Since we use the whole sysyem on production environment we cannot apply the second solution. Do you have any estimated time for the first solution/fix? Thanks. - İbrahim Halil Altun Senior Software Engineer @ Segmentify -- Sent from: http://apache-ignite-use

Re: Error compiling query: entire LINQ expression should bespecifiedwithin lambda passed to Compile method. Part of the query can't beoutsidethe Compile method call.

2019-07-15 Thread Pavel Tupitsyn
I've got to the bottom of this, it is indeed a bug [1] The workaround is to use a different overload [2], this works: CompiledQueryFunc> issueqry = CompiledQuery.Compile(queryable.Where(emp => emp.Value.Name == "unused_value")); foreach (var entry in issueqry("abc")) Console.WriteLine(">

RE: Error compiling query: entire LINQ expression should bespecifiedwithin lambda passed to Compile method. Part of the query can't beoutsidethe Compile method call.

2019-07-15 Thread Alexandr Shapkin
Hi! As I understand correctly, right now CompiledQuery won’t work if there is a non-primitive value inside the WHERE clause. This seems like a bug for me, because it’s pretty common to treat String class as a primitive one. Right now you can rewrite your query to “x.Contains(y)” or “x.StartsWit

[IgniteKernal%ServerNode] Exception during start processors, node will be stopped and close connections java.lang.NullPointerException: null......cache.GridCacheUtils.affinityNode

2019-07-15 Thread siva
Hi, I have .Net Core(2.2.6) Ignite Client And Server Application. Now I am using Apache Ignite Nightly build(apache-ignite-2.8.0-SNAPSHOT-bin)(taken master code, build and added Apache.Ignite core.dll into my Application Project) because due Application in production every time server on the start/

Re: about start -f command in ignitevisorcmd

2019-07-15 Thread Andrei Aleksandrov
Hi, Looks like this file was moved to https://github.com/gridgain/apache-ignite/blob/ignite-2.7.5/config/visor-cmd/node_startup_by_ssh.sample.ini Here is the ticket: https://issues.apache.org/jira/browse/IGNITE-10036 Please double check your config folder or you can download this file from

Re: Metrics for Ignite

2019-07-15 Thread Andrei Aleksandrov
Hi, You can try to use the web console for Ignite. It contains the Monitoring Dashboard with different cache metrics that were calculated during some period of time. Also, it contains different graphics related to cache operation throughput and latency: https://apacheignite-tools.readme.io/d

Re: Metrics for Ignite

2019-07-15 Thread breath1988
Hello. I’m joining the question. Very interested in measuring latency for basic operations. > 15 июля 2019 г., в 16:20, nikhil dhiman написал(а): > > Hi, I am almost production ready, but I want to plot graphs for > Throughput, latency operation wise[get, put, delete, eviction]. Is > there a wa

Metrics for Ignite

2019-07-15 Thread nikhil dhiman
Hi, I am almost production ready, but I want to plot graphs for Throughput, latency operation wise[get, put, delete, eviction]. Is there a way I can produce metrics for time taken by ignite node for get/put/delete. I can see many metrics via rest module. But i am unable to find the above metrics.

Re: unsubscribe

2019-07-15 Thread Вячеслав Коптилин
Hi, Hello, To unsubscribe from the user mailing list send an e-mail to user-unsubscribe @ignite.apache.org If you have a mailing client, follow the unsubscribe link here: https://ignite.apache.org/community/resources.html#mail-lists Thanks, S. пт, 12 июл. 2019 г. в 23:26, Majid Salimi : > unsu

Re: Sudden node failure on Ignite v2.7.5

2019-07-15 Thread Majid Salimi
unsubscribe me, please! I don't want to receive emails. On Mon, Jul 15, 2019 at 1:06 PM Pavel Vinokurov wrote: > Hi, > > It looks like the issue described in > https://issues.apache.org/jira/browse/IGNITE-11953 > There a two options: > 1. I believe it will be fixed very soon. Thus you could crea

Re: Sudden node failure on Ignite v2.7.5

2019-07-15 Thread Pavel Vinokurov
Hi, It looks like the issue described in https://issues.apache.org/jira/browse/IGNITE-11953 There a two options: 1. I believe it will be fixed very soon. Thus you could create a build based on 2.7.5 with cherry-picked fix. 2. You could remove the cachegroup property from the cache configuration. I

Re: about start -f command in ignitevisorcmd

2019-07-15 Thread Majid Salimi
Unsubscribe me On Mon, Jul 15, 2019 at 11:01 AM liyuj <18624049...@163.com> wrote: > Hi, > > In the ignitevisorcmd environment, enter the help start command to see > the following: > - f= > Path to INI file that contains topology specification. > For sample INI file refer > to'bin/include/visorcm

Re: Ignite DB Issues

2019-07-15 Thread Majid Salimi
Unsubscribe me On Mon, Jul 15, 2019 at 6:15 AM anji m wrote: > Hi Team, > > > 1. I have 10 records of CSV and stored in Ignite DB then ten records will > be stored along with new table creation. Now I > have removed drop table code from my java code and removed table creation > code and running

Re: onheapCacheEnabled enormous heap consumption

2019-07-15 Thread Majid Salimi
Unsubscribe me On Sun, Jul 14, 2019 at 12:30 PM Павлухин Иван wrote: > Andrey, > > Yes it is a little bit complicated for understanding. > > CacheConfiguration.evictionPolicy takes it roots back in history where > there were neither offheap nor persisence, cache data was stored in > java heap on

Re: Sudden node failure on Ignite v2.7.5

2019-07-15 Thread Majid Salimi
Unsubscribe me On Sat, Jul 13, 2019 at 7:48 PM ihalilaltun wrote: > Hi Igniters, > > Recently (11.07.2019), we have upgraded our ignite versin from 2.7.0 to > 2.7.5. Just like after 11 hours one of our nodes killed itself without any > notification. I am adding the details that I could get from