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

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

[jira] [Created] (IGNITE-10433) Web Console: "Import models" dialog doesn't unsubscribe from watching agent after closing

Alexey Kuznetsov created IGNITE-10433: - Summary: Web Console: "Import models" dialog doesn't unsubscribe from watching agent after closing Key: IGNITE-10433 URL:

Re: Apache Ignite 2.7. Last Mile

Hi, We found a regression https://issues.apache.org/jira/browse/IGNITE-10432 Please take a look. -- Alexey Kuznetsov

[jira] [Created] (IGNITE-10432) regression on sqlline

Pavel Konstantinov created IGNITE-10432: --- Summary: regression on sqlline Key: IGNITE-10432 URL: https://issues.apache.org/jira/browse/IGNITE-10432 Project: Ignite Issue Type: Bug

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

Vladimir, Please see inline On Mon, Nov 19, 2018 at 8:23 AM Vladimir Ozerov wrote: > Denis, > > I partially agree with you. But there are several problem with syntax > proposed by you: > 1) This is harder to implement technically - more parsing logic to > implement. Ok, this is our internal

[GitHub] ignite pull request #5512: IGNITE-8542: [ML] Add OneVsRest Trainer to handle...

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

[GitHub] ignite pull request #5519: IGNITE-10352 Final version

GitHub user dgovorukhin opened a pull request: https://github.com/apache/ignite/pull/5519 IGNITE-10352 Final version You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10352-final Alternatively you

[GitHub] ignite pull request #5518: Ignite 10413 2

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

[GitHub] ignite pull request #5514: IGNITE-10429: Wrap Scanner in DirectorySerializer...

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

[GitHub] ignite pull request #5517: IGNITE-10298 Cover possible deadlock in case of c...

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/5517 IGNITE-10298 Cover possible deadlock in case of caches start and frequent checkpoints You can merge this pull request into a Git repository by running: $ git pull

[GitHub] dspavlov commented on issue #78: IGNITE-10203 Support for alternative configurations for PR testing

dspavlov commented on issue #78: IGNITE-10203 Support for alternative configurations for PR testing URL: https://github.com/apache/ignite-teamcity-bot/pull/78#issuecomment-442177816 I suggest to - move logic from IgnitedTCImpl to standalone class e.g. BuildTypeSync in build type

[jira] [Created] (IGNITE-10431) Make tests independent of memory size

Sergi Vladykin created IGNITE-10431: --- Summary: Make tests independent of memory size Key: IGNITE-10431 URL: https://issues.apache.org/jira/browse/IGNITE-10431 Project: Ignite Issue Type:

[GitHub] ignite pull request #5516: IGNITE-9298 SSL support in control.sh

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/5516 IGNITE-9298 SSL support in control.sh I have merged two commits to get best of two worlds. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #5446: IGNITE-10193: IgniteBaselineAffinityTopologyActiv...

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

Re: [DISCUSSION] Design document. Rebalance caches by transferring partition files

Sergey, >If I understand correctly when there is a continuous flow of updates to the page already transferred to receiver checkpointer will write this page to the log file over and over again. Do you see here any risks of exhausting disk space on sender's side? We could track the set of page

[GitHub] ignite pull request #5344: IGNITE-10158 Some tests in IgniteCacheAbstractQue...

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

[GitHub] ignite pull request #2882: ignite-1793

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

[jira] [Created] (IGNITE-10430) Ignite.NET Data Region Metrics: PagesRead, PagesWritten, PagesReplaced, OffHeapSize, OffheapUsedSize

Alexey Kukushkin created IGNITE-10430: - Summary: Ignite.NET Data Region Metrics: PagesRead, PagesWritten, PagesReplaced, OffHeapSize, OffheapUsedSize Key: IGNITE-10430 URL:

[GitHub] ignite pull request #5252: IGNITE-10106: Cache 5 test suite optimization

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

Re: [VOTE] Creation dedicated list for github notifiacations

+1 I'm for making the dev list readable without filters of any kind. On Tue, Nov 27, 2018, 15:14 Maxim Muzafarov +1 > > Let's have a look at how it will be. > > On Tue, 27 Nov 2018 at 14:48 Seliverstov Igor > wrote: > > > +1 > > > > вт, 27 нояб. 2018 г. в 14:45, Юрий : > > > > > +1 > > > > > >

[GitHub] ignite pull request #5515: IGNITE-10348 Safely recreate metastore to mitigat...

GitHub user SpiderRus opened a pull request: https://github.com/apache/ignite/pull/5515 IGNITE-10348 Safely recreate metastore to mitigate IGNITE-8735 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #5486: IGNITE-10390 Fixed BPlusTree#isEmpty

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

[GitHub] ignite pull request #5064: IGNITE-7072: IgniteCache.replace(k, v, nv) fix fo...

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

[GitHub] ignite pull request #5490: IGNITE-8718: Updated C++ doxygen comments about B...

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

[GitHub] ignite pull request #5038: IGNITE-9948

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

[GitHub] ignite pull request #5482: IGNITE-7441 Drop IGNITE_SERVICES_COMPATIBILITY_MO...

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

Re: [DISCUSSION] Design document. Rebalance caches by transferring partition files

Eduard, This algorithm looks much easier but could you clarify some edge cased please? If I understand correctly when there is a continuous flow of updates to the page already transferred to receiver checkpointer will write this page to the log file over and over again. Do you see here any risks

[GitHub] ignite pull request #5514: IGNITE-10429: Wrap Scanner in DirectorySerializer...

GitHub user dmitrievanthony opened a pull request: https://github.com/apache/ignite/pull/5514 IGNITE-10429: Wrap Scanner in DirectorySerializerTest into try-with-resources. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-10429) ML: TensorFlowLocalInferenceExample fails on Windows

Anton Dmitriev created IGNITE-10429: --- Summary: ML: TensorFlowLocalInferenceExample fails on Windows Key: IGNITE-10429 URL: https://issues.apache.org/jira/browse/IGNITE-10429 Project: Ignite

[jira] [Created] (IGNITE-10428) [ML] Add example for OneVsRest trainer/model usage

Aleksey Zinoviev created IGNITE-10428: - Summary: [ML] Add example for OneVsRest trainer/model usage Key: IGNITE-10428 URL: https://issues.apache.org/jira/browse/IGNITE-10428 Project: Ignite

Re: [DISCUSSION] Design document. Rebalance caches by transferring partition files

So, after some discussion, I could describe another approach on how to build consistent partition on the fly. 1. We make a checkpoint, fix the size of the partition in OffheapManager. 2. After checkpoint finish, we start sending partition file (without any lock) to the receiver from 0 to fixed

[GitHub] ignite pull request #5513: IGNITE-10427 Wrap state change future before send...

GitHub user antonovsergey93 opened a pull request: https://github.com/apache/ignite/pull/5513 IGNITE-10427 Wrap state change future before sending activation request. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #5512: IGNITE-8542: [ML] Add OneVsRest Trainer to handle...

GitHub user zaleslaw opened a pull request: https://github.com/apache/ignite/pull/5512 IGNITE-8542: [ML] Add OneVsRest Trainer to handle cases with multiple class labels in dataset You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-10427) GridClusterStateProcessor#changeGlobalState0() should wrap future before sending ChangeGlobalStateMessage

Sergey Antonov created IGNITE-10427: --- Summary: GridClusterStateProcessor#changeGlobalState0() should wrap future before sending ChangeGlobalStateMessage Key: IGNITE-10427 URL:

Re: [ANNOUNCE] Welcome Ilya Kasnacheev as a new committer

Ilya, my congratulations! вт, 27 нояб. 2018 г. в 13:56, Dmitriy Pavlov : > > Dear Igniters, > > > > It is last but not least announce. The Apache Ignite Project Management > Committee (PMC) has invited Ilya Kasnacheev to become a new committer and > are happy to announce that he has accepted. > >

Re: Lightweight profiling of messages processing

Alexey, I would say that to implement this feature successfully, we first need to clearly understand specific scenarios we want to target, and only then plan implementation in small iterations. Please take in count the following points: 1) Splitting by message type might be too fine-grained thing

Re: Lightweight profiling of messages processing

Clarification: p.5 is about buffer pool and disk access statistics, not network. On Tue, Nov 27, 2018 at 6:02 PM Vladimir Ozerov wrote: > Alexey, > > I would say that to implement this feature successfully, we first need to > clearly understand specific scenarios we want to target, and only

Re: Code inspection

I'm totally with you in this decision, let's move the file. вт, 27 нояб. 2018 г. в 16:24, Maxim Muzafarov : > Igniters, > > I propose to make inspection configuration default on the project > level. I've created a new issue [1] for it. It can be easily done and > recommend by IntelliJ

[jira] [Created] (IGNITE-10426) [ML] Spread parameter isKeepRawLabels across all models

Aleksey Zinoviev created IGNITE-10426: - Summary: [ML] Spread parameter isKeepRawLabels across all models Key: IGNITE-10426 URL: https://issues.apache.org/jira/browse/IGNITE-10426 Project: Ignite

[jira] [Created] (IGNITE-10425) Node failed to add to topology due to problem with detecting local Address

Max Shonichev created IGNITE-10425: -- Summary: Node failed to add to topology due to problem with detecting local Address Key: IGNITE-10425 URL: https://issues.apache.org/jira/browse/IGNITE-10425

Re: Service grid redesign

We had the private talk with Nikolay Izhikov, Vladimir Ozerov, Alexey Goncharuk, Yakov Zhdanov, Denis Mekhanikov, Dmitriy Pavlov and I would like to share the summary with the community: The architecture of the implemented deployment process looks good in general, but the following points should

Re: Lightweight profiling of messages processing

Hi Alexei, Did you consider general-purpose APM tools like free InspectIT or commercial DynaTrace or AppDynamics ? Java APM tools

[GitHub] ignite pull request #5511: Ignite 10417

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

Lightweight profiling of messages processing

Igniters, At work I often have to solve performance issues with Ignite cluster without having access to source code of running user application. Looks like Ignite have limited capabilities to identify bottlenecks without extensive profiling on server and client side (JFR recording , sampling

[GitHub] ignite pull request #5510: IGNITE-10423 print dump thread on workersRegistry

GitHub user akalash opened a pull request: https://github.com/apache/ignite/pull/5510 IGNITE-10423 print dump thread on workersRegistry You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10423

[jira] [Created] (IGNITE-10424) expected SqlException not thrown

Max Shonichev created IGNITE-10424: -- Summary: expected SqlException not thrown Key: IGNITE-10424 URL: https://issues.apache.org/jira/browse/IGNITE-10424 Project: Ignite Issue Type: Bug

Re: Code inspection

Igniters, I propose to make inspection configuration default on the project level. I've created a new issue [1] for it. It can be easily done and recommend by IntelliJ documentation [2]. Thoughts? Vyacheslav, Can you share an example of your warnings? Currently, we have different inspection

[jira] [Created] (IGNITE-10423) Hangs grid-nio-worker-tcp-comm

Anton Kalashnikov created IGNITE-10423: -- Summary: Hangs grid-nio-worker-tcp-comm Key: IGNITE-10423 URL: https://issues.apache.org/jira/browse/IGNITE-10423 Project: Ignite Issue Type:

Re: Brainstorm: Make TC Run All faster

Roman, Do you have some expectations how faster "correlated" tests elimination will make Run All? Also do you have a vision how can we determine such "correlated" tests, can we do it relatively fast? But all in all, I am not sure that reducing a group of correlated tests to only one test can

[jira] [Created] (IGNITE-10422) Make {{ignite_inspection.xml}} configuration default on the project level

Maxim Muzafarov created IGNITE-10422: Summary: Make {{ignite_inspection.xml}} configuration default on the project level Key: IGNITE-10422 URL: https://issues.apache.org/jira/browse/IGNITE-10422

[jira] [Created] (IGNITE-10421) MVCC: Assertion in checkpointing tread after disabling WAL.

Roman Kondakov created IGNITE-10421: --- Summary: MVCC: Assertion in checkpointing tread after disabling WAL. Key: IGNITE-10421 URL: https://issues.apache.org/jira/browse/IGNITE-10421 Project: Ignite

Re: [VOTE] Creation dedicated list for github notifiacations

+1 Let's have a look at how it will be. On Tue, 27 Nov 2018 at 14:48 Seliverstov Igor wrote: > +1 > > вт, 27 нояб. 2018 г. в 14:45, Юрий : > > > +1 > > > > вт, 27 нояб. 2018 г. в 11:22, Andrey Mashenkov < > andrey.mashen...@gmail.com > > >: > > > > > +1 > > > > > > On Tue, Nov 27, 2018 at

Re: [MTCGA] Disabled tests.

Thanks Ilya. I've create a sub-ticket for IGNITE-9210: https://issues.apache.org/jira/browse/IGNITE-10420 On Mon, Nov 26, 2018 at 2:22 PM Ilya Kasnacheev wrote: > Hello! > > I think we should un-ignore these tests. You can even create a sub-task > under

[jira] [Created] (IGNITE-10420) Enable ignored test in "Cache 1" test suite.

Andrew Mashenkov created IGNITE-10420: - Summary: Enable ignored test in "Cache 1" test suite. Key: IGNITE-10420 URL: https://issues.apache.org/jira/browse/IGNITE-10420 Project: Ignite

Re: [VOTE] Creation dedicated list for github notifiacations

+1 вт, 27 нояб. 2018 г. в 14:45, Юрий : > +1 > > вт, 27 нояб. 2018 г. в 11:22, Andrey Mashenkov >: > > > +1 > > > > On Tue, Nov 27, 2018 at 10:12 AM Sergey Chugunov < > > sergey.chugu...@gmail.com> > > wrote: > > > > > +1 > > > > > > Plus this dedicated list should be properly documented in

Re: [VOTE] Creation dedicated list for github notifiacations

+1 вт, 27 нояб. 2018 г. в 11:22, Andrey Mashenkov : > +1 > > On Tue, Nov 27, 2018 at 10:12 AM Sergey Chugunov < > sergey.chugu...@gmail.com> > wrote: > > > +1 > > > > Plus this dedicated list should be properly documented in wiki, > mentioning > > it in How to Contribute [1] or in Make Teamcity

Re: Historical rebalance

Vladimir, I think I got your point, It should work if we do the next: introduce two structures: active list (txs) and candidate list (updCntr -> txn pairs) Track active txs, mapping them to actual update counter at update time. On each next update put update counter, associated with previous

[GitHub] ignite pull request #5508: 10183

GitHub user SomeFire opened a pull request: https://github.com/apache/ignite/pull/5508 10183 You can merge this pull request into a Git repository by running: $ git pull https://github.com/SomeFire/ignite IGNITE-10183 Alternatively you can review and apply these changes as

[GitHub] ignite pull request #4964: IGNITE-9284 Add standard scaler

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

Re: MVCC test coverage.

Vladimir, Andrey, as you mentioned this approach has several disadvantages. I can name a few of them: 1. This new MVCC suites will be triggered in "long" runs at night - this means developers will not receive feedback about MVCC problems immediately - they will have to wait until their

[ANNOUNCE] Welcome Ilya Kasnacheev as a new committer

Dear Igniters, It is last but not least announce. The Apache Ignite Project Management Committee (PMC) has invited Ilya Kasnacheev to become a new committer and are happy to announce that he has accepted. Being a committer enables you to more easily make changes without needing to go through

[GitHub] ignite pull request #5507: IGNITE-10287: Add ML inference model storage.

GitHub user dmitrievanthony opened a pull request: https://github.com/apache/ignite/pull/5507 IGNITE-10287: Add ML inference model storage. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10287

[jira] [Created] (IGNITE-10419) [ML] Move person dataset to SandboxMLCache class

Yury Babak created IGNITE-10419: --- Summary: [ML] Move person dataset to SandboxMLCache class Key: IGNITE-10419 URL: https://issues.apache.org/jira/browse/IGNITE-10419 Project: Ignite Issue

Re: Historical rebalance

Ivan, 1) The list is saved on each checkpoint, wholly (all transactions in active state at checkpoint begin). We need whole the list to get oldest transaction because after the previous oldest tx finishes, we need to get the following one. 2) I guess there is a description of how persistent

[jira] [Created] (IGNITE-10418) Implement lightweight profiling for message processing

Alexei Scherbakov created IGNITE-10418: -- Summary: Implement lightweight profiling for message processing Key: IGNITE-10418 URL: https://issues.apache.org/jira/browse/IGNITE-10418 Project: Ignite

Re: Historical rebalance

Just thought of this a bit more. I we will look for start of long-running transaction in WAL we may go back too far to the past only to get few entries. What if we consider slightly different approach? We assume that transaction can be represented as a set of independent operations, which are

[jira] [Created] (IGNITE-10417) notifyDiscoveryListener can be lost

Pavel Voronkin created IGNITE-10417: --- Summary: notifyDiscoveryListener can be lost Key: IGNITE-10417 URL: https://issues.apache.org/jira/browse/IGNITE-10417 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-10416) Revisit GridCacheAbstractTest childs.

Andrew Mashenkov created IGNITE-10416: - Summary: Revisit GridCacheAbstractTest childs. Key: IGNITE-10416 URL: https://issues.apache.org/jira/browse/IGNITE-10416 Project: Ignite Issue

[GitHub] ignite pull request #5198: IGNITE-10002: MVCC: Create "Cache 2" test suite f...

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

Re: New API for changing configuration of persistent caches

Ed, I think most questions around API will go away once we understand how users are going to use it. Can you provide several examples of properties which we think are going to be changed often, along with concrete example of API usage (native API, control.sh, whatever we think important)?

[jira] [Created] (IGNITE-10415) MVCC: TxRollbackOnIncorrectParamsTest fails if Mvcc enabled.

Andrew Mashenkov created IGNITE-10415: - Summary: MVCC: TxRollbackOnIncorrectParamsTest fails if Mvcc enabled. Key: IGNITE-10415 URL: https://issues.apache.org/jira/browse/IGNITE-10415 Project:

[GitHub] ignite pull request #5506: Ignite 10223

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

[GitHub] ignite pull request #5380: ignite-10223

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

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

[GitHub] ignite pull request #5505: IGNITE-10352

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

[GitHub] ignite pull request #5504: Ignite gc 371 2

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

Re: [VOTE] Creation dedicated list for github notifiacations

+1 On Tue, Nov 27, 2018 at 10:12 AM Sergey Chugunov wrote: > +1 > > Plus this dedicated list should be properly documented in wiki, mentioning > it in How to Contribute [1] or in Make Teamcity Green Again [2] would be a > good idea. > > [1]

Re: Historical rebalance

Igor, Could you please elaborate - what is the whole set of information we are going to save at checkpoint time? From what I understand this should be: 1) List of active transactions with WAL pointers of their first writes 2) List of prepared transactions with their update counters 3) Partition

[GitHub] ignite pull request #5503: IGNITE-10352

GitHub user dgovorukhin opened a pull request: https://github.com/apache/ignite/pull/5503 IGNITE-10352 You can merge this pull request into a Git repository by running: $ git pull https://github.com/dgovorukhin/ignite ignite-10352-2 Alternatively you can review and apply

Re: proposed realization KILL QUERY command

Yes ("нуы") On Tue, Nov 27, 2018 at 10:56 AM Павлухин Иван wrote: > I believe that the meaning was: > > > I propose to start with running queries VIEW first. > вт, 27 нояб. 2018 г. в 10:47, Vladimir Ozerov : > > > > I propose to start with running queries мшуц first. Once we have it, it > >