Call for Speakers: Apache Ignite at ApacheCon: Big Data Spain 2016

Hello Igniters, ApacheCon Europe is coming November, 2016. I just submitted 3 talks on Apache Ignite: - Apache Ignite - Path to Converged Data Platform - Shared Memory Layer and Faster SQL for Spark Applications - Apache Ignite - JCache and Beyond If you are a user or a developer of Apache

Re: Apache Ignite - New Release

IGNITE-3466 is not a JDBC-only issue. This happens because 'select *' query returns all the fields including _kay and _val which are created by Ignite, not by user. This is actually a usability issue that pops up every now and then. This is very counterintuitive that we return the fields that user

Re: Ignite 2.0 tasks/roadmap

On Fri, Jul 15, 2016 at 1:49 AM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > > > > > > > > I know there is IgniteDataStreamer for writing cache, but how about > > > reading cache as stream for iterate all elements with scan performane > > 1-3M > > > tuple/sec? > > > > > > > We already

Re: Failed to wait for initial partition map exchange

> > Alexey, I like the idea in general, but killing non-responsive nodes seems > a bit drastic to me. How about this approach: > > - print out IDs/IPs of non-responsive nodes at all times > - introduce a certain kill timeout for non-responsive nodes (-1 means > disabled) > - the timeout should be

Re: Ignite 2.0 tasks/roadmap

> > > > > I know there is IgniteDataStreamer for writing cache, but how about > > reading cache as stream for iterate all elements with scan performane > 1-3M > > tuple/sec? > > > > We already have Scan queries which allow for paginated iteration with > filters. Are you suggesting something beyond

Re: Ignite 2.0 tasks/roadmap

​Great stuff! Guys, please go ahead and file corresponding tickets or reassign the fix version to 2.0 if a ticket exists so that we keep track of the scope. It would also be great if you review the ones I created and see if they make sense.

Re: kick off a discussion

On Thu, Jul 14, 2016 at 9:07 PM, Konstantin Boudnik wrote: > On Wed, Jul 13, 2016 at 05:30AM, Dmitriy Setrakyan wrote: > > Hi Alex, > > > > I believe most of your comments have to do with disk-based functionality, > > especially in regard to backups, snapshots, etc. However,

[jira] [Created] (IGNITE-3484) MVCC for cache data structures

Alexey Goncharuk created IGNITE-3484: Summary: MVCC for cache data structures Key: IGNITE-3484 URL: https://issues.apache.org/jira/browse/IGNITE-3484 Project: Ignite Issue Type: Sub-task

Re: Ignite 2.0 tasks/roadmap

On Fri, Jul 15, 2016 at 12:26 AM, AndreyVel wrote: > Good feature may be Aggregated cache - analog materialized view in DBMS > Aggregated cache is great for performance (KPI, analytecal reports). > Do you mean a copy of the aggregated data in another cache? What happens

Re: Ignite 2.0 tasks/roadmap

Good feature may be Aggregated cache - analog materialized view in DBMS Aggregated cache is great for performance (KPI, analytecal reports). Recently I learned network traffic between nodes when node restart/startup and do no found any compressing for transferred data. I know there is

Re: Failed to wait for initial partition map exchange

On Fri, Jul 15, 2016 at 12:02 AM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > This is a cross-post from a user list. > > We faced this issue for a lot of times before and got a lot of users > complaining about the whole cluster freeze. We can protect a cluster from > such a situation

Re: Failed to wait for initial partition map exchange

This is a cross-post from a user list. We faced this issue for a lot of times before and got a lot of users complaining about the whole cluster freeze. We can protect a cluster from such a situation simply by dropping non-responsive nodes from the cluster. Of course, we need to get to the bottom

Re: Ignite monitoring

Yakov, as for now I just have well structured scripts to setup Ganglia agent on Ignite hosts to monitor system metrics like CPU, RAM, IO and etc (this scripts already included in Ignite 1.6). Also experimented with displaying JVM metrics by providing java agent and specifying MBeans to collect

Re: Ignite 2.0 tasks/roadmap

Several points from my side: 1) Drop support for null cache names 2) rework Visor data transfer objects to binary format in order to easily extend them if needed.

Re: kick off a discussion

On Wed, Jul 13, 2016 at 05:30AM, Dmitriy Setrakyan wrote: > Hi Alex, > > I believe most of your comments have to do with disk-based functionality, > especially in regard to backups, snapshots, etc. However, Ignite is > currently an in-memory system, at least for the nearest future. Let me know >

Re: [jira] [Created] (IGNITE-2527) IndexOutOfBoundsException in scheduler future

Hi, I would like to pick up this ticket. Please assign me this ticket. Thanks, Milap Wadhwa On 2 February 2016 at 10:50, Valentin Kulichenko (JIRA) wrote: > Valentin Kulichenko created IGNITE-2527: > --- > > Summary:

[GitHub] ignite pull request #869: ignite-1525

GitHub user avinogradovgg opened a pull request: https://github.com/apache/ignite/pull/869 ignite-1525 You can merge this pull request into a Git repository by running: $ git pull https://github.com/avinogradovgg/ignite ignite-1525 Alternatively you can review and apply

[jira] [Created] (IGNITE-3483) Regression: service is being deployed on the client

Denis Magda created IGNITE-3483: --- Summary: Regression: service is being deployed on the client Key: IGNITE-3483 URL: https://issues.apache.org/jira/browse/IGNITE-3483 Project: Ignite Issue

Re: Ignite 2.0 tasks/roadmap

Yakov, I am not sure we fixed it. Plus sometimes we encode missing value as -1, so it is written as 4 bytes still. Dmitry, to my knowledge Unsafe will be available only when special VM flag is set. It is not a problem for ignite.sh, but may cause usability issues when running in embedded mode.

[jira] [Created] (IGNITE-3482) Implement lazy query execution in H2.

Sergi Vladykin created IGNITE-3482: -- Summary: Implement lazy query execution in H2. Key: IGNITE-3482 URL: https://issues.apache.org/jira/browse/IGNITE-3482 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-3481) Implement lazy query execution in H2.

Sergi Vladykin created IGNITE-3481: -- Summary: Implement lazy query execution in H2. Key: IGNITE-3481 URL: https://issues.apache.org/jira/browse/IGNITE-3481 Project: Ignite Issue Type:

Re: Ignite 2.0 tasks/roadmap

Vova, why Unsafe removal? To my knowledge, Unsafe still remains in Java 9, no? On Thu, Jul 14, 2016 at 4:09 PM, Vladimir Ozerov wrote: > Several points from my side: > 1) Java 9 support - Unsafe removal, modules, etc.. > 2) Rework our "messages" subsystem - we always

Re: Ignite 2.0 tasks/roadmap

Vova, 2) even long zero is encoded as 1 byte now. Do you think it is a problem? --Yakov 2016-07-14 16:09 GMT+03:00 Vladimir Ozerov : > Several points from my side: > 1) Java 9 support - Unsafe removal, modules, etc.. > 2) Rework our "messages" subsystem - we always

Re: Ignite 2.0 tasks/roadmap

Several points from my side: 1) Java 9 support - Unsafe removal, modules, etc.. 2) Rework our "messages" subsystem - we always read/write all fields, thus transferring lots of zeros without any reason. We should support branching. 3) Review all messages (especially cache, double-especially -

Re: [jira] [Created] (IGNITE-3475) Topology aware IP finder

Great, added you to the contributors list and assigned the ticket on you. Here you will find basic information on the contribution process http://ignite.apache.org/community/contribute.html Let us know if you have any question. — Denis > On

Re: [jira] [Created] (IGNITE-3475) Topology aware IP finder

I'm "stash" on Jira. (That's a Polish nickname, not a code management tool ;-) -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/jira-Created-IGNITE-3475-Topology-aware-IP-finder-tp9857p9876.html Sent from the Apache Ignite Developers mailing list archive

Re: Apache Ignite - New Release

All these issues seem to be related to Jdbc driver rather than to SQL engine. I think Andrey Gura was the last who worked on it. IMO they must be easy to fix. Sergi On Thu, Jul 14, 2016 at 9:06 AM, Denis Magda wrote: > Yakov, > > I'm not the one who is eligible for review

Re: Ignite 2.0 tasks/roadmap

Alex, a lot of excitement for Ignite-2.0 from my side! =) I agree with your points and I will take a close look at them in the nearest future. Here are some suggestions from me. I don't remember if I shared my thoughts on moving to single TCP port per node. So, I filed a new ticket -

Re: Ignite monitoring

Igor, can you please share the changes to scripts you did to support monitoring? Can it be done by defining and exporting JAVA_OPTS env variable and then launching ignite.sh? Thanks! --Yakov 2016-07-13 22:45 GMT+03:00 Igor Rudyak : > Hi guys, > > While experimenting with

Re: Apache Ignite - New Release

Yakov, I'm not the one who is eligible for review of IGNITE-3389. Assigned it on Andrey Gura. Andrey please find time for review. Alexander B. when you need a review please send an email to the dev list and someone will assist you. As for IGNITE-3466, IGNITE-3467 and 3468 Sergi's opinion is