Re: IGNITE-5432 fixed

Alexey, Thanks for interest to Apache Ignite development. I briefly checked your changes and see commented codelines, does it mean that PR not ready for review yet? Also, direct "review request" can help to speedup review process, you can find tips here:

Re: "Review workflow" changes to prevent "broken review" issues.

t; > > > > Personally, I’m for 1. > > > > > > > > — > > > > Denis > > > > > > > > > On Jun 5, 2017, at 10:28 AM, Dmitry Pavlov <dpavlov@gmail.com> > > > > wrote: > > > > > > > > >

Re: "Review workflow" changes to prevent "broken review" issues.

Igniters, Since we found that proposed approach can help, no one mind that I'll add text listed above to the wiki? On Tue, Jun 6, 2017 at 1:19 PM, Anton Vinogradov <avinogra...@gridgain.com> wrote: > Dmitry, > > 1) See my initial email, it contains instruction how to find a revie

Re: Suggested changes for Apache Ignite Release procedure

Huge +1 On Wed, Jun 7, 2017 at 1:40 PM, Sergey Kozlov wrote: > Hi, Igniters > > I'd start the discussion for following changes of release procedure. > As you may know we provided not source artifacts only but also a set of > binaries that makes using of the release is more

Re: [DISCUSS] Webinar for Ignite Persistent Store walk-through

+1 On Tue, Jun 13, 2017 at 2:21 PM, Kozlov Maxim wrote: > +1 > > > 13 июня 2017 г., в 14:14, Vyacheslav Daradur > написал(а): > > > > +1 (I will attend) > > > > 2017-06-13 6:35 GMT+03:00 Roman Shtykh : > > > >> Denis, > >>

Re: [VOTE] Apache Ignite 2.0.0 RC2

+1 binding On Tue, May 2, 2017 at 10:44 AM, Nikolai Tikhonov wrote: > +1 binding > > On Tue, May 2, 2017 at 10:42 AM, Sergi Vladykin > wrote: > > > +1 binding > > > > Sergi > > > > 2017-05-02 10:31 GMT+03:00 Alexey Kuznetsov

Re: "Review workflow" changes to prevent "broken review" issues.

at do you think about way 2? Personally, I'm ready to help with analysis > and assignment of these 66 tasks from next week. > > > > вт, 6 июн. 2017 г. в 12:57, Anton Vinogradov <avinogra...@gridgain.com>: > > > Dmitry Pavlov, > > > > There is *HUGE *difference bet

Re: Ignite Benchmarking Rules

Guys, I fully agree that configured servers at Amazon is the best choice. But when you need to check that your changes has no performance drop you're able to use your own PC or PCs to checks that. All you need is to benchmark already released version vs version with your fix at same environment.

Re: Static code analysis for Java

that uploads > bundle > > to server and links build results on TC to results at Sonarqube site. > > 3. https://scan.coverity.com/projects/apache-ignite - Coverity seems to > be > > very powerful, free for opensource, runs locally and then user uploads > > results to ser

[RESULT] [VOTE] Apache Ignite 2.2.0 Release (RC2)

Igniters, Apache Ignite 2.2.0 release (RC2) has been accepted. 4 "+1" binding votes received: - Vladimir Ozerov - Alexey Kuznetsov - Andrey Novikov - Pavel Tupitsyn Vote thread: http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-2-0-RC2-td22261.html Ignite 2.2.0 will

Re: HOLE query entry in CacheContinuousQueryPartitionRecovery

Nikolay, Could you please check? On Tue, Sep 19, 2017 at 1:50 PM, ALEKSEY KUZNETSOV wrote: > HOLE was introduced in CacheContinuousQueryHandler.PartitionRecovery. > Ticket *IGNITE-426 Implemented failover for Continuous query.* > Then it was refactored in *Continuous

Re: IGNITE-1025

Ivan, Issue is still actual. On Tue, Sep 19, 2017 at 2:10 PM, Иван Федотов wrote: > Hi, Igniters! > I've picked up task https://issues.apache.org/jira/browse/IGNITE-1025 > "Need > to print out warning if IP finder has a lot of addresses on Windows", but > this task was

Re: Binary compatibility of persistent storage

Vote for case #4. As far as I know, Vyacheslav Daradur already works on framework allows to check compatibility between different version of Ignite. Vyacheslav, Could you provide us more details? On Tue, Sep 19, 2017 at 2:16 PM, Vladimir Ozerov wrote: > igniters, > >

Re: [RESULT] [VOTE] Apache Ignite 2.2.0 Release (RC2)

- Maven artifacts released - Sources released - Site updated - Git tag added On Mon, Sep 18, 2017 at 6:19 PM, Anton Vinogradov <a...@apache.org> wrote: > Igniters, > > Apache Ignite 2.2.0 release (RC2) has been accepted. > > 4 "+1" binding votes received: &

Re: Adding sqlline tool to Apache Ignite project

How about sqlconsole.sh or sqlcmd.sh ? On Fri, Oct 6, 2017 at 6:04 PM, wrote: > I like ignitesql. > > ⁣D.​ > > On Oct 6, 2017, 4:49 PM, at 4:49 PM, Vladimir Ozerov > wrote: > >Denis, > > > >Setting default host to 127.0.0.1 is bad idea, because it

Re: Adding sqlline tool to Apache Ignite project

; > > > > > > > > Meant accepted by the ignitesql script only such as host name. > > > > > > > > > > > > > > — > > > > > > > Denis > > > > > > > > > > > > > >> On Oct 6, 2017, at 12:20 PM, Denis

Re: Download links on ignite.apache.org not always working

Vyacheslav, 1) That's correct case. All download links except newest version should point to archive. 2) That's correct case. You can change mirror only for newest version. Archived versions have no mirrors. See https://issues.apache.org/jira/browse/IGNITE-2964 for details. On Fri, Oct 13,

Re: Integration of Spark and Ignite. Prototype.

Sounds awesome. I'll try to review API & tests this week. Val, Your review still required :) On Tue, Oct 17, 2017 at 2:36 PM, Николай Ижиков <nizhikov@gmail.com> wrote: > Yes > > 17 окт. 2017 г. 2:34 PM пользователь "Anton Vinogradov" < > avinogra...@g

Re: Integration of Spark and Ignite. Prototype.

Nikolay, > With Data Frame API implementation there are no requirements to have any > Ignite files on spark worker nodes. What do you mean? I see code like: spark.sparkContext.addJar(MAVEN_HOME + "/org/apache/ignite/ignite-core/2.3.0-SNAPSHOT/ignite-core-2.3.0-SNAPSHOT.jar") On Mon, Oct 16,

Re: Integration of Spark and Ignite. Prototype.

http://spark.apache.org/docs/latest/api/java/org/apache/ > spark/SparkContext.html#addFile(java.lang.String) > > > 2017-10-17 13:10 GMT+03:00 Anton Vinogradov <avinogra...@gridgain.com>: > > > Nikolay, > > > > > With Data Frame API implementation

Re: Monitoring of active transactions

Ilya, We extremely need this! Txs and Locks info should be collected on each cluster hang. We already have an issue related to this problem - https://issues.apache.org/jira/browse/IGNITE-4937 Nikolay, Good point, but, seems you should start separate thread to discuss this. On Fri, Sep 8, 2017

[VOTE] Apache Ignite 2.2.0 RC1

Igniters, We have uploaded a 2.2.0 release candidate to https://dist.apache.org/repos/dist/dev/ignite/2.2.0-rc1/ Git tag name is 2.2.0-rc1 This release includes the following changes: Ignite: * Checkpointing algorithm optimized * Default max memory size changed from 80% to 20% Ignite CPP: *

Re: Yardstick framework for Ignite 2.1

to avoid confusion > > and > > >> in the description of the repo ask users to download Ignite directly. > > > > That's why. But for me it's OK just to add a warning. I think it's not > > critical, so let's do it in any of the discussed ways. > > > > 04.09.2017

Re: Ignite Benchmarking page on readme.io

Aleksei, Good idea. Could you please prepare page in MD format and attach link to branch containing it to the issue to review before publication? On Thu, Sep 7, 2017 at 1:45 PM, Aleksei Zaitsev wrote: > Hi, guys. > > Issue[1] stated that we have not any information

Re: [VOTE] Apache Ignite 2.2.0 RC1

gt;>> > > >> >>>> Checked: > > >> >>>> - Build from sources (Java, .NET) > > >> >>>> - Examples (.NET) > > >> >>>> > > >> >>>> On Tue, Sep 12, 2017 at 11:40 AM, Ilya Suntsov < &

Re: [DISCUSSION] Urgent Ignite bug fix release

...@gridgain.com> wrote: > > > > Cherry-picked from master. Changed "Fix version" in ticket. > > > > Best Regards, > > Igor > > > > On Tue, Sep 5, 2017 at 4:15 PM, Anton Vinogradov < > avinogra...@gridgain.com> > > wrote: > >

How much memory/disc I need to keep my data?

Igniters, Since we're developing some kind of storage system it's pretty interesting how effectively it stores data. I propose to develop some Estimator allows to count how much space is needed to keep any data. For example: 1) You have classes A,B and C with known fields and data distribution

Re: [DISCUSSION] Urgent Ignite bug fix release

eated branch ignite-2.2, currently it equals to ignite-2.1. On Mon, Aug 28, 2017 at 4:05 PM, Anton Vinogradov <avinogra...@gridgain.com> wrote: > Denis, > > > BTW, who is considered to be the release manager of this release? > I'll do it. > > On Mon, Aug 28, 2017 at 3:54

Re: [DISCUSSION] Urgent Ignite bug fix release

Denis, > BTW, who is considered to be the release manager of this release? I'll do it. On Mon, Aug 28, 2017 at 3:54 PM, Seliverstov Igor wrote: > Ok, the check happens at the node start time or on NODE_JOIN event > > in general it looks like: > > 1) calculate expected

Re: ContinuousQueryWithTransformer implementation questions - 2

ple, select only fields that are important. > This may bring huge economy to traffic and lower GC pressure as well. > === > > My pull request [2] is ready. > Anton Vinogradov is OK with it. > Nikolay Tikhonov reviewed my changes and want to discuss changes related > t

Re: Yardstick framework for Ignite 2.1

t update this repository, I don't think > that is so difficult (seems need just copy files from /benchmark folder). > > Thoughts? > > On Thu, Aug 31, 2017 at 3:00 PM, Anton Vinogradov <a...@apache.org> wrote: > > > Guys, > > > > Lets's just delete t

Re: Yardstick framework for Ignite 2.1

Guys, Lets's just delete this repo. On Thu, Aug 31, 2017 at 10:18 AM, Aleksei Zaitsev 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 link to

Re: IgniteFuture -> CompletableFuture

Is it still actual to support java 7? On Thu, Aug 31, 2017 at 11:03 AM, Yakov Zhdanov wrote: > CompletableFuture is part of java 8. > > --Yakov > > 2017-08-31 4:46 GMT+03:00 Dmitriy Setrakyan : > > > Igniters, > > > > I received the following proposal

Re: [DISCUSSION] Urgent Ignite bug fix release

not increased and documents do not require >> big changes. >> If the version number is 2.1 series, there is no need to publish a new >> version of the document. >> >> >> 在 2017/8/28 下午10:19, Anton Vinogradov 写道: >> > Igniters, >> > >> &

Re: ContinuousQueryWithTransformer implementation questions - 2

+1 to keep current behavior and start new thread to solve notification issue. On Mon, Sep 4, 2017 at 2:05 PM, Николай Ижиков wrote: > Hello, Yakov. > > I made a bit of investigation about your proposal of handling filter and > transformer exceptions: > > 1. If we cancel

Re: Yardstick framework for Ignite 2.1

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 Vinogradov <a...@apache.org> wrote: > > > Dmitriy, > > > > No, > > We should

Re: Yardstick framework for Ignite 2.1

e simply update this page with a link to the new repo hosting the > benchmarks? > https://github.com/apacheignite/yardstick-ignite/blob/master/README.md > > Once we update the page, we can remove the old benchmark code. > > D. > > On Thu, Aug 31, 2017 at 5:29 AM, Anton Vinogradov

Re: Yardstick framework for Ignite 2.1

e benchmarks) and > link > >> to a repo with actual version of benchmark. > > I've already done it in this pull request: https://github.com/ > apacheignite/yardstick-ignite/pull/6. If it's OK, let's merge it. > > 04.09.2017, 13:02, "Anton Vinogradov" <avinogra...@grid

Re: ContinuousQueryWithTransformer implementation questions - 2

Nikolay, You can also use: 1) Global Exception Registry ctx.kernalContext().exceptionRegistry().onException(shortMsg, ex); 2) Statistic final boolean statsEnabled = cctx.config().isStatisticsEnabled(); if (statsEnabled) metrics.incrementOnFails(); P.s. Please make sure that code still

Re: [DISCUSSION] Urgent Ignite bug fix release

s. > > > > — > > Denis > > > > > On Aug 28, 2017, at 7:19 AM, Anton Vinogradov < > avinogra...@gridgain.com> > > wrote: > > > > > > Igniters, > > > > > > Seems 2.2 is a urgent bugfix release, so it shoul

Re: Ignite Durable Memory & Persistent Store introduction for developers

Awesome! Thanks! 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.org/confluence/display/IGNITE/

Re: [DISCUSSION] Urgent Ignite bug fix release

> > > > 在 2017/8/28 下午10:19, Anton Vinogradov 写道: > >> Igniters, >> >> Seems 2.2 is a urgent bugfix release, so it should be based on 2.1, >> In this case all other issues with fixVersion = 2.2 should be moved to >> 2.3. >> >> Currently

Re: [DISCUSSION] Urgent Ignite bug fix release

>> Since it's an urgent bugfix version, why can't the version number be > > >> defined as 2.1.1 or 2.1.4? > > >> After all, functionality has not increased and documents do not > require > > >> big changes. > > >> If the version number is 2.1

Re: Adding sqlline tool to Apache Ignite project

> > >> editing and documentation. > > > >> > > > >> — > > > >> Denis > > > >> > > > >>> On Oct 9, 2017, at 10:13 AM, Oleg Ostanin <oosta...@gridgain.com> > > > wrote: > > > >>> > >

Re: Facility to detect long STW pauses and other system response degradations

t; The question is why user may need so precise measurement? I share Andrey’s > opinion - cannot understand the value. > > вт, 21 нояб. 2017 г. в 19:33, Anton Vinogradov <avinogra...@gridgain.com>: > > > Andrey, > > > > > JVM provides sufficient mean

Re: Facility to detect long STW pauses and other system response degradations

ly dead? > 2) How duration is distributed? Was 10 pauses 10 seconds each, or 9 short > pauses of 1 sec and one critical pause of 90s? > > May be a kind of sliding window plus min/max values will do better job. > > On Wed, Nov 22, 2017 at 1:07 PM, Anton Vinogradov < > avinogra

Re: Ignite node crashes after one query fetches many entries from cache

Ray, Seems you're looking for org.apache.ignite.cache.query.SqlFieldsQuery#timeout? On Tue, Nov 28, 2017 at 5:30 PM, Alexey Kukushkin wrote: > Ignite Developers, > > I know community is developing an "Internal Problems Detection" feature >

Re: Enable/disable cache statistics in runtime

Seems, We have to use custom discovery message to are about new nodes that joining grid. On Thu, Nov 30, 2017 at 5:08 AM, Alexey Kuznetsov wrote: > Alex, > > We have such issue in JIRA: https://issues.apache.org/ > jira/browse/IGNITE-369 > I think you can update its

[GitHub] ignite pull request #3137: IGNITE-6411 WIP

GitHub user anton-vinogradov opened a pull request: https://github.com/apache/ignite/pull/3137 IGNITE-6411 WIP Signed-off-by: Anton Vinogradov <a...@apache.org> You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/

Re: Ignite Enhancement Proposal #6 (Metrics)

t; usability > > issue to fix in the scope of this IEP: > > https://issues.apache.org/jira/browse/IGNITE-6925 < > > https://issues.apache.org/jira/browse/IGNITE-6925> > > > > — > > Denis > > > > > On Nov 15, 2017, at 9:21 AM, Anton Vinogradov < &g

Re: Switching Java language level to 8

+1 Can we switch to Java8 right now and then support Java9? That's the easiest way I think. On Thu, Dec 14, 2017 at 1:50 PM, Andrey Kuznetsov wrote: > Hi Igniters, > > As far as I know, we planned to get the project compilable/runnable on Java > 9 and then switch to Java 8

Re: Removing "fabric" from Ignite binary package name

+1б фо шур On Tue, Dec 19, 2017 at 9:59 AM, Vladimir Ozerov wrote: > +1б вуаштшеудн > > On Tue, Dec 19, 2017 at 2:34 AM, Valentin Kulichenko < > valentin.kuliche...@gmail.com> wrote: > > > +1 > > > > On Mon, Dec 18, 2017 at 12:24 PM, Dmitriy Setrakyan < >

Re: IgniteProjectionStartStopRestartSelfTest is failing for about a week on TC

t; again. > > 2017-12-12 16:25 GMT+03:00 Anton Vinogradov <avinogra...@gridgain.com>: > > > Hi, > > > > Seems we have merge conflict. > > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_ > > IgniteStartNodes=buildTypeHi

Re: Switching Java language level to 8

Correct :) Url is https://issues.apache.org/jira/browse/IGNITE-7203 On Thu, Dec 14, 2017 at 5:28 PM, Petr Ivanov wrote: > Sorry, I meant IGNITE-7203. > > > On 14 Dec 2017, at 17:26, vveider wrote: > > > > Got task IGNITE-7209. Started work on

Re: Ignite Enhancement Proposal #6 (Metrics)

>> The ticket for the memory metrics improved is anxiously waiting to be > >> solved: https://issues.apache.org/jira/browse/IGNITE-5796 < > >> https://issues.apache.org/jira/browse/IGNITE-5796> > >> > >> — > >> Denis > >> > On No

Re: Add emergency node closing handler to public Ignite API

Vova, That's not about "kill -9" or OOM, that's about case when node detected something and decided to stop itself (eg. persistence errors, IgniteOutOfMemoryException, ExchangeWorker died) Sure, we can't handle OOM or 100% CPU utilization by GC it that way, but we can handle some logical

Ignite Enhancement Proposal #6 (Metrics)

Igniters, As you may know Ignite have a lot of JMX based metric, but to perform more effective grid monitoring some new JMX metrics needs to be implemented. Here's the accumulated list of metrics I'd like to see at nearest Ignite version: Topology - Current topology version - Total server nodes

Re: IGNITE-6745. Status

Cergey, Please assign https://issues.apache.org/jira/browse/IGNITE-6745 to yourself and change status to Patch Available. Also, before asking review, please check that TeamCity status is ok, see

Re: Facility to detect long STW pauses and other system response degradations

Igniters, Since no one rejected proposal, let's start from part one. > I propose to add a special thread that will record current time every N > milliseconds and check the difference with the latest recorded value. > The maximum and total pause values for a certain period can be published in >

Re: Ignite Enhancement Proposal #7 (Internal problems detection)

inator or other > node, that 'current node is in STW, please wait longer than 3 heartbeat > timeout'. > > It is probable such pauses will occur not often? > > Sincerely, > Dmitriy Pavlov > > пн, 20 нояб. 2017 г. в 18:53, Anton Vinogradov <avinogra...@gridgain.com&g

Ignite Enhancement Proposal #7 (Internal problems detection)

Igniters, Internal problems may and, unfortunately, cause unexpected cluster behavior. We should determine behavior in case any of internal problem happened. Well known internal problems can be split to: 1) OOM or any other reason cause node crash 2) Situations required graceful node shutdown

Re: IGNITE-6745. Status

a 7. Maybe it's time to cease it > (especially when we have java 9 to worry about) ? > > > > -Original Message- > > From: Anton Vinogradov [mailto:avinogra...@gridgain.com] > > Sent: Monday, November 20, 2017 2:01 PM > > To: dev@ignite.apache.org > >

Re: Facility to detect long STW pauses and other system response degradations

ith an > unstable node. The events might be as follows - kill a node, restart a > node, trigger a custom script using Runtime.exec or other methods. > > What’d you think? Specifically on point 2. > > — > Denis > > > On Nov 20, 2017, at 6:47 AM, Anton

Re: Facility to detect long STW pauses and other system response degradations

eration systems? > > > пн, 20 нояб. 2017 г. в 14:55, Anton Vinogradov <avinogra...@gridgain.com>: > > > Igniters, > > > > Since no one rejected proposal, let's start from part one. > > > > > I propose to add a special thread that will record cu

Re: Facility to detect long STW pauses and other system response degradations

Yakov, Issue is https://issues.apache.org/jira/browse/IGNITE-6171 We split issue to #1 STW duration metrics #2 External monitoring allows to stop node during STW > Testing GC pause with java thread is > a bit strange and can give info only after GC pause finishes. That's ok since it's #1 On

Re: Facility to detect long STW pauses and other system response degradations

ode. The events might be as follows - kill a node, restart a > node, trigger a custom script using Runtime.exec or other methods. > > What’d you think? Specifically on point 2. > > — > Denis > > > On Nov 20, 2017, at 6:47 AM, Anton Vinogradov <avinogra...@gridgain.com>

Re: Add emergency node closing handler to public Ignite API

> Alternatively, we can expose this info through JMX only and ask user to get > instance of that bean manually. > > On Wed, Nov 15, 2017 at 1:19 PM, Anton Vinogradov < > avinogra...@gridgain.com> > wrote: > > > Vova, > > > > Could you point to metric you'

Re: Add emergency node closing handler to public Ignite API

Vova, Could you point to metric you're talking about? On Wed, Nov 15, 2017 at 1:06 PM, Andrey Kuznetsov wrote: > Vladimir, > > Could you please refine, what are local metrics? Should I extend Ignite > interface by adding something similar to dataRegionMetrics() or there is >

Re: Add emergency node closing handler to public Ignite API

wrote: > I am not quite I understand how tasks are split. How can we discuss > graceful shutdown without discussing the reasons of this shutdown? What > leads to it? > > On Wed, Nov 15, 2017 at 2:10 PM, Anton Vinogradov < > avinogra...@gridgain.com> > wrote: > > >

Re: Add emergency node closing handler to public Ignite API

be placed there? And why do we > need another configuration property and/or interface? We already have > LifecycleBean, where Ignite instance could be injected, so user is already > able to perform anything there. > > On Tue, Nov 14, 2017 at 7:46 PM, Anton Vinogradov < > avi

Re: Add emergency node closing handler to public Ignite API

s (not only in affected) and interruption > of service. Instead, administrator might decide to gradually reconfigure > and restart nodes one by one, instead of killing them all immediately. > > This is why we need the design first. > > On Wed, Nov 15, 2017 at 2:39 PM, Anton

Re: Ignite Enhancement Proposal #6 (Metrics)

unclear how to get started on it. > > Thanks, > D. > > On Tue, Nov 14, 2017 at 3:44 AM, Anton Vinogradov < > avinogra...@gridgain.com> > wrote: > > > Val, Denis, > > > > I've updated issues list, thanks for tips. > > > > On Tue, Nov 14, 2017 at

Re: Ignite Enhancement Proposal #6 (Metrics)

t; wrote: > > > On Tue, Nov 14, 2017 at 10:12 AM, Anton Vinogradov < > > avinogra...@gridgain.com > > > wrote: > > > > > Dmitriy, > > > > > > It looks like a confluence bug. > > > Please login and push refresh button at issues li

Re: Let's keep Apache Ignite docs up-to-date

+1 to Pavel's proposal, > Markdown can also be visualized by many IDEs, so it is easy to edit locally. IDEA shows Markdown out of the box. Yakov, > having docs under separate git repository We should not use separate git repo, Apache Ignite repo should be used. Documentation should be a part of

Re: Request for contributors permissions

Hi, Added you to the contributors list. Please go ahead and assign the tickets on yourself. On Wed, Nov 8, 2017 at 4:20 PM, Alex Plehanov wrote: > Hello Ignite Community! > > > My name is Aleksey. I want to contribute to Apache Ignite and want to start > with

[GitHub] ignite pull request #3004: Ignite 6411 benchmark

GitHub user anton-vinogradov opened a pull request: https://github.com/apache/ignite/pull/3004 Ignite 6411 benchmark You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6411-benchmark Alternatively you

Re: Internal problems requiring graceful node shutdown, reboot, etc.

Dmitry, Seems, we found that it's impossible to specify one action for all cases, but it's a good idea to allow user to decide what to do. We should make something like interface IgniteFailureHandler { IgniteFailureAction onFailure(IgniteFailureCause cause); } public enum IgniteFailureAction

Re: Ignite Enhancement Proposal #6 (Metrics)

PS Looks like you don't close pull requests when merging them to master. > Please make sure to include "This closes #prnum" in the commit messages, > as the autogenerated comments in JIRA suggest. > > > On Tue, Dec 5, 2017 at 12:41 PM, Anton Vinogradov < > avinogra...@

Re: IgniteProjectionStartStopRestartSelfTest is failing for about a week on TC

Hi, Seems we have merge conflict. https://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgniteStartNodes=buildTypeHistoryList_Ignite20Tests=%3Cdefault%3E On Tue, Dec 12, 2017 at 3:55 PM, Andrey Kuznetsov wrote: > Hi Igniters, > >

Re: Ignite Enhancement Proposal #6 (Metrics)

> The point is that pull requests should not be left open. > Either close them manually or use that autoclose feature. > > On Tue, Dec 5, 2017 at 4:02 PM, Anton Vinogradov <avinogra...@gridgain.com > > > wrote: > > > Pavel, > > > > >> There is correspon

Re: [VOTE] Apache Ignite 2.3.0 RC2

+1 (binding) I've checked release using automated checker https://ci.ignite.apache.org/viewLog.html?buildId=919727=AssemblyAndRelease_PrepareVote4CheckRcLicensesChecksum=buildLog Project should be visible for any PMC member. It checks: - licenses - pgp signatures - md5 & sha512 hashes -

Re: Ability to disable WAL in runtime to speed up load

gt; > > > > > > On Wed, Oct 25, 2017 at 2:35 PM, Vladimir Ozerov < > > voze...@gridgain.com > > > > > > > > > wrote: > > > > > > > > > > > Igniters, > > > > > > > > > > > > We

Re: Let's keep Apache Ignite docs up-to-date

Simplified: Current flow is over-complicated for me as developer, I see a lot of problems and have no clue how to fix them using readme.io or wiki. But I know how to fix them using git. I'm good at git, let me write documentation in way I'm good in :) On Tue, Oct 31, 2017 at 7:29 PM, Pavel

Re: Let's keep Apache Ignite docs up-to-date

+1 to git case. On Tue, Oct 31, 2017 at 12:35 PM, Pavel Tupitsyn wrote: > Hi Denis, > > Are there plans to move away from readme.io? > > * It is not properly versioned, which is very painful > * Documentation should be in Apache git, not on some third party site > >

Re: Ticket review checklist

t; > > > > > >> > > > > > > > > > > +1 > >> > > > > > > > > > > > >> > > > > > > > > > > > > > 2) Documentation > >> > > > > > >

Re: abbrevation rules plugin

e can consider Apache repo. > > But for wiki I need some distribution to attach first. > > Vyacheslav, could you remind me if we already have one? > > пн, 14 мая 2018 г. в 19:00, Anton Vinogradov <a...@apache.org>: > > > Awesome! > > > > Let's

Re: Disable WAL for several cache groups within one exchange

Ivan, enableWal/disableWal will return false in case enabling/disabling was caused not by this call. For example it will return false in case wal already enabled/disabled. Example: boolean res1 = srv.cluster().enableWal(CACHE_NAME); boolean res2 = srv.cluster().enableWal(CACHE_NAME); assert

Re: Ticket review checklist

gt; >> > > > > > > > > > > Hi Ed, > > > >> > > > > > > > > > > > > > >> > > > > > > > > > > Unfortunately some of these points are not good &

Re: Ticket review checklist

checklist looks pleasant enough for me. > > I'd like to suggest one minor change. In 1.6 *MUST* seems to be too strict, > *SHOULD* would be enough. It can be frustrating for API user if I explain > how to fix NPEs in a trivial way, for example. > > 2018-05-08 11:34 GMT+03:00 Anton

Re: Ticket review checklist

r > > > > releases. It should be possible to start newer version on data files > > > > created by the previous version > > > > 2.2) Thin client forward and backward compatibility *SHOULD* be > > > maintained > > > > between two consecutive m

[GitHub] ignite pull request #3959: IGNITE-8446 Ability to check and completely fill ...

GitHub user anton-vinogradov opened a pull request: https://github.com/apache/ignite/pull/3959 IGNITE-8446 Ability to check and completely fill transactions on crea… …tion Signed-off-by: Anton Vinogradov <a...@apache.org> You can merge this pull request into

Re: Looks like a bug in ServerImpl.joinTopology()

Alex, I checked reproducer you presented, please fix it according to the following rules 1) Never use System.out.println() as a part of reproducer, use assetrions if necessary. 2) Reproducer should be small. As small as possible. 3) Try to make reproducer clear. As crear as possible. In case

Re: Replace Cron4J with Quartz for ignite-schedule module.

Folks, How can it be at PATCH AVAILABLE since *none* of my latest comments (made Feb 8) are resolved at Upsource? Changed state to IP. пн, 23 апр. 2018 г. в 20:00, Dmitry Pavlov : > Hi Andrey, > > Could you please pick up review? > > Sincerely, > Dmitriy Pavlov > > пн, 23

Re: Ability to check and completely fill transactions on creation

Yakov, thank's for deep check. >> I think that we should think about some other solution instead of altering >> event sub-system. Thank's to your comments now I see that solution is not perfect. How about to create interface TransactionsValidator { boolean validate(IgniteTransactions tx){

Re: Ability to check and completely fill transactions on creation

г. в 17:48, Dmitriy Setrakyan <dsetrak...@apache.org>: > Anton, > > The change looks very questionable. We cannot be adding configuration > validators for every piece of Ignite API. What is it you are trying to > achieve? > > D. > > On Mon, May 21, 2018 at 7:22 AM,

Re: Ability to check and completely fill transactions on creation

or with empty timeout. This will allow you to find a team responsible for that and make sure that they will fix their code. пн, 21 мая 2018 г. в 18:14, Anton Vinogradov <a...@apache.org>: > Dmitriy, > > Main idea is to restrict transaction creation in case label or timeout are > not se

[GitHub] ignite pull request #4036: IGNITE-8446 Ability to check and completely fill ...

GitHub user anton-vinogradov opened a pull request: https://github.com/apache/ignite/pull/4036 IGNITE-8446 Ability to check and completely fill transactions on crea… …tion Signed-off-by: Anton Vinogradov <a...@apache.org> You can merge this pull request into

Re: Ability to check and completely fill transactions on creation

/4036/files Public API changes: New EvenType: EVT_TX_STARTED = 129. New Event: TransactionEvent extends EventAdapter { private IgniteInternalTx tx; } In case there are no objection I'll merge the changes soon. пт, 6 апр. 2018 г. в 14:12, Anton Vinogradov <a...@apache.org>: > >

Re: Ability to check and completely fill transactions on creation

Dmitriy, Yakov Are there any objections to updated design taking into account the comments I provided? пн, 21 мая 2018 г. в 18:49, Anton Vinogradov <a...@apache.org>: > One more case is to analize and log tx's creators info without tx creation > restriction. > This is very im

Re: Ability to check and completely fill transactions on creation

e share your thoughts on that? чт, 24 мая 2018 г. в 8:58, Dmitriy Setrakyan <dsetrak...@apache.org>: > On Wed, May 23, 2018 at 4:08 AM, Anton Vinogradov <a...@apache.org> wrote: > > > Dmitriy, Yakov > > > > Are there any objections to updated design t

<    1   2   3   4   5   6   7   8   9   >