Upgrading from 1.3 to 1.4

Hi, I'm upgrading from 1.3 to 1.4. Some notes/questions: I implemented my own GridComponent (in order to implement a security plugin), after the upgrade I had to implement these to new methods @Override public void onDisconnected(IgniteFuture i) throws IgniteCheckedException { }

Re: [RESULT] [VOTE] Apache Ignite 1.4.0 Release (RC1)

Hi, I'm looking forward to upgrade to 1.4 ! I can't see maven artifacts on maven central -- Enrico 2015-09-28 19:52 GMT+02:00 Konstantin Boudnik : > Congrats! Well timed to @ApacheCon too! > > Please make sure to do the announcement cc'ed to annou...@apache.org > > Thanks >

Re: How to config Ignite on hadoop

Hi, xukun. You start Ignite using command "./bin/ignite.sh". With this command default configuration file ${IGNITE_HOME}/config/default-config.xml is picked. If you want to use "example-igfs.xml", please start Ignite as follows: "./bin/ignite.sh examples/config/filesystem/example-igfs.xml". Let

Re: [RESULT] [VOTE] Apache Ignite 1.4.0 Release (RC1)

Enrico, Please try again, everything seems to be ok: https://repo.maven.apache.org/maven2/org/apache/ignite/ignite-core/ On Tue, Sep 29, 2015 at 10:08 AM, Enrico Olivelli wrote: > Hi, > I'm looking forward to upgrade to 1.4 ! I can't see maven artifacts on > maven central

Re: How to config Ignite on hadoop

Hi, Xukun, you have fs.defaultFS hdfs://clcluster/ in core-sire.xml. There is nothing wrong in that, but that forces you to specify a full URI in Hadoop client commands. When you're connecting to IGFS, the full URI should have form ://@:/ , with part being mandatory. In you

Re: How to config Ignite on hadoop

We submitted https://issues.apache.org/jira/browse/IGNITE-1566 on this. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-to-config-Ignite-on-hadoop-tp1306p1516.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Upgrading from 1.3 to 1.4

Enrico, Classes inside internal package has no compatibility guarantee between releases. IgniteConfiguration.consistentId can't guarantee correct node identifying. Usage of user-attribute seems to be a correct choice. On Tue, Sep 29, 2015 at 11:07 AM, Enrico Olivelli

Re: Hibernate L2 cache transactions

Hi Val: Our test system has been locked down due to a business deliverable and I can't restart it at the moment. I'm looking for a window to do so and hope to be able to get you some logs. I'm also keen to get this solved so let's sit tight for the time being. Dan -- View this message in

Re: Exception during node initialization

First of all, I would upgrade to 1.4 and see if it works there as you expect. There were fixes for SQL failover since 1.1. Can you describe you deployment in more details? Do you have a web-application with an embedded Ignite client node and several server nodes that this client node connects to?

Re: Exception during node initialization

The client is in this case an automated test, which issues REST requests to the application (which hosts the grid). The fact that the client joins the ignite cluster as a client with a sole purpose of pre-populating some caches is irrelevant to my question. What is happening here is that queries

Re: Exception during node initialization

vpasynkova wrote > The client (even though it does join the ignite cluster) doesn't query the > cache directly. It sends http requests to the nodes, which in turn query > the cache using query API. We are using Ignite verison 1.1.0. If the client joins the cluster, I don't see any reason to use

Re: Exception during node initialization

Hi, Can you please properly subscribe to the user list so we can get email notifications? You can refer to these instructions for more info: http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1 vpasynkova wrote > I have a client node in my multi-node