[jira] [Created] (IGNITE-10648) Ignite hang to stop if node wasn't started completely. GridTcpRestNioListener hangs on latch.

Pavel Voronkin created IGNITE-10648: --- Summary: Ignite hang to stop if node wasn't started completely. GridTcpRestNioListener hangs on latch. Key: IGNITE-10648 URL: https://issues.apache.org/jira/browse/IGNITE-10

[MTCGA]: new failures in builds [2421292] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize

Re: [Fwd: Returned post for annou...@apache.org]

Ok, I'll fix issues 3-5. On Mon, Dec 10, 2018 at 11:44 AM Denis Magda wrote: > Forwarding to the dev list. > > *Prachi*, could you please help us with 3-5? It requires minor updates on > the webpage. > > *Sergey K.*, *Peter*, could you assist with 1 and 2? > > -- > Denis > > On Fri, Dec 7, 2018

[MTCGA]: new failures in builds [2375823] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize

[MTCGA]: new failures in builds [2446283, 2368367] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize

Re: Packt wants to feature books

Hello Hishit, Thanks for sharing the news, great! Prachi, could you please add a reference to the to our website menu? -- Denis On Tue, Dec 11, 2018 at 10:14 AM Nishit Rajput wrote: > Hi team, > > > I am Nishit from Packt. We publish over 50 books related to trending and > upcoming technologi

Packt wants to feature books

Hi team, I am Nishit from Packt. We publish over 50 books related to trending and upcoming technologies every month. We also feature various books on Project websites. We would be interested in featuring our recently published book Apache Ignite Quick Start Guide

[jira] [Created] (IGNITE-10647) Spark example code potentially confusing

Stephen Darlington created IGNITE-10647: --- Summary: Spark example code potentially confusing Key: IGNITE-10647 URL: https://issues.apache.org/jira/browse/IGNITE-10647 Project: Ignite Iss

Re: [MTCGA]: new failures in builds [2342751] needs to be handled

This notification probably came from some old TC Bot DB records, while the test is flaky - it is not a mistake. Now server uses time-based statistics, so bot keeps data for a longer time. вт, 11 дек. 2018 г. в 20:11, : > Hi Igniters, > > I've detected some new issue on TeamCity to be handled. Y

[jira] [Created] (IGNITE-10646) Typo in partition map exchange diagnostics

Stephen Darlington created IGNITE-10646: --- Summary: Typo in partition map exchange diagnostics Key: IGNITE-10646 URL: https://issues.apache.org/jira/browse/IGNITE-10646 Project: Ignite I

Re: Is it time to move forward to JUnit4 (5)?

Hi Ivan, That's a very good question and I think you spotted a point where Ignite test developer's preferences need to change when migrating from Junit 3 to 4. In brief, when developing under JUnit 3 there were good reasons to prefer our homebrew template methods (beforeTestsStarted, beforeTest,

[MTCGA]: new failures in builds [2342751] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize

RE: Pre-touch for Ignite off-heap memory

Igniters, What is being suggested here is an Ignite off-heap’s version of Java’s -XX:+AlwaysPreTouch. The latter is known to be used to guarantee that the committed memory is backed by physical RAM. This ensures that a) JVM doesn’t have to do it during the actual work (avoiding overhead for phy

Re: [DISCUSSION] Relocation of Apache git repositories from git-wip-us.apache.org to GitBox

Given that there is no option to stay on the old repository and mass-migration is scheduled for Feb, 7th, I think it is better to prepare and move the repository before the date. As far as I understand, from developers standpoint we only need to change the git remote entry. Petr, Sergey, can you a

Re: [DISCUSSION] Relocation of Apache git repositories from git-wip-us.apache.org to GitBox

Hi All, The Apache Ignite still has a repository on git-wip-us for its code, as well, for release. Does anyone have a problem with moving over the Ignite git-wip-us repository to gitbox voluntarily? This means integrated access and easy PRs (write access to the GitHub repo). We need to document

Re: Clean up of our PRs and IEPs before 2019

Infra should be the owner. BTW, How about to specify strict PR flow and get community approval before starting such batch closes? On Tue, Dec 11, 2018 at 5:35 PM Pavel Tupitsyn wrote: > Dmitriy, admin rights allow closing any PRs, I wonder who is admin for > Ignite GitHub mirror. > > On Tue, De

[jira] [Created] (IGNITE-10645) SQL properties ownership flag should be set at configuration parsing, not query execution.

Pavel Kuznetsov created IGNITE-10645: Summary: SQL properties ownership flag should be set at configuration parsing, not query execution. Key: IGNITE-10645 URL: https://issues.apache.org/jira/browse/IGNITE-106

[jira] [Created] (IGNITE-10644) CorruptedTreeException might occur after force node kill during transaction

Pavel Voronkin created IGNITE-10644: --- Summary: CorruptedTreeException might occur after force node kill during transaction Key: IGNITE-10644 URL: https://issues.apache.org/jira/browse/IGNITE-10644 P

[jira] [Created] (IGNITE-10643) GridCacheContextInfo should not use isCacheContextInited() method to calculate constant properties

Vladimir Ozerov created IGNITE-10643: Summary: GridCacheContextInfo should not use isCacheContextInited() method to calculate constant properties Key: IGNITE-10643 URL: https://issues.apache.org/jira/browse/IG

Re: Clean up of our PRs and IEPs before 2019

Dmitriy, admin rights allow closing any PRs, I wonder who is admin for Ignite GitHub mirror. On Tue, Dec 11, 2018 at 1:29 PM Павлухин Иван wrote: > Dmitiy, > > I see the point. And also I see that not everyone supports a suggested > cleanup. (I personally like the idea very much). But all in all

Re: [DISCUSSION] Performance issue with cluster-wide cache metrics distribution

Denis, I measure the impact of metrics collecting on my laptop, it's about 5 seconds on each node for collecting metrics of 1000 caches (all caches in one cache group) with 32000 partitions. All this time tcp-disco-msg-worker is blocked. Guys, thanks for your proposals, I'd filled ticket [1]. [1]

[jira] [Created] (IGNITE-10642) Cache metrics distribution mechanism should be changed from broadcast to request-response communication pattern

Aleksey Plekhanov created IGNITE-10642: -- Summary: Cache metrics distribution mechanism should be changed from broadcast to request-response communication pattern Key: IGNITE-10642 URL: https://issues.apache.o

[ML][DISCUSSION] ML Package reorganization

Igniters, I want to discuss package structure for ML module. Actually I don't like our current package organization. The main problem is that we have lots of different packages under root package. For examples algorithm related packages on same level like some utility infrastructure packages such

Re: [Result][VOTE] Creation dedicated list for github notifiacations

IMO it is not possible, but you can always ask Infra. One from ideas behind lists is forever-archived interaction, so I guess it is not possible to remove something from a list. вт, 11 дек. 2018 г. в 15:27, Denis Mekhanikov : > Great news! > > Is it possible to move all GitHub messages from the

[jira] [Created] (IGNITE-10641) [ML] Package reorganization

Yury Babak created IGNITE-10641: --- Summary: [ML] Package reorganization Key: IGNITE-10641 URL: https://issues.apache.org/jira/browse/IGNITE-10641 Project: Ignite Issue Type: Improvement

Re: [Result][VOTE] Creation dedicated list for github notifiacations

Great news! Is it possible to move all GitHub messages from the archive of the developers list to the newly-created one? Denis вт, 11 дек. 2018 г. в 10:05, Dmitriy Pavlov : > Hi Igniters, > > Infra changed notifications, so now GitHub emails are being sent to > notifications@ > > Web UI: https:

[jira] [Created] (IGNITE-10640) Create cluster-wide MetaStorage analogue

Ivan Bessonov created IGNITE-10640: -- Summary: Create cluster-wide MetaStorage analogue Key: IGNITE-10640 URL: https://issues.apache.org/jira/browse/IGNITE-10640 Project: Ignite Issue Type: N

Re: Is it time to move forward to JUnit4 (5)?

Ed, Oleg, Could you please clarify on the following point: > 3. Add @Before, @After on methods which should run before, after a > test (setUp, tearDown in current approach). Beforehand we used to override beforeTestsStarted, beforeTest, afterTest, afterTestsStarted. What will happen with these met

Re: Clean up of our PRs and IEPs before 2019

Dmitiy, I see the point. And also I see that not everyone supports a suggested cleanup. (I personally like the idea very much). But all in all I think that everyone is free to close his own PRs if he would like to. As already have done I, Pavel and others. Nikolay, > 3. I dont' see any issues wi

[jira] [Created] (IGNITE-10639) Proof of concept for internal description for packages

Dmitriy Pavlov created IGNITE-10639: --- Summary: Proof of concept for internal description for packages Key: IGNITE-10639 URL: https://issues.apache.org/jira/browse/IGNITE-10639 Project: Ignite

Re: Clean up of our PRs and IEPs before 2019

+1 When I just joined the project I was really confused with the huge number of opened PRs with poor description and cryptic reason. This can give to newcomers a weird representation of what is actually happening in the project. Don't be lazy, just spend 5-10 minutes of free time and clean up afte

[jira] [Created] (IGNITE-10638) Improve CacheNoAffinityExchangeTest.testNoAffinityChangeOnClientLeftWithMergedExchanges to cover persistence case

Pavel Voronkin created IGNITE-10638: --- Summary: Improve CacheNoAffinityExchangeTest.testNoAffinityChangeOnClientLeftWithMergedExchanges to cover persistence case Key: IGNITE-10638 URL: https://issues.apache.org/

[jira] [Created] (IGNITE-10637) MVCC: Make diagnostic log messages more informative.

Andrew Mashenkov created IGNITE-10637: - Summary: MVCC: Make diagnostic log messages more informative. Key: IGNITE-10637 URL: https://issues.apache.org/jira/browse/IGNITE-10637 Project: Ignite

[jira] [Created] (IGNITE-10636) Deadlock on stopping node due to segmentation

Anton Kalashnikov created IGNITE-10636: -- Summary: Deadlock on stopping node due to segmentation Key: IGNITE-10636 URL: https://issues.apache.org/jira/browse/IGNITE-10636 Project: Ignite