Re: Not able to start second server node due to authentication failure

2019-11-13 Thread Sankar Ramiah
Thank you Andei and Zaheer for your response. I have tried setting a security subject with defaultAllowAll true for the server node but there is no change in the output. It is going through authenticateNode of my plugin (that implements GridSecurityProcessor), creates security subject, sets it to

Re: Ignite.Net configuration for storing large cache data

2019-11-13 Thread Sudhir Patil
Ok. Thanks Alexandr. On Wednesday, November 13, 2019, Alexandr Shapkin wrote: > Thin client does not store data and is not a part of a cluster, instead, > you can think of it as an interface of accessing and manipulating your data. > > Please, note, that you can not configure these properties

Ignite.Net Read through approach - error : could not create .Net cachestore

2019-11-13 Thread Sudhir Patil
Hi All, I have started 2 nodes - 1) Server node - using Ignition.Start. On Server node cache is created with ReadThrough = true with CacheStoreFactory value set to property implementation. 2) Client one - using Ignition.Start (for client with Ignition.ClientMode = true). With this when i do 1st

Re: Ignite.Net configuration for storing large cache data

2019-11-13 Thread Sudhir Patil
Thanks Pavel. 1) i will look into this. 2) ok. 3) DefaultDataRegionConfiguration - What is default unit used for different properties to set size values ? Is it byte?? For - By default, only one region is configured with max size set to 20% of available RAM. What is the way to set max size ?

Re: excessive timeouts and load on NODE_JOINED and NODE_LEFT events

2019-11-13 Thread Maksim Stepachev
Hi, I suppose this fix should fix your problem https://issues.apache.org/jira/browse/IGNITE-9558 . ср, 13 нояб. 2019 г. в 10:43, ihalilaltun : > Hi, > > Timeouts always starts when NODE_JOINED event has been fired, i am not sure > if this event causes PME to take place or not. > > As I said

Re: Ignite.Net Read through approach - error : could not create .Net cachestore

2019-11-13 Thread Sudhir Patil
I am extremely sorry for typing mistakes. Here is correct details Hi All, I have started 2 nodes - 1) Server node - using Ignition.Start. On Server node cache is created with ReadThrough = true with CacheStoreFactory value set to property implementation. 2) Client one - using Ignition.Start

unsubscribe

2019-11-13 Thread Hitesh
unsubscribe -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Confusion about how to connect to Kubernetes cluster remotely from client app

2019-11-13 Thread Ilya Kasnacheev
Hello! You can surely use REST from .Net, but writing code for such use is left as exercise for reader. You can also use .Net thin client, with API & description available in docs: https://apacheignite-net.readme.io/docs/thin-client Regards, -- Ilya Kasnacheev ср, 13 нояб. 2019 г. в 01:43,

Re: excessive timeouts and load on NODE_JOINED and NODE_LEFT events

2019-11-13 Thread ihalilaltun
Hi Maksim, Thanks, i think it will regards - İbrahim Halil Altun Senior Software Engineer @ Segmentify -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Re: Ignite.Net configuration for storing large cache data

2019-11-13 Thread Alexandr Shapkin
Thin client does not store data and is not a part of a cluster, instead, you can think of it as an interface of accessing and manipulating your data.Please, note, that you can not configure these properties for IgniteClientConfiguration.The data region configuration makes sense only for server

Re: Ignite.Net configuration for storing large cache data

2019-11-13 Thread Pavel Tupitsyn
Yes, region sizes are in bytes (thanks for pointing this out, I'll update the XMLDoc) Yes, MaxSize is the right property. Docs say it should not be *less* than 10 mb. Here is an example of C# config with multiple regions: var cfg = new IgniteConfiguration { DataStorageConfiguration = new

Re: Ignite.Net configuration for storing large cache data

2019-11-13 Thread Sudhir Patil
Outside this question, such large data will not work with thin client??? Regards, Sudhir On Wednesday, November 13, 2019, Pavel Tupitsyn wrote: > Yes, region sizes are in bytes (thanks for pointing this out, I'll update > the XMLDoc) > Yes, MaxSize is the right property. Docs say it should not

Is there a way to convert a cache (setup from the XML config file) to a table that we can query?

2019-11-13 Thread devinbost
Hi, We set up a cache in the default-config.xml file, but we're having trouble getting visibility into the cache's data. We'd like to be able to use SQL queries (or something we can run in an ad-hoc CLI or web tool) to occasionally inspect the data. 1. Is there a way to inspect the data in an

Re: Confusion about how to connect to Kubernetes cluster remotely from client app

2019-11-13 Thread Denis Magda
What prevents you from deploying the application within the same K8 environment as a pod? If the thick client and the servers are within the same network then you won't have any hurdles at all. That's the best approach. Otherwise, you need to a) expose K8 network if you want to connect from a

Re: Ignite.Net Read through approach - error : could not create .Net cachestore

2019-11-13 Thread Sudhir Patil
Alexandr, Ok. But what is type of those 2 nodes ??? On Wednesday, November 13, 2019, Alexandr Shapkin wrote: > Sudhir, > > > > > Are there any samples for ReadThrough operation done from normal ignite > client node? > > > > I tried the AspNetCachestore example with two nodes and it worked well

Re: Ignite query performance with lots of joins

2019-11-13 Thread spoutnik_be
Hi, Bad news is that there is no short term solution, good news are that the issue/case is acknowledged and that Ignite is moving forward. See approach: https://cwiki.apache.org/confluence/display/IGNITE/IEP-37%3A+New+query+execution+engine -- Sent from:

RE: Re: Ignite.Net Read through approach - error : could not create .Net cachestore

2019-11-13 Thread Alexandr Shapkin
Sudhir, What exception are you getting? Can you share a full stacktrace/code snippet?Most likely you have an issue with the underlying DB configuration. You could have a look at Pavel’s examples for 3rd party persistence: https://github.com/ptupitsyn/ignite-net-examples From: Sudhir PatilSent:

Re: Ignite.Net Read through approach - error : could not create .Net cachestore

2019-11-13 Thread Sudhir Patil
Ok. That is good to hear Maybe I need to check configurations. On Wednesday, November 13, 2019, Alexandr Shapkin wrote: > I configured 1 server node with : > > > > Name = "cars", > > CacheStoreFactory = new AdoNetCacheStoreFactory(), > > KeepBinaryInStore = true, > > ReadThrough = true, > >

Re: Ignite.Net Read through approach - error : could not create .Net cachestore

2019-11-13 Thread Sudhir Patil
Alexandr, Thanks for details. I can not share snippet now but I will try to type it later...:( I am getting cacheexception with message as - could not create .Net CacheStore. >From ignite samples i rendered same sample code e.g. AspNetCachestore one. This works when used with thin client but

Re: Ignite.Net Read through approach - error : could not create .Net cachestore

2019-11-13 Thread Sudhir Patil
Hi All, I am really struggling with this exception / error message. I am using same configurations on client & server node but still it is giving same error / exception - could not create .Net CacheStore. Can someone please help / provide what is issue here?? Regards, Sudhir On Wednesday,

RE: Re: Ignite.Net Read through approach - error : could not create .Net cachestore

2019-11-13 Thread Alexandr Shapkin
Sudhir, > Are there any samples for ReadThrough operation done from normal ignite client node? I tried the AspNetCachestore example with two nodes and it worked well for me. > I can not share snippet now but I will try to type it later...:(That’s ok. Feel free to add details whenever you get

Re: Ignite.Net Read through approach - error : could not create .Net cachestore

2019-11-13 Thread Sudhir Patil
Alexandr, Can you share the code u used + configuration ? I am not able to send snippets as i have to type in and can't send those from my work. On Wednesday, November 13, 2019, Alexandr Shapkin wrote: > I configured 1 server node with : > > > > Name = "cars", > > CacheStoreFactory = new

Re: Not able to start second server node due to authentication failure

2019-11-13 Thread Maksim Stepachev
Hi, Look at the parent of DataStreamerPermissionCheckTest. This code contains a test implementation of security: org.apache.ignite.internal.processors.security.impl.* ср, 13 нояб. 2019 г. в 15:24, Sankar Ramiah : > Thank you Andei and Zaheer for your response. > > I have tried setting a

RE: Re: Ignite.Net Read through approach - error : could not create .Net cachestore

2019-11-13 Thread Alexandr Shapkin
I configured 1 server node with : Name = "cars",CacheStoreFactory = new AdoNetCacheStoreFactory(),KeepBinaryInStore = true,ReadThrough = true,WriteThrough = true The second one with ClientMode = true just accesses the cache by its name and performs all operations. From: Sudhir PatilSent:

Re: Ignite.Net Read through approach - error : could not create .Net cachestore

2019-11-13 Thread Sudhir Patil
Hi All, Server node is started & cache is created with configuration like var cacheCfg = new CacheConfiguration { Name = "cars", CacheStoreFactory = new AdoNetCacheStoreFactory(), KeepBinaryInStore = true,

Question about memory when uploading CSV using .NET DataStreamer

2019-11-13 Thread camer314
I have a large CSV file (50 million rows) that i wish to upload to a cache. I am using .NET and a DataStreamer from my application which is designated as a client only node. What i dont understand is i quickly run out of memory on my C# streaming (client) application while my data node (an

Re: Ignite.Net Read through approach - error : could not create .Net cachestore

2019-11-13 Thread Mikael
Hi! The client should not have to pass any cache configuration, once the cache is created in the server, you should just be able to get the cache, I do not see any reason that should not work but I have never used .NET so it is possible there is some hickup there that I am not seeing. You