Re: Not able to join cluster with Zookeeper based IP finder

Nikolay, can you please join this thread and point out how to build cluster using docker? --Yakov 2016-12-10 5:48 GMT+07:00 ghughal : > Yakov - I'll try to see if I can remove AddressResolver. The main reason > for > adding it was because we are running it inside docker

Re: Database Connection Pooling

Hi Saji, I’m not aware of such a concept in Ignite. Most likely it’s somehow related to JDBC and ODBC drivers supported by the product https://apacheignite.readme.io/docs/jdbc-driver https://apacheignite.readme.io/docs/odbc-driver

Re: Performance with increase in node

Sam, See below > On Dec 9, 2016, at 11:24 AM, javastuff@gmail.com wrote: > > Thank you Denis. Are you saying test application should not act as server > node for Ignite and it should be client node? it does not matter. Most likely an application will connect to a cluster in the client

Re: Not able to join cluster with Zookeeper based IP finder

Yakov - I'll try to see if I can remove AddressResolver. The main reason for adding it was because we are running it inside docker container and if we run docker in BRIDGE mode then the IP address of host is not available to ignite running inside docker container. -- View this message in

enabling log4j, read previous post, still have issues

Hi, I've tried enabling log4j simply by including the ignite-log4j library. However, it does not seem to have an effect. I've also read that to enable Log4J module we should move the "optional/ignite-log4j" folder to the libs directory before running "ignite.bat". My question is in order to

Re: Cluster hung after a node killed

Hi Val, Did you had chance to look at attached sample program? Did it help figuring out what is going on? -Sam -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cluster-hung-after-a-node-killed-tp8965p9465.html Sent from the Apache Ignite Users mailing list

Re: Performance with increase in node

Thank you Denis. Are you saying test application should not act as server node for Ignite and it should be client node? it does not matter. Regarding Yardstick, I had difficulty setting up no credential user to launch remote commands, so not able to make it fully functional. On other side

Re: Blogging about new .NET features

Excellent! Prachi, please post the blog on DZone. — Denis > On Dec 9, 2016, at 6:07 AM, Pavel Tupitsyn wrote: > > There you go: https://ptupitsyn.github.io/Whats-New-In-Ignite-Net-1-8/ > > > On Wed, Nov 30,

Re: Blogging about new .NET features

There you go: https://ptupitsyn.github.io/Whats-New-In-Ignite-Net-1-8/ On Wed, Nov 30, 2016 at 4:35 AM, Denis Magda wrote: > Cos, > > This sounds interesting. Did it help to promote BigTop somehow? > > As I understand the blogging engine lacks of advanced text and code >

Re: Affinity based on the fields NOT in the key

Hello Alexey, yes it does thanks. No that I know that it is the way of doing it, it's fine. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Affinity-based-on-the-fields-NOT-in-the-key-tp9457p9460.html Sent from the Apache Ignite Users mailing list archive at

Re: Affinity based on the fields NOT in the key

Hello Steve, You are right, Ignite requires all fields participating in affinity calculation to be included in the key. The main reason behind this restriction is that Ignite is a distributed system and it is an absolute requirement to be able to calculate affinity based only on a key. Imagine

Affinity based on the fields NOT in the key

Hello, first let me apologize if there is any double submit. I think that my first post on this subject was not visible because I did not do the subscription completely. My understanding is that affinities can only be based on fields in the key. Is this correct? This seems counter-intuitive

Re: How can I call a Java Service from .NET

Thank you, Denis, looks good to me. On Thu, Dec 8, 2016 at 9:53 PM, Denis Magda wrote: > Pavel, > > Fixed all the places including that .NET block. > > — > Denis > > On Dec 8, 2016, at 1:35 AM, Pavel Tupitsyn wrote: > > Denis, > > There is a callout at

Re: Fetching large number of records

Hi Val, Seems ResultSet#next() not fetching next page. i tried the following snippet - JdbcConnection conn = (JdbcConnection)DriverManager.getConnection(""); String sql = "select count from Test_counts where id is not null limit 1000"; PreparedStatement statement = conn.prepareStatement(sql);