[jira] [Created] (IGNITE-9680) Web console: add component for status output

Ilya Borisov created IGNITE-9680: Summary: Web console: add component for status output Key: IGNITE-9680 URL: https://issues.apache.org/jira/browse/IGNITE-9680 Project: Ignite Issue Type: Imp

Re: Spring Session Ignite plugin

Hi Denis, I've created pull request: https://github.com/apache/ignite/pull/4820 and filed an JIRA issue: https://issues.apache.org/jira/browse/IGNITE-9676 . An initial review would be highly app

Re: Spring Session Ignite plugin

Hello Anton, I would merge the contribution to "ignite-spring-session" module. Create it. We already have "ignite-spring", "ignite-spring-date" modules and the addition of one more looks natural. -- Denis On Mon, Sep 24, 2018 at 3:31 AM Dmitriy Pavlov wrote: > Hi Anton, > > There is GitHub mir

Re: [TC Bot] Proposal of improvement

Hi Nikolay, What about the case when committer creates ignite-9679 branch and tests it without PR? We have 1100+ open PRs and less than 100 open tickets. So scanning seems to be possible only in JIRA. Mention probably will work for GitHub, but it needs to be researched. Two open PRs is not a val

Re: [TC Bot] Proposal of improvement

Hello, Dmitriy. > But it could be a lot of work to handle mentions (probably from the email> > account and inbox). Actually, it can be done via GitHub REST API [1]. It has 'since' param, so getting new GitHub comments is a very basic task. > Patch available ticket I think we shouldn't take a t

Re: [TC Bot] Proposal of improvement

Hi Nikolay, The idea makes perfect sense for me, and we should definitely take the best practices from other big Apache projects. But it could be a lot of work to handle mentions (probably from the email account and inbox). I would like to suggest the following algorithm: Patch available ticket

[GitHub] ignite pull request #4821: IGNITE-9655 DML benchmark suite (except selects)

GitHub user pavel-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/4821 IGNITE-9655 DML benchmark suite (except selects) Created benchmark suite for updates and insert+deletes. Removed outdated benchmarks. You can merge this pull request into a Git reposito

Re: Critical worker threads liveness checking drawbacks

Denis, I've created the ticket [1] with short description of the functionality. [1] https://issues.apache.org/jira/browse/IGNITE-9679 пн, 24 сент. 2018 г. в 17:46, Denis Magda : > Andrey K. and G., > > Thanks, do we have a documentation ticket created? Prachi (copied) can help > with the docum

[jira] [Created] (IGNITE-9679) Document critical workers liveness checking implementation

Andrey Kuznetsov created IGNITE-9679: Summary: Document critical workers liveness checking implementation Key: IGNITE-9679 URL: https://issues.apache.org/jira/browse/IGNITE-9679 Project: Ignite

[TC Bot] Proposal of improvement

Hello, Igniters. I propose to implement following behaviour: 1. Execute "Run all" suite for specific PR when the author of PR makes a comment "@mtcga.bot Run Tests!" in GitHub comments. 2. Send a comment with "Run All" results both: to a Jira ticket and GitHub comment. 3. Label PR based on "Ru

[jira] [Created] (IGNITE-9678) [TC Bot] Trigger Run All for github comment

Nikolay Izhikov created IGNITE-9678: --- Summary: [TC Bot] Trigger Run All for github comment Key: IGNITE-9678 URL: https://issues.apache.org/jira/browse/IGNITE-9678 Project: Ignite Issue Type

[GitHub] ignite pull request #4820: IGNITE-9676 Spring Session integration implemente...

GitHub user antkr opened a pull request: https://github.com/apache/ignite/pull/4820 IGNITE-9676 Spring Session integration implemented. You can merge this pull request into a Git repository by running: $ git pull https://github.com/antkr/ignite IGNITE-9676 Alternatively you c

[jira] [Created] (IGNITE-9677) [TC Bot] Automatic build trigger should track all branches defined in configuration.

Pavel Pereslegin created IGNITE-9677: Summary: [TC Bot] Automatic build trigger should track all branches defined in configuration. Key: IGNITE-9677 URL: https://issues.apache.org/jira/browse/IGNITE-9677

[GitHub] ignite pull request #4819: IGNITE-9674 Optimize network usage on P2P class l...

GitHub user antonovsergey93 opened a pull request: https://github.com/apache/ignite/pull/4819 IGNITE-9674 Optimize network usage on P2P class loading. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-

Re: affinityBackupFilter for AWS Availability Zones

Yes, thanks Val! On Mon, Sep 24, 2018 at 11:35 AM Dmitriy Pavlov wrote: > Hi Val, many thanks for the review. > > ср, 12 сент. 2018 г. в 20:35, Valentin Kulichenko < > valentin.kuliche...@gmail.com>: > > > Yes, will try to review this week. > > > > -Val > > > > On Wed, Sep 12, 2018 at 10:24 AM D

Re: Sign Keys for release artifacts

Nikolay, Please check all vote_* steps to make sure that's the only problem пн, 24 сент. 2018 г. в 18:53, Petr Ivanov : > How then you’ll be able to push artifacts to SVN repository for vote? > > > > > On 24 Sep 2018, at 18:28, Nikolay Izhikov wrote: > > > > Hello, Igniters. > > > > Cos, I have

Re: Ignite-2.7 branch created

Thank you, Petr! Done with the Bot. I will not enable notifications to dev. list. A user can come to its own preferences page and enable "Notify on all failures in ignite-2.7" пн, 24 сент. 2018 г. в 19:18, Petr Ivanov : > Done with trigger. > > > > > On 24 Sep 2018, at 19:15, Dmitriy Pavlov wr

Re: Ignite-2.7 branch created

Done with trigger. > On 24 Sep 2018, at 19:15, Dmitriy Pavlov wrote: > > Hi Nikolay, Petr > > could you please create triggers for nightly builds? > > I will also add the branch to be tracked to TC Bot. > > Sincerely, > Dmitriy Pavlov > > пн, 24 сент. 2018 г. в 18:24, Nikolay Izhikov : >

Re: Ignite-2.7 branch created

Hi Nikolay, Petr could you please create triggers for nightly builds? I will also add the branch to be tracked to TC Bot. Sincerely, Dmitriy Pavlov пн, 24 сент. 2018 г. в 18:24, Nikolay Izhikov : > Hello, Igniters. > > I've created branch for an Apache Ignite 2.7 release [1] > Please, cherry-p

[GitHub] ignite pull request #4818: IGNITE-9451: Cache.size for key-value API

GitHub user pavlukhin opened a pull request: https://github.com/apache/ignite/pull/4818 IGNITE-9451: Cache.size for key-value API You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9451 Alternatively y

Re: Sign Keys for release artifacts

How then you’ll be able to push artifacts to SVN repository for vote? > On 24 Sep 2018, at 18:28, Nikolay Izhikov wrote: > > Hello, Igniters. > > Cos, I have a question regarding Apache Ignite release. > > I have committer priveledges in Apache Ignite. > I don't have PMC role. > > Since I

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

Andrei, I totally agree with you and I think that "ClusterMetrics" should also be fixed, I'm just not sure that we should include this change in the same ticket. пн, 24 сент. 2018 г. в 18:43, aealexsandrov : > > Hi, > > OK, the user can use it to calculate the off-heap. But I think that the > reaso

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

Hi, OK, the user can use it to calculate the off-heap. But I think that the reason for your changes to fix the calculation of the nonHeap used in Ignite now. For example now REST return "-1" for nonHeapMemoryMaximum. I think that it can't be used somehow. So REST possible should be updated as you

Re: [MTCGA]: new failures in builds [1888723] needs to be handled

Hi Igniters, I've found Parity check test was muted. The test itself contains the possibility to exclude property. No reason to mute this test. Could you please ignore property in code? Sincerely, Dmitriy Pavlov пн, 17 сент. 2018 г. в 17:25, : > Hi Ignite Developer, > > I am MTCGA.Bot, and I'v

Re: affinityBackupFilter for AWS Availability Zones

Hi Val, many thanks for the review. ср, 12 сент. 2018 г. в 20:35, Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Yes, will try to review this week. > > -Val > > On Wed, Sep 12, 2018 at 10:24 AM Dmitriy Pavlov > wrote: > > > Hi Val, > > > > I'm not an expert in AWS, so could you please p

[GitHub] ignite pull request #4014: IGNITE-6500

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

Sign Keys for release artifacts

Hello, Igniters. Cos, I have a question regarding Apache Ignite release. I have committer priveledges in Apache Ignite. I don't have PMC role. Since I don't have PMC role, I can't add my GPG key to KEYS [1] file. Is it OK if someone with PMC role adds my GPG key to KEYS file? [1] https://dist

Ignite-2.7 branch created

Hello, Igniters. I've created branch for an Apache Ignite 2.7 release [1] Please, cherry-pick tickets that should be in 2.7 to that branch. [1] https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=shortlog;h=refs/heads/ignite-2.7 signature.asc Description: This is a digitally signed message p

Apache Ignite community update

Hello, Igniters! It’s been a busy September for us here in the Apache Ignite community. We’ve been preparing for the In-Memory Computing Summit North America 2018 happening Oct. 2-3 in San Francisco. I’ll have details on some Ignite sessions below. Meantime, our conference preparations haven’t

[jira] [Created] (IGNITE-9676) Ignite as storage in Spring Session

Anton Kurbanov created IGNITE-9676: -- Summary: Ignite as storage in Spring Session Key: IGNITE-9676 URL: https://issues.apache.org/jira/browse/IGNITE-9676 Project: Ignite Issue Type: New Feat

Re: TeamCity Helper's wiki page

Awesome, thanks! Added you to list of contributors. Feel free to create a new page under https://cwiki.apache.org/confluence/display/IGNITE/Testing+and+benchmarking Sincerely, Dmitriy Pavlov пн, 24 сент. 2018 г. в 15:39, Dmitrii Ryabov : > I signed up. My username - somefire. > > 2018-09-24 15:

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

Hello Andrei, All these metrics available through JMX (see "DataRegionMetrics" group) [1]. [1] https://apacheignite.readme.io/docs/memory-metrics пн, 24 сент. 2018 г. в 17:58, aealexsandrov : > > Hi Igniters, > > Small notes according to these fix. > > As I see that all logic of calculation off-n

[GitHub] ignite pull request #4817: IGNITE-9669 implemented

GitHub user SGrimstad opened a pull request: https://github.com/apache/ignite/pull/4817 IGNITE-9669 implemented You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite IGNITE-9669 Alternatively you can review and

[jira] [Created] (IGNITE-9675) Deadlock on Ignite:active() and stopping grid simultaneously calling

Alexey Platonov created IGNITE-9675: --- Summary: Deadlock on Ignite:active() and stopping grid simultaneously calling Key: IGNITE-9675 URL: https://issues.apache.org/jira/browse/IGNITE-9675 Project: I

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

Hi Igniters, Small notes according to these fix. As I see that all logic of calculation off-neap max size at the moment located in the ackNodeMetrics method in IgniteKernal.java. I think that it isn't ok because this logic should be added to other functionality too. I think that will be better t

[jira] [Created] (IGNITE-9674) Double p2p class loading

Sergey Antonov created IGNITE-9674: -- Summary: Double p2p class loading Key: IGNITE-9674 URL: https://issues.apache.org/jira/browse/IGNITE-9674 Project: Ignite Issue Type: Bug Rep

[jira] [Created] (IGNITE-9673) Timeout in Java Client suite.

Amelchev Nikita created IGNITE-9673: --- Summary: Timeout in Java Client suite. Key: IGNITE-9673 URL: https://issues.apache.org/jira/browse/IGNITE-9673 Project: Ignite Issue Type: Bug

Re: Critical worker threads liveness checking drawbacks

Andrey K. and G., Thanks, do we have a documentation ticket created? Prachi (copied) can help with the documentation. -- Denis On Mon, Sep 24, 2018 at 5:51 AM Andrey Gura wrote: > Andrey, > > finally your change is merged to master branch. Congratulations and > thank you very much! :) > > I th

[GitHub] ignite pull request #4815: IGNITE-8022 Need to add README.txt for ignite-dir...

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

[GitHub] ignite pull request #4816: Ignite 9004 2.5.1

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

[jira] [Created] (IGNITE-9672) Move o.a.i.i.processors.cache.persistence.tree.io.PageMetaIO to metastore.

Alexei Scherbakov created IGNITE-9672: - Summary: Move o.a.i.i.processors.cache.persistence.tree.io.PageMetaIO to metastore. Key: IGNITE-9672 URL: https://issues.apache.org/jira/browse/IGNITE-9672

[GitHub] ignite pull request #4815: IGNITE-8022 Need to add README.txt for ignite-dir...

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/4815 IGNITE-8022 Need to add README.txt for ignite-direct-io You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/ignite ignite-8022 Alternative

[jira] [Created] (IGNITE-9671) Hanging the end of the CacheAsyncOperationsFailoverTxTest#testPutAllAsyncFailover test.

Alexey Stelmak created IGNITE-9671: -- Summary: Hanging the end of the CacheAsyncOperationsFailoverTxTest#testPutAllAsyncFailover test. Key: IGNITE-9671 URL: https://issues.apache.org/jira/browse/IGNITE-9671

[GitHub] ignite pull request #4814: IGNITE-9670: debug changes

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/4814 IGNITE-9670: debug changes You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9670 Alternatively you can r

Re: java.lang.ClassCastException: org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl cannot be cast to org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryEx

Hello! What is the Ignite version used there? I remember seeing errors like this one, but way back. Regards, -- Ilya Kasnacheev вс, 23 сент. 2018 г. в 21:07, kcheng.mvp : > I ran into this error with below configuration(IgniteSpringBean) > > I set * defaultDataRegionConfiguration* as * nam

[jira] [Created] (IGNITE-9670) JDK9: supports hadoop Ignite module

Taras Ledkov created IGNITE-9670: Summary: JDK9: supports hadoop Ignite module Key: IGNITE-9670 URL: https://issues.apache.org/jira/browse/IGNITE-9670 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-9669) Spark Integration fails test after fix IGNITE-8552

Sergey Grimstad created IGNITE-9669: --- Summary: Spark Integration fails test after fix IGNITE-8552 Key: IGNITE-9669 URL: https://issues.apache.org/jira/browse/IGNITE-9669 Project: Ignite Iss

[jira] [Created] (IGNITE-9668) Comment JIRA from pr.html

Ryabov Dmitrii created IGNITE-9668: -- Summary: Comment JIRA from pr.html Key: IGNITE-9668 URL: https://issues.apache.org/jira/browse/IGNITE-9668 Project: Ignite Issue Type: Sub-task

[GitHub] ignite pull request #4737: IGNITE-9544 BinaryOutputStream#writeByte excessiv...

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

Re: Critical worker threads liveness checking drawbacks

Andrey, finally your change is merged to master branch. Congratulations and thank you very much! :) I think that the next step is feature that will allow signal about blocked threads to the monitoring tools via MXBean. I hope you will continue development of this feature and provide your vision

Re: TeamCity Helper's wiki page

I signed up. My username - somefire. 2018-09-24 15:08 GMT+03:00 Dmitriy Pavlov : > Dmitrii, > > could you please sign up to the wiki and share your ID. I will set > necessary permissions. > > Sincerely, > Dmitriy Pavlov > > пн, 24 сент. 2018 г. в 14:57, Dmitrii Ryabov : > > > Hello, Igniters! > >

[GitHub] ignite pull request #4808: IGNITE-9665: fix for RPM build

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

Re: Include TeamCity Helper into contribution process

++1 Only one concern - the domain name is now GridGain. I will ask infra about Apache domain, but it will require some time to be done. пн, 24 сент. 2018 г. в 15:07, Dmitrii Ryabov : > Hello, Igniters! > > I propose to update the "How to Contribute" page to include TeamCity > Helper's JIRA commen

Re: Apache Ignite 2.7 - Release Procedure issues

Hello, Petr. My suggestion is to migrate to a newer version of GPG and throw an error message if one use old version. В Пн, 24/09/2018 в 14:53 +0300, Petr Ivanov пишет: > I’ve checked the changes and they are good both on old and latest versions of > Ubuntu. > > > However, I’ve stumbled upon

Re: TeamCity Helper's wiki page

Dmitrii, could you please sign up to the wiki and share your ID. I will set necessary permissions. Sincerely, Dmitriy Pavlov пн, 24 сент. 2018 г. в 14:57, Dmitrii Ryabov : > Hello, Igniters! > > I propose to create page about TeamCity Helper on the wiki and move here > information about Helper

Include TeamCity Helper into contribution process

Hello, Igniters! I propose to update the "How to Contribute" page to include TeamCity Helper's JIRA commenting functionality into contribution process. This will speedup review process by highlighting new failures, timeouts and othe critical failures in the JIRA ticket. For example, we can repl

TeamCity Helper's wiki page

Hello, Igniters! I propose to create page about TeamCity Helper on the wiki and move here information about Helper from the MTCGA page. Also, I want to add instruction about how to use TCH to comment JIRA: 1. Start "Run All" build for PR on TeamCity. 2. Check failures and fix possible blockers.

Re: Apache Ignite 2.7 - Release Procedure issues

I’ve checked the changes and they are good both on old and latest versions of Ubuntu. However, I’ve stumbled upon another problem — GPG: current release scripts do not honour latest GPG versions. I can introduce corresponding changes, but question is — should release script check for GPG versi

Re: IgniteEvents for MVCC caches

Igniters, Igniters, I see three distinct problems with cache events, if we are to put SQL aside. 1) Strange "ENTRY_CREATED" and "ENTRY_DESTROYED" events They simply look outdated. I propose to deprecate them in the next AI release with optional flag to re-enalbe them if someone really used them.

Re: [MTCGA]: new failures in builds [1848302] needs to be handled

Hi Igniters, It seems it is duplicate. But anyway Hadoop needs to be fixed. Sincerely, Dmitriy Pavlov пн, 24 сент. 2018 г. в 0:14, : > 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)

[jira] [Created] (IGNITE-9667) Error in DataRegionMetrics.getTotalAllocatedSize in case of CREATE/INSERT/DROP/CREATE/INSERT

Vasiliy Sisko created IGNITE-9667: - Summary: Error in DataRegionMetrics.getTotalAllocatedSize in case of CREATE/INSERT/DROP/CREATE/INSERT Key: IGNITE-9667 URL: https://issues.apache.org/jira/browse/IGNITE-9667

Re: Spring Session Ignite plugin

Hi Anton, There is GitHub mirror of Apache Ignite codebase here: https://github.com/apache/ignite You can create JIRA ticket and pull request from your Apache Ignite fork. Another option is to donate to some supplementary repository, but this way is much more complex and requires discussion from

Re: IgniteEvents for MVCC caches

Hi guys, Andrey, thanks for pointing out explicit lock/unlock operations. Actually, I think that lock/unlock events are perfectly valid for TRANSACTIONAL caches, so there is a little chance that they could be deprecated. On the other hand mvcc lock/unlock is not related to non-mvcc lock/unlock bec

Spring Session Ignite plugin

Hello Igniters, I have implemented small community extension to use Apache Ignite as backing repository for session clustering with Spring Session: github link . I was wondering what would be the best way to share this with community, is there any

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