Re: proposed design for thin client SQL management and monitoring (view running queries and kill it)

Hey Igniters! I continue working on IEP-29 in part related to expose view with currently running queries. I checked how we track running queries right now and see that it's complicated and spread by few c

[jira] [Created] (IGNITE-10518) MVCC: Update operation may hangs on backup on unstable topology.

Andrew Mashenkov created IGNITE-10518: - Summary: MVCC: Update operation may hangs on backup on unstable topology. Key: IGNITE-10518 URL: https://issues.apache.org/jira/browse/IGNITE-10518 Project

[jira] [Created] (IGNITE-10517) [ML] Merge inference and learning architectures

Alexey Platonov created IGNITE-10517: Summary: [ML] Merge inference and learning architectures Key: IGNITE-10517 URL: https://issues.apache.org/jira/browse/IGNITE-10517 Project: Ignite Is

IEP-29 IGNITE-10165 Gather query stats and expose interfaces to access it

Hello, Igniters, I want to do IGNITE-10165 (Gather query stats and expose interfaces to access it) [1], if you don't mind. Yury, Vladimir, did you planned something about statistics implementation? Also, can you point out in which sessions should be available option to turn on/off stats gatherin

[jira] [Created] (IGNITE-10519) [TC Bot] Fill JavaDocs

PetrovMikhail created IGNITE-10519: -- Summary: [TC Bot] Fill JavaDocs Key: IGNITE-10519 URL: https://issues.apache.org/jira/browse/IGNITE-10519 Project: Ignite Issue Type: Task Re

[GitHub] ignite pull request #5565: IGNITE-9839 Web console: update to RxJS 6

GitHub user Klaster1 opened a pull request: https://github.com/apache/ignite/pull/5565 IGNITE-9839 Web console: update to RxJS 6 https://issues.apache.org/jira/browse/IGNITE-9839 @akuznetsov-gridgain please review. You can merge this pull request into a Git repository by runnin

[GitHub] ignite pull request #5566: IGNITE-10440: Analyse test suites for possible ac...

GitHub user avplatonov opened a pull request: https://github.com/apache/ignite/pull/5566 IGNITE-10440: Analyse test suites for possible acceleration You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10

Re: IEP-29 IGNITE-10165 Gather query stats and expose interfaces to access it

Hi Dmitry, AFAIK this is already work in progress by Yuriy. IEP-29 has a number of tickets, but they should be implemented one by one, not in parallel, because they heavily depend on each other. First we need to build infrastructure for running queries (see topic "proposed design for thin client S

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

Hi Igniters, In the current implementation, cache metrics are collected on each node and sent across the whole cluster with discovery message (TcpDiscoveryMetricsUpdateMessage) with configured frequency (MetricsUpdateFrequency, 2 seconds by default) even if no one requested them. If there are a lo

[GitHub] ignite pull request #5462: IGNITE-10369 PDS 4 hangs on TC

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

[jira] [Created] (IGNITE-10520) MVCC: Next to mvcc-tx non-mvcc-Tx failed with unexpected exception.

Andrew Mashenkov created IGNITE-10520: - Summary: MVCC: Next to mvcc-tx non-mvcc-Tx failed with unexpected exception. Key: IGNITE-10520 URL: https://issues.apache.org/jira/browse/IGNITE-10520 Proje

[GitHub] ignite pull request #5551: IGNITE-10405: Refactor GaussianNaiveBayesTrainerE...

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

[GitHub] ignite pull request #5484: IGNITE-10272: Inject learning environment into sc...

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

Re: proposed design for thin client SQL management and monitoring (view running queries and kill it)

Sounds good to me. On Tue, Dec 4, 2018 at 12:06 PM Юрий wrote: > Hey Igniters! > > I continue working on IEP-29 > < > https://cwiki.apache.org/confluence/display/IGNITE/IEP-29%3A+SQL+management+and+monitoring > > > in > part related to expose view with currently running queries. > > I checked ho

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

Alex, Did you measure the impact of metrics collection? What is the overhead you are trying to avoid? Just to make it clear, MetricUpdateMessage-s are used as heartbeats. So they are sent anyways, even if no metrics are distributed between nodes. Denis вт, 4 дек. 2018 г. в 12:46, Alex Plehanov

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

hi, Alex. imo: 1. metrics through discovery require refactoring. 2. local cache metrics should be available (if configured) on each node. 3. there must be an opportunity to configure metrics in runtime. thanks. > > >Hi Igniters, > >In the current implementation, cache metrics are collected on ea

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

Hi Alex, Agree with you. Most of the time these distribution of metrics is not needed. In future we will have more and more information which potentially needs to be shared between nodes. E.g. IO statistics, SQL statistics for query optimizer, SQL execution history, etc. We need common mechanics f

Re: Case sensitive indexes question.

I think that this is not an exceptional case, as nothing is broken. Throwing exception may make migration from other systems harder. Warning should be enough. Also remember that all SQL caches already have 1-2 automatic indexes out of the box, and we haven't seen much performance complaints about t

[jira] [Created] (IGNITE-10521) Creating table with datetime for PK leads to j.l.IndexOutOfBoundsException on server node

Sergey Kozlov created IGNITE-10521: -- Summary: Creating table with datetime for PK leads to j.l.IndexOutOfBoundsException on server node Key: IGNITE-10521 URL: https://issues.apache.org/jira/browse/IGNITE-10521

[GitHub] ignite pull request #5567: IGNITE-10462: Create Pds Mvcc test suite 2.

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/5567 IGNITE-10462: Create Pds Mvcc test suite 2. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10462 Alternative

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

Following up prior discussion in this thread, suggested changes were merged to master as a part of IGNITE-10422 and are now included in project default inspections profile. Thanks to Maxim and Dmitriy for making it happen. As for the ticket IGNITE-10450, I plan to keep it open for a little while

[GitHub] ignite pull request #5568: IGNITE-10446 control.sh --cache idle_verify fail ...

GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/5568 IGNITE-10446 control.sh --cache idle_verify fail with NPE when node l… …eft grid You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain

[GitHub] ignite pull request #5569: IGNITE-10434

GitHub user gvvinblade opened a pull request: https://github.com/apache/ignite/pull/5569 IGNITE-10434 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10434 Alternatively you can review and apply the

[jira] [Created] (IGNITE-10522) Remote node has not joined

Anton Kalashnikov created IGNITE-10522: -- Summary: Remote node has not joined Key: IGNITE-10522 URL: https://issues.apache.org/jira/browse/IGNITE-10522 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-10523) Ignite Compatibility: add check that started node is of expected version

Vyacheslav Daradur created IGNITE-10523: --- Summary: Ignite Compatibility: add check that started node is of expected version Key: IGNITE-10523 URL: https://issues.apache.org/jira/browse/IGNITE-10523

[GitHub] ignite pull request #5538: IGNITE-10457

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

[jira] [Created] (IGNITE-10524) IgniteCache.iterator() from a client node leads to OOM

Pavel Vinokurov created IGNITE-10524: Summary: IgniteCache.iterator() from a client node leads to OOM Key: IGNITE-10524 URL: https://issues.apache.org/jira/browse/IGNITE-10524 Project: Ignite

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

Hi, One of the problems with metrics is a huge size in case when a lot caches started on node (for example, I see 7000 caches). We have to think how to compact them. Not all metrics changed frequently, so, we may store locally and send over wire only a difference from previous collect. And think

[jira] [Created] (IGNITE-10525) Web Console: "Import models" dialog should be a singleton.

Alexey Kuznetsov created IGNITE-10525: - Summary: Web Console: "Import models" dialog should be a singleton. Key: IGNITE-10525 URL: https://issues.apache.org/jira/browse/IGNITE-10525 Project: Ignite

[GitHub] ignite pull request #5570: IGNITE-10523 Ignite Compatibility: add check that...

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/5570 IGNITE-10523 Ignite Compatibility: add check that started node is of expected version You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradu

[GitHub] ignite pull request #4974: IGNITE-8227 test failure handler

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

[GitHub] ignite pull request #5571: IGNITE-10522 added removing .tmp checkpoint files...

GitHub user akalash opened a pull request: https://github.com/apache/ignite/pull/5571 IGNITE-10522 added removing .tmp checkpoint files on start You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10522

Default failure handler was changed for tests

Hello, Igniters! Today the test framework's default no-op failure handler was changed to the handler, which stops the node and fails the test. Over 100 tests kept no-op failure handler by overrided `getFailureHandler()` method. If you'll found a problem or something unexpected - write here or in

[GitHub] ignite pull request #5572: IGNITE-9630

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

[jira] [Created] (IGNITE-10526) IgniteWalReaderTest logs too much garbage on node stop.

Andrew Mashenkov created IGNITE-10526: - Summary: IgniteWalReaderTest logs too much garbage on node stop. Key: IGNITE-10526 URL: https://issues.apache.org/jira/browse/IGNITE-10526 Project: Ignite

[jira] [Created] (IGNITE-10527) DenseMatrix(double[] mtx, int rows) mixes args

Artem Malykh created IGNITE-10527: - Summary: DenseMatrix(double[] mtx, int rows) mixes args Key: IGNITE-10527 URL: https://issues.apache.org/jira/browse/IGNITE-10527 Project: Ignite Issue Typ

Exceptions thrown in IndexingSpi and "fail fast" principle

Hello! Currently, Apache Ignite is mostly written in "fail fast" fashion. All of Apache Ignite codebase is assumed to have no bugs. When an unexpected exception happens, it will be printed to log and will usually *leave current operation hanging forever*. This is useful to developers since they c

Re: Default failure handler was changed for tests

Dmitrii, Could you please explain the reason of explicit set of 100+ NoOpFailureHandlers? вт, 4 дек. 2018 г. в 19:12, Dmitrii Ryabov : > Hello, Igniters! > > Today the test framework's default no-op failure handler was changed to the > handler, which stops the node and fails the test. > > Over

Re: Default failure handler was changed for tests

Hi Igniters, BTW, if you find in any of your tests it does't need an old value of handler (=NoOp), feel free to remove it. Sincerely, Dmitriy Pavlov вт, 4 дек. 2018 г. в 20:02, Anton Vinogradov : > Dmitrii, > > Could you please explain the reason of explicit set of 100+ > NoOpFailureHandlers? >

[GitHub] ignite pull request #5570: IGNITE-10523 Ignite Compatibility: add check that...

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

[jira] [Created] (IGNITE-10528) [ML] Fix incorrect comparing of double values in ML examples

Aleksey Zinoviev created IGNITE-10528: - Summary: [ML] Fix incorrect comparing of double values in ML examples Key: IGNITE-10528 URL: https://issues.apache.org/jira/browse/IGNITE-10528 Project: Ign

Re: Exceptions thrown in IndexingSpi and "fail fast" principle

Regarding PME: I think some kind of exceptions may be caught in 'GridDhtPartitionsExchangeFuture' to be able to notify the coordinator. For example, if an exception occurred during cache or index (or something else) creation on some node, the node can notify coordinator and coordinator should be a

[jira] [Created] (IGNITE-10529) [ML] Add Confusion Matrix support for classification algorithms

Aleksey Zinoviev created IGNITE-10529: - Summary: [ML] Add Confusion Matrix support for classification algorithms Key: IGNITE-10529 URL: https://issues.apache.org/jira/browse/IGNITE-10529 Project:

[jira] [Created] (IGNITE-10530) [ML] Add Confusion Matrix for Binary Classification

Aleksey Zinoviev created IGNITE-10530: - Summary: [ML] Add Confusion Matrix for Binary Classification Key: IGNITE-10530 URL: https://issues.apache.org/jira/browse/IGNITE-10530 Project: Ignite

[jira] [Created] (IGNITE-10531) [ML] Refactor all examples to use Binary Confusion Matrix instead of calculations by hand

Aleksey Zinoviev created IGNITE-10531: - Summary: [ML] Refactor all examples to use Binary Confusion Matrix instead of calculations by hand Key: IGNITE-10531 URL: https://issues.apache.org/jira/browse/IGNITE-10

[jira] [Created] (IGNITE-10532) [ML] Add Confusion Matrix for multi-class classification

Aleksey Zinoviev created IGNITE-10532: - Summary: [ML] Add Confusion Matrix for multi-class classification Key: IGNITE-10532 URL: https://issues.apache.org/jira/browse/IGNITE-10532 Project: Ignite

Re: Default failure handler was changed for tests

Anton, Tests in these classes check fail cases when we expect critical failure like node stop or exception thrown. Such tests trigger failure handler and it fails test when everything goes as it should go. That's why we need no-op handler here. вт, 4 дек. 2018 г. в 20:06, Dmitriy Pavlov : > > Hi I

Re: Default failure handler was changed for tests

Dmitrii, The solution is not clear to me. In case you expect the failure then a correct case is to wrap it with try-catch block instead of no-op failure handler usage. вт, 4 дек. 2018 г. в 21:41, Dmitrii Ryabov : > Anton, > > Tests in these classes check fail cases when we expect critical > fail

Re: Default failure handler was changed for tests

And you have to check the reason of failure inside the try-catch block, of course. In case found not equals to expected then test should rethrow the exception. вт, 4 дек. 2018 г. в 23:21, Anton Vinogradov : > Dmitrii, > > The solution is not clear to me. > In case you expect the failure then a c

Re: Default failure handler was changed for tests

Hi all, Really, why noop? If you expect failure handler should be triggered, you can override default one and rise some flag, which can be checked in test. This will make test clearer. With noop, you'll get previous unwanted behavior, that you are trying to improve, isnt'it? 4 дек. 2018 г. 23:

[jira] [Created] (IGNITE-10533) Web Console: Images outdated on web site.

Alexey Kuznetsov created IGNITE-10533: - Summary: Web Console: Images outdated on web site. Key: IGNITE-10533 URL: https://issues.apache.org/jira/browse/IGNITE-10533 Project: Ignite Issue

[GitHub] ignite pull request #5573: Ignite 2.4.8 p8

GitHub user gromtech opened a pull request: https://github.com/apache/ignite/pull/5573 Ignite 2.4.8 p8 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.4.8-p8 Alternatively you can review and apply

Re: welcome letter

Can you please add me to contributors group? Jira : mrsrinivas Thank you - Srinivas - Typed on tiny keys. pls ignore typos.{mobile app} On Tue, 4 Dec, 2018, 04:01 Dmitriy Pavlov Hi Vladimir, > > Welcome to the Apache Software Foundation and to the Apache Ignite > Community. > > I've added you

Re: Default failure handler was changed for tests

Folks let me remind you that Dmitry changed default of ALL tests from noop to a meaningful handler. So we should start every message here from saying thank you to Dmitry. Please review remaining tests and remove noop where possible. вт, 4 дек. 2018 г., 23:48 Andrey Mashenkov : > Hi all, > > Real

[jira] [Created] (IGNITE-10534) DDL operations don't work on not started caches

Yury Gerzhedovich created IGNITE-10534: -- Summary: DDL operations don't work on not started caches Key: IGNITE-10534 URL: https://issues.apache.org/jira/browse/IGNITE-10534 Project: Ignite

[GitHub] ignite pull request #5574: Ignite-10534

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