[GitHub] ignite pull request #5617: IGNITE-10189 Added support for SSL Ciphers for co...

GitHub user akuznetsov-gridgain opened a pull request: https://github.com/apache/ignite/pull/5617 IGNITE-10189 Added support for SSL Ciphers for control.sh You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ig

[GitHub] ignite pull request #5392: IGNITE-10189 Added SSL ciphers suites support for...

Github user akuznetsov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/5392 ---

[jira] [Created] (IGNITE-10615) Ignite Compatibility: fix arguments' checking in the node runner

Vyacheslav Daradur created IGNITE-10615: --- Summary: Ignite Compatibility: fix arguments' checking in the node runner Key: IGNITE-10615 URL: https://issues.apache.org/jira/browse/IGNITE-10615 Proj

Re: Support service on inactive cluster

Alexey, Have a look at the 'PluginProvider' interface, if you implemented a telemetry service as a plugin: * plugin may be placed in the 'web-console' module; * plugin is initialized at node startup and is stopped at node shutdown; * plugin have access to all Ignite's internals through context; *

[GitHub] ignite pull request #5618: IGNITE-10615 Ignite Compatibility: fix arguments'...

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/5618 IGNITE-10615 Ignite Compatibility: fix arguments' checking in the node runner You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/igni

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

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

[GitHub] ignite pull request #5429: IGNITE-8432: Test for column name case in PK and ...

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

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

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

[jira] [Created] (IGNITE-10616) Web console: new security token must be applied immediately

Pavel Konstantinov created IGNITE-10616: --- Summary: Web console: new security token must be applied immediately Key: IGNITE-10616 URL: https://issues.apache.org/jira/browse/IGNITE-10616 Project:

[GitHub] SomeFire opened a new pull request #96: fix typo in schedulers

SomeFire opened a new pull request #96: fix typo in schedulers URL: https://github.com/apache/ignite-teamcity-bot/pull/96 This is an automated message from the Apache Git Service. To respond to the message, please log on GitH

Re: Ignite cloud readiness and as a managed service

>From my point of view, it's important to further develop the thin client. Users should be able to use most of Ignite's components via thin client, as far as possible, just for example: * transactional CRUD operations over data in the cluster; * deploy/undeploy and monitor services in the Service

Re: java.lang.IllegalAccessError: tried to access field org.h2.util.LocalDateTimeUtils.LOCAL_DATE from class org.apache.ignite.internal.processors.query.h2.H2DatabaseType

Hi Ken, It looks like you have a dependency to different h2 version in your project. Ignite requires com.h2database:h2 version 1.4.197. пн, 10 дек. 2018 г. в 07:08, kcheng.mvp : > > > There are total 82 unite test for my system. > > this unit test works well in ignite 2.6. > > when I switch to ign

[jira] [Created] (IGNITE-10617) Web console: Invalid class name in frontend/app/components/connected-clusters-dialog/components/list/controller.js

Vasiliy Sisko created IGNITE-10617: -- Summary: Web console: Invalid class name in frontend/app/components/connected-clusters-dialog/components/list/controller.js Key: IGNITE-10617 URL: https://issues.apache.org/ji

[jira] [Created] (IGNITE-10618) Web console: exclude daemon node from cluster size on Connected Clusters modal

Pavel Konstantinov created IGNITE-10618: --- Summary: Web console: exclude daemon node from cluster size on Connected Clusters modal Key: IGNITE-10618 URL: https://issues.apache.org/jira/browse/IGNITE-10618

[jira] [Created] (IGNITE-10619) Add support for ReadableByteChannel, WritableByteChannel over CommunicationSpi

Maxim Muzafarov created IGNITE-10619: Summary: Add support for ReadableByteChannel, WritableByteChannel over CommunicationSpi Key: IGNITE-10619 URL: https://issues.apache.org/jira/browse/IGNITE-10619

[GitHub] ignite pull request #5619: IGNITE-10619: CommunicationSpi support channels i...

GitHub user Mmuzaf opened a pull request: https://github.com/apache/ignite/pull/5619 IGNITE-10619: CommunicationSpi support channels initial commit - GridNioServer supports channel creation from GridNioSession - rework createTcpClient method - new GridIoManager channel creati

Re: Default failure handler was changed for tests

Dmitriy, You confirmed that fix should be reverted and reworked last Friday. Why it still not reverted? On Mon, Dec 10, 2018 at 12:46 AM Dmitrii Ryabov wrote: > Agree, it is reasonable to revert. > пт, 7 дек. 2018 г. в 18:44, Dmitriy Pavlov : > > > > Hi Ilya, > > > > thank you for noticing. > >

Re: [RESULT] [VOTE] Apache Ignite 2.7.0 Release (RC2)

AFAIK, there is no such procedure yet and it definitely requires introduction. I guess, thin client developers should share the process of updating official repositories. > On 10 Dec 2018, at 09:49, Nikolay Izhikov wrote: > > Hello, Roman. > > Do we have release procedure for this pacakage? >

[GitHub] ignite pull request #5357: IGNITE-10167: MVCC-compatible IgniteCache.localEn...

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

Re: About readme.io's latest docs

Prachi, Can you help to export all the latest version of all documents to me? I am ready to make a synchronization of the chinese version of the document. thanks! 在 2018/6/2 上午4:38, Prachi Garg 写道: Please see attached. On Fri, Jun 1, 2018 at 9:22 AM, 李玉珏@163 <18624049...@163.com

[GitHub] ignite pull request #5500: IGNITE-10366: MVCC: Create "Cache 1" test suite f...

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

[GitHub] ignite pull request #5585: IGNITE-10367: MVCC: Create "Cache 8" test suite f...

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

[jira] [Created] (IGNITE-10620) [TC Bot] Implement Tracked Branches processor and IssueDetector unit tests

Dmitriy Pavlov created IGNITE-10620: --- Summary: [TC Bot] Implement Tracked Branches processor and IssueDetector unit tests Key: IGNITE-10620 URL: https://issues.apache.org/jira/browse/IGNITE-10620 Pr

[GitHub] ignite pull request #5409: IGNITE-10263: MVCC: Concurrent cache stop can cau...

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

[GitHub] asfgit closed pull request #96: fix typo in schedulers

asfgit closed pull request #96: fix typo in schedulers URL: https://github.com/apache/ignite-teamcity-bot/pull/96 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (

[GitHub] asfgit closed pull request #94: Visa History page fix

asfgit closed pull request #94: Visa History page fix URL: https://github.com/apache/ignite-teamcity-bot/pull/94 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (f

[jira] [Created] (IGNITE-10621) Track all running queries

Yury Gerzhedovich created IGNITE-10621: -- Summary: Track all running queries Key: IGNITE-10621 URL: https://issues.apache.org/jira/browse/IGNITE-10621 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #4685: IGNITE-4111

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

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

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

[GitHub] ignite pull request #5593: IGNITE-10578

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

[GitHub] ignite pull request #5590: IGNITE-8626: ODBC and C++ thin now support OpenSS...

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

[GitHub] ignite pull request #5620: IGNITE-10621

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

Re: Default failure handler was changed for tests

Anton, I was expecting that you revert, because you wanted to do it. Provided that I agree that fix could be reverted because of both functional and style possible improvements, does not mean I believe it is the only option and it should be reverted. Even if I agree to revert doesn't mean all com

[jira] [Created] (IGNITE-10622) Undelivered ensure message to some nodes

Anton Kalashnikov created IGNITE-10622: -- Summary: Undelivered ensure message to some nodes Key: IGNITE-10622 URL: https://issues.apache.org/jira/browse/IGNITE-10622 Project: Ignite Issue

[GitHub] ignite pull request #5563: IGNITE-10511 removeExplicitNodeLocks() removed.

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

[GitHub] ignite pull request #5425: IGNITE-10300 Fixed correct message in case of use...

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

[GitHub] ignite pull request #5621: Ignite 2.5.1 p162

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

Re: Default failure handler was changed for tests

Reverted. https://issues.apache.org/jira/browse/IGNITE-8227 reopened пн, 10 дек. 2018 г. в 16:23, Dmitriy Pavlov : > Anton, I was expecting that you revert, because you wanted to do it. > > Provided that I agree that fix could be reverted because of both > functional and style possible improveme

[jira] [Created] (IGNITE-10623) Possible JVM crash in case of stopping node with errors

Eduard Shangareev created IGNITE-10623: -- Summary: Possible JVM crash in case of stopping node with errors Key: IGNITE-10623 URL: https://issues.apache.org/jira/browse/IGNITE-10623 Project: Ignite

[GitHub] ignite pull request #5622: IGNITE-10472: MVCC: Add Dependency Injection supp...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/5622 IGNITE-10472: MVCC: Add Dependency Injection support for EntryProcessor. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ign

[GitHub] ignite pull request #5623: IGNITE-10623 Possible JVM crash when node stopped...

GitHub user EdShangGG opened a pull request: https://github.com/apache/ignite/pull/5623 IGNITE-10623 Possible JVM crash when node stopped with errors You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1

[GitHub] ignite pull request #5624: IGNITE-10556 Skip records deserialization on reco...

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/5624 IGNITE-10556 Skip records deserialization on recovery You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10556 Alter

[GitHub] ignite pull request #5625: IGNITE-8717 Cache configuration was moved to meta...

GitHub user antonovsergey93 opened a pull request: https://github.com/apache/ignite/pull/5625 IGNITE-8717 Cache configuration was moved to metastore You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-87

[GitHub] ignite pull request #5425: IGNITE-10300 Fixed correct message in case of use...

GitHub user voropava reopened a pull request: https://github.com/apache/ignite/pull/5425 IGNITE-10300 Fixed correct message in case of user/password retries e… …xceeded. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain

[GitHub] ignite pull request #5626: IGNITE-10359: Add deployment feature for EntryPro...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/5626 IGNITE-10359: Add deployment feature for EntryProcessor. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10359

[GitHub] ignite pull request #5627: IGNITE-10464: MVCC: Create "PDS 4" test suite for...

GitHub user rkondakov opened a pull request: https://github.com/apache/ignite/pull/5627 IGNITE-10464: MVCC: Create "PDS 4" 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-10

[GitHub] ignite pull request #5628: IGNITE-10622 to sent pending messages when new ne...

GitHub user akalash opened a pull request: https://github.com/apache/ignite/pull/5628 IGNITE-10622 to sent pending messages when new next node was selected You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ig

Clean up of our PRs and IEPs before 2019

Hi Igniters, Newcomers to Apache Ignite sometimes became concerned about many open PRs in the project. Apache Ignite TC Bot also performs runs checks with a PR open. Apache Ignite pulls list https://github.com/apache/ignite/pulls contains 1442 PRs open while only 84 issues are waiting for review.

[GitHub] ignite pull request #3919: Ignite 2.4.2 p10

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

[GitHub] ignite pull request #4239: IGNITE-8849

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

[GitHub] ignite pull request #1481: IGNITE-4552 support eviction for dhtLocalPartitio...

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

[GitHub] ignite pull request #1522: IGNITE-4484 fix not compliant with tx isolation s...

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

[GitHub] zzzadruga commented on a change in pull request #95: IGNITE-9542: new run history stripe

zzzadruga commented on a change in pull request #95: IGNITE-9542: new run history stripe URL: https://github.com/apache/ignite-teamcity-bot/pull/95#discussion_r240279974 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcbot/issue/IssueDetector.java ##

[GitHub] ignite pull request #2779: IGNITE-6437: DataStructure can not be obtained on...

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

[GitHub] dspavlov commented on a change in pull request #95: IGNITE-9542: new run history stripe

dspavlov commented on a change in pull request #95: IGNITE-9542: new run history stripe URL: https://github.com/apache/ignite-teamcity-bot/pull/95#discussion_r240287246 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcbot/issue/IssueDetector.java ##

[GitHub] ignite pull request #3144: IGNITE-7112 More informative: Failed to wait PME

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

[GitHub] ignite pull request #1493: IGNITE-4654 GridMarshallerPerformanceTest#testGri...

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

[GitHub] ignite pull request #1544: IGNITE-4710: extended optimistic tx lock conflict...

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

[GitHub] ignite pull request #1922: IGNITE-5125, improve logging in case of hang whil...

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

[GitHub] ignite pull request #1955: IGNITE-5100 don`t remove active exchange events f...

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

[GitHub] ignite pull request #2482: IGNITE-5869 client hangs infinitely while binary ...

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

[GitHub] asfgit closed pull request #95: IGNITE-9542: new run history stripe

asfgit closed pull request #95: IGNITE-9542: new run history stripe URL: https://github.com/apache/ignite-teamcity-bot/pull/95 This is an automated message from the Apache Git Service. To respond to the message, please log on

[GitHub] ignite pull request #2986: IGNITE-5955: IgniteCacheContinuousQueryClientReco...

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

[GitHub] ignite pull request #3190: IGNITE-3935: Switch to the peer-class-loading loa...

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

Re: Clean up of our PRs and IEPs before 2019

Hello, Dmitriy. What, exactly concerns newcomers? What is wrong with opened PR? How project will benefit from closed PR? > The same proposal is related to IEP statuses. If you were involved in an IEP, please validate its status +1. We should maintain IEP description up to date. пн, 10 дек. 2018

[GitHub] ignite pull request #2121: IGNITE-1583: fix test, removeNode partition id up...

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

[jira] [Created] (IGNITE-10624) Cache deployment id may be different that cluster-wide after recovery

Pavel Kovalenko created IGNITE-10624: Summary: Cache deployment id may be different that cluster-wide after recovery Key: IGNITE-10624 URL: https://issues.apache.org/jira/browse/IGNITE-10624 Proje

[GitHub] ignite pull request #5629: IGNITE-10624 Update deployment id for recovered c...

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/5629 IGNITE-10624 Update deployment id for recovered cache after join to topology You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ign

Re: Clean up of our PRs and IEPs before 2019

The main concern is related to chances that newcomer will have to obtain a review support from the community. Actually, a lot of people doing their best to provide a feedback to newcomers, and count of issues still in PA state goes down (84 is a relatively small count of issues in PA state). But 1

[GitHub] ignite pull request #2276: Ignite 5515

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

[GitHub] ignite pull request #1892: Ignite 5078: Pull request for partition lost even...

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

[jira] [Created] (IGNITE-10625) Do first checkpoint on node start before join to topology

Pavel Kovalenko created IGNITE-10625: Summary: Do first checkpoint on node start before join to topology Key: IGNITE-10625 URL: https://issues.apache.org/jira/browse/IGNITE-10625 Project: Ignite

Re: Is it time to move forward to JUnit4 (5)?

Ivan, So, suggested actions with the new approach: 1. Add @Test annotation on test methods. 2. Add @RunWith(JUnit4.class) annotation on test class. 3. Add @Before, @After on methods which should run before, after a test (setUp, tearDown in current approach). 4. Add your test-class to a suite using

Re: Is it time to move forward to JUnit4 (5)?

Ed, Several questions from my side: 1) When the change is expected to be merged? 2) What contributors with opened PRs and new or updated JUnit3 tests are supposed to do? Rewrite to JUnit4? If yes, then we should give them time to have a chance to get used to new approach and resolve possible conf

Re: Is it time to move forward to JUnit4 (5)?

Vovan, 1) Tomorrow in core-module. 2) I believe that nothing, old JUnit3 would work if they are a new one. Otherwise, they need to fix merge conflict and add @Test on their new test. And I think that it's unavoidable, we couldn't ask all people to finish their current activity and not start a new

Re: Is it time to move forward to JUnit4 (5)?

Vladimir, AFAIK there will be no single change for overall migration. All migration will be in a step-by-step manner and mostly transparent for contributors. Both approaches 3&4 will be available for some time. First of all, we need an opportunity to run existing integration tests in JUnit4. пн,

[jira] [Created] (IGNITE-10626) Save authenticated Webconsole session for more than one page refresh

Evgenii Zhuravlev created IGNITE-10626: -- Summary: Save authenticated Webconsole session for more than one page refresh Key: IGNITE-10626 URL: https://issues.apache.org/jira/browse/IGNITE-10626 Pr

[GitHub] ignite pull request #5584: IGNITE-8227: Proper NoOpHandler injection.

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

Re: Schema in CacheConfig is not updated after DDL commands(Add/drop column, Create/drop index)

Vladimir. Since we are talking about internal component(Spark Data Frame integration) can we use same technique as JdbcRequestHandler to obtain columns metadata? Seems, code above will fetch up to date columns info: org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler#getColumnsMeta

Re: Is it time to move forward to JUnit4 (5)?

Got it. Thank you. пн, 10 дек. 2018 г. в 20:52, Dmitriy Pavlov : > Vladimir, AFAIK there will be no single change for overall migration. All > migration will be in a step-by-step manner and mostly transparent for > contributors. > > Both approaches 3&4 will be available for some time. > > First o

[jira] [Created] (IGNITE-10627) Support custom preferences like date format and other similar features

Evgenii Zhuravlev created IGNITE-10627: -- Summary: Support custom preferences like date format and other similar features Key: IGNITE-10627 URL: https://issues.apache.org/jira/browse/IGNITE-10627

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

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/5541 ---

[GitHub] ignite pull request #5219: IGNITE-10079 Fixed inconsistent lastCompactedSegm...

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/5219 ---

[GitHub] ignite pull request #5092: TDR-93 Several WAL compressor fixes.

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/5092 ---

[GitHub] ignite pull request #4547: Tdr 26

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/4547 ---

[jira] [Created] (IGNITE-10628) Add support for nightly RunAll

Nikolai Kulagin created IGNITE-10628: Summary: Add support for nightly RunAll Key: IGNITE-10628 URL: https://issues.apache.org/jira/browse/IGNITE-10628 Project: Ignite Issue Type: Sub-tas

[GitHub] zzzadruga opened a new pull request #97: IGNITE-10628 Add support for nightly RunAll

zzzadruga opened a new pull request #97: IGNITE-10628 Add support for nightly RunAll URL: https://github.com/apache/ignite-teamcity-bot/pull/97 This is an automated message from the Apache Git Service. To respond to the mess

Re: Is it time to move forward to JUnit4 (5)?

Hello, I would like add few minor clarifications to what Ed wrote. 1. After transition to JUnit4 is fully over (ETA this week) there won't be a need to use @RunWith(JUnit4.class) anymore, so you will be writing test classes as a normal JUnit 4 user, without any special scaffolding. 1.1. Please ke

[jira] [Created] (IGNITE-10629) Migration follow up: check for old style tests that could be slipped through in transition period

Oleg Ignatenko created IGNITE-10629: --- Summary: Migration follow up: check for old style tests that could be slipped through in transition period Key: IGNITE-10629 URL: https://issues.apache.org/jira/browse/IGNIT

[GitHub] ignite pull request #3413: Ignite system views (prototype)

Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3413 ---

[GitHub] ignite pull request #3433: IGNITE-7527 SQL system views: local transactions

Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3433 ---

[GitHub] ignite pull request #3664: IGNITE-7969 Fixed failure of failure of IgniteTop...

Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3664 ---

[GitHub] ignite pull request #3855: IGNITE-8191 Print out information when cluster is...

Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3855 ---

[GitHub] ignite pull request #3866: IGNITE-8192 Print out information on how many nod...

Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3866 ---

[GitHub] ignite pull request #3875: IGNITE-8190 Print out an information message when...

Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3875 ---

[GitHub] ignite pull request #3906: IGNITE-8191 Hotfix (don't wait for transition)

Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3906 ---

[GitHub] ignite pull request #3963: IGNITE-8443 Transaction hangs when some error occ...

Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3963 ---

[GitHub] ignite pull request #3922: IGNITE-8400 IgniteTopologyValidatorGridSplitCache...

Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3922 ---

[GitHub] ignite pull request #3930: IGNITE-8400 IgniteTopologyValidatorGridSplitCache...

Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3930 ---

[GitHub] ignite pull request #3964: IGNITE-8443 Transaction hangs when some error occ...

Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3964 ---

  1   2   >