Re: Monitoring of active transactions

It seems that the community (including me) really would like to see this feature in Ignite. Ilya, can you create a ticket and submit it for review? D. On Fri, Sep 8, 2017 at 7:15 AM, Anton Vinogradov wrote: > Ilya, > > We extremely need this! > > Txs and Locks info should be collected on each

Re: [VOTE] Apache Ignite 2.2.0 RC1

Igniters... at this point this is becoming almost amusing to watch. All we aimed to do is fix one issue with memory consumption, then bunch of community members started pouring in other fixes into this "emergency" release, and as a result, nothing works. I propose to go back to the original goal -

Re: Ignite Benchmarking Rules

Alexey, I completely agree. However, for the benchmarks to be useful, then need to be run on the same hardware all the time. Apache Ignite does not have servers sitting around, available to run the benchmarks. Would be nice to see how other projects address it. Can Amazon donate servers for the Ap

Re: Ignite.NET static analysis with NDepend

Pavel, nice blog! If there is a way to integrate nDepend into Ignite builds, would be nice. D. On Thu, Sep 14, 2017 at 6:38 AM, Pavel Tupitsyn wrote: > Igniters, > > NDepend [1] has contacted me and provided us with build machine licenses > for their tool. > I've played with it for some time a

Re: Static code analysis for Java

Hm... LGTM tool looks nice! Check out all the errors it already found in Ignite :) https://lgtm.com/projects/g/apache/ignite/alerts/?mode=list&severity=error D. On Thu, Sep 14, 2017 at 9:21 AM, Pavel Tupitsyn wrote: > Yes, we can run IDEA inspections, and this is the simplest thing to do, > si

Re: Durable Memory and Ignite Persistence Tuning

Completely agree with Nikita. Why not add this information here? https://apacheignite.readme.io/docs/durable-memory-tuning D. On Wed, Sep 13, 2017 at 2:54 AM, Nikita Ivanov wrote: > Excellent work on this... This should be expanded and be prominently placed > in our docs/tutorials/javadocs/etc

Re: Experimental features - thin client protocol as a first candidate

Vladimir, As far as the client, I don't think we need to call it experimental. An "experimental" feature sounds like it might explode if you come close :) How about we have client protocol versions instead? Then each Ignite release can announce which protocol versions it is compatible with. D.

Re: Expiry policy for Cache.invoke

Denis, I agree that the behavior should be consistent, but you will not find anything about transactions in JCache. To my knowledge, JCache does not have transactions. I would file a ticket about the issue you found, so the community could address it. If you are interested, perhaps you can contri

Re: Specifying schema name with thin JDBC driver

Vova, I think we need to abandon this "schema-name = table name" legacy. It is impossible to explain. Also, I would like to understand the current behavior. When I connect through JDBC, which schema am I connecting to? How do I know which schemas are there? D. On Wed, Sep 13, 2017 at 1:19 AM, Vl

Re: guard() and checkClusterState() checks in Ignite Kernal

Is there a ticket for this change? On Tue, Sep 12, 2017 at 4:25 AM, Ilya Kasnacheev wrote: > Rehi, > > After some discussions https://github.com/apache/ignite/pull/2526 seems to > have correct changeset that covers two methods which seem to have been > overlooked before. > It's already reviewed

Re: sql documentation

02:19, Denis Magda wrote: > > > Please check you inbox. > > > > — > > Denis > > > > > On Sep 8, 2017, at 3:38 PM, Dmitriy Setrakyan > > wrote: > > > > > > Denis, > > > > > > Can you please add me as an admin to that site? > >

Re: New thin client and interfaces/facades

Vladimir, I disagree. We already have client mode which support the full Ignite API. Here we are talking about the new client binary protocol. To my knowledge, the following APIs can be implemented over the new binary protocol: - JDBC - ODBC - REST - .NET Thin All these protocols are already cu

Re: Persistence per memory policy configuration

To extend on the idea of 2 different policies for memory and persistence, can we have 2 completely different configuration classes? - MemoryPolicy - PersistentMemoryPolicy (extends MemoryPolicy?) Every cache should be associated with either MemoryPolicy or PersistentMemoryPolicy, but not both.

Re: ContinuousQueryWithTransformer implementation questions - 2

Vladimir, are their factories for the proposed listeners? On Tue, Sep 12, 2017 at 7:52 AM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Vladimir, > > Can you please clarify how the proposed API will work? > > My opinion is that our query API is big piece of ... you know, especially > >

Re: How to configure new thin client connector on the server?

In that case, ClientConnectorConfiguration seems like a good name. Can the migration be done in such a way that the old configuration will be deprecated, but still work? D. On Tue, Sep 12, 2017 at 2:34 AM, Vladimir Ozerov wrote: > Dima, > > Yes. > > On Tue, Sep 12, 2017 at 1

Fwd: Re: When cache node switch between primary and backup any notification be received?

: Dmitriy Setrakyan Date: Mon, Sep 11, 2017 at 10:41 PM Subject: Re: Re: When cache node switch between primary and backup any notification be received? To: user Cc: aa...@tophold.com On Mon, Sep 11, 2017 at 6:54 PM, aa...@tophold.com wrote: > Thanks Alexey! what we real want, we deploy serv

Re: AffinityKeyMapper alternatives

On Mon, Sep 11, 2017 at 4:47 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Even if CacheKeyConfiguration is part of CacheConfiguration, the affinity > key field name can be provided only on cache startup. In many cases this > name can be resolved only based on the actual key in

Re: Ignite Benchmarking page on readme.io

On Mon, Sep 11, 2017 at 6:10 PM, Denis Magda wrote: > 1. It’s fine to have it under the current section that will include > testing related documentation proposed by Yakov in other discussion thread. > I think we should avoid having 1-page sections. They look bad. Also, benchmarking is a very co

Re: Ignite Benchmarking page on readme.io

: > > Thanks. Here is a direct link on the new page about Ignite > Benchmarking(hidden for now): https://apacheignite.readme. > io/v2.1/docs/perfomance-tests. Please review. > Mostly it was aggregated from the information in the repo > > 07.09.2017, 20:57, "Dmitriy Setr

Re: AffinityKeyMapper alternatives

On Mon, Sep 11, 2017 at 4:01 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Guys, > > Some time ago we deprecated AffinityKeyMapper in favor > of CacheKeyConfiguration#affinityKeyFieldName and AffinityKeyMapped > annotation. While I understand the reasons why we did this, I thin

Re: How to configure new thin client connector on the server?

In my opinion all clients, including JDBC, ODBC, and REST should be implemented over the same protocol and we should not have the protocol mess we have today. Vladimir, does your suggestion about ODBC and JDBC include migration to the new client? D. On Mon, Sep 11, 2017 at 12:39 AM, Vladimir Oze

Re: IGNITE-5655: Mixing binary string encodings in Ignite cluster

hould either pass information about this encoding too all > > cluster members and to all clients, so that they construct correct binary > > object in the first place, or you should re-convert binary object on fly, > > this is what I suggested. No simple solution here. > > >

Re: NPE from service processor

erviceProcessor > shouldn't have changed this behavior in any way. > It must be somehow connected with a lifecycle of IgniteKernal and other > components. A reproducing example would help to find the problem. > > - Denis > > пн, 11 сент. 2017 г. в 1:32, Dmitriy Setrakyan : &

Re: Deprecate IgniteCache.query(Query, IgniteClosure)

On Mon, Sep 11, 2017 at 7:13 AM, Vladimir Ozerov wrote: > Igniters, > > We have that very strange method, which accepts transformer. It is only > supported for ScanQuery and we do not have any plans to extend it in > future. > > Let's just deprecate it and add transformer to ScanQuery directly. >

NPE from service processor

Igniters, I am seeing an NPE reported from the GridServiceProcessor class here: https://stackoverflow.com/questions/46144413/apache-ignite-cluster-does-not-start-with-persistent-storage Has this been fixed? D.

[jira] [Created] (IGNITE-6325) Need to update the GitHub page

Dmitriy Setrakyan created IGNITE-6325: - Summary: Need to update the GitHub page Key: IGNITE-6325 URL: https://issues.apache.org/jira/browse/IGNITE-6325 Project: Ignite Issue Type

Re: Add ANTLR dependency (BSD!) to Apache Ignite

ndency on H2 > > Performance will be evaluated separately [1]. > > [1] https://issues.apache.org/jira/plugins/servlet/mobile# > issue/IGNITE-6320 > > > > пт, 8 сент. 2017 г. в 21:01, Dmitriy Setrakyan : > > > Vova, license-wise it is OK, but I do not like adding the

Re: Annoying extra steps for enabling metrics

gt; cache events. The API is a mess. Let’s contemplate how to fix it. Agree, this is horrible. We need to fix it in 2.3. Is there a ticket? > > — > Denis > > > On Sep 7, 2017, at 7:33 PM, Dmitriy Setrakyan > wrote: > > > > On Thu, Sep 7, 2017 at 7:30 PM, Denis Magd

Re: Who are the custodians of Ignite?

On Sat, Sep 9, 2017 at 10:31 AM, Jim Apple wrote: > https://www.meetup.com/datariders/events/242523245/ > > "GridGain Systems is also the custodians of the open-source Apache > Ignite -- a memory-centric data platform that is strongly consistent > and highly available with powerful SQL, key-value

Re: Logging documentation

Great! I think the next task should be to explain expiration vs eviction. I am seeing too many questions on it as well. At this point, I am also confused about how it really works. D. On Fri, Sep 8, 2017 at 10:18 AM, Denis Magda wrote: > Unbelievable! So many years went by and finally we got t

Re: sql documentation

omething just send us a message here. > > Presently the doc is not indexed by searching engines. Let’s finish it > first and announce afterwards. > > — > Denis > > > On Aug 30, 2017, at 5:43 PM, Dmitriy Setrakyan > wrote: > > > > On Wed, Aug 30, 2017 at 10:04 PM,

Re: Add ANTLR dependency (BSD!) to Apache Ignite

Vova, license-wise it is OK, but I do not like adding the dependency. Right now we have H2 doing parsing for us. Why would ANTLR be better? What happens when we potentially notice a performance issue or any other issue in ANTLR under load? Can we try doing parsing ourselves instead of adding a dep

[jira] [Created] (IGNITE-6305) Need to add update checker to Ignite

Dmitriy Setrakyan created IGNITE-6305: - Summary: Need to add update checker to Ignite Key: IGNITE-6305 URL: https://issues.apache.org/jira/browse/IGNITE-6305 Project: Ignite Issue Type

Re: [DISCUSS] Ignite Update Checker

I think it is safe to assume at this point that everyone is in general agreement, since there are no active objections. I have filed a ticket for the 2.3 release. Let's try to make it happen: https://issues.apache.org/jira/browse/IGNITE-6305 D. On Sat, Aug 26, 2017 at 3:06 PM, Dmitriy Setr

Fwd: 2.1.4 visor console - activate/deactivate command?

Cross-sending to dev@ Igniters, can we try to include the fixes to the cluster activation command into 2.3 release, including the renaming suggestion? https://issues.apache.org/jira/browse/IGNITE-6064 D. -- Forwarded message -- From: Denis Magda Date: Thu, Sep 7, 2017 at 7:49 PM

Re: Annoying extra steps for enabling metrics

On Thu, Sep 7, 2017 at 7:30 PM, Denis Magda wrote: > My point is different. Before I had to do this only assuming that “Ignite > will spend 99%” sending events: > > > > > > > > > >

Re: Annoying extra steps for enabling metrics

On Thu, Sep 7, 2017 at 7:19 PM, Denis Magda wrote: > Any metric from of org.apache.ignite.events.EventType (cache operations, > compute, etc.) > If you enable them all, Ignite will spend 99% of its time doing event notifications. > > — > Denis > > > On Sep 7

Re: Annoying extra steps for enabling metrics

Denis, which metrics are you talking about? On Thu, Sep 7, 2017 at 7:12 PM, Denis Magda wrote: > Igniters, > > It was a surprise for me to reveal that even if the default config is used > [1] I still will not see the metrics in Web Console or in a custom app. > However, the config was left uncha

Re: Ignite Benchmarking page on readme.io

Actually, it can be contributed directly to readme.io. Alexey, I just sent you an invite. You can create a new page for benchmarking and make it invisible for now, while you are working on it. If you need us to review it, please send a direct link to it here. D. On Thu, Sep 7, 2017 at 8:26 AM, A

Re: Disable compute job results cache by default

On Thu, Sep 7, 2017 at 8:52 AM, Yakov Zhdanov wrote: > Guys, according to this - > http://apache-ignite-users.70518.x6.nabble.com/Task-manageme > nt-MapReduce-amp-ForkJoin-performance-penalty-td16542.html > - I would think that we need to disable result caching by default.0 > Or at least find o

Re: Future of Ignite transactions

Vova, Thanks for doing the research. The changes you are suggesting are a bit too bold, so let's discuss them in some more detail... On Wed, Sep 6, 2017 at 4:51 AM, Vladimir Ozerov wrote: > Igniters, > > We are moving towards DBMS system. None of them has a notion of > OPTIMISTIC/PESSIMISTIC tr

Re: IGNITE-5655: Mixing binary string encodings in Ignite cluster

I would agree with Andrey, it does look a bit over-architected to me. Why would anyone try to move data from one encoding to another? Is it a real use case that needs to be handled automatically? Here is what I think we should handle: 1. Ability to set cluster-wide encoding. This should be eas

Re: Batch service deployment

ll > > require > > > > some additional code during the deployment for a very questionable > > value. > > > > > > > > > > > > > > > > > > On Wed, Sep 6, 2017 at 6:21 PM, Vladimir Ozerov < > > voze...@gridgain.co

Re: Batch service deployment

ack services easily then when we have a mode > > where > > > we declare a kind of false "atomicity"? > > > > > > On Wed, Sep 6, 2017 at 6:17 PM, Dmitriy Setrakyan < > dsetrak...@apache.org > > > > > > wrote: > > > > > >&

Re: Batch service deployment

; On Wed, Sep 6, 2017 at 6:06 PM, Dmitriy Setrakyan > wrote: > > > Vova, makes sense. Couple of comments. > > > > > >1. allowPartialUpdate -> allowPartialDeploy > >2. I do not think we need the 2nd deployAll method. This is not the > API > >

Re: Batch service deployment

ething went wrong, we should return the list of offending > services in exception. This way API reduces to: > > void deployAll(Collection cfgs) > throws ServiceDeploymentException > > Clean, simple, covers 99% of real use cases. > > Thoughts? > > > On Fri, Aug 18, 2017

Re: POJO field having wrapper type, mapped to cassandra table are getting initialized to respective default value of primitive type instead of null if column value is null

Cross-sending to user@ as well. On Tue, Sep 5, 2017 at 10:44 PM, kotamrajuyashasvi < kotamrajuyasha...@gmail.com> wrote: > Hi > > I'm using ignite with cassandra as persistent store. I have a POJO class > mapped to cassandra table. I have used > ignite-cassandra-store/KeyValuePersistenceSettings

Re: IGNITE-2894 - Binary object inside of Externalizable still serialized with OptimizedMarshaller

Vova, I agree. Let's stay loyal to our binary serialization protocol. Do you know if we will be loosing any functionality available in Externalizable, but not present in our binary protocol? D. On Mon, Sep 4, 2017 at 11:38 PM, Vladimir Ozerov wrote: > Folks, > > Let's discuss how this should b

Re: IGNITE-5655: Mixing binary string encodings in Ignite cluster

Can we just detect the encoding at cache, or at least column level? This way if the encoding does not match, we throw an exception immediately. Will it work? D. On Tue, Sep 5, 2017 at 9:16 AM, Andrey Kuznetsov wrote: > Hi Igniters! > > I met a couple of issues related to different binary strin

Fwd: Specifying location of persistent storage location

Cross sending to dev@ list. Igniters, can you please check my analysis in the thread on the user@ list and see if it is plausible? D. -- Forwarded message -- From: Dmitriy Setrakyan Date: Mon, Sep 4, 2017 at 4:17 PM Subject: Re: Specifying location of persistent storage

Re: Hello

Hello, Ivan! Welcome to the Ignite community! You should get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process Instructions on how to contribute can be found here: https://cwiki.apache.org/confluence/display/IGNITE/How

Re: Error during activation of cluster

well. > Got it. > > --Yakov > > 2017-09-04 17:19 GMT+03:00 Dmitriy Setrakyan : > > > On Mon, Sep 4, 2017 at 3:05 AM, Yakov Zhdanov > wrote: > > > > > >> Why are we throwing checked exceptions without any error message? > > Should > > > we fix

Re: Yardstick framework for Ignite 2.1

ote in > >> >> readme.md file (about that repository contains outdate benchmarks) > and > >> >> link > >> >> to a repo with actual version of benchmark. > >> >> > >> >> On Mon, Sep 4, 2017 at 12:30 PM, Anton Vino

Re: Cluster auto activation design proposal

pinions? > Alexey Goncharuk, given that you provided the initial implementation of the cluster activation, can you please take a look at this design and provide comments? > > On Fri, Sep 1, 2017 at 2:35 PM, Dmitriy Setrakyan > wrote: > > > How about this: > > > >

Re: Error during activation of cluster

On Mon, Sep 4, 2017 at 3:05 AM, Yakov Zhdanov wrote: > >> Why are we throwing checked exceptions without any error message? Should > we fix it? > > I don't think it is important. This exception is instantiated inside > IgniteUtils.cast() and has a cause. > Why not add the same message as in the

[jira] [Created] (IGNITE-6260) Need to rename setDistributedJoins to setNonCollocatedJoins

Dmitriy Setrakyan created IGNITE-6260: - Summary: Need to rename setDistributedJoins to setNonCollocatedJoins Key: IGNITE-6260 URL: https://issues.apache.org/jira/browse/IGNITE-6260 Project

Re: Thin client and binary metadata

I think we should support and clearly document both modes, with and without metadata. On Mon, Sep 4, 2017 at 2:06 AM, Pavel Tupitsyn wrote: > In my understanding such objects are completely fine. > > Even typeId is not necessary, since we have > GridBinaryMarshaller.UNREGISTERED_TYPE_ID mode, >

Re: Yardstick framework for Ignite 2.1

.@alexzaitzev.pro> > > > wrote: > > > > > > > Exactly, because that benchmarks works only with Ignite 1.9. So not > to > > > > maintain code in two places I deleted it in yardstick-ignite repo and > > > gave > > > > a direct l

Fwd: Error during activation of cluster

Cross sending to dev@ Igniters (especially the persistence experts), the NPE in the log seems like a bug. Should we file a ticket? Also, I am seeing the following in the log; > class org.apache.ignite.IgniteCheckedException: null Why are we throwing checked exceptions without any error message

Re: UPDATE SQL for nested BinaryObject throws exception.

Cross sending to dev@ Igniters, up until version 1.9, the nested fields were supported by flattening the names. Do we still support it? I cannot seem to find documentation for it. D. On Thu, Aug 31, 2017 at 7:12 AM, takumi wrote: > This is a part of the real code that I wrote. > >

Fwd: SQLQuery with simple Join return no results

Cross sending to dev@ Igniters, is there a way that we could detect whether JOIN keys are collocated or not? If not, then the query should fail with an appropriate error message. I understand that this may not be possible for 100% of all JOIN queries, but even if we cover 50%, we will significantl

Fwd: Limiting the size of Persistent Store and clearing data on restart

...@ignite.apache.org Sorry, I didn't know that. I found a bunch of matches by "swapEnabled" keyword on master branch in the project, mostly in benchmarks configurations. These properties should probably be removed not to confuse readers. пт, 1 сент. 2017 г. в 19:23, Dmitriy Setrakyan : > On Fri

Ignite meetup in Moscow

Denis, Should we add this meetup to the website? https://www.meetup.com/Moscow-Apache-Ignite-Meetup/ D.

Re: DataStreamer usability

rces. > Evgenii, I agree with you. But a simple warning here to alert the user about the config differences could go a long way. > > Evgenii > > 2017-09-03 20:18 GMT+03:00 Dmitriy Setrakyan : > > > On Sun, Sep 3, 2017 at 10:09 AM, Evgenii Zhuravlev < > > e.zhuravle

Re: DataStreamer usability

gurations for streaming into the same cache on the same node? In this case, we should print out a warning if the configuration of one streamer is different from another. Agree? > > Evgenii > > > 2017-09-03 19:59 GMT+03:00 Dmitriy Setrakyan : > > > On Sun, Sep 3, 2017 at

Re: DataStreamer usability

we already have an improvement too: > https://issues.apache.org/jira/browse/IGNITE-5195 Argh, what a horrible issue. We spit out an exception 2 pages long, and then telling the poor user to ignore it. This is just sad. I updated the ticket and added a link to the user thread. > > >

Re: DataStreamer usability

ted to Data Streamer at > all. Usually, as it was in this question on SO, it was a wrong > configuration or conflicted configuration between nodes. > > Evgenii > > 2017-09-03 2:10 GMT+03:00 Dmitriy Setrakyan : > > > Igniters, > > > > I am noticing quite a few

DataStreamer usability

Igniters, I am noticing quite a few issues on the user list and Stack Overflow that have to do with Data Streamer usability. Here is just one example: https://stackoverflow.com/questions/46015833/datastreamer-adddata-method-not-work-as-expected-in-cluster I think, as a community, we should try t

Re: Cluster auto activation design proposal

sting however I cannot come up with a clear use case > which can be widely adopted. > I would give users a simple API at first to cover 80% of their needs and > then collect some feedback and start thinking about adding new > functionality. > > Makes sense? > > Sergey. &g

Re: IgniteFuture -> CompletableFuture

1, 2017 at 3:28 PM, Dmitry Pavlov > wrote: > > > +1 for migrating to java 8. > > > > Sincerely, > > Dmitriy Pavlov > > > > > > On чт, 31 авг. 2017 г., 11:03 Yakov Zhdanov wrote: > > > > > CompletableFuture is part of java

IgniteFuture -> CompletableFuture

Igniters, I received the following proposal in my blog. I think this is useful. Any thoughts? Please extend IgniteFuture by conversion method to CompletableFuture. I > bored to write something like this: > asyncCache.invoke(key, entryProcessor); > CompletableFuture completableFuture = new Compl

Re: Override cache name created with CREATE TABLE

I think Denis' idea makes sense. Vladimir, what do you think? D. On Wed, Aug 30, 2017 at 2:57 AM, Denis Magda wrote: > Igniters, > > That’s one more feedback about CREATE TABLE usage in practice. > > The command automatically creates an IgniteCache naming it > SQL_PUBLIC_{TABLE}. So, if a Pers

Re: Cluster auto activation design proposal

ke > > > Ignite::activation::setInitialActivationNodes(Collection > > > nodes) to provide collection of nodes that grid must reach to activate > > > automatically. > > > > > > And then using the collection we'll create BaselineTopology abstraction > >

Re: Ignite Durable Memory & Persistent Store introduction for developers

Dmitriy, this is very useful! Any chance you can also blog about it? On Wed, Aug 30, 2017 at 6:24 PM, Dmitry Pavlov wrote: > Hi Igniters, > > > I am glad to introduce two new wiki articles. These articles contain > high-level description of > > - Ignite Durable Memory ( > https://cwiki.apache.or

Re: Yardstick framework for Ignite 2.1

> 24.08.2017, 02:02, "Dmitriy Setrakyan" : > > I would delete all the code from the Yardstick repo to avoid confusion > and > > in the description of the repo ask users to download Ignite directly. > > > > On Wed, Aug 23, 2017 at 7:40 AM, Aleksei Zaitsev >

Re: sql documentation

On Wed, Aug 30, 2017 at 10:04 PM, Denis Magda wrote: > Serge, > > Undoubtedly, I like this format. I’ve created a new documentation domain > for all our SQL capabilities: > https://apacheignite-sql.readme.io/docs readme.io/docs> > > Once I get an open source license f

Re: Cluster auto activation design proposal

join is successful we have an undefined state of the resulting grid: > values for the same key may (and will) differ between grid parts. > > So to prevent this we should keep nodes with BLT#2 from joining the grid > with BLT#3. And we should fail nodes with an error message. > > T

Re: Ignite not friendly for Monitoring

On Mon, Aug 28, 2017 at 1:22 AM, Vladimir Ozerov wrote: > IGNITE-5620 is about error codes thrown from drivers. This is completely > different story, as every driver has specification with it's own specific > error codes. There is no common denominator. > Vova, I am not sure I understand. I woul

Re: [DISCUSSION] Urgent Ignite bug fix release

ap, needed memory for OS, etc > > 2017-08-28 14:38 GMT+03:00 Dmitriy Setrakyan : > > > Looks good, but why in the example provided are we suggesting 8GB? 2 > nodes > > with 8GB will completely exhaust the available memory. I would suggest 6 > or > > 7GB. > >

Re: [DISCUSSION] Urgent Ignite bug fix release

missing in 2.1 release! That must be fixed and rolled > > out in this emergency release: > > https://issues.apache.org/jira/browse/IGNITE-6193 < > > https://issues.apache.org/jira/browse/IGNITE-6193> > > > > Oleg, Yuri, please step in and handle the issue. > > >

Re: [DISCUSS] Ignite Update Checker

Sure, would be nice to hear from Roman as well. > Cheers. > > [1] > https://developers.google.com/analytics/devguides/ > collection/analyticsjs/events > > On Sat, Aug 26, 2017 at 12:23 AM, Dmitriy Setrakyan > > wrote: > > > Raul, > > > > Could point

Re: Testing Ignite Applications Locally

Love the idea. Let's add Testing Ignite Apps page on Readme. Denis, I don't think we need many snippets, just a few. As far as Maven archetype, Yakov, is the only purpose of it to load a project, so users can add tests to it? D. On Fri, Aug 25, 2017 at 8:51 AM, Denis Magda wrote: > Yasha, > >

Re: [DISCUSS] Ignite Update Checker

s endpoint anyway, then there's no point > placing another file on Git or elsewhere for reporting the latest versions: > the endpoint itself can return them. > > WDYT? > > Cheers. > > On Fri, Aug 25, 2017 at 9:56 PM, Dmitriy Setrakyan > wrote: > > > Cos, Raul

Re: Shell script to stop Ignite node

t; /var/log/ignite/. It will significally reduce the efforts to install Apache > Ignite for newbies ("just add the reporsitory and run package manager") > > > > On Tue, Aug 22, 2017 at 2:16 AM, Dmitriy Setrakyan > wrote: > > > Completely agree. Why do we

Re: [DISCUSSION] Urgent Ignite bug fix release

e: 12853MB > > > > I think it's make sense to describe what these numbers are consist of. > > > > We simple say which parameters have an impact on how much memory the > > instance needs and their (parameters) actual values. > > > > Also we notice that mo

Re: [DISCUSS] Ignite Update Checker

A versions for each major > version > > line (1.x, 2.x). > > > > I would advocate this last option, but it requires somebody remembering > to > > update the file with every release, unless we automate it with a Maven > > plugin. > > > > Hope that helps! > &g

Re: [DISCUSSION] Urgent Ignite bug fix release

ignite instanses on > > the server require: 12853MB > > [2017-08-25 19:44:37,741][WARN ][disco-event-worker-#29%internal. > > GridHomePathSelfTest0%][GridDiscoveryManager] > > > > > > 2017-08-25 17:40 GMT+03:00 Sergey Kozlov : > > > >> I suppose we s

Re: [DISCUSSION] Urgent Ignite bug fix release

Igor, I would change the message. How about this: Required RAM size is larger than total physical memory available for OS. > Please change MemoryConfiguration.WhichProperty and > MemoryPolicyConfiguration.WhichProperty to decrease memory allocated for > each node. Also, can we calculate what the

Re: Ignite Usability: Deadlocks and Starvation

On Thu, Aug 24, 2017 at 10:09 AM, Yakov Zhdanov wrote: > > I think as a first step, the deadlock detection should kick off after a > > certain timeout, even if the transaction timeout was not set. > > > What do you think? > > Dmitry, I thought that was what I suggested, no? =) > I am never sure

Re: [DISCUSSION] Urgent Ignite bug fix release

+1 on the release, let's do it ASAP. On Thu, Aug 24, 2017 at 12:32 PM, Denis Magda wrote: > Igniters, > > Presently every Apache Ignite node requests 80% of RAM from an operating > system. We debated a lot about this default [1] and as a practice shows > those who voted for the lower value (20%-

Re: [DISCUSS] Ignite Update Checker

Is everyone OK with this approach? Should I file a ticket on it? On Mon, Aug 21, 2017 at 2:07 PM, Dmitriy Setrakyan wrote: > Igniters, > > There has been lots of talk of proposals about various usage metrics for > Ignite and nothing came of it. I would like to resurrect the topic a

Re: Adding Apache Ignite to Kubernetes Example

Hm... don't we have one already? https://apacheignite.readme.io/docs/kubernetes-deployment D. On Wed, Aug 23, 2017 at 7:23 PM, Dani Traphagen wrote: > Hi Igniters, > > What are your thoughts on providing an Apache Ignite example for the > Kubernetes > project as shown

Re: Expanding Apache Ignite Use Case

ays and send the pages to my fellow editor and SEO for *non-technical* > corrections and improvements. > > — > Denis > > > On Aug 21, 2017, at 9:30 PM, Dmitriy Setrakyan > wrote: > > > > Denis, great progress. > > > > At a first glance, I would suggest

Re: Data compression in Ignite

Object structure is preserved, we will still have fast > constant-time per-field access. > > Please share your thoughts. > > Vladimir. > > > On Sat, Aug 12, 2017 at 4:08 AM, Dmitriy Setrakyan > wrote: > > > I still don't understand per-partition compression, which

Re: DML and transaction boundaries

I prefer the (3) - print out a warning in the log. Otherwise, if you throw an exception, you are risking breaking all the existing user code. On Wed, Aug 23, 2017 at 7:20 AM, Vladimir Ozerov wrote: > Igniters, > > Our docs say that DML statements are executed outside of current > transaction. Th

Re: Yardstick framework for Ignite 2.1

tter to add information in yardstick repo README, that Apache Ignite > contains benchmarks since version 2.0? > > 22.08.2017, 16:55, "Dmitriy Setrakyan" : > > On Tue, Aug 22, 2017 at 7:19 AM, Aleksei Zaitsev > > > wrote: > > > >> If newer versions of

Re: Ignite Usability: Deadlocks and Starvation

Yakov, I think as a first step, the deadlock detection should kick off after a certain timeout, even if the transaction timeout was not set. What do you think? D. On Wed, Aug 23, 2017 at 9:44 AM, Yakov Zhdanov wrote: > Hello, guys! > > Currently Ignite clusters are very vulnerable to deadlock

Re: Criteria query to web console

fficient H2 API producing > garbage, etc.. > > Vladimir. > > On Wed, Aug 23, 2017 at 8:25 AM, Dmitriy Setrakyan > wrote: > > > I still don't get it. If I need a filter, then I will just use SQL. > > > > On Tue, Aug 22, 2017 at 8:46 PM, Alexey Kuznetsov <

Re: Criteria query to web console

Criteria(...)).or(TCriteria(...)).andNot( > TCriteria(...)).build(); > > ScanQuery q = new ScanQuery(filter); > > cache.query(q) > > And we could have nice Web UI for this: IgniteBiPredicate filter = > builder.add(TCriteria(...)).and(TCriteria(...)).or(TCriteria(...)).andN

Re: Cluster auto activation design proposal

ers, does this description match with your understanding of > functionality? If it does I'll create a set of tickets and start working on > implementation. > > Thanks, > Sergey. > > > On Sat, Aug 19, 2017 at 5:41 PM, Dmitriy Setrakyan > wrote: > > >

<    2   3   4   5   6   7   8   9   10   11   >