Question about client disco-/reconnect behaviour

Hello igniters, I have a question about expected client reconnection behaviour. I have two server nodes and one client node. When everything is connected and one of the servers fails (because it is killed) the client is supposed to 1. Connect to the remaining server transparently, no

RE: Question about client disco-/reconnect behaviour

Hi, Yes, that’s the expected behavior. The client is connected to a single server, not both. If the server it’s connected to is killed, the client will reconnect, producing the events in the process. When you kill one of the servers and the client doesn’t get disconnected it’s probably because

Re: [Bug-7688] DDL does not working properly on sql queries

Hello Muratcan, I am sorry for the late response. > Could you reproduce the problem so far? Yes, the issue is reproduced on the latest 'master' branch. I hope that this bug will be fixed in the nearest release. Anyway, I will keep you posted. Best regards, Slava. -- Sent from:

Re: Re: About Apache Ignite 2.4 with jdk

If possible dont rebuild the source, just use JDK8 instead of JDK7. According my observation in my project JDK8 performs lot better than JDK7 when it comes to lots of computing and dealing with GC and large Heap sizes. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Ignite Client is taking a long time to connect with large number of Client connections

Hi I setup 4 Ignite Servers on 4 different machines. Then Ignite Clients are started on other machine to connect to these Ignite servers. A single Client is getting connected fast. But as the number of Client connections increase the connection time is decreasing. Is there any way to speed up the

New feature with 2.4 - Using 3rd Party Persistence With Native Persistence

Hi Looks like dual persistence - 3rd party (Oracle) and native persistence - both are supported "*Starting with Apache Ignite 2.4, 3rd party persistence can be used together with native persistence*" Can someone explain how this is going to work, how do we config this. Thanks Naveen --

Re:Re: Re: About Apache Ignite 2.4 with jdk

Ignite server can use JDK8. But my system can not support JDK8. So I have to build a JDK7 version for client. Thanks. At 2018-03-19 19:27:24, "piyush" wrote: >If possible dont rebuild the source, just use JDK8 instead of JDK7. >According my observation in my

Re: Re: About Apache Ignite 2.4 with jdk

Hello, Lucky. In Ignite 2.4 JDK 7 support was dropped (see release notes). You will need to use JDK8 or fork Ignite project and try to fix compilation under JDK7. -- Alexey Kuznetsov

Azul Zing JVM with Apache Ignite

Is anybody using Azul's Zing JVM with Ignite ? How was the experience ? Does it help in some way as they claim ? https://www.azul.com/products/zing/ -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: New feature with 2.4 - Using 3rd Party Persistence With Native Persistence

IIgnite persistence is per data region https://apacheignite.readme.io/docs/memory-configuration#section-data-regions On Mon, Mar 19, 2018 at 10:11 AM, Naveen wrote: > Hi > > Looks like dual persistence - 3rd party (Oracle) and native persistence - > both are supported

AW: Question about client disco-/reconnect behaviour

Hey Stan, alright, then my cluster is behaving like it should. Anyways: wouldn’t it be nice to transition to another server node transparently when the “connected” server node goes away? Would that be feasible? One could spare a lot of code messing around with connection status (“Client

Re: Data Loss while upgrading custom jar from old jar in server and client nodes

Hi , Thanks for the reply Did you restart all nodes after updating jar-files? Ans) Yes i have restarted client and server node after updated the jar file. I have shared a sample project on github ,so you can have look at through following link Link:

Re: Documentation Ignite 2.3.0

Hi Humphrey, Thanks for bringing this to our attention. I've updated the doc to make it vivider. As for the priority, yes, I see the confusion, but this is exactly how it works for now - the system priority has a bigger priority. -- Denis On Tue, Mar 13, 2018 at 2:07 AM, Humphrey

Basic Subquery Failure

I'm running 2.4.0 locally on a single node and I'm trying to get a basic SQL subquery to work and I seem to be having problems. The following is the simplest thing I could find to reproduce to the error: The error is as follows: Any help for what I'm doing wrong here would be appreciated.

Re: Basic Subquery Failure

Hi, I can see neither the query nor the stack trace. Most likely you attached them as images. Please paste as text or HTML text. -- Denis On Mon, Mar 19, 2018 at 4:56 PM, besquared wrote: > I'm running 2.4.0 locally on a single node and I'm trying to get a basic > SQL

Re: New feature with 2.4 - Using 3rd Party Persistence With Native Persistence

Hi Naveen, Here is a documentation section that answers your question: https://apacheignite.readme.io/docs/3rd-party-store#section-using-3rd-party-persistence-together-with-ignite-persistence -- Denis On Mon, Mar 19, 2018 at 7:11 AM, Naveen wrote: > Hi > > Looks

Re: Disk Persistence Performance

Hi, That's an answer to the question of how much Ignite with the persistence enabled is faster than other NoSQL databases: https://www.gridgain.com/resources/blog/apacher-ignitetm-and-apacher-cassandratm-benchmarks-power-in-memory-computing I didnt know we could define multiple data regions and

Re: And again... Failed to get page IO instance (page content is corrupted)

Sergey, Arseny, We've fixed a number of similar issues in 2.4 Ignite version. However, this one, ExpiryPolicy with persistence still buggy. Here is a ticket for it [1]. The ticket has a PR that should fix this issue, but it broke backward compatibility as TTLManager, who responsible for expired

DataFrame support for Apache Spark 1.6

I'm trying to save spark dataframe to Ignite 2.4 using Apache Spark 1.6. But it failed, with the following error Exception in thread "main" java.util.ServiceConfigurationError: org.apache.spark.sql.sources.DataSourceRegister: Provider org.apache.ignite.spark.impl.IgniteRelationProvider could not

About Apache Ignite 2.4 with jdk

Hi, Apache Ignite 2.4 is built in JDK1.8. Can you provide a JDK1.7 version? Or Give the dependency jar list ,then I can build it myself. Thanks very much.

Re: And again... Failed to get page IO instance (page content is corrupted)

Hi, Arseny We are using ext4 with defaults,noatime,lazytime options on Virtuozzo Linux release 7.3. We have refactored parts of logic and abandoned the use of any expired policies(( On Thu, Mar 15, 2018 at 7:34 PM, Arseny Kovalchuk < arseny.kovalc...@synesis.ru> wrote: > Hi guys. > > I've

Re: About Apache Ignite 2.4 with jdk

Hello, Lucky. You can download source of Ignite from official repository: https://ignite.apache.org/download.cgi#sources В Пн, 19/03/2018 в 16:39 +0800, Lucky пишет: > Hi, >Apache Ignite 2.4 is built in JDK1.8. > Can you provide a JDK1.7 version? > Or Give the dependency jar list

Re: Ignite Expiry Inconsistency with Native Persistence

If you can send me the working code I can try to compare what’s missing. On Thu, Mar 15, 2018 at 10:14 AM Subash Chaturanga wrote: > Here’s my code. > > *public static void *main(String[] args) *throws*InterruptedException { > > String region = *"4GRegion"*; >

Re: Protobuf value objects, SCAN query and Indexes

Hi AU, 1. You can try to convert Protobuf object to Ignite BinaryObject [1] to store it in cache. Please, take a look at Binary Object concept [2]. 2. Then you can try to create index via SQL "CREATE INDEX" clause [3]. [1]

Re: DataFrame support for Apache Spark 1.6

Hello, Ray. Currently, There is no plans to support Spark 1.6 in Ignite. I doubt if it can be done without significat changes in existing code base. Anyway, you can create a ticket [1]. And I will try to look what can be done. [1] https://issues.apache.org/jira/browse/IGNITE В Пн, 19/03/2018 в