[MTCGA]: new failures in builds [1848300] 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

Ignite and Spark on Yarn

Can anyone familiar with the subject respond here? https://stackoverflow.com/questions/52488073/ignite-yarn-and-hortonworks D.

[jira] [Created] (IGNITE-9712) SQL: Select query benchmarks

Pavel Kuznetsov created IGNITE-9712: --- Summary: SQL: Select query benchmarks Key: IGNITE-9712 URL: https://issues.apache.org/jira/browse/IGNITE-9712 Project: Ignite Issue Type: Task

Re: ML examples wrap logic in IgniteThread. Why?

Denis, Thanks for this notice, actually this is some kind of atavism. Run this code inside IgniteThread was a requirement when we had a distributed matrices. But now all our algorithms builds over distributed datasets and we don't need it anymore. I created JIRA ticket

[jira] [Created] (IGNITE-9711) [ML] Remove IgniteThread wrapper from ml examples

Yury Babak created IGNITE-9711: -- Summary: [ML] Remove IgniteThread wrapper from ml examples Key: IGNITE-9711 URL: https://issues.apache.org/jira/browse/IGNITE-9711 Project: Ignite Issue Type: Ne

[GitHub] ignite pull request #4846: IGNITE-9550 Get operation returns null for a lost...

GitHub user dgovorukhin opened a pull request: https://github.com/apache/ignite/pull/4846 IGNITE-9550 Get operation returns null for a lost partition with READ_SAFE policy You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain

[GitHub] ignite pull request #4844: IGNITE-9550 change affReady future listen

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

ML examples wrap logic in IgniteThread. Why?

Yury, ML folks, I've mentioned a strange thing. Looks like every example we have wraps up its logic in the following block IgniteThread igniteThread = new IgniteThread(ignite.configuration().getIgniteInstanceName(), KMeansClusterizationExample.class.getSimpleName(), () -> { //ML specific st

Re: Apache Ignite project summary at people.apache.org

Ok, I will try ComDev list first and then incubator mailing lists. It seems ComDev list contains some mentioning of people.apache.org. ср, 26 сент. 2018 г. в 22:00, Denis Magda : > Hi Dmitriy and thanks for putting this out, > > Ignite definition needs to be changed to this one > > > > *Memory-cen

Re: Wrong off-heap size is reported for a node

Oops, my fault. It seems I forgot to cherry-pick to 2.7, but I resolved ticket with 2.7 assigned. I will fix it tomorrow. ср, 26 сент. 2018 г. в 21:52, Denis Magda : > Thanks, Pavel and the rest of the Igniters involved. > > That simple usability improvement is a big deal for those who use Ignit

Re: Critical worker threads liveness checking drawbacks

Andrey Gura, thank you for the answer! I agree that wrapping of 'init' method reduces the profit of watchdog service in case of PME worker, but in other cases, we should wrap all possible long sections on GridDhtPartitionExchangeFuture. For example 'onCacheChangeRequest' method or 'cctx.affinity()

Re: Critical worker threads liveness checking drawbacks

Vyacheslav, Exchange worker is strongly tied with GridDhtPartitionExchangeFuture#init and it is ok. Exchange worker also shouldn't be blocked for long time but in reality it happens.It also means that your change doesn't make sense. What actually make sense it is identification of places which in

Re: Apache Ignite project summary at people.apache.org

Hi Dmitriy and thanks for putting this out, Ignite definition needs to be changed to this one *Memory-centric distributed database, caching, and processing platform fortransactional, analytical, and streaming workloads delivering in-memoryspeeds at petabyte scale* Have no idea how to update it

Re: Wrong off-heap size is reported for a node

Thanks, Pavel and the rest of the Igniters involved. That simple usability improvement is a big deal for those who use Ignite in production. Are we getting it in 2.7? -- Denis On Wed, Sep 26, 2018 at 10:11 AM Dmitriy Pavlov wrote: > Hi Igniters, > > Thanks to everyone, who has participated in

Re: Critical worker threads liveness checking drawbacks

Hi Igniters! Thank you for this important improvement! I've looked through implementation and noticed that GridDhtPartitionsExchangeFuture#init has not been wrapped in blocked section. This means it easy to halt the node in case of longrunning actions during PME, for example when we create a cach

[GitHub] ignite pull request #4845: IGNITE-9710 Ignite watchdog service handles longr...

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/4845 IGNITE-9710 Ignite watchdog service handles longrunning cache creation You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite ignit

[jira] [Created] (IGNITE-9710) Ignite watchdog service handles cache creation

Vyacheslav Daradur created IGNITE-9710: -- Summary: Ignite watchdog service handles cache creation Key: IGNITE-9710 URL: https://issues.apache.org/jira/browse/IGNITE-9710 Project: Ignite I

Re: [ML] New features and improvement of ML module for 2.7 release

Great stuff! Would be nice to see a series of blogs outlining Ignite ML capabilities.This would give us a better momentum. D. On Wed, Sep 26, 2018 at 10:31 AM Юрий Бабак wrote: > Hello Igniters, > > I want to make up some overview of all features and major improvement of ML > module for this re

Re: [ML] New features and improvement of ML module for 2.7 release

Enormous and outstanding addition! Yuriy, I've talked to Akmal and he is happy to help with the documentation. Please start documenting everything and reach out Akmal directly. -- Denis On Wed, Sep 26, 2018 at 10:31 AM Юрий Бабак wrote: > Hello Igniters, > > I want to make up some overview of

[GitHub] asfgit closed pull request #21: IGNITE-9541 Fix bugs, refactor and add new info on html page

asfgit closed pull request #21: IGNITE-9541 Fix bugs, refactor and add new info on html page URL: https://github.com/apache/ignite-teamcity-bot/pull/21 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenanc

[ML] New features and improvement of ML module for 2.7 release

Hello Igniters, I want to make up some overview of all features and major improvement of ML module for this release. So let me start from the one of our main feature for this release: *TensorFlow integration* This integration allows us to use

[GitHub] ignite pull request #4844: IGNITE-9550 change affReady future listen

GitHub user dgovorukhin opened a pull request: https://github.com/apache/ignite/pull/4844 IGNITE-9550 change affReady future listen You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignit4e-9550-dg Alternati

Re: Wrong off-heap size is reported for a node

Hi Igniters, Thanks to everyone, who has participated in this discussion and shared their view and ideas. I've merged fix of changes related to logging only. Fixing of cluster metrics can be done in a separate ticket/discussion. Pavel, thank you for your contribution and for answering my questio

[GitHub] ignite pull request #4593: IGNITE-9305

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

[GitHub] zzzadruga opened a new pull request #21: IGNITE-9541 Fix bugs, refactor and add new info on html page

zzzadruga opened a new pull request #21: IGNITE-9541 Fix bugs, refactor and add new info on html page URL: https://github.com/apache/ignite-teamcity-bot/pull/21 This is an automated message from the Apache Git Service. To re

Apache Ignite project summary at people.apache.org

Hi Igniters, It seems to me, that the project description at http://people.apache.org/phonebook.html is a little bit outdated. It says High-performance, integrated and distributed in-memory platform for computing and transacting on large-scale data sets in real-time But our site says Memory-c

[GitHub] ignite pull request #4843: IGN-11747 [IGNITE-9298] control.sh does not suppo...

GitHub user a-polyakov opened a pull request: https://github.com/apache/ignite/pull/4843 IGN-11747 [IGNITE-9298] control.sh does not support SSL in 5.2.1-p14 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: Volunteer needed: AWS Elastic Load Balancer IP Finders implemented

Igniters, Don't we have experts in our networking component? I do believe that's a small improvement that can be verified and merged quickly. -- Denis On Wed, Sep 26, 2018 at 8:50 AM Dmitriy Pavlov wrote: > Igniters, Friendly reminder. > > Denis, could you advice how to proceed in this case? I

Re: Volunteer needed: AWS Elastic Load Balancer IP Finders implemented

Igniters, Friendly reminder. Denis, could you advice how to proceed in this case? It seems feature can be useful, but committers are not involved in a review. Should we send a proposal with lazy consensus and automatically merge? Any alternative ideas on how to proceed with issues stuck in the re

[GitHub] ignite pull request #4842: IGN-11747 [IGNITE-9298] control.sh does not suppo...

Github user a-polyakov closed the pull request at: https://github.com/apache/ignite/pull/4842 ---

[jira] [Created] (IGNITE-9709) IgniteCache : Put/Get operations hang on deactivated cluster

Vyacheslav Daradur created IGNITE-9709: -- Summary: IgniteCache : Put/Get operations hang on deactivated cluster Key: IGNITE-9709 URL: https://issues.apache.org/jira/browse/IGNITE-9709 Project: Ign

[jira] [Created] (IGNITE-9708) Node didn't detect corrup of file index.bin in FS

ARomantsov created IGNITE-9708: -- Summary: Node didn't detect corrup of file index.bin in FS Key: IGNITE-9708 URL: https://issues.apache.org/jira/browse/IGNITE-9708 Project: Ignite Issue Type: Bu

[GitHub] ignite pull request #4830: IGNITE-9649 Debug logs enhacement

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

[GitHub] ignite pull request #4840: IGNITE-9704

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

[jira] [Created] (IGNITE-9707) TouchedExpiryPolicy with persistent on atomic cache, update TTL without lock

Vladislav Pyatkov created IGNITE-9707: - Summary: TouchedExpiryPolicy with persistent on atomic cache, update TTL without lock Key: IGNITE-9707 URL: https://issues.apache.org/jira/browse/IGNITE-9707

[jira] [Created] (IGNITE-9706) ML: Update ignite-tensorflow to support TensorFlow standalone client mode

Anton Dmitriev created IGNITE-9706: -- Summary: ML: Update ignite-tensorflow to support TensorFlow standalone client mode Key: IGNITE-9706 URL: https://issues.apache.org/jira/browse/IGNITE-9706 Project

[GitHub] ignite pull request #4842: IGN-11747 [IGNITE-9298] control.sh does not suppo...

GitHub user a-polyakov opened a pull request: https://github.com/apache/ignite/pull/4842 IGN-11747 [IGNITE-9298] control.sh does not support SSL in 5.2.1-p14 (org.apache.ignite.internal.commandline.CommandHandler) You can merge this pull request into a Git repository by running:

[GitHub] dspavlov opened a new pull request #20: Ignite 9645

dspavlov opened a new pull request #20: Ignite 9645 URL: https://github.com/apache/ignite-teamcity-bot/pull/20 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use

[GitHub] ignite pull request #4841: IGNITE-9705 GridCacheDatabaseSharedManager#create...

GitHub user ibessonov opened a pull request: https://github.com/apache/ignite/pull/4841 IGNITE-9705 GridCacheDatabaseSharedManager#createPageMemory flushes invalid byte buffer into snapshot manager. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-9705) GridCacheDatabaseSharedManager#createPageMemory flushes invalid byte buffer into snapshot manager

Ivan Bessonov created IGNITE-9705: - Summary: GridCacheDatabaseSharedManager#createPageMemory flushes invalid byte buffer into snapshot manager Key: IGNITE-9705 URL: https://issues.apache.org/jira/browse/IGNITE-970

[GitHub] ignite pull request #4784: IGNITE-9381 On leaving node from cluster all clas...

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

[GitHub] ignite pull request #4840: IGNITE-9704

GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/4840 IGNITE-9704 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9704-1 Alternatively you can review and apply thes

[jira] [Created] (IGNITE-9704) JDBC thin: round-robin connection distribution

Vladimir Ozerov created IGNITE-9704: --- Summary: JDBC thin: round-robin connection distribution Key: IGNITE-9704 URL: https://issues.apache.org/jira/browse/IGNITE-9704 Project: Ignite Issue T

[jira] [Created] (IGNITE-9703) JDBC thick: do no throw exception from setReadOnly method

Vladimir Ozerov created IGNITE-9703: --- Summary: JDBC thick: do no throw exception from setReadOnly method Key: IGNITE-9703 URL: https://issues.apache.org/jira/browse/IGNITE-9703 Project: Ignite

[jira] [Created] (IGNITE-9702) Make IGNITE_BINARY_SORT_OBJECT_FIELDS enabled by default

Mikhail Cherkasov created IGNITE-9702: - Summary: Make IGNITE_BINARY_SORT_OBJECT_FIELDS enabled by default Key: IGNITE-9702 URL: https://issues.apache.org/jira/browse/IGNITE-9702 Project: Ignite

[GitHub] asfgit closed pull request #19: DI refactoring

asfgit closed pull request #19: DI refactoring URL: https://github.com/apache/ignite-teamcity-bot/pull/19 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the U

[GitHub] SomeFire commented on a change in pull request #19: DI refactoring

SomeFire commented on a change in pull request #19: DI refactoring URL: https://github.com/apache/ignite-teamcity-bot/pull/19#discussion_r220537287 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/ObserverTask.java ## @@ -17,43 +17,82 @@ pa

[jira] [Created] (IGNITE-9701) Create pass-through identifier for every single Parrtition Map Exchange

Andrey Kalinin created IGNITE-9701: -- Summary: Create pass-through identifier for every single Parrtition Map Exchange Key: IGNITE-9701 URL: https://issues.apache.org/jira/browse/IGNITE-9701 Project:

[GitHub] SomeFire commented on a change in pull request #19: DI refactoring

SomeFire commented on a change in pull request #19: DI refactoring URL: https://github.com/apache/ignite-teamcity-bot/pull/19#discussion_r220537287 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/ObserverTask.java ## @@ -17,43 +17,82 @@ pa

[GitHub] ignite pull request #4836: Ignite 9683

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

[GitHub] ignite pull request #4839: Ignite 9683 2

GitHub user andrewmed opened a pull request: https://github.com/apache/ignite/pull/4839 Ignite 9683 2 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite IGNITE-9683-2 Alternatively you can review and apply th

[GitHub] ignite pull request #4838: IGNITE-9700: Remove configurable values from meso...

GitHub user shroman opened a pull request: https://github.com/apache/ignite/pull/4838 IGNITE-9700: Remove configurable values from mesos pom.xml. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shroman/ignite IGNITE-9700 Alterna

[jira] [Created] (IGNITE-9700) Remove configurable values from mesos pom.xml

Roman Shtykh created IGNITE-9700: Summary: Remove configurable values from mesos pom.xml Key: IGNITE-9700 URL: https://issues.apache.org/jira/browse/IGNITE-9700 Project: Ignite Issue Type: Bu

[GitHub] ignite pull request #4837: Ignite 8717

GitHub user antonovsergey93 opened a pull request: https://github.com/apache/ignite/pull/4837 Ignite 8717 Cache configuration was moved to meta store. Verification of cache configuration on node joining was added. You can merge this pull request into a Git repository by running:

Re: mesos IgniteProvider improvement

Ilya, Sorry for getting back to you so late. No idea, why it was necessary to make them configurable during the build process.I would go with this solution, since the whole process depends on the the links and will not likely be changed in near future.- Update the links in the file once and remo

Re: Apache Ignite TeamCity Bot - wiki page available

Dmitriy, thank you for your efforts and for creating this page. A lot of Igniters were asking about it. ср, 26 сент. 2018 г. в 14:46, Dmitrii Ryabov : > Hello, Igniters! > > You've all seen the messages with new failures from MTCGA.Bot. > > But the bot can also be used to analyze TeamCity runs an

[GitHub] ignite pull request #4773: IGNITE-9492 Ignore SingleMessage updated where th...

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

Apache Ignite TeamCity Bot - wiki page available

Hello, Igniters! You've all seen the messages with new failures from MTCGA.Bot. But the bot can also be used to analyze TeamCity runs and to print tests analysis results in the JIRA ticket. Now you can learn how to work with the bot at the wiki page [1]. [1] https://cwiki.apache.org/confluence/

[jira] [Created] (IGNITE-9699) Web console: Mutual authentication on Web Console isn't supported

Andrey Aleksandrov created IGNITE-9699: -- Summary: Web console: Mutual authentication on Web Console isn't supported Key: IGNITE-9699 URL: https://issues.apache.org/jira/browse/IGNITE-9699 Project

[GitHub] ignite pull request #4836: Ignite 9683

GitHub user andrewmed opened a pull request: https://github.com/apache/ignite/pull/4836 Ignite 9683 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite IGNITE-9683 Alternatively you can review and apply these

[GitHub] dspavlov opened a new pull request #19: DI refactoring

dspavlov opened a new pull request #19: DI refactoring URL: https://github.com/apache/ignite-teamcity-bot/pull/19 Monitor observer tasks This is an automated message from the Apache Git Service. To respond to the message, plea

[jira] [Created] (IGNITE-9698) Add tests to control.sh with ssl authentication

Sergey Kosarev created IGNITE-9698: -- Summary: Add tests to control.sh with ssl authentication Key: IGNITE-9698 URL: https://issues.apache.org/jira/browse/IGNITE-9698 Project: Ignite Issue T

[jira] [Created] (IGNITE-9697) [TC Bot] Autocomplete branch for TC field

Ryabov Dmitrii created IGNITE-9697: -- Summary: [TC Bot] Autocomplete branch for TC field Key: IGNITE-9697 URL: https://issues.apache.org/jira/browse/IGNITE-9697 Project: Ignite Issue Type: Bu

[GitHub] ignite pull request #4835: IGNITE-9695 WAL disabling prohibition in WalState...

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/4835 IGNITE-9695 WAL disabling prohibition in WalStateManager. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite igni

[GitHub] ignite pull request #4674: IGNITE-9419 Async wait for caches registration an...

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

[GitHub] ignite pull request #4761: IGNITE-9558

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

[jira] [Created] (IGNITE-9696) SQL: Remove documentation about bad IN performance

Vladimir Ozerov created IGNITE-9696: --- Summary: SQL: Remove documentation about bad IN performance Key: IGNITE-9696 URL: https://issues.apache.org/jira/browse/IGNITE-9696 Project: Ignite Iss

[GitHub] ignite pull request #3956: IGNITE-4150

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

[GitHub] ignite pull request #4834: ignite-8507: Print a warning if SQL index inline ...

GitHub user ygerzhedovich opened a pull request: https://github.com/apache/ignite/pull/4834 ignite-8507: Print a warning if SQL index inline size is not sufficient. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-

[GitHub] ignite pull request #4833: Ig 7196 retest

GitHub user Mmuzaf opened a pull request: https://github.com/apache/ignite/pull/4833 Ig 7196 retest You can merge this pull request into a Git repository by running: $ git pull https://github.com/Mmuzaf/ignite ig-7196-retest Alternatively you can review and apply these change