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

[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(">>>" + entry.Value.Name);


[1] https://issues.apache.org/jira/browse/IGNITE-11985
[2]
https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Linq.CompiledQuery.html#Apache_Ignite_Linq_CompiledQuery_Compile__1_System_Linq_IQueryable___0__

On Mon, Jul 15, 2019 at 8:04 PM Alexandr Shapkin  wrote:

> 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.StartsWith(y)”, but it’s not the same as Equals.
>
>
>
> *From: *siva 
> *Sent: *Friday, July 12, 2019 9:36 PM
> *To: *user@ignite.apache.org
> *Subject: *RE: Error compiling query: entire LINQ expression should
> bespecifiedwithin lambda passed to Compile method. Part of the query can't
> beoutsidethe Compile method call.
>
>
>
> Hi ,
>
>
>
>
>
> Thanks for reply
>
>
>
>
>
> i have attached sample code  git hub link.please verify it .
>
>
>
>
>
>
>
>
>
>
>
>
>
> Thanks
>
> siva https://github.com/cvakarna/ApacheIgnite/blob/master/Program.cs
>
> 
>
>
>
>
>
>
>
> --
>
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
>
>

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

[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.StartsWith(y)”, 
but it’s not the same as Equals.
 

From: siva
Sent: Friday, July 12, 2019 9:36 PM
To: user@ignite.apache.org
Subject: RE: Error compiling query: entire LINQ expression should 
bespecifiedwithin lambda passed to Compile method. Part of the query can't 
beoutsidethe Compile method call.

Hi ,


Thanks for reply 


i have attached sample code  git hub link.please verify it .






Thanks 
siva https://github.com/cvakarna/ApacheIgnite/blob/master/Program.cs
  



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

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

[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/stop
loading data taking more time. but not able to start the Server with disk
cache data.

Once I started Server and client and loaded data after stopped when starting
the server with existing disk data getting the following error in the log.

So I am Not able to start Server with disk data.

here the issue but it already closed and  Resolved
  .

GitHub   

Configuration File
-
server-config.xml
  

here is the log file

ignite.log
  

So whether this issue still there or not, whether I can use or not still I
have to wait for the release or any other way. Any configuration I need to
configure to Start Server with existing data.

please give suggestion to me. 

Thanks.



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

Re: about start -f command in ignitevisorcmd

[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 the link above.


BR,
Andrei

On 2019/07/15 06:30:55, liyuj <1...@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/visorcmd/node_startup_by_ssh.sample.ini'.>
>
> But the node_startup_by_ssh.sample.ini file does not exist. Can 
somebody >

> provide an example of this file?>
>
>

Re: Metrics for Ignite

[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/docs/ignite-web-console

You can try to use the next "ready to go" installation for testing:

https://console.gridgain.com/monitoring/dashboard

BR,
Andrei

On 2019/07/15 13:20:09, nikhil dhiman  wrote:
> 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.>
>
> I am on Ignite 2.7.5 version.>
>
> Thanks & Regards,>
> Nikhil Dhiman>
>

Re: Metrics for Ignite

[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 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.
> 
> I am on Ignite 2.7.5 version.
> 
> Thanks & Regards,
> Nikhil Dhiman

Metrics for Ignite

[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.

I am on Ignite 2.7.5 version.

Thanks & Regards,
Nikhil Dhiman

Re: unsubscribe

[Вячеслав Коптилин]

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 :

> unsubscribe
>
> --
>
>
>
>
> *Regards,Majid Salimi BeniM.Sc. Student of Computer Engineering,Department
> of Computer Science and Engineering & IT*
> *Shiraz University*
> Attachments area
>

Re: Sudden node failure on Ignite v2.7.5

[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 create a build
> based on 2.7.5 with cherry-picked fix.
> 2. You could remove the cachegroup property from the cache configuration.
> In this case you have to start a new cluster and it requires much more
> heap memory on the startup since there are about 650 caches.
>
> Thanks,
> Pavel
>
> сб, 13 июл. 2019 г. в 18:18, ihalilaltun :
>
>> 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 the server and
>> the topology we use;
>>
>> *Ignite version*: 2.7.5
>> *Cluster size*: 16
>> *Client size*: 22
>> *Cluster OS version*: Centos 7
>> *Cluster Kernel version*: 4.4.185-1.el7.elrepo.x86_64
>> *Java version* :
>> openjdk version "1.8.0_212"
>> OpenJDK Runtime Environment (build 1.8.0_212-b04)
>> OpenJDK 64-Bit Server VM (build 25.212-b04, mixed mode)
>>
>> By the way this is a production environment and we have been using this
>> topology for almost 5 months. Our average tps size is ~5000 for the
>> cluster.
>> We have 8 to 10 different object that we persist on ignite, some of them
>> relatively big and some ara just strings.
>>
>> ignite.zip
>> 
>> gc.current
>> 
>> hs_err_pid18537.log
>> <
>> http://apache-ignite-users.70518.x6.nabble.com/file/t2515/hs_err_pid18537.log>
>>
>>
>>
>>
>>
>> -
>> İbrahim Halil Altun
>> Senior Software Engineer @ Segmentify
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>
>
>
> --
>
> Regards
>
> Pavel Vinokurov
>


-- 




*Regards,Majid Salimi BeniM.Sc. Student of Computer Engineering,Department
of Computer Science and Engineering & IT*
*Shiraz University*
Attachments area

Re: Sudden node failure on Ignite v2.7.5

[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.
In this case you have to start a new cluster and it requires much more heap
memory on the startup since there are about 650 caches.

Thanks,
Pavel

сб, 13 июл. 2019 г. в 18:18, ihalilaltun :

> 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 the server and
> the topology we use;
>
> *Ignite version*: 2.7.5
> *Cluster size*: 16
> *Client size*: 22
> *Cluster OS version*: Centos 7
> *Cluster Kernel version*: 4.4.185-1.el7.elrepo.x86_64
> *Java version* :
> openjdk version "1.8.0_212"
> OpenJDK Runtime Environment (build 1.8.0_212-b04)
> OpenJDK 64-Bit Server VM (build 25.212-b04, mixed mode)
>
> By the way this is a production environment and we have been using this
> topology for almost 5 months. Our average tps size is ~5000 for the
> cluster.
> We have 8 to 10 different object that we persist on ignite, some of them
> relatively big and some ara just strings.
>
> ignite.zip
> 
> gc.current
> 
> hs_err_pid18537.log
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/t2515/hs_err_pid18537.log>
>
>
>
>
>
> -
> İbrahim Halil Altun
> Senior Software Engineer @ Segmentify
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


-- 

Regards

Pavel Vinokurov

Re: about start -f command in ignitevisorcmd

[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/visorcmd/node_startup_by_ssh.sample.ini'.
>
> But the node_startup_by_ssh.sample.ini file does not exist. Can somebody
> provide an example of this file?
>
>

-- 




*Regards,Majid Salimi BeniM.Sc. Student of Computer Engineering,Department
of Computer Science and Engineering & IT*
*Shiraz University*
Attachments area

Re: onheapCacheEnabled enormous heap consumption

[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 only. Also, as far as I know, today
> CacheConfiguration.evictionPolicy (as already mentioned) works only
> when onheap caching is enabled and an entry is still available in
> offheap after it was evicted from onheap. And it worth noting (correct
> me if I am wrong) that data is NOT buffered in onheap and then written
> to offheap on eviction but written to both places on each writing
> operation. So, I expect that onheap caching can speedup only read
> operations.
>
> DataRegionConfiguration.pageEvictionMode is a different thing (similar
> naming brings confusion) and it appeared with PageMemory. It cannot be
> configured on a cache level. It is applicable ONLY for data regions
> WITHOUT persistense and controls offheap pages eviction. If
> pageEvictionMode is not DataPageEvictionMode.DISABLED then in case of
> not enough memory (see also evictionThreshold) some page will be
> evicted (actually cleaned and reused).
>
> If persistence is enabled DataRegionConfiguration.pageEvictionMode has
> no effect (there should be a warning in Ignite node startup logs). For
> a persistent data regions there is an internal page replacement
> algorithm allowing to reuse offeap memory pages when some data need to
> be pulled from disk.
>
> пн, 8 июл. 2019 г. в 18:38, Ilya Kasnacheev :
> >
> > Hello!
> >
> > Data is always written to persistence immediately (via WAL). You can
> control eviction of offheap with evictionThreshold and pageEvictionMode
> settings of DataRegionConfiguration.
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > пн, 8 июл. 2019 г. в 17:50, Andrey Dolmatov :
> >>
> >> When data overfit dataRegion max size, so no more available offheap
> space, then data goes to persistence. So, what option controls how data
> pages should be evicted from offheap to persistence.
> >>
> >> On Mon, Jul 8, 2019, 5:33 PM Ilya Kasnacheev 
> wrote:
> >>>
> >>> Hello!
> >>>
> >>> Data is always stored in offheap. Eviction strictly controls onheap
> cache. Once data is evicted from onheap it is available in offheap.
> >>>
> >>> Regards,
> >>> --
> >>> Ilya Kasnacheev
> >>>
> >>>
> >>> пн, 8 июл. 2019 г. в 17:31, Andrey Dolmatov :
> 
>  We plan to use persistence in production. I didn't understand,
> CacheConfiguration.EvictionPolicy specify heap->offheap eviction,
> offheap->persistence eviction or both. It's not clear for me.
> 
>  On Mon, Jul 8, 2019, 5:19 PM Ilya Kasnacheev <
> ilya.kasnach...@gmail.com> wrote:
> >
> > Hello!
> >
> > Oops, I was wrong. This is indeed the wrong setting.
> >
> > Have you tried specifying evictionPolicy? I think it is the one that
> controls eviction from onheap cache. You can put a LruEvictionPolicy of 100
> 000 here, for example.
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > пн, 8 июл. 2019 г. в 17:09, Andrey Dolmatov :
> >>
> >> No, because we didnt specify QueryEntity.
> >> Does onheapCacheEnabled uses for SQL only?
> >> What default value for sqlOnheapCacheMaxSize?
> >>
> >> пн, 8 июл. 2019 г. в 17:05, Ilya Kasnacheev <
> ilya.kasnach...@gmail.com>:
> >>>
> >>> Hello!
> >>>
> >>> Have you tried also specifying sqlOnheapCacheMaxSize? You can
> specify 100 000 if you like.
> >>>
> >>> Regards,
> >>> --
> >>> Ilya Kasnacheev
> >>>
> >>>
> >>> пн, 8 июл. 2019 г. в 17:01, Andrey Dolmatov  >:
> 
>  We use simple replicated KV cache.
>  We try to upload 32 000 000 small records  to it
> (about 6Gb in data region, persistance disabled). We load data using
> DataStreamer.
> 
>  If we set onheapCacheEnabled=false, server node consumes heap
> about 500 Mb.
>  If we set onheapCacheEnabled=true, server node consumes heap
> about 6 Gb.
> 
>  Why DataStreamer uses heap memory to load data? Why on-heap size
> is unlimited (not just 100.000 records)? What default on-heap eviction
> policy?
> 
>  
>   value="REPLICATED"/>
>   value="true"/>
>  
> 
>  Thanks!
>
>
>
> --
> Best regards,
> Ivan Pavlukhin
>


-- 




*Regards,Majid Salimi BeniM.Sc. Student of Computer Engineering,Department
of Computer Science and Engineering & IT*
*Shiraz University*
Attachments area

Re: Sudden node failure on Ignite v2.7.5

[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 the server and
> the topology we use;
>
> *Ignite version*: 2.7.5
> *Cluster size*: 16
> *Client size*: 22
> *Cluster OS version*: Centos 7
> *Cluster Kernel version*: 4.4.185-1.el7.elrepo.x86_64
> *Java version* :
> openjdk version "1.8.0_212"
> OpenJDK Runtime Environment (build 1.8.0_212-b04)
> OpenJDK 64-Bit Server VM (build 25.212-b04, mixed mode)
>
> By the way this is a production environment and we have been using this
> topology for almost 5 months. Our average tps size is ~5000 for the
> cluster.
> We have 8 to 10 different object that we persist on ignite, some of them
> relatively big and some ara just strings.
>
> ignite.zip
> 
> gc.current
> 
> hs_err_pid18537.log
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/t2515/hs_err_pid18537.log>
>
>
>
>
>
> -
> İbrahim Halil Altun
> Senior Software Engineer @ Segmentify
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


-- 




*Regards,Majid Salimi BeniM.Sc. Student of Computer Engineering,Department
of Computer Science and Engineering & IT*
*Shiraz University*
Attachments area

about start -f command in ignitevisorcmd

[liyuj]

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/visorcmd/node_startup_by_ssh.sample.ini'.


But the node_startup_by_ssh.sample.ini file does not exist. Can somebody 
provide an example of this file?