[jira] [Created] (IGNITE-8187) Additional parameters like ACL lists should be taken into account when calculating request overhead

Sergey Chugunov created IGNITE-8187: --- Summary: Additional parameters like ACL lists should be taken into account when calculating request overhead Key: IGNITE-8187 URL:

[jira] [Created] (IGNITE-8190) Print out an information message when local node is not in baseline

Alexey Goncharuk created IGNITE-8190: Summary: Print out an information message when local node is not in baseline Key: IGNITE-8190 URL: https://issues.apache.org/jira/browse/IGNITE-8190 Project:

[GitHub] ignite pull request #3780: IGNITE-4958: Make data pages recyclable into inde...

GitHub user x-kreator opened a pull request: https://github.com/apache/ignite/pull/3780 IGNITE-4958: Make data pages recyclable into index/meta/etc pages and… … vice versa. You can merge this pull request into a Git repository by running: $ git pull

Re: IGNITE-6827 - Review needed.

Guys, I've slightly modified public API javadoc as Denis Magda has suggested in PR review. Please take a look. Pavel Tupitsyn, what about .NET stuff ? I provided all necessary information in ticket [2] Upsource link [1] [1] https://reviews.ignite.apache.org/ignite/branch/PR%203624 [2]

Re: Thin clients release cycle

Guys, has anybody checked with INFRA if we can have module structure? Denis? --Yakov

Re: Service grid redesign

Another question, that I would like to discuss is whether services should be preserved on cluster restarts. Currently it depends on persistence configuration. If persistence for any data region is enabled, then services will be persisted as well. This is a pretty strange way of configuring this

Re: Contributor permissions

Hello, Yoko and welcome aboard! Added your account to JIRA contributors' list. Let me share a piece of useful information with you that usually helps contributors to start with the contribution. Please subscribe to both dev and user lists:

[jira] [Created] (IGNITE-8196) ZookeeperDiscoverySpi should be documented on readme.io

Sergey Chugunov created IGNITE-8196: --- Summary: ZookeeperDiscoverySpi should be documented on readme.io Key: IGNITE-8196 URL: https://issues.apache.org/jira/browse/IGNITE-8196 Project: Ignite

Re: IEP-18: Transparent Data Encryption

Hello, Igniters. I'm going to create tickets and start implementation of TDE in a few days. Any objections? В Пн, 09/04/2018 в 17:55 +0300, Nikolay Izhikov пишет: > Hello, Denis > > > Is it necessary to have CEP keys for every cache? > > With current design, It's necessary to have difference

Re: iep-6 metrics ticket review

Val, As an initial reviewer and reporter, could you have a look and sign the contribution off? -- Denis On Mon, Apr 9, 2018 at 12:56 AM, Aleksey Kuznetsov wrote: > Hi ,Igniters! > > Do we still need this ticket, about invoke metrics : [1] ? > > If yes, than could

Re: IEP-18: Transparent Data Encryption

Hi Nikolay, I would like to look to IEP. Please give me couple days. Sincerely, Dmitriy Pavlov пн, 9 апр. 2018 г. в 20:11, Nikolay Izhikov : > Hello, Igniters. > > I'm going to create tickets and start implementation of TDE in a few days. > > Any objections? > > В Пн,

[jira] [Created] (IGNITE-8186) SQL: Create test base to cover sql by features with flexible configuration

Pavel Kuznetsov created IGNITE-8186: --- Summary: SQL: Create test base to cover sql by features with flexible configuration Key: IGNITE-8186 URL: https://issues.apache.org/jira/browse/IGNITE-8186

[GitHub] ignite-release pull request #1: IGNITE-8172

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

Re: Service grid redesign

Val, Sounds reasonable. I just think, that user should have some way to know, that new version of a service class was deployed. One way to do it is to listen to *EVT_CLASS_DEPLOYED. *I'm not sure, whether it is triggered on class redeployment, though. If not, then another event type should be

[jira] [Created] (IGNITE-8191) Print out information when cluster is not activated

Alexey Goncharuk created IGNITE-8191: Summary: Print out information when cluster is not activated Key: IGNITE-8191 URL: https://issues.apache.org/jira/browse/IGNITE-8191 Project: Ignite

[jira] [Created] (IGNITE-8195) ZookeeperDiscoverySpi should be properly documented

Sergey Chugunov created IGNITE-8195: --- Summary: ZookeeperDiscoverySpi should be properly documented Key: IGNITE-8195 URL: https://issues.apache.org/jira/browse/IGNITE-8195 Project: Ignite

[GitHub] ignite pull request #3782: IGNITE-8078

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

Re: IGNITE-6879

Hi Denis, could we support just one version instead of leaving compatible module? Sincerely, Dmitriy Pavlov пн, 9 апр. 2018 г. в 20:08, Dmitry Pavlov : > > > пн, 9 апр. 2018 г. в 20:07, Dmitry Pavlov : > >> Hi Roman, >> >> I've applied PR locally

[GitHub] ignite pull request #3781: Ignite 1.9.12

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

Re: Rebalancing - how to make it faster

>> I would enable this option only after we confirm it's stable. We have to add system property in that case. It's a bad idea to have such options at API because it can be unstable. It's like allowMoreThan1024Node(bool) since we have issues with that. 2018-04-09 20:03 GMT+03:00 Yakov Zhdanov

Re: IGNITE-6879

Hi Roman, I've applied PR locally and I have class name conflict at least for org.apache.ignite.springdata.repository.query.IgniteQueryGenerator How could we solve it? Is it better to rename class for new plugin version? Sincerely, Dmitriy Pavlov пт, 6 апр. 2018 г. в 17:38, Dmitry Pavlov

[jira] [Created] (IGNITE-8189) Improve ZkDistributedCollectDataFuture#deleteFutureData implementation

Sergey Chugunov created IGNITE-8189: --- Summary: Improve ZkDistributedCollectDataFuture#deleteFutureData implementation Key: IGNITE-8189 URL: https://issues.apache.org/jira/browse/IGNITE-8189

Re: Rebalancing - how to make it faster

Ilya, WAL should be automatically disabled at initial rebalancing. It can't be disabled at regilar rebalancing, since you never ready to lose data you protected by WAL. Is there any need to have special param in that case? 2018-04-09 16:41 GMT+03:00 Ilya Lantukh : >

[jira] [Created] (IGNITE-8193) Joining node data should be cleaned in some cases

Sergey Chugunov created IGNITE-8193: --- Summary: Joining node data should be cleaned in some cases Key: IGNITE-8193 URL: https://issues.apache.org/jira/browse/IGNITE-8193 Project: Ignite

Re: Rebalancing - how to make it faster

Not sure I agree. I think feature toggle is best practice. Eventually we can remove related code, but it always good to have migration stages: 1) old and new provided but new is disabled, 2) both provided and new is enabled 3) new is enabled, old is not available. It is common practice for

[jira] [Created] (IGNITE-8188) Batching operations should perform check for ZooKeeper request max size

Sergey Chugunov created IGNITE-8188: --- Summary: Batching operations should perform check for ZooKeeper request max size Key: IGNITE-8188 URL: https://issues.apache.org/jira/browse/IGNITE-8188

[jira] [Created] (IGNITE-8194) Coordinator may need to delete acks for event if the ack with the same id is already published

Sergey Chugunov created IGNITE-8194: --- Summary: Coordinator may need to delete acks for event if the ack with the same id is already published Key: IGNITE-8194 URL:

Re: Rebalancing - how to make it faster

I would enable this option only after we confirm it's stable. Until it happens it should be treated as an experimental feature that is turned on manually with a parameter like Ilya is suggesting. Ilya, the name sounds good to me. -- Denis On Mon, Apr 9, 2018 at 9:16 AM, Anton Vinogradov

Re: Rebalancing - how to make it faster

How about skipWalOnRebalancing or disableWalOnRebalancing? I like the first one better and both are shorter. --Yakov 2018-04-09 19:55 GMT+03:00 Denis Magda : > I would enable this option only after we confirm it's stable. Until it > happens it should be treated as an

Re: IGNITE-6879

Hi Dmitry! Could you specify where you find conflict? Because I don’t have any. пн, 9 апр. 2018 г. в 21:09, Dmitry Pavlov : > Hi Denis, > > could we support just one version instead of leaving compatible module? > > Sincerely, > Dmitriy Pavlov > > пн, 9 апр. 2018 г. в

Re: IGNITE-6879

There are 2 classes IgniteQueryGenerator with same package name. Ignite in Idea can't compile. пн, 9 апр. 2018 г., 21:38 Роман Меерсон : > Hi Dmitry! > Could you specify where you find conflict? Because I don’t have any. > пн, 9 апр. 2018 г. в 21:09, Dmitry Pavlov

Re: IGNITE-6827 - Review needed.

> Pavel Tupitsyn, what about .NET stuff ? 1) Thank you for filing the ticket, personally I have no plans to work on it in the near future. 2) .NET tests fail, please make sure they are fixed before merging: https://ci.ignite.apache.org/viewLog.html?buildId=1175956 TransactionsParityTest should

[jira] [Created] (IGNITE-8197) ignite won't start with spring-boot 1.5.11 - h2 property NESTED_JOINS doesn't exist

Scott Feldstein created IGNITE-8197: --- Summary: ignite won't start with spring-boot 1.5.11 - h2 property NESTED_JOINS doesn't exist Key: IGNITE-8197 URL: https://issues.apache.org/jira/browse/IGNITE-8197

Re: Service grid redesign

Denis, I would encourage us to persist a service configuration in the meta store and have this capability enabled by default. That's essential for services started dynamically. Moreover, we support similar behavior for caches, indexes, and other DDL changes happened at runtime. -- Denis On Mon,

Re: Rebalancing - how to make it faster

Dmitry, I see no problems to use system property for cases you specified. Migration possibility is not a reason to change the API. пн, 9 апр. 2018 г., 20:18 Dmitry Pavlov : > Not sure I agree. I think feature toggle is best practice. > > Eventually we can remove related

Re: Atomic caches

On Mon, Apr 9, 2018 at 6:29 AM, Ilya Lantukh wrote: > Anton, > > Please do not use term "atomic cache" for system caches that hold internal > data for atomic data structures. This is very confusing. > > You are right, currently there is no logic that will validate cache >

affinityRun/Call in C++

Guys, Is there a way to run collocated compute job in C++? I can't find affinityRun and affinityCall method in C++ compute API, am I missing something? If we really don't have them, is there any particular reason for this and/or plans to add them? -Val

Re: Service grid redesign

Denis, EVT_CLASS_DEPLOYED should be fired every time a class is deployed or redeployed. If this doesn't happen in some cases, I believe this would be a bug. I don't think we need to add any new events. -Val On Mon, Apr 9, 2018 at 10:50 AM, Denis Magda wrote: > Denis, > > I

Re: Rebalancing - how to make it faster

The system property is a good choice, especially for experimental features. Anton, thanks for reminding about that. Once the feature will be about to graduate from the experimental state we might not need any API parameter at all if the functionality is enabled by default. -- Denis On Mon, Apr

Re: Service grid redesign

Val, Guess we're talking about other situations. I'm bringing up the case when a service was deployed dynamically and has to be brought up after a full cluster restart w/o user intervention. To achieve this we need to persist the service's configuration somewhere. -- Denis On Mon, Apr 9, 2018

Re: Service grid redesign

I was responding to another Denis :) Agree with you on your point though. -Val On Mon, Apr 9, 2018 at 2:48 PM, Denis Magda wrote: > Val, > > Guess we're talking about other situations. I'm bringing up the case when a > service was deployed dynamically and has to be brought

[jira] [Created] (IGNITE-8198) Document how to use username/password for REST and thin protocol connections

Prachi Garg created IGNITE-8198: --- Summary: Document how to use username/password for REST and thin protocol connections Key: IGNITE-8198 URL: https://issues.apache.org/jira/browse/IGNITE-8198 Project:

[jira] [Created] (IGNITE-8199) Make the Confirmation dialog a more clear

Pavel Konstantinov created IGNITE-8199: -- Summary: Make the Confirmation dialog a more clear Key: IGNITE-8199 URL: https://issues.apache.org/jira/browse/IGNITE-8199 Project: Ignite Issue

[jira] [Created] (IGNITE-8200) Web console: unexpected confirmation

Pavel Konstantinov created IGNITE-8200: -- Summary: Web console: unexpected confirmation Key: IGNITE-8200 URL: https://issues.apache.org/jira/browse/IGNITE-8200 Project: Ignite Issue

REST API and new authentication API

Igniters, Recently new authentication API was added. I added support for it on REST, but several problems appeared: 1) "=login" and "=pwd" should be used for credentials. May be we should use "=user" and " =pwd " instead? But this will lead to conflict with new authentication API: For example

[GitHub] ignite pull request #3783: IGNITE-7712 Fix for tests

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/3783 IGNITE-7712 Fix for tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7712v1 Alternatively you can

Re: IGNITE-6879

Ok, I'll check it, but I haven't face this problem. If I'll find same issue, what is the proper way? Renaming to something like Ignite2QueryGenerator or module removing? пн, 9 апр. 2018 г. в 23:40, Dmitry Pavlov : > There are 2 classes IgniteQueryGenerator with same package

Re: IEP-18: Transparent Data Encryption

Hello, Denis > Is it necessary to have CEP keys for every cache? With current design, It's necessary to have difference CEK for every encrypted cache. I don't this it's an issue because CEK should be generated automatically and stored internally in Ignite. Cluster administrator should manage

Re: Apache Ignite RPM packaging (Stage II)

To top new RPM architecture off, update to release process is introduced — [1] [2]. Both tasks (this one and IGNITE-7647) are ready for review and should be merged simultaneously. [1] https://issues.apache.org/jira/browse/IGNITE-8172 [2] https://github.com/apache/ignite-release/pull/1 >

[jira] [Created] (IGNITE-8192) Print out information on how many nodes left until auto-activation

Alexey Goncharuk created IGNITE-8192: Summary: Print out information on how many nodes left until auto-activation Key: IGNITE-8192 URL: https://issues.apache.org/jira/browse/IGNITE-8192 Project:

Re: IEP-18: Transparent Data Encryption

Hello, Vladimir. > 1) Why do you propose to store CEK in separate cache? All CEKs data should be available on all cluster nodes. We want to use system cache to get data synchronization feature "for free". > We consider storing any metadata in system caches as antipattern from our > previous

[GitHub] ignite pull request #3774: Ignite 7791

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

[jira] [Created] (IGNITE-8175) Missed CRC update in Lucene index.

Andrew Mashenkov created IGNITE-8175: Summary: Missed CRC update in Lucene index. Key: IGNITE-8175 URL: https://issues.apache.org/jira/browse/IGNITE-8175 Project: Ignite Issue Type: Bug

Re: Lucene CorruptIndexException (checksum failed) on GridLuceneIndex - suggested patch

Hi Andrey, I know you helped to migrate AI to newer Lucene version. Could you please take a look at the patch? Vladimir. On Fri, Apr 6, 2018 at 12:02 PM, Manu wrote: > Hi, > > GridLuceneOutputStream has a bug on copyBytes method and > GridLuceneInputStream on readBytes

Re: Lucene CorruptIndexException (checksum failed) on GridLuceneIndex - suggested patch

Hi Vladimir, Patch looks good. I'll try to make a test for the case described and prepare a PR. On Mon, Apr 9, 2018 at 11:58 AM, Vladimir Ozerov wrote: > Hi Andrey, > > I know you helped to migrate AI to newer Lucene version. Could you please > take a look at the patch? >

[jira] [Created] (IGNITE-8173) ignite.getOrCreateCache(cacheConfig).iterator() method works incorrect for replicated cache in case if some data node isn't in baseline

Andrey Aleksandrov created IGNITE-8173: -- Summary: ignite.getOrCreateCache(cacheConfig).iterator() method works incorrect for replicated cache in case if some data node isn't in baseline Key: IGNITE-8173 URL:

[jira] [Created] (IGNITE-8172) Update Apache Ignite's release scripts to match new RPM build and deploy architecture

Peter Ivanov created IGNITE-8172: Summary: Update Apache Ignite's release scripts to match new RPM build and deploy architecture Key: IGNITE-8172 URL: https://issues.apache.org/jira/browse/IGNITE-8172

Re: IEP-18: Transparent Data Encryption

Hi Nikolay, First of all thank you for excellent summary. Two-tiered key management is well respected technique and makes perfect sense to me. However, several questions regarding architecture arises: 1) Why do you propose to store CEK in separate cache? We consider storing any metadata in system

iep-6 metrics ticket review

Hi ,Igniters! Do we still need this ticket, about invoke metrics : [1] ? If yes, than could somebody review it ? If no, should we close this ticket ? [1] : https://issues.apache.org/jira/browse/IGNITE-6846 -- *Best Regards,* *Kuznetsov Aleksey*

[jira] [Created] (IGNITE-8174) Web console: Skip saving of cluster data

Vasiliy Sisko created IGNITE-8174: - Summary: Web console: Skip saving of cluster data Key: IGNITE-8174 URL: https://issues.apache.org/jira/browse/IGNITE-8174 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #3683: IGNITE-7904: Changed IgniteUtils::cast not to tri...

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

[jira] [Created] (IGNITE-8181) Broken javadoc in GA Grid

Yury Babak created IGNITE-8181: -- Summary: Broken javadoc in GA Grid Key: IGNITE-8181 URL: https://issues.apache.org/jira/browse/IGNITE-8181 Project: Ignite Issue Type: Bug Components:

Re: Upsource update required

Hi All Upsource server (https://reviews.ignite.apache.org) has been upgraded to build 2017.3.2888 -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-8182) ZookeeperDiscoverySpiTest#testRandomTopologyChanges_RestartZk fails on TC

Sergey Chugunov created IGNITE-8182: --- Summary: ZookeeperDiscoverySpiTest#testRandomTopologyChanges_RestartZk fails on TC Key: IGNITE-8182 URL: https://issues.apache.org/jira/browse/IGNITE-8182

[jira] [Created] (IGNITE-8176) Integrate gradient descent linear regression with partition based dataset

Anton Dmitriev created IGNITE-8176: -- Summary: Integrate gradient descent linear regression with partition based dataset Key: IGNITE-8176 URL: https://issues.apache.org/jira/browse/IGNITE-8176

[jira] [Created] (IGNITE-8177) Reduce weight of error messages like "Failed completing transaction" in log files.

Oleg Ostanin created IGNITE-8177: Summary: Reduce weight of error messages like "Failed completing transaction" in log files. Key: IGNITE-8177 URL: https://issues.apache.org/jira/browse/IGNITE-8177

[jira] [Created] (IGNITE-8178) ZookeeperDiscoverySpiTest#testReconnectServersRestart* tests fail on TC

Sergey Chugunov created IGNITE-8178: --- Summary: ZookeeperDiscoverySpiTest#testReconnectServersRestart* tests fail on TC Key: IGNITE-8178 URL: https://issues.apache.org/jira/browse/IGNITE-8178

[jira] [Created] (IGNITE-8180) ZookeeperDiscoverySpiTest#testQuorumRestore fails on TC

Sergey Chugunov created IGNITE-8180: --- Summary: ZookeeperDiscoverySpiTest#testQuorumRestore fails on TC Key: IGNITE-8180 URL: https://issues.apache.org/jira/browse/IGNITE-8180 Project: Ignite

[GitHub] ignite pull request #3737: IGNITE-7944 Disconnected client node tries to sen...

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

[jira] [Created] (IGNITE-8179) ZookeeperDiscoverySpiTest#testCommunicationFailureResolve_KillRandom always fails on TC

Sergey Chugunov created IGNITE-8179: --- Summary: ZookeeperDiscoverySpiTest#testCommunicationFailureResolve_KillRandom always fails on TC Key: IGNITE-8179 URL: https://issues.apache.org/jira/browse/IGNITE-8179

Contributor permissions

Dear Ignite community Could you please provide me a contributor permissions? My Jira account: ytabira Thanks, Yoko.

[jira] [Created] (IGNITE-8183) ZookeeperDiscoverySpiTest#testSegmentation3 fails on TC and locally

Sergey Chugunov created IGNITE-8183: --- Summary: ZookeeperDiscoverySpiTest#testSegmentation3 fails on TC and locally Key: IGNITE-8183 URL: https://issues.apache.org/jira/browse/IGNITE-8183 Project:

[GitHub] ignite pull request #3772: Ignite 1.9.12

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

[GitHub] ignite pull request #3777: Fix CRC calculation in Lucene index.

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/3777 Fix CRC calculation in Lucene index. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8175 Alternatively you

[GitHub] ignite pull request #3776: IGNITE-8181: Broken javadoc in GA Grid

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

[jira] [Created] (IGNITE-8184) ZookeeperDiscoverySpiTest#testTopologyChangeMultithreaded_RestartZk* tests fail on TC

Sergey Chugunov created IGNITE-8184: --- Summary: ZookeeperDiscoverySpiTest#testTopologyChangeMultithreaded_RestartZk* tests fail on TC Key: IGNITE-8184 URL: https://issues.apache.org/jira/browse/IGNITE-8184

Re: IGNITE-6827 - Review needed.

Guys, After the review in Upsource the configuration parameter was renamed to txTimeoutOnPartMapSync, and it makes sense to me because PME is an implementation detail and it may change in future, partition map sync is a more abstract term. For the same reason I like this parameter being placed on

Re: IGNITE-6827 - Review needed.

On Mon, Apr 9, 2018 at 5:42 AM, Alexey Goncharuk wrote: > Guys, > > After the review in Upsource the configuration parameter was renamed > to txTimeoutOnPartMapSync, and it makes sense to me because PME is an > implementation detail and it may change in future,

Re: Lucene CorruptIndexException (checksum failed) on GridLuceneIndex - suggested patch

Guys, I've create a ticker for this [1]. Looks like crc update was really missed, but I can't reproduce the issue. I've tried different cases with no luck: putting\updating various large strings in single\multiple threads. [1] https://issues.apache.org/jira/browse/IGNITE-8175 On Mon, Apr 9,

Re: Atomic caches

I've attached .java file to https://issues.apache.org/jira/browse/IGNITE-2096 Atomic references created with cacheMode=REPLICATED configuration are being lost when first references are created with cacheMode=PARTITIONED, no validation errors. -- Sent from:

Re: Atomic caches

Anton, Please do not use term "atomic cache" for system caches that hold internal data for atomic data structures. This is very confusing. You are right, currently there is no logic that will validate cache configuration. It definitely should be fixed. And having configuration parameters encoded

[jira] [Created] (IGNITE-8185) There is deadlock when client tries to reconnect and node stop was initiated simultaneously

Eduard Shangareev created IGNITE-8185: - Summary: There is deadlock when client tries to reconnect and node stop was initiated simultaneously Key: IGNITE-8185 URL:

[GitHub] ignite pull request #3778: IGNITE-7918: memory leak was fixed. Unit test was...

GitHub user aealeksandrov opened a pull request: https://github.com/apache/ignite/pull/3778 IGNITE-7918: memory leak was fixed. Unit test was added. Some caches didn't take into account that topology minor version could be changed during creating/destroying of the caches

Re: Rebalancing - how to make it faster

Denis, Those ticket are rather complex, and so I don't know when I'll be able to start working on them. On Fri, Mar 30, 2018 at 11:45 PM, Denis Magda wrote: > Ilya, > > Just came across the IEP put together by you: > https://cwiki.apache.org/confluence/display/IGNITE/IEP- >

Re: Upsource update required

Hi Vitaliy, Thank you for your time and updating Upsource. It seems for PR branches with master merge into branch, Upsource still shows different changes with PR (github). Example https://reviews.ignite.apache.org/ignite/review/IGNT-CR-556 & https://github.com/apache/ignite/pull/3243 This

Re: Rebalancing - how to make it faster

Igniters, I am currently at the finish line of https://issues.apache.org/jira/browse/IGNITE-8017 ("Disable WAL during initial preloading") implementation. And I need that such behavior should be configurable. In my intermediate implementation I have parameter called "disableWalDuringRebalancing"

Re: IGNITE-6827 - Review needed.

I am not aware of any additional timeouts that we are willing to add in the nearest future. 2018-04-09 16:01 GMT+03:00 Dmitriy Setrakyan : > On Mon, Apr 9, 2018 at 5:42 AM, Alexey Goncharuk < > alexey.goncha...@gmail.com > > wrote: > > > Guys, > > > > After the review in

[GitHub] ignite pull request #3779: IGNITE-7791: fix CacheInfo initialization after c...

GitHub user Mmuzaf opened a pull request: https://github.com/apache/ignite/pull/3779 IGNITE-7791: fix CacheInfo initialization after client reconnect You can merge this pull request into a Git repository by running: $ git pull https://github.com/Mmuzaf/ignite ignite-7791_2