[GitHub] ignite pull request #5463: IGNITE-10301 GridToStringBuilder is broken for cl...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5463 ---

[jira] [Created] (IGNITE-10454) [TC Bot] Create page with muted tests

Ryabov Dmitrii created IGNITE-10454: --- Summary: [TC Bot] Create page with muted tests Key: IGNITE-10454 URL: https://issues.apache.org/jira/browse/IGNITE-10454 Project: Ignite Issue Type: Ta

[GitHub] ignite pull request #4480: IGNITE-8640 earlier validation of cache config

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4480 ---

[jira] [Created] (IGNITE-10455) MVCC: Tx timeout can cause update counters inconsistency.

Roman Kondakov created IGNITE-10455: --- Summary: MVCC: Tx timeout can cause update counters inconsistency. Key: IGNITE-10455 URL: https://issues.apache.org/jira/browse/IGNITE-10455 Project: Ignite

[jira] [Created] (IGNITE-10456) Lost data in cache after restart node

Ivan Fedotov created IGNITE-10456: - Summary: Lost data in cache after restart node Key: IGNITE-10456 URL: https://issues.apache.org/jira/browse/IGNITE-10456 Project: Ignite Issue Type: Test

[jira] [Created] (IGNITE-10457) MVCC TX: GridIndexRebuildWithMvccEnabledSelfTest fails

Igor Seliverstov created IGNITE-10457: - Summary: MVCC TX: GridIndexRebuildWithMvccEnabledSelfTest fails Key: IGNITE-10457 URL: https://issues.apache.org/jira/browse/IGNITE-10457 Project: Ignite

[GitHub] ignite pull request #5521: IGNITE-10435

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/5521 ---

[GitHub] ignite pull request #4892: Ignite 2.5.3

Github user alamar closed the pull request at: https://github.com/apache/ignite/pull/4892 ---

[jira] [Created] (IGNITE-10458) MVCC: Create "Cache (Failover) 1" test suite for MVCC mode.

Andrew Mashenkov created IGNITE-10458: - Summary: MVCC: Create "Cache (Failover) 1" test suite for MVCC mode. Key: IGNITE-10458 URL: https://issues.apache.org/jira/browse/IGNITE-10458 Project: Igni

[jira] [Created] (IGNITE-10459) MVCC: Create "Cache (Failover) 2" test suite for MVCC mode.

Andrew Mashenkov created IGNITE-10459: - Summary: MVCC: Create "Cache (Failover) 2" test suite for MVCC mode. Key: IGNITE-10459 URL: https://issues.apache.org/jira/browse/IGNITE-10459 Project: Igni

[jira] [Created] (IGNITE-10461) MVCC: Create "PDS 1" test suite for MVCC mode.

Andrew Mashenkov created IGNITE-10461: - Summary: MVCC: Create "PDS 1" test suite for MVCC mode. Key: IGNITE-10461 URL: https://issues.apache.org/jira/browse/IGNITE-10461 Project: Ignite I

[jira] [Created] (IGNITE-10462) MVCC: Create "PDS 2" test suite for MVCC mode.

Andrew Mashenkov created IGNITE-10462: - Summary: MVCC: Create "PDS 2" test suite for MVCC mode. Key: IGNITE-10462 URL: https://issues.apache.org/jira/browse/IGNITE-10462 Project: Ignite I

[jira] [Created] (IGNITE-10463) MVCC: Create "PDS 3" test suite for MVCC mode.

Andrew Mashenkov created IGNITE-10463: - Summary: MVCC: Create "PDS 3" test suite for MVCC mode. Key: IGNITE-10463 URL: https://issues.apache.org/jira/browse/IGNITE-10463 Project: Ignite I

[jira] [Created] (IGNITE-10464) MVCC: Create "PDS 4" test suite for MVCC mode.

Andrew Mashenkov created IGNITE-10464: - Summary: MVCC: Create "PDS 4" test suite for MVCC mode. Key: IGNITE-10464 URL: https://issues.apache.org/jira/browse/IGNITE-10464 Project: Ignite I

[jira] [Created] (IGNITE-10460) MVCC: Create "Cache (Failover) 3" test suite for MVCC mode.

Andrew Mashenkov created IGNITE-10460: - Summary: MVCC: Create "Cache (Failover) 3" test suite for MVCC mode. Key: IGNITE-10460 URL: https://issues.apache.org/jira/browse/IGNITE-10460 Project: Igni

[jira] [Created] (IGNITE-10465) TTL Worker can fails on node start due to a race.

Andrew Mashenkov created IGNITE-10465: - Summary: TTL Worker can fails on node start due to a race. Key: IGNITE-10465 URL: https://issues.apache.org/jira/browse/IGNITE-10465 Project: Ignite

Re: Historical rebalance

Ivan, different transactions may be applied in different order on backup nodes. That's why we need an active tx set and some sorting by their update times. The idea is to identify a point in time which starting from we may lost some updates. This point: 1) is the last acknowledged by all backup

[jira] [Created] (IGNITE-10466) Test IgniteClusterActivateDeactivateTestWithPersistenceAndMemoryReuse fails sporadically.

Andrew Mashenkov created IGNITE-10466: - Summary: Test IgniteClusterActivateDeactivateTestWithPersistenceAndMemoryReuse fails sporadically. Key: IGNITE-10466 URL: https://issues.apache.org/jira/browse/IGNITE-1

[jira] [Created] (IGNITE-10467) MVCC: Failure handling for vacuum threads.

Roman Kondakov created IGNITE-10467: --- Summary: MVCC: Failure handling for vacuum threads. Key: IGNITE-10467 URL: https://issues.apache.org/jira/browse/IGNITE-10467 Project: Ignite Issue Typ

[jira] [Created] (IGNITE-10468) MVCC TX: Failover

Igor Seliverstov created IGNITE-10468: - Summary: MVCC TX: Failover Key: IGNITE-10468 URL: https://issues.apache.org/jira/browse/IGNITE-10468 Project: Ignite Issue Type: Task R

[jira] [Created] (IGNITE-10469) TcpCommunicationSpi does not break tcp connection after IdleConnectionTimeout seconds of inactivity

Igor Kamyshnikov created IGNITE-10469: - Summary: TcpCommunicationSpi does not break tcp connection after IdleConnectionTimeout seconds of inactivity Key: IGNITE-10469 URL: https://issues.apache.org/jira/browse

[GitHub] ignite pull request #5501: IGNITE-10412 Reproducer

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/5501 ---

[GitHub] ignite pull request #5355: Tdr 127 ag

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/5355 ---

[GitHub] ignite pull request #5372: Tdr 127 ag master

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/5372 ---

[jira] [Created] (IGNITE-10470) MVCC: Missed error handling for mvcc transaction updates.

Roman Kondakov created IGNITE-10470: --- Summary: MVCC: Missed error handling for mvcc transaction updates. Key: IGNITE-10470 URL: https://issues.apache.org/jira/browse/IGNITE-10470 Project: Ignite

[jira] [Created] (IGNITE-10471) SQL: Alter table to add column sytax doesn't support the user types but drop column can drop such fields

Andrey Aleksandrov created IGNITE-10471: --- Summary: SQL: Alter table to add column sytax doesn't support the user types but drop column can drop such fields Key: IGNITE-10471 URL: https://issues.apache.org/ji

[jira] [Created] (IGNITE-10472) MVCC: EntryProcessor resource injection missed.

Andrew Mashenkov created IGNITE-10472: - Summary: MVCC: EntryProcessor resource injection missed. Key: IGNITE-10472 URL: https://issues.apache.org/jira/browse/IGNITE-10472 Project: Ignite

[GitHub] ololo3000 opened a new pull request #85: IGNITE-10436 Add ticket and PR links on report TC Bot page

ololo3000 opened a new pull request #85: IGNITE-10436 Add ticket and PR links on report TC Bot page URL: https://github.com/apache/ignite-teamcity-bot/pull/85 This is an automated message from the Apache Git Service. To resp

[jira] [Created] (IGNITE-10473) MVCC: Add support for nested system transactions.

Andrew Mashenkov created IGNITE-10473: - Summary: MVCC: Add support for nested system transactions. Key: IGNITE-10473 URL: https://issues.apache.org/jira/browse/IGNITE-10473 Project: Ignite

[jira] [Created] (IGNITE-10474) MVCC: IgniteCacheConnectionRecovery10ConnectionsTest.testConnectionRecovery fails.

Andrew Mashenkov created IGNITE-10474: - Summary: MVCC: IgniteCacheConnectionRecovery10ConnectionsTest.testConnectionRecovery fails. Key: IGNITE-10474 URL: https://issues.apache.org/jira/browse/IGNITE-10474

[jira] [Created] (IGNITE-10475) Introduce IDEA async debugger annotations.

Ivan Bessonov created IGNITE-10475: -- Summary: Introduce IDEA async debugger annotations. Key: IGNITE-10475 URL: https://issues.apache.org/jira/browse/IGNITE-10475 Project: Ignite Issue Type:

Re: Change code style inspections to use red mark for those used at Teamcity build checks (IGNITE-10450)

Hi Ivan, You are right that these things will distract people and from this perspective it is very well justified that vast majority of style deviations (currently, all of them) are marked yellow. These are non-critical and if developer ignores them nothing immediately bad happens. (For the sake

[jira] [Created] (IGNITE-10476) Merge similar tests.

Andrew Mashenkov created IGNITE-10476: - Summary: Merge similar tests. Key: IGNITE-10476 URL: https://issues.apache.org/jira/browse/IGNITE-10476 Project: Ignite Issue Type: Test

[jira] [Created] (IGNITE-10477) An empty cluster falls if wal segment size small

ARomantsov created IGNITE-10477: --- Summary: An empty cluster falls if wal segment size small Key: IGNITE-10477 URL: https://issues.apache.org/jira/browse/IGNITE-10477 Project: Ignite Issue Type

[GitHub] ignite pull request #5485: IGNITE-10354 Failing client node due to not recei...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5485 ---

Re: Apache Ignite 2.7. Last Mile

Hello Igniters. During my work at the ticket IGNITE-10376 I found that it started to fail after integration Continuous Query with MVCC. I launched CacheContinuousQueryOrderingEventTest.testAtomicOnheapTwoBackupAsyncFullSync before correspondin

[GitHub] ignite pull request #5530: Ignite ign 12530

GitHub user aealeksandrov opened a pull request: https://github.com/apache/ignite/pull/5530 Ignite ign 12530 created for TC run You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-ign-12530 Alternatively

Re: Change code style inspections to use red mark for those used at Teamcity build checks (IGNITE-10450)

Hi Oleg, First of all I am not against giving it a try. Let's try it. P.S. Did not really get what was the main problem related to IGNITE-10399 [1]. I suppose it should go: simple problem -- fast fix. [1] https://issues.apache.org/jira/browse/IGNITE-10399 чт, 29 нояб. 2018 г. в 16:04, oignatenko

[GitHub] ignite pull request #5526: IGNITE-10449: Fix javadoc and typos in ML module.

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5526 ---

[jira] [Created] (IGNITE-10478) SQL index creation fails if cache, which query method was called, was statically configured

Eduard Shangareev created IGNITE-10478: -- Summary: SQL index creation fails if cache, which query method was called, was statically configured Key: IGNITE-10478 URL: https://issues.apache.org/jira/browse/IGNIT

[GitHub] ignite pull request #5531: IGNITE-5759 unmuted testPartitionRent test

GitHub user akalash opened a pull request: https://github.com/apache/ignite/pull/5531 IGNITE-5759 unmuted testPartitionRent test You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5759-2 Alternatively

Re: Apache Ignite 2.7. Last Mile

Vladimir, can you please take a look at https://issues.apache.org/jira/browse/IGNITE-10376? --Yakov

Re: Change code style inspections to use red mark for those used at Teamcity build checks (IGNITE-10450)

Hi Ivan, Павлухин Иван wrote > P.S. Did not really get what was the main problem related to > IGNITE-10399 [1]. I suppose it should go: simple problem -- fast fix. Well, speaking of IGNITE-10399 it turned out that problem is indeed simple and fix was fast, just as you wrote. What looked wrong i

[GitHub] ignite pull request #5532: IGNITE-10353: Spring Add Update/Delete support fo...

GitHub user JonathanGiovanny opened a pull request: https://github.com/apache/ignite/pull/5532 IGNITE-10353: Spring Add Update/Delete support for Spring Data Added Query support for Delete, Remove and ```@Query``` support for other DML queries including ```UPDATE```, ```DELETE``` an

[jira] [Created] (IGNITE-10479) [ML] Umbrella: Ensemble training and inference

Yury Babak created IGNITE-10479: --- Summary: [ML] Umbrella: Ensemble training and inference Key: IGNITE-10479 URL: https://issues.apache.org/jira/browse/IGNITE-10479 Project: Ignite Issue Type: N

[jira] [Created] (IGNITE-10480) [ML] Stacking for training and inference

Yury Babak created IGNITE-10480: --- Summary: [ML] Stacking for training and inference Key: IGNITE-10480 URL: https://issues.apache.org/jira/browse/IGNITE-10480 Project: Ignite Issue Type: New Fea

[GitHub] ignite pull request #5533: IGNITE-10289: Import models from XGBoost

GitHub user dmitrievanthony opened a pull request: https://github.com/apache/ignite/pull/5533 IGNITE-10289: Import models from XGBoost You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10289 Alternati

[jira] [Created] (IGNITE-10481) [ML] Examples of stacking usage

Yury Babak created IGNITE-10481: --- Summary: [ML] Examples of stacking usage Key: IGNITE-10481 URL: https://issues.apache.org/jira/browse/IGNITE-10481 Project: Ignite Issue Type: Sub-task

[GitHub] ignite pull request #5329: IGNITE-10108: Refactored a test to avoid passing ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5329 ---

Re: Apache Ignite 2.7. Last Mile

I think that it's not a blocker since MVCC is in the beta state and some of the APIs might not work well with it yet. Apart from that, are we done with the stabilization and ready to start the vote? What blocks us from that? -- Denis On Thu, Nov 29, 2018 at 7:43 AM Yakov Zhdanov wrote: > Vlad

Re: Apache Ignite 2.7. Last Mile

Hello, Denis. Nothing blocks now. I preparing vote artifacts right now. There are some issues with TC tasks. I think I resolve them in a couple of hours. чт, 29 нояб. 2018 г., 19:30 Denis Magda dma...@apache.org: > I think that it's not a blocker since MVCC is in the beta state and some of > the

[jira] [Created] (IGNITE-10482) Print stacktrace of the blocked thread in failure handler.

Roman Kondakov created IGNITE-10482: --- Summary: Print stacktrace of the blocked thread in failure handler. Key: IGNITE-10482 URL: https://issues.apache.org/jira/browse/IGNITE-10482 Project: Ignite

Re: Apache Ignite 2.7. Last Mile

Denis, It looks like the failing test is related to existing ATOMIC caches but it was broken by the MVCC commit, so it is a regression. Let's wait for Vladimir Ozerov or Igor Seliverstov to comment. чт, 29 нояб. 2018 г. в 19:32, Nikolay Izhikov : > Hello, Denis. > > Nothing blocks now. > I prepa

Re: Apache Ignite 2.7. Last Mile

Ivan, Could you provide a bit more details? I don't see any NPE among all available logs. I don't think the issue is caused by changes in scope of IGNITE-7953. The test fails both before

[jira] [Created] (IGNITE-10483) MVCC: Enlist request deserialization failure causes grid hanging.

Andrew Mashenkov created IGNITE-10483: - Summary: MVCC: Enlist request deserialization failure causes grid hanging. Key: IGNITE-10483 URL: https://issues.apache.org/jira/browse/IGNITE-10483 Project

[GitHub] ignite pull request #5411: IGNITE-8379 Add maven-surefire-plugin support for...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5411 ---

Re: Change code style inspections to use red mark for those used at Teamcity build checks (IGNITE-10450)

Hi Oleg, Thank you for the story. Now I see the concerns better. чт, 29 нояб. 2018 г. в 18:45, oignatenko : > > Hi Ivan, > > > Павлухин Иван wrote > > P.S. Did not really get what was the main problem related to > > IGNITE-10399 [1]. I suppose it should go: simple problem -- fast fix. > > Well, sp

[jira] [Created] (IGNITE-10484) Activate/deactivate cluster suite hangs sporadically

Alexey Goncharuk created IGNITE-10484: - Summary: Activate/deactivate cluster suite hangs sporadically Key: IGNITE-10484 URL: https://issues.apache.org/jira/browse/IGNITE-10484 Project: Ignite

[GitHub] asfgit closed pull request #84: IGNITE-9542 new invocation history implementation

asfgit closed pull request #84: IGNITE-9542 new invocation history implementation URL: https://github.com/apache/ignite-teamcity-bot/pull/84 This is an automated message from the Apache Git Service. To respond to the message

[GitHub] ignite pull request #5534: IGNITE-10484 Fixed activate/deactivate hang

GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/5534 IGNITE-10484 Fixed activate/deactivate hang You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10484 Alternative

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

Igniters, The result is successful. No "-1". 11 "+1". 2 "0". Vote thread: http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Creation-dedicated-list-for-github-notifiacations-td38485.html

Re: Historical rebalance

"If more recent WAL records will contain *ALL* updates of the transaction" -> "More recent WAL records will contain *ALL* updates of the transaction" On Thu, Nov 29, 2018 at 10:15 PM Vladimir Ozerov wrote: > Igor, > > Yes, I tried to draw different configurations, and it really seems to > work,

Re: Historical rebalance

Igor, Yes, I tried to draw different configurations, and it really seems to work, despite of being very hard to proof due to non-inituitive HB edges. So let me try to spell the algorithm once again to make sure that we are on the same page here. 1) There are two nodes - primary (P) and backup (B)

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

Denis, could you please create a new list for Apache Ignite, e.g. notificati...@ignite.apache.org ? Only PMC Chair can create a list https://infra.apache.org/ Create list feature has been restricted to ASF members and PMC chairs only. Thank you in advance. Sincerely, Dmitriy Pavlov чт, 29 нояб

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

A request has been submitted. -- Denis On Thu, Nov 29, 2018 at 11:45 AM Dmitriy Pavlov wrote: > Denis, could you please create a new list for Apache Ignite, e.g. > notificati...@ignite.apache.org ? > > Only PMC Chair can create a list https://infra.apache.org/ > > Create list feature has been

Re: IEP-24: SQL Partition Pruning

Vladimir, thanks for the extensive description. Everything is clear for me from a user perspective. Hope Sergi, Taras, and other SQL experts would share their feedback. -- Denis On Mon, Nov 26, 2018 at 6:33 AM Vladimir Ozerov wrote: > Igniters, > > I prepared and IEP-24 [1] for so-called "part

Re: Thin clients all in one

Hi Stepan, pls check the Ignite cfg you use - see the comments in the jira. Also, the examples executors (including AuthTlsExample) are included into NodeJS test suite in TeamCity which run periodically and successfully passed. Eg. the latest one: https://ci.ignite.apache.org/viewLog.html?bui

Re: Historical rebalance

Vladimir, Look at my example: One active transaction (Tx1 which does opX ops) while another tx (Tx2 which does opX' ops) is finishes with uc4: uc1--op1op2---uc2--op1'uc3--uc4---op3X- Node1 uc1op1uc2op2uc3--op3--uc4cp1

[jira] [Created] (IGNITE-10485) Ability to get know more about cluster state before NODE_JOINED event is fired cluster-wide

Pavel Kovalenko created IGNITE-10485: Summary: Ability to get know more about cluster state before NODE_JOINED event is fired cluster-wide Key: IGNITE-10485 URL: https://issues.apache.org/jira/browse/IGNITE-10

[jira] [Created] (IGNITE-10486) Web console: wrong custom validation messages priority

Ilya Borisov created IGNITE-10486: - Summary: Web console: wrong custom validation messages priority Key: IGNITE-10486 URL: https://issues.apache.org/jira/browse/IGNITE-10486 Project: Ignite I

Re: [GitHub] ignite pull request #5528: Continuous query node restart fails when remote filter factory is defined

Looks like this issue has already been filed: https://issues.apache.org/jira/browse/IGNITE-9181 The actual failing code: `assert rmtFilterFactory != null;` Looks like the filter factory is not propagated to the remote node. Note: When I use setRemoteFilter() (which is now

Re: lost partition recovery with native persistence should not require resetLostPartitions call

Ivan, Thanks for the pointer to discussion. It doesn't actually address the point around the need for 'resetLostPartitions()'. It does point to a ticket that would fix the logic in it when BLT is used. My concern is that Ignite relies on the user to call this method at all. Original message

[GitHub] ignite pull request #5031: IGNITE-9938 Updated ScalaTest version

Github user akuznetsov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/5031 ---

[jira] [Created] (IGNITE-10487) SQL: Make sure that partition pruning is integrated with DML properly

Vladimir Ozerov created IGNITE-10487: Summary: SQL: Make sure that partition pruning is integrated with DML properly Key: IGNITE-10487 URL: https://issues.apache.org/jira/browse/IGNITE-10487 Proje

[VOTE] Apache Ignite 2.7.0 RC1

Igniters, We've uploaded a 2.7.0 release candidate to https://dist.apache.org/repos/dist/dev/ignite/2.7.0-rc1/ Git tag name is 2.7.0-rc1 This release includes the following changes: Apache Ignite In-Memory Database and Caching Platform 2.7 --

Re: [VOTE] Apache Ignite 2.7.0 RC1

+1 пт, 30 нояб. 2018 г., 9:59 Nikolay Izhikov nizhi...@apache.org: > Igniters, > > We've uploaded a 2.7.0 release candidate to > > https://dist.apache.org/repos/dist/dev/ignite/2.7.0-rc1/ > > Git tag name is 2.7.0-rc1 > > This release includes the following changes: > > Apache Ignite In-Memory Da

Re: Apache Ignite 2.7. Last Mile

Igor, NPE is available in a full log, now I also attached it in the ticket. IGNITE-7953 was commited on the 15 October. I could not take a look on the testAtomicOnheapTwoBackupAsyncFullSync before this date, because

Re: Apache Ignite 2.7. Last Mile

Ivan. Please, provide a link for a ticket with NPE stack trace attached. I've looked at IGNITE-10376 and can't see any attachments. пт, 30 нояб. 2018 г., 10:14 Ivan Fedotov ivanan...@gmail.com: > Igor, > NPE is available in a full log, now I also attached it in the ticket. > > IGNITE-7953 > < >

[jira] [Created] (IGNITE-10488) ClusterCachesInfo.validateCacheGroupConfiguration should check cache compression configuration

Vasiliy Sisko created IGNITE-10488: -- Summary: ClusterCachesInfo.validateCacheGroupConfiguration should check cache compression configuration Key: IGNITE-10488 URL: https://issues.apache.org/jira/browse/IGNITE-104