[jira] [Created] (IGNITE-12978) Cancel snapshot command

Maxim Muzafarov created IGNITE-12978: Summary: Cancel snapshot command Key: IGNITE-12978 URL: https://issues.apache.org/jira/browse/IGNITE-12978 Project: Ignite Issue Type: Improvement

Re: [DISCUSSION] Pull-request checks on GitHub

Hello, I have the following in my mind: 1. This checklist is for discussion and may be changed. 2. Commits can be squashed in the branch prior to asking a review, but when the review is in progress a good naming may help to understand the changes. 3. It's true that the commit message can be change

[jira] [Created] (IGNITE-12979) Peer-class-loading behavior causes the server's metaspace out of memory

xubo guo created IGNITE-12979: - Summary: Peer-class-loading behavior causes the server's metaspace out of memory Key: IGNITE-12979 URL: https://issues.apache.org/jira/browse/IGNITE-12979 Project: Ignite

Re: [VOTE][EXTENSION] Release Apache Ignite Spring Boot extensions 1.0.0 RC2

+1 On Sat, 2 May 2020 at 04:23, Saikat Maitra wrote: > > +1 (binding) > > Regards, > Saikat > > On Fri, May 1, 2020 at 2:52 PM Denis Magda wrote: > > > +1 (binding) > > > > Checked and edited the docs. Nikolay, please double-check for the technical > > accuracy. Also, I hid the page for now. Ple

Re: [DISCUSSION] Pull-request checks on GitHub

Igniters, Maxim, I think this thread is a good opportunity to discuss commit message guidelines. I suggest the following: 1. Treat PR title + description as the final squashed commit message. PR author is responsible for writing that properly. Committer who merges the PR is responsible for valida

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

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *Test with high flaky rate in master IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeAfterKillTwoNodesWithPersistence[TRANSACTIONAL] https://ci.ignite.apache.org/project.html

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

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *Test with high flaky rate in master IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeAfterKillTwoNodesWithPersistence[TRANSACTIONAL] https://ci.ignite.apache.org/project.html

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

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *Test with high flaky rate in master IgniteClusterActivateDeactivateTest.testActivateWithReadOnlyFailover3 https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testN

Re: About Rebalance Mode (SYNC & NONE)

Hi. You are correct, NONE is a legacy mode and should be removed [1] Note the baseline can be used with in-memory caches as well. To make it working you have to disable baseline auto-adjust or set non-zero auto-adjust timeout. This will prevent unnecessary rebalancing. [1] https://issues.apache.

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

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