Re: Ignite client thread amount control

Hi vkulichenko, Thanks for the reply! I already subscribed. What if I have multiple users query at the same time? One user hold the Ignite client and the others just wait? -- View this message in context:

how to control client node connect to server node, not the other way around

hi guys, The situation is this: we want to have C# Ignite Client node run in A environment we already have 3 Java Ignite Server nodes in B environment we only opened firewall that A can access B at port 47500-47509 and 47100-47109 we don't want to let B access any ports at A when we try to start

Ignite stuck at cache.put()

Hi Ignite community, when I tried to run some junit tests against Ignite, my tests are basically some Ignite API(put, getAndPut, getAndReplace...) with a little logic.. if i run these tests one at a time, they all can pass. but if i run all of them, i found it stuck after 2 or 3 tests, when I

(.NET) localPort and localPortRange question

Hi Ignite, I want to start up a .NET Ignite client to connect to my existing Ignite servers. for the firewall, I opened 47500-47509 and 47100-47109 both way between servers and clients in my .NET Ignite client log below, I have 2 questions: 1. do i need to worry about the DEBUG log like this:

Re: Ignite stuck at cache.put()

ok.. from the thread dump, since I configured a cache store, it looks like my database session config problem, b/c if I set read/write through to false, tests will go on, i will check... -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Memory configuration change from 80%(Ignite 2.1) to 20%(Ignite 2.3)??

Thank you.. We have very large data set and several servers with big memory so it will be ok to reach 80% or even 90%. I recommend to highlight this major change in detail in "[ANNOUNCE] Apache Ignite 2.2.0/2.3.0 Released", now I understand in 2.2 release announcement "This release includes a

Memory configuration change from 80%(Ignite 2.1) to 20%(Ignite 2.3)??

Hi Ignite community, In 2.1 version document, it says "By default, Ignite nodes consume up to 80% of the RAM available locally, and in most cases this is the only parameter you might need to change. " https://apacheignite.readme.io/v2.1/docs/memory-configuration In 2.3 version document, it says

Re: when client node connect to server node, server node throws NotSerializableException

ok I tried to comment out this part, the exception I saw on server node before doesn't appear this time... so it looks like Cache Factory/Store problem... but why...

Re: when client node connect to server node, server node throws NotSerializableException

just in case you don't see my replies, I will put all of these in one msg. yes, PIgniteCacheStoreFactory implements javax.cache.configuration.Factory, and this factory extends Serializable. like I said " I already created my own factory to create the cache store to avoid Serialization

Re: when client node connect to server node, server node throws NotSerializableException

yes, PIgniteCacheStoreFactory implements javax.cache.configuration.Factory, and this factory extends Serializable. like I said " I already created my own factory to create the cache store to avoid Serialization problem." without the custom factory, it cannot start any nodes b/c my own cacheStore

when client node connect to server node, server node throws NotSerializableException

Hi Ignite Community, I have a Ignite server node running well, it has a cache store connect to Oracle, and here I already created my own factory to create the cache store to avoid Serialization problem. The server node suppose to store BinaryObject as value. I already tested all the get, put,

Re: when client node connect to server node, server node throws NotSerializableException

my factory is very easy, just override the create method and set attributes, please see the code below. In the cache store i use hibernate to get data from Oracle and convert it to binaryObject and then put into Ignite, so I make people can config their own converter and class. Thanks. import

Re: when client node connect to server node, server node throws NotSerializableException

Hi Andrew, Thanks a lot for all the replies. yes BoConverter implements Serializable, or Ignite will throw NotSerializableException. The "Class" here is actually for hibernate to get data from DB: org.hibernate.Session.get(Class clazz, Serializable id). After getting the data, BoConverter

Re: create two client instance in one JVM to connect two ignite

Hi Shawn, Have you solved this problem? I'm encountering the same problem. how to start two Ignite instances in one JVM, I already have 2 separate Ignite cluster(Server) running. when I start two ignite clients in one JVM, it throws: org.apache.ignite.IgniteException: Default Ignite instance

RE: create two client instance in one JVM to connect two ignite

got it, thanks -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: when client node connect to server node, server node throws NotSerializableException

hi guys, can anyone give some advice... what can you see from this exception server side log when client connect to it: Caused by: java.io.NotSerializableException: org.apache.ignite.internal.processors.cache.binary.IgniteBinaryImpl why it says IgniteBinaryImpl is not serializable? -- Sent

need suggestions for Ignite cluster isolation

Hi Ignite Community, We implemented a generic Ignite cache component in our group, the purpose is that we want everyone in our group can integrate Ignite caches in their applications by simply adding some configurations. But we find that Ignite cluster isolation mechanism is not very friendly

Re: Connection problem between client and server

Hi Denis, Thanks for the analysis. Today we tried to reduce the Java class path(.../lib/*) when start a server node, but it still sends all the jar files(absolute path) to client. and we also find that, it looks like client node sends its info(path...) to server node, and then server node sends

Re: Connection problem between client and server

dev2.cap Hi Denis, the attachment is the packages that server transport to client when connect, we catched it using tool (Microsoft network monitor), can you please take a look and see what you can find? we only configured 12

Re: Connection problem between client and server

Hi Denis, We think the problem is when a client connect to an existing cluster, server node will send the attributes of all the nodes in the cluster(Servers & Clients) to that new client. it will be a lot of data here... We may also have problems for our network configuration, we are still

Re: Connection problem between client and server

Thank you very much Denis, we will give it a try and let you know, I think this should solve our problem. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Limit cache size ?

Hi Val, Is there a max entry limit for a single cache by default? Is it Integer.MAX_VALUE? what will happen if the data amount reaches the limit or pass it? Thanks, Jeff -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Connection problem between client and server

Hi Denis, Does Ignite dev team give any feedback for this? Thanks -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Connection problem between client and server

Hi Ignite community, we are encountering a connection problem, in our production environment, we have 3 Ignite servers with 500G+ of data each, and about 30 Ignite clients running. then we tried to start a simple Ignite client in different environment, Citrix environment, it cannot connect to

Connection reset by peer

Hi guys, we are using Ignite 2.3.0 we have a Ignite cluster in production which has 4 server nodes, recently we found that Ignite throws "Connection reset by peer" occasionally after some complex query, we know it is caused by connection closed while socket reading/writing, but why it closed?

Re: Connection reset by peer

Thank you Ilya, I found that I increased this timeout on server side but not on client side, i guess this should be the problem, it should be the client who closed the connection. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: max size of Ignite cache (not memory size, i mean max amount ofrecords)

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

max size of Ignite cache (not memory size, i mean max amount of records)

hi Igniter, Is there a max limit for the amount of records in one cache? (is it Integer.MAX_VALUE?) what will happen when a cache reaches the max limit and we keep adding data into it? Thanks, Jeff -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite authentication without persistence enabled?

Thanks Mikael! I will have a try. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Ignite authentication without persistence enabled?

Hi Igniters, We want to enable the authentication feature for our Ignite cluster, but currently, it still requires us to enable Ignite native persistence which is not suitable for our use case. Is there a way to enable persistence in IgniteConfiguration but disabled for all the caches inside? If

Re: Ignite authentication without persistence enabled?

I tried to implement the plugin but stuck at specify SecurityCredentials when Ignite node start up, I cannot find any useful information here how to specify it. But I find one Ignite user posted a doable and much easier way to implement Ignite authentication, if anyone wants to do this, you can