Re: Apache Ignite 2.5 release

Igniters, I would like to add this issue https://issues.apache.org/jira/browse/IGNITE-8405 to 2.5 scope. 2018-04-27 16:59 GMT+03:00 Eduard Shangareev : > Guys, > I have finished > ttps://issues.apache.org/jira/browse/IGNITE-7628. > > It looks like a good candidate to

Re: New committer: Ivan Rakov

Hi Ivan, Congratulations, you deserved it! 2018-05-10 19:08 GMT+03:00 Denis Magda : > The Project Management Committee (PMC) for Apache Ignite > has invited Ivan Rakov to become a committer and we are pleased > to announce that he has accepted. > > Being a committer enables

Re: supporting different configuration format json,yaml...

+1 to Dmitriy G. proposal. Since we're moving Ignite towards outside of Java world, we should definitely care about config usability for users who are not familiar with Java/Spring. If we take a look at any of our XML-configs, we can see a lot of boilerplate like "", "" - terms which say nothing

Re: supporting different configuration format json,yaml...

lo! > > > > Maybe we should take .Net configuration as a standard, extend it to JSON > > and YAML? > > > > > > https://apacheignite-net.readme.io/docs/configuration > > > > It should be fairly robust, and there's much less boilerplate. > > > > Regards

Re: work with files and directories

+1 to this approach, It can be also very helpful in failover scenarios when something wrong happened with disk. In this case we're reducing the number of points of failure. 2018-05-15 18:37 GMT+03:00 Dmitriy Govorukhin : > Hi Ignite, > > Do we have a general

Re: work with files and directories

/dashboard?id=org.apache. > ignite%3Aapache-ignite > > > [2] > > > > > > > > https://sonarcloud.io/component_measures?id=org. > apache.ignite%3Aapache-ignite=duplicated_blocks > > > [3] > > > > > > > > https://sonarcloud.io/com

Re: Ignite 2.6 emergency release suggestion

Igniters, Recently we noticed the issue when we don't completely persist some data on the disk: https://issues.apache.org/jira/browse/IGNITE-8780 . In some cases it can lead node to unrecoverable state. I think this problem should be included to release. ср, 13 июн. 2018 г. в 14:06, Alexey

Re: Ignite as distributed file storage

> based on HDFS API). It is not clear to me that you are talking about IGFS. > Can you confirm? > > D. > > > On Sat, Jun 30, 2018 at 10:59 AM, Pavel Kovalenko > wrote: > > > Dmitriy, > > > > Yes, I have approximate design in my mind. The main idea is tha

Introduce a sample of activation policy when cluster is activated first time

Igniters, By the results of the recent Ignite meeting at St. Petersburg I've noticed that some of our users getting stuck with the problem when a cluster is activated the first time. At the moment we have only manual options to do it (control.sh, Visor, etc.), but it's not enough. Manual

Re: Ignite contibutors page

Igniters, I've just noticed that I also not mentioned in Contributors table. вт, 26 июн. 2018 г. в 12:11, Anton Vinogradov : > Denis, could you please also fix Committers table? > Seems it was broken on last append. > > пн, 25 июн. 2018 г. в 22:18, Denis Magda : > > > Done, thanks for your

Re: Ignite contibutors page

; > > > > > > > вт, 26 июн. 2018 г. в 15:20, Denis Magda : > > > > > > > > > > > Only static code is allowed on the site. The downloads' code > > snippets > > > > are > > > > > > prepared and enabled by

Re: Automatic Handling of Long Stop-the-World Pauses

Denis, I think, JVM can't easily help to itself if it's in SW pause. Most solutions what I saw about handling such situations are checking heartbeats on other nodes or run in parallel supervisor process which can detect that JVM with Ignite in SW. 2018-07-02 20:54 GMT+03:00 Denis Magda : >

Re: Ignite as distributed file storage

information about how it should look. сб, 30 июн. 2018 г. в 19:40, Dmitriy Setrakyan : > Pavel, it definitely makes sense. Do you have a design in mind? > > D. > > On Sat, Jun 30, 2018, 07:24 Pavel Kovalenko wrote: > > > Igniters, > > > > I would like to start a disc

Ignite as distributed file storage

Igniters, I would like to start a discussion about designing a new feature because I think it's time to start making steps towards it. I noticed, that some of our users have tried to store large homogenous entries (> 1, 10, 100 Mb/Gb/Tb) to our caches, but without big success. IGFS project has

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

This failure is known and happened because of missed maxSize of DataRegion. All such problems will be fixed in https://issues.apache.org/jira/browse/IGNITE-9157 2018-08-01 18:12 GMT+03:00 : > Hi Ignite Developer, > > I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. > I

Re: Ignite as distributed file storage

GMT+03:00 Dmitriy Setrakyan : > On Thu, Aug 2, 2018 at 1:08 AM, Pavel Kovalenko > wrote: > > > Dmitriy, > > > > I still don't understand why do you think that it will be file system? > > In all my previous messages I emphasized that this storage shouldn't be > &g

Re: Exchange stucks while node restoring state from WAL

Hello Maxim, 1) Yes, Discovery Manager is starting after GridCacheProcessor, which starts GridCacheDatabaseSharedManager which invokes readMetastorage on start. 2) Before we complete the local join future, we create and add Exchange future on local node join to ExchangeManager. So, when local

Re: IP finder in tests

Hi Denis, I also definitely support this change. As an engineer who tightly working with MakeTeamCityGreenAgain activity, I notice several test suites hanging related with MulticastIpFinder infinite loops on datagram receiving. Here is last recorded fail -

Re: Ignite as distributed file storage

ple batches to be able to > > transfer it over the network faster. > > > > D. > > > > > > On Fri, Aug 3, 2018 at 3:21 AM, Pavel Kovalenko > > wrote: > > > > > Dmitriy, > > > > > > I think we don't need a separate implement

Re: [Distributed SQL] Do we have a plan to implement QuadTree index?

Hello Alexey, It's not so difficult to implement new type of indexing of data, but if you want to reach performance in distributed environment you need to have strong knowledge of a data you're indexing and what kind of queries you want to execute. Should be this index in-memory only or you want

Re: IP finder in tests

Hi Yakov, Currently TC agents defended by Docker virtual network, that's why we don't see intersection between several clusters, but in case of any step aside (running several suites on one agent, running several tests on one machine and so on) we will have problems and return back to this

Re: Ignite as distributed file storage

; > 3) Just drop IGFS from the product, and do not implement any > replacement > > at > > > all - personally, I am all for this decision. > > > > > > If you want I can guide you through IGFS architecture so that we better > > > understand what should be done t

Re: Deprecating LOCAL cache

directly supported and they shouldn’t expect too much of it. > That’s a drawback of the existing LOCAL cache – it appears as a > well-supported use case in the API, but if one actually tries to use it > they’ll see lower performance and more awkward behavior than what they > could expect. >

Re: Deprecate force server mode for clients.

Andrey, Huge +1 for that. "Force server mode" increases the complexity of understanding how cluster in ring mode works without real benefits. If a user wants to start client node first before server nodes have started, he can adjust timeouts on connection and spin till a client is connected.

Re: Benchmarking

Igniters, I would like to add that it would be very nice to have prepared scenarios in packed docker images with docker-compose, to easily deploy and run it on AWS environment. This will give the possibility to benchmark any changes independently and fastly. 2018-08-09 18:51 GMT+03:00 Anton

Re: Exchange stucks while node restoring state from WAL

of these cases, you need just local available CacheDescriptors to restore binary state from WAL. I would like also see a test when Ignite is stopped in the middle of a checkpoint and binary recovery succeed before PME in that case also. ср, 22 авг. 2018 г. в 15:31, Pavel Kovalenko : > Hello Maxim, > &

Re: Exchange stucks while node restoring state from WAL

issed > - fix abbreviations regarding IdeaAbbrPlugin > - createDataRegionConfiguration method can be removed and simplified > - startMemoryPolicies rename to startDataRegion > - output messages format fix code style needed > - fix format javadoc's > - make inner classes private > -

Re: Storage Class Memory and Persistent Collections

Hello Steve, I've looked at Persistent Collectors library, but don't see any big advantages to use it inside Ignite right now. Why do you think, that marshalling/unmarshalling process will be speeded up with this library? As I can see there are no explicit changes in serialization process, just

Re: Deprecating LOCAL cache

It's not easy to just make such caches as PARTITIONED with NodeFilter. Even in the case when a node is not affinity node for this cache we create entities like GridClientPartitionTopology for such caches on all nodes. These caches participate in the exchange, calculate affinity, etc. on all nodes.

Re: New PMC member: Dmitriy Pavlov

Dmitriy, Congratulations. This is very nice to see such valuable community member in PMC role. чт, 30 авг. 2018 г. в 20:11, Dmitriy Govorukhin < dmitriy.govoruk...@gmail.com>: > Dmitriy, > > My congratulations! > Thank you for your work! > > On Thu, Aug 30, 2018 at 1:58 PM Maxim Muzafarov >

Re: New committer: Dmitriy Govorukhin

Dmitriy, Congratulations, you finally got it :) чт, 30 авг. 2018 г. в 20:25, Ivan Rakov : > Dmitriy, > > Congratulations! Your new role is well deserved, keep going! > > Best Regards, > Ivan Rakov > > On 30.08.2018 1:20, Dmitriy Setrakyan wrote: > > Dmitriy, congrats! Looking forward to many

Re: Ignite as distributed file storage

> > > > > > I suggest that we create an IEP about this use case alone and leave the > > > file system for the future discussions. > > > > > > D. > > > > > > On Mon, Jul 2, 2018 at 6:50 AM, Vladimir Ozerov > > > wrote: > > > &g

Re: Ignite as distributed file storage

n with IGFS? > > Even if we agree that mmap usage is a critical piece, all we need is to > implement a single IGFS interface. > > On Thu, Jul 5, 2018 at 10:44 PM Pavel Kovalenko > wrote: > > > Vladimir, > > > > The key difference between BLOB storage and IGF

Re: Ignite as distributed file storage

0:47 GMT+03:00 Pavel Kovalenko : > Vladimir, > > I didn't say that it stores data in on-heap, I said that it performs a lot > of operations with byte[] arrays in on-heap as I see in , which will lead > to frequent GCs and unnecessary data copying. > "But the whole idea

Re: MTCGA: JVM crash in .NET tests - IGNITE-7871

=buildResultsDiv=IgniteTests24Java8_IgnitePlatformNetCoreLinux 2018-04-11 17:17 GMT+03:00 Pavel Tupitsyn <ptupit...@apache.org>: > Igniters, > > There is JVM crash in .NET Core Linux tests [1] after IGNITE-7871 merge > [2]. > > Pavel Kovalenko, Alexey Goncharuk, please have

Re: Triggering rebalancing on timeout or manually if the baseline topology is not reassembled

Denis, In case of incomplete baseline topology IgniteCache.rebalance() will do nothing, because this event doesn't trigger partitions exchange or affinity change, so states of existing partitions are hold. 2018-04-11 22:27 GMT+03:00 Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Denis,

Re: Triggering rebalancing on timeout or manually if the baseline topology is not reassembled

Denis, It's just one of the ways to implement it. We also can subscribe on node join / fail events to properly track downtime of a node. 2018-04-12 19:38 GMT+03:00 Pavel Kovalenko <jokse...@gmail.com>: > Denis, > > Using our API we can implement this task as follows: > Do eac

Re: Triggering rebalancing on timeout or manually if the baseline topology is not reassembled

1 > minute. What would you do and what Ignite provides to fulfill the task? > > -- > Denis > > On Wed, Apr 11, 2018 at 1:01 PM, Pavel Kovalenko <jokse...@gmail.com> > wrote: > > > Denis, > > > > In case of incomplete baseline topology IgniteCache.

Re: Triggering rebalancing on timeout or manually if the baseline topology is not reassembled

Pavel! >> >> Alexey, Ivan, could you check that there are no any pitfalls in the >> example >> and it can be used as a template for our users? >> https://issues.apache.org/jira/secure/attachment/12919452/ >> BaselineWatcher.java >> >> -- >

Re: Deprecate CacheRebalanceMode.NONE

+1 I also agree to remove this option in 3.0 2018-04-17 19:00 GMT+03:00 Yakov Zhdanov : > +1 here > > Always wanted to remove ForceKeysRequest =) > > --Yakov >

Re: Triggering rebalancing on timeout or manually if the baseline topology is not reassembled

ybe this option should be provided also on per-cache-group level). > > Policy can also specify conditions for including new nodes in BLT if they > > are present - including node attributes filters and so on. > > > > What do you think? > > > > Best Regards, > > Ivan Rakov

Re: Apache Ignite 2.5 release

Igniters, I've found blocker issue https://issues.apache.org/jira/browse/IGNITE-8390 Cause of the problem is incorrect assertion that could be fixed very quickly. I would like to add this issue to 2.5 release. 2018-04-25 17:38 GMT+03:00 Andrey Gura : > Igniters, > > We have

2 phase waiting for partitions release

Hello Igniters, Current implementation of GridDhtPartitionsExchangeFuture#waitPartitionRelease function doesn't give us 100% guarantees that after this method completes there are no ongoing atomic or transactional updates on current node during main stage of PME. It gives us only guarantee that

Re: Abbreviation code-style requirement.

Eduard, +1 for that topic. I don't see any reasons to use these abbreviations at all and vote to deprecate them. If anybody can explain why we still need them (less number of letters in variable names is not an argument) we can discuss and revisit the current list. >From my side of view, these

Re: How to run TDE tests locally?

Nikolay, JDK 1.8.0_151-b12 пн, 29 окт. 2018 г. в 15:31, Nikolay Izhikov : > Hello, Pavel. > > What jdk version do you use? > > В Пн, 29/10/2018 в 15:30 +0300, Pavel Kovalenko пишет: > > Hello Igniters, > > > > I have a problem with running TDE tests on my local

Re: Clean up of our PRs and IEPs before 2019

+1 When I just joined the project I was really confused with the huge number of opened PRs with poor description and cryptic reason. This can give to newcomers a weird representation of what is actually happening in the project. Don't be lazy, just spend 5-10 minutes of free time and clean up

Re: GridDhtInvalidPartitionException takes the cluster down

Hi Roman, I think this InvalidPartition case can be simply handled in GridCacheTtlManager.expire method. For workaround a custom FailureHandler can be configured that will not stop a node in case of such exception is thrown. пн, 25 мар. 2019 г. в 08:38, Roman Shtykh : > Igniters, > > Restarting

Re: Lightweight version of partitions map exchange

Hi Nikita, Thank you for your work. This is great improvement. I'll take look on it in next couple of days. Could you please run TC and provide MTCGA bot status about this change? чт, 28 мар. 2019 г. в 14:29, Nikita Amelchev : > Hello, Igniters! > > I have implemented lightweight version of

Re: [Discussion] Persistence compatibility framework refactoring

> tests. > > What do you think? > > > > ср, 20 февр. 2019 г. в 11:41, Pavel Kovalenko : > > > Vyacheslav, > > > > Thank you for answers! > > > > >> I'm not sure what is a problem here? > > At the moment it's a little bit hard to unders

[Discussion] Persistence compatibility framework refactoring

Igniters, I would like to start a discussion about replacement existing persistence compatibility test framework with the newer version. The main purpose of that action is simplifying compatibility tests development and support. The current version of the test framework has 3 disadvantages: 1)

Re: [Discussion] Persistence compatibility framework refactoring

moval or updates. > > >> Each new version is represented by a single pom > Sound not good. > Could you please share examples for each feature you mentioned? > > Anyway. I don't like the idea to implement something new instead of > improving the existing. > > On Tue

Re: [Discussion] Persistence compatibility framework refactoring

; 3) It doesn't cover the case when some code which works on the current > version will not work on older versions due to compile/runtime > incompatibility. > > Please, describe the issue in more details? > > On Tue, Feb 19, 2019 at 7:55 PM Pavel Kovalenko > wrote: > >

Re: [DISCUSSION] Ignite 3.0 and to be removed list

I would like to add to the list following: 1. Remove ForceKeyRequests and related code. Since we have Late affinity assignment and primary node partitions are always up to date we don't need to request actual data from backups. 2. Remove @CentralizedAffinityFunction and related code. I don't see

Re: Update Apache Zookeeper dependency

Hi Dmitrii, Thank you for contribution. I'll take a look at it. Could you please describe in the ticket what changes have you done besides version update and why they are needed? ср, 11 сент. 2019 г. в 14:06, Dmitrii Ryabov : > Hello, Igniters! > > I want to update Apachee Zookeeper version

Re: Deprecate\remove REBALANCE_OBJECT_LOADED cache event

Hello Maxim, Thank you for researching this. It seems those events can be used as an interceptor for the rebalance process to make some extra actions after the entry is rebalanced. However, I don't see any real usages despite tests. Most likely functionality that used such rebalance events no

Re: Replacing NodeFilter functionality with label approach

r forgot to implement > .equals() > > or did it incorrectly we can't deal anything with it. > > All of those problems can lead to cluster instability and unpredictable > > behavior. > > This is common issue to every user-provided code. > Wrong implementation of affininty function is o

Re: Replacing NodeFilter functionality with label approach

Nikolay, Thank you for your feedback. Could you please tell more about cases when custom node filter that not relies on node attributes may be used? For me, it's flexibility just for flexibility that introduces problems described in the topic. I don't see yet any practical cases with NodeFilter

Re: Coding guidelines. Useless JavaDoc comments.

I can agree that some part of javadocs we have is useless. It relates to DTOs, getters/setters without side-effects, short self-descriptive methods. In an ideal world, proper modularization of architecture, leading to KISS/SOLID/DRY/etc. principles, writing self-documented code should result in

Replacing NodeFilter functionality with label approach

Hello Igniters, I would like to start a discussion about simplifying NodeFilter functionality. At the moment NodeFilter's are used to control Caches and Services distribution across nodes. In most cases, NodeFIlter implementation seeks for a specific attribute in NodeAttributes map. If the

Re: Replacing NodeFilter functionality with label approach

Ivan, > And there is also one idea (I am not fan of it but still). Can we use > some kind of scripting for nodes filtering? In that case node filter > is represented by script string, e.g. javascript. I guess it can lead to the same situation as in Java NodeFilter's. We can't control what

Re: Partition map exchange metrics

> > > > What's the reason for duration counting? > > > > AFAIU, it's a monitoring system feature to count the durations. > > > > Sine monitoring system checks metrics periodically it will know the > > > > duration by its own log. > > >

Re: Partition map exchange metrics

Hi Nikita, Thank you for working on this. What do you think if we change the boolean value of metric to a long value that represents time in milliseconds when operations were blocked? Since we have not only JMX and now metrics are periodically exported to some backend it can give a more clear

Re: [DISCUSSION] Remove preload predicate in GridCachePreloader

Maxim, Go ahead. I don't see any real usages of this functionality and seems it obsolete and should be removed. пт, 19 июл. 2019 г. в 08:36, Anton Vinogradov : > Folks, > > To be clear, I'm going to merge the PR next Monday in case of interest lack > (which means the feature is obsolete and can

Re: Partition map exchange metrics

released yet). Seems for users it > useless in case of non-blocking PME. > Lets name it timeSinceOperationsBlocked. It'll be timestamp when > blocking started (minimal value of cluster nodes) and 0 if blocking > ends (there is no running PME). > > WDYT? > > пт, 19 ию

Re: Partition map exchange metrics

CurrentBlockingPmeDuration. But I haven't come up with a better > name yet. > > пт, 19 июл. 2019 г. в 18:30, Pavel Kovalenko : > > > > Nikita, > > > > I think getCurrentPmeDuration doesn't show useful information. The main > PME side effect for end-users i

Re: Partition map exchange metrics

cheOperationsBlockedDuration` - histogram of blocking PME durations. > > В Чт, 25/07/2019 в 22:40 +0300, Pavel Kovalenko пишет: > > Nikolay, > > > > Okay, sounds reasonable. > > I just want to add that currentPmeTime is also useful alerting systems, > not > > only

Re: Partition map exchange metrics

then 1000, more then > 1000] millis. > > чт, 25 июля 2019 г., 18:55 Pavel Kovalenko : > > > Nikolay, > > > > Could you please explain deeper what structure will be of PME histogram? > > > > чт, 25 июл. 2019 г. в 11:56, Nikolay I

Re: Partition map exchange metrics

ates and translations on a previous topology. > > > > > > > > > > > > 5. sendSingleMessageTime. Time when a node sent a > single message. > > > > > > > > > > > > 6. recieveFullMessageTime. Time when a node received > a full message. > > > > >

Re: Partition map exchange metrics

, Nikolay Izhikov wrote: > I think exact time should be obtained from logs, isnt it? > > > чт, 25 июля 2019 г., 20:00 Pavel Kovalenko : > > > Nikolay, > > > > Yes, I have a chance to see HistogramMetric and moreover reviewed it) My > > question was mostly about

Re: Re[2]: [VOTE] Apache Ignite PMC Chair

+1 for Dmitry Pavlov ср, 30 окт. 2019 г. в 18:46, Alexei Scherbakov : > +1 for Dmitry Pavlov > > ср, 30 окт. 2019 г. в 18:22, aealexsandrov : > > > +1 Alexey Goncharuk > > > > > > > > -- > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ > > > > > -- > > Best regards, > Alexei

Re: [ANNOUNCE] New committer: Aleksei Scherbakov

Aleksei, Congratulations! You definitely deserve it. пн, 16 дек. 2019 г. в 14:42, Ivan Pavlukhin : > Aleksei, my congratulations! > > сб, 14 дек. 2019 г. в 10:50, Zhenya Stanilovsky >: > > > > Big deal and huge responsibility. > > > > Congrats Aleksei! > > > > > Hello Ignite Community, > > > >

Re: Unclear to use methods in the DiscoverySpiCustomMessage interface

Hi Nikita, 1. As I can understand, this functionality is needed if a custom message is needed to be processed only on the coordinator node. I'm not following for what purposes it was implemented and I see the real usage only in tests. As far as this functionality is not used in production code, I

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

Issues link is broken, because it has a filter that can't be found. Here is correct link:

Re: Review needed for IGNITE-11410 Sandbox for user-defined code

Denis, The idea of having a sandbox for running a user-defined code is useful, but I don't fully understand the implementation approach. There is no detailed description of the ticket about what public API methods or configuration parameters should be covered. There is no description of what have

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

Anton, Slava I guess we should have a system property to have ability to turn off PME free switch behavior if something goes wrong after release. After feature battle testing we can remove it in the next release. чт, 19 дек. 2019 г. в 15:26, Anton Vinogradov : > Slava, > > >> It would be nice

Re: [ANNOUNCE] New committer: Vyacheslav Koptilin

Congratulations, Slava! Don't let the bad code occupy master :) вт, 18 февр. 2020 г. в 22:20, Dmitriy Pavlov : > Hello Ignite Community, > > The Project Management Committee (PMC) for Apache Ignite has invited > Vyacheslav Koptilin to become a committer and we are pleased to announce > that he

Re: [ANNOUNCE] New committer: Vyacheslav Koptilin

Congratulations Slava! On Tue 18. Feb 2020 at 22.20, Dmitriy Pavlov wrote: > Hello Ignite Community, > > The Project Management Committee (PMC) for Apache Ignite has invited > Vyacheslav Koptilin to become a committer and we are pleased to announce > that he has accepted. > > Vyacheslav

Re: [DISCUSSION] IEP-59: CDC - Capture Data Change

Alexey, >> If a CDC agent is restarted, it will have to start from scratch >> If a CDC reader does not keep up with the WAL write rate (e.g. there is a short-term write burst and WAL archive is small), the Ignite node will delete WAL segments while the consumer is still reading it. I think

Re: [DISCUSSION] IEP-59: CDC - Capture Data Change

This tool is also can be used to store snapshots in an external warehouse. ср, 14 окт. 2020 г. в 14:57, Pavel Kovalenko : > Hi Nikolay, > > The idea is good. But what do you think to integrate these ideas into > WAL-G project? > https://github.com/wal-g/wal-g > It's

Re: [DISCUSSION] IEP-59: CDC - Capture Data Change

Hi Nikolay, The idea is good. But what do you think to integrate these ideas into WAL-G project? https://github.com/wal-g/wal-g It's a well-known tool that is already used to stream WAL for PostgreSQL, MySQL, and MongoDB. The advantages are integration with S3, GCP, Azure out of the box,

Re: IEP-57: API to implement different storage engines, modularization

Hi Maksim, I think your proposal is very good and useful not only for introducing new types of storage engine but also it's a good trigger to rework the existing storage engine to decouple its components of each other. I have a key question that we should answer. Where we should place our

Re: New Committer: Sergey Chugunov

Nice job Sergey. You deserve it! On Fri 17. Jul 2020 at 20.46, Sergey Antonov wrote: > Congratulations, Sergey! > > сб, 18 июл. 2020 г., 0:24 Andrey Mashenkov : > > > Congratulations, Sergey. > > > > пт, 17 июл. 2020 г., 15:06 Вячеслав Коптилин : > > > > > Hi, > > > > > > Well deserved! Keep it

Re: [DISCUSSION] Java 11 for Ignite 3.0 development

Huge +1 I guess jigsaw, "var" and VarHandle features can really improve the codebase. чт, 10 дек. 2020 г. в 23:41, Vladimir Steshin : > My + for java 11 > > On 08.12.2020 15:00, Nikolay Izhikov wrote: > > +1 for using java 11. > > > >> 8 дек. 2020 г., в 13:18, ткаленко кирилл > написал(а): > >>

Re: [DISCUSSION] Code style. Variable abbrevations

I think in this discussion there should be a question - why do we still need abbreviations for all variables and fields? What problem does it solve? Nobody still clearly answered this question. I saw only 2 arguments to keep abbreviations: 1) Less codebase symbols. I think it is a weak argument.

Re: [DISCUSSION] Code style. Variable abbrevations

tributions. I contributed to other open source projects and did < > 10 commits to each. Because in daily work generally we use stable > libraries and can allow ourselves to work only with bugs or > improvements in open source libraries. And I consider it a way to go >

[jira] [Created] (IGNITE-5865) TxOptimisticDeadlockDetectionTest.testDeadlocksPartitioned is failing

Pavel Kovalenko created IGNITE-5865: --- Summary: TxOptimisticDeadlockDetectionTest.testDeadlocksPartitioned is failing Key: IGNITE-5865 URL: https://issues.apache.org/jira/browse/IGNITE-5865 Project

[jira] [Created] (IGNITE-6029) Refactor WAL Record serialization and introduce RecordV2Serializer

Pavel Kovalenko created IGNITE-6029: --- Summary: Refactor WAL Record serialization and introduce RecordV2Serializer Key: IGNITE-6029 URL: https://issues.apache.org/jira/browse/IGNITE-6029 Project

[jira] [Created] (IGNITE-5752) Fix stale sequence updates for local partition map

Pavel Kovalenko created IGNITE-5752: --- Summary: Fix stale sequence updates for local partition map Key: IGNITE-5752 URL: https://issues.apache.org/jira/browse/IGNITE-5752 Project: Ignite

[jira] [Created] (IGNITE-5729) IgniteCacheProxy instances from "with..." methods are not reusable

Pavel Kovalenko created IGNITE-5729: --- Summary: IgniteCacheProxy instances from "with..." methods are not reusable Key: IGNITE-5729 URL: https://issues.apache.org/jira/browse/IGNITE-5729

[jira] [Created] (IGNITE-5829) Writing entry contents only single time

Pavel Kovalenko created IGNITE-5829: --- Summary: Writing entry contents only single time Key: IGNITE-5829 URL: https://issues.apache.org/jira/browse/IGNITE-5829 Project: Ignite Issue Type

[jira] [Created] (IGNITE-5830) Introduce cache start & stop order on cluster activation

Pavel Kovalenko created IGNITE-5830: --- Summary: Introduce cache start & stop order on cluster activation Key: IGNITE-5830 URL: https://issues.apache.org/jira/browse/IGNITE-5830 Project: Ig

[jira] [Created] (IGNITE-5692) IgnitePdsCacheRebalancingAbstractTest suite hangs on TC

Pavel Kovalenko created IGNITE-5692: --- Summary: IgnitePdsCacheRebalancingAbstractTest suite hangs on TC Key: IGNITE-5692 URL: https://issues.apache.org/jira/browse/IGNITE-5692 Project: Ignite

[jira] [Created] (IGNITE-6018) Introduce WAL backward compatibility for new DataPage insert/update records

Pavel Kovalenko created IGNITE-6018: --- Summary: Introduce WAL backward compatibility for new DataPage insert/update records Key: IGNITE-6018 URL: https://issues.apache.org/jira/browse/IGNITE-6018

[jira] [Created] (IGNITE-6017) Ignite IGFS: IgfsStreamsSelfTest#testCreateFileFragmented fails

Pavel Kovalenko created IGNITE-6017: --- Summary: Ignite IGFS: IgfsStreamsSelfTest#testCreateFileFragmented fails Key: IGNITE-6017 URL: https://issues.apache.org/jira/browse/IGNITE-6017 Project

[jira] [Created] (IGNITE-5958) Ignite Cache 3: IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidator fails

Pavel Kovalenko created IGNITE-5958: --- Summary: Ignite Cache 3: IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidator fails Key: IGNITE-5958 URL: https://issues.apache.org/jira/browse/IGNITE-5958

[jira] [Created] (IGNITE-5957) Ignite IGFS: IgfsStreamsSelfTest.testCreateFileColocated fails

Pavel Kovalenko created IGNITE-5957: --- Summary: Ignite IGFS: IgfsStreamsSelfTest.testCreateFileColocated fails Key: IGNITE-5957 URL: https://issues.apache.org/jira/browse/IGNITE-5957 Project: Ignite

[jira] [Created] (IGNITE-5959) Ignite Hadoop: testClientReconnect and testClientReconnectMultithreaded fail

Pavel Kovalenko created IGNITE-5959: --- Summary: Ignite Hadoop: testClientReconnect and testClientReconnectMultithreaded fail Key: IGNITE-5959 URL: https://issues.apache.org/jira/browse/IGNITE-5959

[jira] [Created] (IGNITE-5503) Affinity information for cache is not cleared after cache destroy

Pavel Kovalenko created IGNITE-5503: --- Summary: Affinity information for cache is not cleared after cache destroy Key: IGNITE-5503 URL: https://issues.apache.org/jira/browse/IGNITE-5503 Project

[jira] [Created] (IGNITE-5509) Test CacheLateAffinityAssignmentTest#testRandomOperations() is hanging

Pavel Kovalenko created IGNITE-5509: --- Summary: Test CacheLateAffinityAssignmentTest#testRandomOperations() is hanging Key: IGNITE-5509 URL: https://issues.apache.org/jira/browse/IGNITE-5509 Project

[jira] [Created] (IGNITE-8482) Skip 2-phase partition release wait in case of activation or dynamic caches start

Pavel Kovalenko created IGNITE-8482: --- Summary: Skip 2-phase partition release wait in case of activation or dynamic caches start Key: IGNITE-8482 URL: https://issues.apache.org/jira/browse/IGNITE-8482

  1   2   >