[jira] [Created] (IGNITE-10489) Web console: validation messages are shown twice in configuration

Ilya Borisov created IGNITE-10489: - Summary: Web console: validation messages are shown twice in configuration Key: IGNITE-10489 URL: https://issues.apache.org/jira/browse/IGNITE-10489 Project: Ignite

[GitHub] ignite pull request #5535: Ignite 10242

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

Re: Apache Ignite 2.7. Last Mile

Null pointer there due to cache stop. Look at GridCacheContext#cleanup (GridCacheContext.java:2050) which is called by GridCacheProcessor#stopCache (GridCacheProcessor.java:1372) That's why at the time GridCacheMapEntry#touch (GridCacheMapEntry.java:5063) invoked there is no eviction manager. Th

[GitHub] ignite pull request #5536: IGNITE-10489 Do no trigger both types of validati...

GitHub user Klaster1 opened a pull request: https://github.com/apache/ignite/pull/5536 IGNITE-10489 Do no trigger both types of validation notifications at the same time @akuznetsov-gridgain please review. Besides the fix, I've also partially converted related files to TS and added

[jira] [Created] (IGNITE-10490) Web Console: ui-grid should refresh its content on parent element resize

Alexey Kuznetsov created IGNITE-10490: - Summary: Web Console: ui-grid should refresh its content on parent element resize Key: IGNITE-10490 URL: https://issues.apache.org/jira/browse/IGNITE-10490

[GitHub] ignite pull request #5382: IGNITE-10200 GridCacheSetAbstractSelfTest#testMul...

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

[jira] [Created] (IGNITE-10491) Out of memory: unable to create new native thread(test150Clients)

Anton Kalashnikov created IGNITE-10491: -- Summary: Out of memory: unable to create new native thread(test150Clients) Key: IGNITE-10491 URL: https://issues.apache.org/jira/browse/IGNITE-10491 Proj

Asynchronous index rebuild

Igniters, During work on index rebuild bug [1] I realized that our asynchronous nature of index rebuild logic may lead to long SQL queries in user applications, indistinguishable from hangs. Fundamental problem here is that we think that node is ready to become partition owner when partition data

[jira] [Created] (IGNITE-10492) No need to normalize QueryEntities if cache in restarting state.

Stanilovsky Evgeny created IGNITE-10492: --- Summary: No need to normalize QueryEntities if cache in restarting state. Key: IGNITE-10492 URL: https://issues.apache.org/jira/browse/IGNITE-10492 Proj

Re: Apache Ignite 2.7. Last Mile

Hi all! I've reproduced this problem locally and attached the log to the ticket in my comment [1]. As Igor noted, NPE there is caused by node stop in the end of the test. The real problem here seems to be in the binary metadata registration flow. [1] https://issues.apache.org/jira/browse/

[GitHub] ignite pull request #5537: IGNITE-10492 QueryEntities erroneous normalizatio...

GitHub user zstan opened a pull request: https://github.com/apache/ignite/pull/5537 IGNITE-10492 QueryEntities erroneous normalization. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10492 Alternat

Re: Apache Ignite 2.7. Last Mile

Hello, Roman. Is this issue blocks the 2.7 release? пт, 30 нояб. 2018 г., 13:19 Roman Kondakov kondako...@mail.ru.invalid: > Hi all! > > I've reproduced this problem locally and attached the log to the ticket > in my comment [1]. > > As Igor noted, NPE there is caused by node stop in the end of

Re: [VOTE] Apache Ignite 2.7.0 RC1

+1 пт, 30 нояб. 2018 г. в 10:05, Seliverstov Igor : > +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 > > >

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

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

[jira] [Created] (IGNITE-10493) Refactor exchange stages time measurements

Pavel Kovalenko created IGNITE-10493: Summary: Refactor exchange stages time measurements Key: IGNITE-10493 URL: https://issues.apache.org/jira/browse/IGNITE-10493 Project: Ignite Issue T

Re: Apache Ignite 2.7. Last Mile

Nikolay, I couldn't quickly find the root cause of this problem because I'm not an expert in the binary metadata flow. I think community should decide whether this is a release blocker or not. -- Kind Regards Roman Kondakov On 30.11.2018 13:23, Nikolay Izhikov wrote: Hello, Roman. Is this

Re: [VOTE] Apache Ignite 2.7.0 RC1

+1 пт, 30 нояб. 2018 г. в 13:25, Anton Vinogradov : > +1 > > пт, 30 нояб. 2018 г. в 10:05, Seliverstov Igor : > > > +1 > > > > пт, 30 нояб. 2018 г., 9:59 Nikolay Izhikov nizhi...@apache.org: > > > > > Igniters, > > > > > > We've uploaded a 2.7.0 release candidate to > > > > > > https://dist.apach

Re: Apache Ignite 2.7. Last Mile

Igor, thank you for explanation. Now it seems that when the one thread tries to invoke GridCacheMapEntry#touch, the another one makes GridCacheProcessor#stopCache. If I am wrong, please feel free to correct me. But it still does not clear for me why this fail appears after commit

Re: Partition Loss Policies issues

Hi Stan, Thank you for revealing (at least for me) one more dark corner in Ignite. As I see from your analysis it looks like a partition loss policy should be taken into account in many places (persistence, different query types, different cache modes). And it seems that with multiple options to c

[jira] [Created] (IGNITE-10494) fail with closed ticket IGNITE-1094 on tests.

Stanilovsky Evgeny created IGNITE-10494: --- Summary: fail with closed ticket IGNITE-1094 on tests. Key: IGNITE-10494 URL: https://issues.apache.org/jira/browse/IGNITE-10494 Project: Ignite

Re: [VOTE] Apache Ignite 2.7.0 RC1

+1 (accept Apache Ignite 2.7.0-RC1) пт, 30 нояб. 2018 г. в 13:43, Юрий : > > +1 > > пт, 30 нояб. 2018 г. в 13:25, Anton Vinogradov : > > > +1 > > > > пт, 30 нояб. 2018 г. в 10:05, Seliverstov Igor : > > > > > +1 > > > > > > пт, 30 нояб. 2018 г., 9:59 Nikolay Izhikov nizhi...@apache.org: > > > > > >

Re: [VOTE] Apache Ignite 2.7.0 RC1

+1 Best wishes, Amelchev Nikita пт, 30 нояб. 2018 г., 13:43 Юрий jury.gerzhedow...@gmail.com: > +1 > > пт, 30 нояб. 2018 г. в 13:25, Anton Vinogradov : > > > +1 > > > > пт, 30 нояб. 2018 г. в 10:05, Seliverstov Igor : > > > > > +1 > > > > > > пт, 30 нояб. 2018 г., 9:59 Nikolay Izhikov nizhi...@a

[GitHub] ignite pull request #5539: IGNITE-4841: Improve javadoc for Ignite Query cla...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/5539 IGNITE-4841: Improve javadoc for Ignite Query classes. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4841 A

[GitHub] ignite pull request #5540: IGNITE-10422: move default inspections config to ...

GitHub user Mmuzaf opened a pull request: https://github.com/apache/ignite/pull/5540 IGNITE-10422: move default inspections config to the project level You can merge this pull request into a Git repository by running: $ git pull https://github.com/Mmuzaf/ignite ignite-10422 A

[GitHub] ignite pull request #5541: IGNITE-10386 Add mode when WAL won't be disabled ...

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/5541 IGNITE-10386 Add mode when WAL won't be disabled during rebalancing caused by BLT change Just for tests now You can merge this pull request into a Git repository by running: $ git pu

[GitHub] ignite pull request #5524: fix index upper case

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

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

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

[GitHub] ignite pull request #2918: IGNITE-6692

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

[GitHub] ignite pull request #4680: IGNITE-9442

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

[GitHub] ignite pull request #5445: IGNITE-10236: MVCC: Create "Cache 3" test suite f...

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

[GitHub] ignite pull request #5474: IGNITE-10050: MVCC: Create "Cache 5" test suite f...

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

[jira] [Created] (IGNITE-10495) Get rid of local node ID in IgniteConfiguration

Alexey Goncharuk created IGNITE-10495: - Summary: Get rid of local node ID in IgniteConfiguration Key: IGNITE-10495 URL: https://issues.apache.org/jira/browse/IGNITE-10495 Project: Ignite

Re: Case sensitive indexes question.

Vladimir, thank you for clarification. i.e. you suggest creating two tickets: 1. for performance log message. 2. restrict such indexes creation. is it correct ? what about flag disabled by default, thus nothing would be broken? >Пятница, 30 ноября 2018, 15:15 +03:00 от Evgeniy Stanilovskiy >: > >

Re: MVCC test coverage.

Hi Roman, Agree with your suggestions. Regarding the problem 2 - note that we added cache mode valuation to MVCC suites. So yes, we may have some duplication, but it will be revealed on the next nightly test run. Not convenient, but at the very least we will know about it. Though, I am pretty sur

Re: [jira] [Created] (IGNITE-10441) Fluent API refactoring.

Hi, Artem! In the first, I don't remember many places (trainers/models) where the overriding is a big deal. Could you provide any examples, where it can be a problem? In the second, 'with' methods are unified way to inject hyperparameters via Reflection API for Pipeline API. But, in common, it's

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

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

Re: Case sensitive indexes question.

Zhenya, Vladimir suggested not to restrict anything. However, my opinion is to throw exception on duplicating indexes. We should better add ability to rename index if it can be useful for anyone. Having same field set indexed with same index type is pretty strange and adds a lot of risk for perfor

[GitHub] ignite pull request #5542: IGNITE-14091 added test to max threads

GitHub user akalash opened a pull request: https://github.com/apache/ignite/pull/5542 IGNITE-14091 added test to max threads You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10491 Alternatively you c

[GitHub] ignite pull request #5478: IGNITE-10365: MVCC: Create "Cache 6" test suite f...

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

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

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

JDBC thin driver: support connection timeout

Hi Igniters, Within context of connection timeout [ https://issues.apache.org/jira/browse/IGNITE-5234] it's not obvious whether it's required to use setNetworkTimeout's executor or not. According to the javadoc of java.sql.Connection#setNetworkTimeout(Executor executor, int milliseconds), executo

Re: [VOTE] Apache Ignite 2.7.0 RC1

-1 (binding) I can't launch TC Bot on RC, Seems it is related to https://issues.apache.org/jira/browse/IGNITE-9794 Steps to reproduce: org.apache.ignite.ci.teamcity.ignited.IgnitedTcInMemoryIntegrationTest in https://github.com/apache/ignite-teamcity-bot class org.apache.ignite.binary.BinaryObj

Re: [VOTE] Apache Ignite 2.7.0 RC1

Dmitry, Why do you think that product cannot be released with this exception? What is broken? пт, 30 нояб. 2018 г. в 16:36, Dmitriy Pavlov : > -1 (binding) > > I can't launch TC Bot on RC, Seems it is related to > https://issues.apache.org/jira/browse/IGNITE-9794 > > Steps to > reproduce: > org.

Re: [VOTE] Apache Ignite 2.7.0 RC1

Indeed, IGNITE-8926 was fixed in 2.7, but introduced a regression. The regression was fixed in IGNITE-9794, but for some reason the last ticket escaped the ignite-2.7 scope. Given that the regression prevents any new type registration inside an entry processor, I think we should cherry-pick the fix

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

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

Re: This morning I added ssl support to...

Hello! Proud to announce that we were able to merge this change finally. Unfortunately it is only getting into 2.8 now. Regards, -- Ilya Kasnacheev чт, 16 авг. 2018 г. в 17:05, Paul Anderson : > IGNITE-9298 > > On Thu, 16 Aug 2018, 15:35 Nikolay Izhikov, wrote: > > > Let's do it. > > > > Pl

[GitHub] ignite pull request #5543: Unmute EncryptedCacheCreateTest.testCreateEncrypt...

GitHub user dgarus opened a pull request: https://github.com/apache/ignite/pull/5543 Unmute EncryptedCacheCreateTest.testCreateEncryptedNotPersistedCacheFail You can merge this pull request into a Git repository by running: $ git pull https://github.com/dgarus/ignite unmute_en

Re: [VOTE] Apache Ignite 2.7.0 RC1

Vladimir, Apache Ignite TC bot, which writes comments into JIRA tickets about TC runs, uses internally Apache Ignite to store all build history and statistics. The bot uses only public API to store and load data, so it is emulating how end users will use the product. If it is not able to start an

Re: [VOTE] Apache Ignite 2.7.0 RC1

Got it, thank you. Definitely a blocker. пт, 30 нояб. 2018 г. в 16:56, Dmitriy Pavlov : > Vladimir, > > Apache Ignite TC bot, which writes comments into JIRA tickets about TC > runs, uses internally Apache Ignite to store all build history and > statistics. > > The bot uses only public API to sto

Re: [VOTE] Apache Ignite 2.7.0 RC1

Thanks, Alexey I will do it in a couple hours. пт, 30 нояб. 2018 г., 16:44 Alexey Goncharuk alexey.goncha...@gmail.com: > Indeed, IGNITE-8926 was fixed in 2.7, but introduced a regression. The > regression was fixed in IGNITE-9794, but for some reason the last ticket > escaped the ignite-2.7 sco

Fwd: [NOTICE] List created: notificati...@ignite.apache.org

The notifications list for GIT messages has been created. -- Forwarded message - From: ASF Self-Service Platform Date: Fri, Nov 30, 2018 at 4:30 AM Subject: [NOTICE] List created: notificati...@ignite.apache.org To: , , ASF Infrastructure < priv...@infra.apache.org> As requeste

[jira] [Created] (IGNITE-10496) Unfair queue polling for mostly empty queue

Peter Karich created IGNITE-10496: - Summary: Unfair queue polling for mostly empty queue Key: IGNITE-10496 URL: https://issues.apache.org/jira/browse/IGNITE-10496 Project: Ignite Issue Type:

[GitHub] ignite pull request #5544: IGNITE-10251

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

[GitHub] ignite pull request #5545: IGNITE-10483: Fix marshaller failures handling fo...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/5545 IGNITE-10483: Fix marshaller failures handling for mvcc Enlist requests. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ign

[GitHub] ignite pull request #5545: IGNITE-10483: Fix marshaller failures handling fo...

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

Re: [NOTICE] List created: notificati...@ignite.apache.org

Denis, thank you. Is it required to request INFRA to setup redirection of GitHub/GitBox? Or nothing is required now and we can subscribe to the new list? Sincerely, Dmitriy Pavlov пт, 30 нояб. 2018 г. в 17:16, Denis Magda : > The notifications list for GIT messages has been created. > > --

[GitHub] dspavlov opened a new pull request #86: IGNITE-10071 Queued and running builds hang in the TC bot

dspavlov opened a new pull request #86: IGNITE-10071 Queued and running builds hang in the TC bot URL: https://github.com/apache/ignite-teamcity-bot/pull/86 Fix for Platform .NET [ tests 1 ] 72 queued This is an automate

Re: [NOTICE] List created: notificati...@ignite.apache.org

Hi Eduard, could you please issue ticket similar to https://issues.apache.org/jira/browse/INFRA-17032 but referring to our new list? It seems notifications are still sent, at least from gitbox. Thank you in advance! Sincerely, Dmitriy Pavlov пт, 30 нояб. 2018 г. в 17:56, Dmitriy Pavlov : > D

[GitHub] ignite pull request #4697: IGNITE-9298 control.sh does not support SSL

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

[GitHub] ignite pull request #4684: IGNITE-9298

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

[GitHub] ignite pull request #5546: IGNITE-10475 @Async introduced in GridFutureAdapt...

GitHub user ibessonov opened a pull request: https://github.com/apache/ignite/pull/5546 IGNITE-10475 @Async introduced in GridFutureAdapter. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10475 Alt

Re: [NOTICE] List created: notificati...@ignite.apache.org

Yes, the messages have to be redirected. Talk to INFRA please. -- Denis On Fri, Nov 30, 2018 at 7:12 AM Dmitriy Pavlov wrote: > Hi Eduard, > > could you please issue ticket similar to > https://issues.apache.org/jira/browse/INFRA-17032 > but referring to our new list? > > It seems notification

Re: [NOTICE] List created: notificati...@ignite.apache.org

Meanwhile some of us can subscribe for this list. пт, 30 нояб. 2018 г. в 19:09, Denis Magda : > > Yes, the messages have to be redirected. Talk to INFRA please. > > -- > Denis > > On Fri, Nov 30, 2018 at 7:12 AM Dmitriy Pavlov wrote: > > > Hi Eduard, > > > > could you please issue ticket similar t

[GitHub] ignite pull request #5547: IGNITE-10442

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

[GitHub] ignite pull request #5548: Tests for IGNITE 10442

GitHub user 1vanan opened a pull request: https://github.com/apache/ignite/pull/5548 Tests for IGNITE 10442 You can merge this pull request into a Git repository by running: $ git pull https://github.com/1vanan/ignite tests-IGNITE-10442 Alternatively you can review and apply

[GitHub] ignite pull request #5416: IGNITE-10172 System flag introduced to disable di...

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

[GitHub] ignite pull request #5085: IGNITE-10017: Fix for infinite loop with 3rd part...

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

[GitHub] ignite pull request #5549: IGNITE-10410: Create "Cache 7" test suite for MVC...

GitHub user rkondakov opened a pull request: https://github.com/apache/ignite/pull/5549 IGNITE-10410: Create "Cache 7" test suite for MVCC mode. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10410

[GitHub] ignite pull request #5550: master before MVCC in ConQuery

GitHub user 1vanan opened a pull request: https://github.com/apache/ignite/pull/5550 master before MVCC in ConQuery You can merge this pull request into a Git repository by running: $ git pull https://github.com/1vanan/ignite before-MVCC Alternatively you can review and apply

[jira] [Created] (IGNITE-10497) jvm-pause-detector-worker should be JVM singleton

Anton Vinogradov created IGNITE-10497: - Summary: jvm-pause-detector-worker should be JVM singleton Key: IGNITE-10497 URL: https://issues.apache.org/jira/browse/IGNITE-10497 Project: Ignite

[jira] [Created] (IGNITE-10498) [TC Bot] Handle conflict error returned by TeamCity for some build problems

Dmitriy Pavlov created IGNITE-10498: --- Summary: [TC Bot] Handle conflict error returned by TeamCity for some build problems Key: IGNITE-10498 URL: https://issues.apache.org/jira/browse/IGNITE-10498 P

Re: [VOTE] Apache Ignite 2.7.0 RC1

Officially cancel the vote. Will prepare rc2 with IGNITE-9794 included. В Пт, 30/11/2018 в 17:05 +0300, Vladimir Ozerov пишет: > Got it, thank you. Definitely a blocker. > > пт, 30 нояб. 2018 г. в 16:56, Dmitriy Pavlov : > > > Vladimir, > > > > Apache Ignite TC bot, which writes comments into

[jira] [Created] (IGNITE-10499) Stopping ignite node when a transaction on this node in process of commit(rollback) may cause hang up

Sergey Kosarev created IGNITE-10499: --- Summary: Stopping ignite node when a transaction on this node in process of commit(rollback) may cause hang up Key: IGNITE-10499 URL: https://issues.apache.org/jira/browse/I

[VOTE] Apache Ignite 2.7.0 RC2

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

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

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

[jira] [Created] (IGNITE-10500) .NET: Compiler warning when building examples

Pavel Tupitsyn created IGNITE-10500: --- Summary: .NET: Compiler warning when building examples Key: IGNITE-10500 URL: https://issues.apache.org/jira/browse/IGNITE-10500 Project: Ignite Issue

Re: [VOTE] Apache Ignite 2.7.0 RC2

+1 Downloaded sources, build Java and .NET parts, ran examples. There is a minor issue with .NET Core examples, compiler warning is displayed (certainly not a blocker) [1] [1] https://issues.apache.org/jira/browse/IGNITE-10500 On Sat, Dec 1, 2018 at 12:47 AM Nikolay Izhikov wrote: > Igniters,