Request for contributor permissions

Hello Ignite Community! My name is Ivan Daschinskiy. I want to contribute to Apache Ignite and want to start with this issue - IGNITE-6860 , my JIRA username *ivandasch*. Any help on this will be appreciated. Thanks a lot! -- Sincerely yours,

Re: IGNITE-6827 - Review needed.

Hi all, I've implemented corresponded .NET api. Pavel, could you review my PR, please? https://issues.apache.org/jira/browse/IGNITE-8075 2018-04-10 21:06 GMT+03:00 Dmitry Pavlov : > Hi Pavel, > > thank you for bring up test questions. It seems my previous comments were

PR#3697 IGNITE-8021: Delete cache config files when destroyed

Hi Team, Could you review this PR https://github.com/apache/ignite/pull/3697 please? Tests result: https://ci.ignite.apache.org/viewLog.html?buildId=1159660 Jira ticket: https://issues.apache.org/jira/browse/IGNITE-8021 -- Sincerely yours, Ivan Daschinskiy

Re: Apache Ignite 2.7. Last Mile

Hi! Is it possible to merge IGNITE-9854? Fix is pretty simple, but quite important. ср, 17 окт. 2018 г. в 17:49, Andrey Gura : > JFYI > > IGNITE-9737 and IGNITE-9710 are merged to release branch. > On Wed, Oct 17, 2018 at 5:41 PM Pavel Tupitsyn > wrote: > > > > Thank you. Fix has been merged to

Re: Possible concurrency bug in GridCacheLockImpl

Sorry, I meant not GridCacheLockImpl but CacheLockImpl. пт, 3 апр. 2020 г. в 17:04, Ivan Daschinskiy : > Folks, > > Lurking through code, it seems I found some concurrency issue in subj. > > * This class contains two fields, volatile Thread lockedThread and > non-volatile int cntr (used for

Re: Why OPTIMIZE_REUSE_RESULT is set to 0 explicitly in o.a.i.i.p.query.h2.ConnectionManager#DEFAULT_DB_OPTIONS

Thank you for your response, Konstantin I think we cannot just turn this optimization > Of course not, that is the reason why I started this thread. org.apache.ignite.internal.processors.query.h2.opt.GridH2Table don't change > it neither on remove or update Yes, but we can increment this

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

Artem, in ignite 2.9 a way to build C++ for linux/mac os x was changed (autotools to cmake). As an author of this change, I want to contribute in documentation. As far as I understand, now it should be done through PR to specific repository. Could you please help me with this? пт, 28 авг. 2020 г.

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

It seems, that in this test we use MulticastIpFinder. I suppose, that it should be fixed. Excerpts from a failed test's log: [15-Oct-2020 02:47:10][WARN ][main][TcpDiscoveryMulticastIpFinder] TcpDiscoveryMulticastIpFinder has no pre-configured addresses (it is recommended in production to specify

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

lticastIpFinder, which can be problematic in > tests, > but it was fine for 5 years, and now got broken. > > Do you think this can be caused by the recent changes in GridNioServer? > > Pavel > > On Thu, Oct 15, 2020 at 9:41 AM Ivan Daschinsky > wrote: > > > It s

Sql consistency when partition evicts.

Hi! I found recently quite surprising on the first sight behaviour. Scenario: 1. Start 2 node with indexed atomic partitioned cache with 0 backups. 2. Load sufficient amout of data (or emulate slow removal from idx) 4. Start another node. 4. Perform SELECT * FROM . Due to partition eviction,

Re: [DISCUSS] Use Netty for Java thin client

Hi. >> Potentially reduced resource usage - share EventLoopGroop across all connections within one IgniteClient. Not potentially, definitely. Current approach (one receiver thread per TcpClientChannel and shared FJP for continuation) requires too many threads. When TcpClientChannel is the only

Re: [DISCUSS] Use Netty for Java thin client

ehanov : > Pavel, > > Why can't we use GridNioServer for java thin clients? > It has the same advantages as Netty (future based async API, SSL, etc) but > without extra dependency. > GridClient (control.sh), for example, uses GridNioServer for communication. > > сб,

Re: [DISCUSS] Missed (non-suited) tests

Ivan, as far as I understand, Max also created verification check for not included test and found a few tests, that have never been included in any testsuites. Also, I suppose, that even if we cannot run some tests, these tests should be ignored using annotation, but not commented. пн, 19 окт.

Re: IEP-52: Binary Delivery & Upgradability Enhancements

Hi! I recently found that in slim binary release (at least in nightly build of 2.9.0) there is no ignite-zookeeper module. But, for example, ignite-kubernetes is in. Petr, could you please clarify why this decision was made? We currently have only two discovery implementation in project and leave

Re: IEP-52: Binary Delivery & Upgradability Enhancements

zookeeper-2.8.1.jar > slf4j-api-1.7.7.jar > zookeeper-jute-3.5.5.jar > > ignite-zookeeper just has way more dependencies than ignite-kubernetes, and > their size is 5-fold. > > These dependencies are not just weight but also vulnerability surface. > > Regards, >

Re: IEP-52: Binary Delivery & Upgradability Enhancements

I mean, that we should fix this issue, not just throw away zookeeper discovery. чт, 17 сент. 2020 г. в 16:44, Ivan Daschinsky : > I suggested to move TcpDiscoveryZookeeperIpFinder to ignite-extension. > This tiny recipe-like class brings tons of dependency and has nothing &g

Re: [DISCUSSION] Ignite.C++ and CMake

: > Hello! > > I will assist with checking on Linux if you would contribute a patch. > Please start with a ticket (or even an IEP maybe?) > > Regards, > -- > Ilya Kasnacheev > > > вт, 26 мая 2020 г. в 16:47, Ivan Daschinsky : > > > Guys, I will certai

Re: [DISCUSSION] Ignite.C++ and CMake

Guys, I will certainly thoroughly test my fix not only unices, but on windows too. And I will describe it very thoroughly. When I was C++ developer (more than 10 years ago), I have not any trouble at all with CMake and Visual Studio 2005. Everything works and works good. Moreover, you can build

Re: [DISCUSSION] Ignite.C++ and CMake

Igor, I just said about native support from Visual Studio, not from cmake itself. Modern cmake can generate projects even for Visual Studio 2008 [1] [1] -- https://cmake.org/cmake/help/v3.16/generator/Visual%20Studio%209%202008.html вт, 26 мая 2020 г. в 16:16, Igor Sapego : > Nikolay, removing

Re: Prevent insertion of cache entry if the binary field type and the type of the query entity do not match.

I think this feature quite easy to implement. Before put in cache tree, we can iterate over query descriptor fields and check whether this field presents in binary object and if typeId is the same. But I think there can l be a quite noticeable performance penalty when this feature is enabled. It

Re: [DISCUSSION] Ignite.C++ and CMake

reports are welcomed! вт, 26 мая 2020 г. в 18:51, Ivan Daschinsky : > Stephen, looks great! I do mostly the same things in C++ code. Thank you! > > вт, 26 мая 2020 г. в 18:33, Stephen Darlington < > stephen.darling...@gridgain.com>: > >> Not sure if it’ll help, but

Re: Re[2]: [DISCUSSION] Ignite.C++ and CMake

e we should wait for Igor Sapego to check. > > > >Regards, > >-- > >Ilya Kasnacheev > > > > > >пт, 29 мая 2020 г. в 12:20, Ivan Daschinsky < ivanda...@gmail.com >: > > > >> Ilya, thanks a lot! What about tests? I found one flag that must b

Re: [DISCUSSION] Ignite.C++ and CMake

Also without with flag we can observe many failures of suites on TC https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformCLinux?branch=%3Cdefault%3E=builds#all-projects пт, 29 мая 2020 г. в 12:20, Ivan Daschinsky : > Ilya, thanks a lot! What about tests? I found one f

Re: [DISCUSSION] Ignite.C++ and CMake

ebug and release, without and with odbc, checked running thick > node and ODBC connection on Linux. > > Regards, > -- > Ilya Kasnacheev > > > чт, 28 мая 2020 г. в 17:31, Ivan Daschinsky : > > > Ok, PR is ready > > https://issues.apache.org/jira/browse/IGNITE-13078 &g

Re: [DISCUSSION] Ignite.C++ and CMake

e code worth taking. > > https://github.com/apache/ignite/pull/4872 < > https://github.com/apache/ignite/pull/4872> > > Regards, > Stephen > > > On 26 May 2020, at 16:02, Ivan Daschinsky wrote: > > > > I appreciate any help, thank you, Ilya. > > >

Re: [DISCUSSION] Add autocompletion for commands in control.sh

ive benchmark CLI, has ** Apache [Ignite TensorFlow] **, and Apache > Sling. > > > [1] https://github.com/remkop/picocli/blame/master/README.md#L199 > > On Tue, 2 Jun 2020 at 16:09, Ivan Daschinsky wrote: > > > > +1 But this is not only usability improvement, but also a

Re: [DISCUSSION] Add autocompletion for commands in control.sh

+1 But this is not only usability improvement, but also a huge code improvement. With picocli developers can add custom command without writing a lot of boilerplate and error prone code to do a trivial task of parsing CLI arguments. Cleaner code, less bugs also matter. вт, 2 июн. 2020 г. в 16:02,

Re: New Ignite Docs: Status and Incomplete Items

Hi! As we introduce CMake build system for Ignite C++ for Linux and Mac OS X and this improvement is in ignite 2.9, we should document it. (CMake for windows is not ready yet and will be in 2.10) I created ticket for it and assigned it to me. Patch will be available soon. [1] -

Re: Apache Ignite 3.0

ly in TLA+? [1] -- https://www.consul.io/docs/architecture/gossip [2] -- https://www.microsoft.com/en-us/research/wp-content/uploads/2008/02/tr-2008-25.pdf пт, 23 окт. 2020 г. в 13:05, Alexey Goncharuk : > Hello Ivan, > > Thanks for the feedback, see my comments inline: > > чт, 22 ок

Re: Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

I recently found, that control.sh is broken since 2.8.0 a little bit. Script returns always 0 code, despite the fact, that CommandHandler returns code correctly. Here is the issue https://issues.apache.org/jira/browse/IGNITE-13328, patch is available. пт, 31 июл. 2020 г. в 14:09, Alex Plehanov :

Re: [DISCUSSION] Ignite.C++ and CMake

Ok, CMake now is the only option to build C++ on non-windows platforms. Autotools is removed from master. Many thanks to Igor Sapego, Zhenya Stanilovsky, Nickolay Izhikov and Ilya Kasnacheev for review, testing and suggestions. вт, 23 июн. 2020 г. в 18:42, Ivan Daschinsky : > I supp

Re: Re[2]: IGNITE-6499 Compact NULL fields

rd party clients too), we can't release a minor > version which will change this format unilaterally without any change of > operation (same data, same calls, different result after upgrade, broken > clients). > > Regards, > -- > Ilya Kasnacheev > > > ср, 8 июл. 2020

Re: Re[2]: IGNITE-6499 Compact NULL fields

Hi! Ilya, unfortunatelly yes, subsequent changes should be made in C++, .NET and other platform code. ср, 8 июл. 2020 г. в 12:22, Ilya Kasnacheev : > Hello fellow devs, > > I just wanted to ask, how would this Binary Object format change affect > thin clients? C++/.Net nodes? Etc? > > Is it

Re: Checkstyle fails Build Apache Ignite - can we split it?

I think, that we should enable checkstyle profile by default. Checkstyle should run even before compile lifecycle, may be on process-source. Codestyle problem should be handled immediately, but not on quite expensive TC run. пн, 6 июл. 2020 г. в 20:34, Maxim Muzafarov : > Hello Ilya, > > Why do

Re: [DISCUSSION] Ignite.C++ and CMake

itignore accordingly? > > > Thanks, > Pavel > > > On Tue, Jun 30, 2020 at 9:33 PM Ivan Daschinsky > wrote: > > > Ok, CMake now is the only option to build C++ on non-windows platforms. > > Autotools is removed from master. > > > > Many thanks to Igor S

Re: [DISCUSSION] Ignite.C++ and CMake

at all. For example, we don't explain basics of maven, though it is not obvious at all as it seems to us, Ignite developers. ср, 1 июл. 2020 г. в 06:18, Ivan Daschinsky : > Pavel, pay attention to two dots at the end. All build files should stay > at current dir, and cmake-build-r

Re: [DISCUSSION] Ignite.C++ and CMake

Tupitsyn : > Ivan, > > Thank you for such a detailed explanation! > I am sorry if I upset you. > > I just wanted to make sure that instructions are correct, > and I simply missed those 2 dots. Now it all works perfectly. > > Pavel > > On Wed, Jul 1, 2020 at

Re: [DISCUSSION] Ignite.C++ and CMake

buildTypeStatusDiv > > пн, 22 июн. 2020 г. в 12:03, Ilya Kasnacheev : > >> Hello! >> >> I think you should contact Peter Ivanov if you want anything to be >> installed on agents. >> >> Regards, >> -- >> Ilya Kasnacheev >> >> >

Re: [DISCUSSION] Ignite.C++ and CMake

1 июня 2020 г., в 13:21, Ivan Daschinsky > написал(а): > > > > Igor, could you please check my PR? > > > > пт, 29 мая 2020 г. в 15:28, Ivan Daschinsky : > > > >> Thanks you all. Run patch (I've changed some code also) on TC -- all CPP > >> suit

MTCGA spam about BinaryConfigurationTest in .NET Core suite

Hi folks! It seems, that this test mysteriously fails only on one agent aitc-lin01_04 with this error. [1] Locally this .NET Core tests doesn't fail for about 20 minutes of continuously run (Mac OS X 10.15, .NET Core 3.1.200) According to stacktrace, it seems that there is problem with build

Re: [DISCUSSION] Ignite.C++ and CMake

Ok, I changed agents requirements to builds and add them to runAll пн, 22 июн. 2020 г. в 22:39, Petr Ivanov : > Cmake is installed on all agents (except 10 which is currently down and > will be updated later). > > > > On 22 Jun 2020, at 21:03, Ivan Daschinsky wrote: &

Re: [DISCUSSION] Ignite.C++ and CMake

Daschinsky : > Ok, I changed agents requirements to builds and add them to runAll > > пн, 22 июн. 2020 г. в 22:39, Petr Ivanov : > >> Cmake is installed on all agents (except 10 which is currently down and >> will be updated later). >> >> >> > On

Re: [DISCUSSION] Ignite.C++ and CMake

, Nikolay Izhikov wrote: > > > >> So, folks, is it ok to remove old suites from build chain > > > > +1 from me. > > > > > >> 23 июня 2020 г., в 13:15, Ivan Daschinsky > написал(а): > >> > >> Well, new suites added to RunAll and all se

Re: [DISCUSSION] Ignite.C++ and CMake

Petr, I see, that cmake is missing on aitc10_05 but it is in pool and trying to run build. [1] -- https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformCPPCMakeLinux/5412025 вт, 23 июн. 2020 г. в 17:33, Ivan Daschinsky : > >> For the sake of discretion, I'

Re: [DISCUSSION] Ignite.C++ and CMake

he future we may choose to > remove autotools support entirely. > > Regards, > -- > Ilya Kasnacheev > > > вт, 23 июн. 2020 г. в 18:00, Petr Ivanov : > > > That host was down for some time and got up only recently. > > Installed cmake there also. > > >

Re: [DISCUSSION] Ignite.C++ and CMake

Kasnacheev : > Hello! > > I think you should contact Peter Ivanov if you want anything to be > installed on agents. > > Regards, > -- > Ilya Kasnacheev > > > пн, 22 июн. 2020 г. в 12:00, Ivan Daschinsky : > > > Actually, I'm going to create 2 new suites based o

Re: MTCGA spam about BinaryConfigurationTest in .NET Core suite

1] > > https://github.com/apache/ignite/blob/master/modules/platforms/dotnet/Apache.Ignite.Core/Impl/Common/Classpath.cs#L136 > > > On Thu, Jun 25, 2020 at 5:10 PM Ivan Daschinsky > wrote: > > > I think that just add an array of ignored modules for test platform > > class

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

It seems, that this test mysteriously fails only on one agent aitc-lin01_04 with this error. [1] Locally this .NET Core tests doesn't fail for about 20 minutes of continuously run (Mac OS X 10.15, .NET Core 3.1.200) According to stacktrace, it seems that there is problem with build configuration

Re: [DISCUSSION] Ignite.C++ and CMake

, > -- > Ilya Kasnacheev > > > вс, 21 июн. 2020 г. в 17:35, Ivan Daschinsky : > > > Hi folks. > > > > Patch is rigorously tested and with Igor Sapego help it is possible to > > build with cmake Ignite.C++ even on windows. > > But, it's required

Re: Tool for performance statistics reports

According to [1], it's absolutely OK to include files under MIT licence. But we should mention these components or modules in LICENCE file. [1] -- https://www.apache.org/legal/resolved.html вс, 21 июн. 2020 г. в 23:34, Saikat Maitra : > Hi Nikita, > > I have reviewed the PR and shared

Re: MTCGA spam about BinaryConfigurationTest in .NET Core suite

Hi igniters! I found that .NET Core suite and C++ suites fails on two agents -- aitc-lin01_04 and aitc-lin11_02. So I think the best solution is to exclude these agents as requirement for these suites and debug problems on these agents separately вт, 23 июн. 2020 г. в 09:33, Ivan Daschinsky

Re: MTCGA spam about BinaryConfigurationTest in .NET Core suite

://issues.apache.org/jira/browse/IGNITE-13187 чт, 25 июн. 2020 г. в 11:46, Ivan Daschinsky : > Hi igniters! > > I found that .NET Core suite and C++ suites fails on two agents -- > aitc-lin01_04 and aitc-lin11_02. > > So I think the best solution is to exclude these age

Re: MTCGA spam about BinaryConfigurationTest in .NET Core suite

o we have two versions of spring-data, and which one is correct? > > On Thu, Jun 25, 2020 at 4:34 PM Ivan Daschinsky > wrote: > > > The main reason of failure is jar-hell. When .NET or C++ tests are > started, > > if IGNITE_NATIVE_TEST_CLASSPATH is set to true, source

Re: MTCGA spam about BinaryConfigurationTest in .NET Core suite

I think that just add an array of ignored modules for test platform classpath is absolutely ok fix. But I have a discussion with Igor Sapego and he thinks that this fix is a little bit crutchy. чт, 25 июн. 2020 г. в 17:06, Ivan Daschinsky : > Actually, We have 3 (sic!) versions of spring d

Discussion: Existence of manual pinger for ZK client

Igniters, I suppose, that existence of manual pinger, introduced in [1], in our ZkDiscoveryImpl is under a big question. This weird thing was introduced to solve specific issue, specifically strange freeze of all threads of process during deallocate (Unsafe.freeMemory) of large amount of data.

IGNITE-12808 Allow create tables for existing caches

Hi Igniters. I've recently submitted patch[1] that implemented subj. Any help with review would be appreciated. [1] - https://issues.apache.org/jira/browse/IGNITE-12808 -- Sincerely yours, Ivan Daschinskiy

Re: PDS suites fail with exit code 137

Ivan, I think that we should use mmap/munmap to allocate huge chunks of memory. I've experimented with JNA and invoke mmap/munmap with it and it works fine. May be we can create module (similar to direct-io) that use mmap/munap on platforms, that support them and fallback to Unsafe if not? чт,

Re: PDS suites fail with exit code 137

your > proposal is > a major change for Ignite that can't be implemented fast enough. > > Anyway, I think this makes sense, considering that one day Unsafe will be > removed. But I wouldn't think about it right now, maybe as a separate > proposal... > > > > чт, 23 июл. 202

Re: PDS suites fail with exit code 137

lloc" - it's also an option, but it also requires reconfiguring > suites on > TC, maybe in a more complicated way. It requires additional installation, > right? > Can we stick to the solution that I already tested or should we update TC > agents? :) > > чт, 23 июл. 202

Re: New Committer: Sergey Chugunov

Congrats! Well deserved! пт, 17 июл. 2020 г. в 20:46, Sergey Antonov : > Congratulations, Sergey! > > сб, 18 июл. 2020 г., 0:24 Andrey Mashenkov : > > > Congratulations, Sergey. > > > > пт, 17 июл. 2020 г., 15:06 Вячеслав Коптилин : > > > > > Hi, > > > > > > Well deserved! Keep it up, Sergey! >

Move TcpDiscoveryZookeeperIpFinder to ignite-extensions as part of IEP-36

Hello, Igniters. Currently, in module ignite-zookeeper, that contains full implementation of ZookeeperDiscoverySpi, also presents one class that looks like a little snippet and I have some concerns about presence of this class in the module. 1) This class is a simple snippet-like implementation

Re: 2.9.1 release scope and dates

v, > > > > > > > > > It seems we've reached the proposed voting date - Nov. 26th > > > Do you need any help with the release preparation? > > > > > >> On Fri, 20 Nov 2020 at 14:46, Steshin Vladimir > > wrote: > > >> > > >> Yaroslav, Hi. > > >>

Re: IEP-61 Technical discussion

IM etc. > >>> > >>> 1 -- > >>> http://www.cs.cornell.edu/Info/Projects/Spinglass/public_pdfs/SWIM.pdf > >>> 2 -- > >>> > >>> > http://www.antonkharenko.com/2015/09/swim-distributed-group-membership.html > >>>

Re: IEP-61 Technical discussion

б. 2020 г. в 21:38, Ivan Daschinsky : > > > Alexey, I kindly ask you to move the meeting a little bit earlier, ideal > > variant -- in the morning. > > > > ср, 25 нояб. 2020 г. в 20:10, Alexey Goncharuk < > alexey.goncha...@gmail.com > > >: > > > > &

Re: [DISCUSS] Use GridNioServer in Java thin client

pache.org/confluence/display/IGNITE/IEP-60%3A+Java+Thin+Client+Non-Blocking+Async+IO > > [2] https://github.com/apache/ignite/pull/8483 > > > > On Mon, Nov 9, 2020 at 4:07 PM Ivan Daschinsky > > wrote: > > > >> I suppose that the best variant -- ability

Re: Replace Future.get with Future.get(int timeout) in tests

Not only futures, there are a lot of latches, barriers etc. with same problem. вт, 8 дек. 2020 г. в 18:41, ткаленко кирилл : > It seems to be a good topic, but it seems to be left to the reviewer's > discretion. > > 08.12.2020, 18:36, "Nikolay Izhikov" : > > Hello, Igniters. > > > > Currently,

Re: Migrating NodeJS client to TypeScript

> Is there any value in keeping both versions - the plain JavaScript one and the TypeScript specific Hi! No, there is no value. TS sources should be transpiled to JS before execution. вт, 1 дек. 2020 г. в 01:31, Denis Magda : > Hi Semyon, > > Is there any value in keeping both versions - the

Re: Re[2]: 2.9.1 release scope and dates

> > >> [1] https://issues.apache.org/jira/browse/IGNITE-13765 > >> > >> >Ivan, it's added, thanks for pointing that out > >> > > >> >On Mon, Nov 30, 2020 at 5:44 PM Ivan Daschinsky < ivanda...@gmail.com > > > >> wrote: >

Re: 2.9.1 release scope and dates

ser permissions) > > On Thu, Nov 5, 2020 at 6:24 PM Ivan Daschinsky > wrote: > > > Hi. I'd suggest to add this issue. This is a usability improvement for zk > > discovery, and also this patch incorporates fixes for JMX metrics > > concurrency issues > > > >

Re: Incorrect failure handler exceptions

Ilya, thanks for your effort. ср, 11 нояб. 2020 г. в 14:28, Ilya Kasnacheev : > Hello! > > The fix is now merged. > > Regards, > -- > Ilya Kasnacheev > > > вт, 3 нояб. 2020 г. в 22:51, Ivan Daschinsky : > > > There is not a big problem to fix it. > >

Re: [jira] [Created] (IGNITE-13696) [ML] Tutorial examples fails

I'm sorry, but this is so funny, can't stop laughing :) ср, 11 нояб. 2020 г. в 23:19, Alexey Zinoviev : > What errors did you found? > > ср, 11 нояб. 2020 г., 22:13 Stepan Pilschikov (Jira) : > > > Stepan Pilschikov created IGNITE-13696: > > -- > > > >

Re: [DISCUSS] Ignite 3.0 development approach

>> b. Implement IEP-61 - Common Replication Infrastructure I suppose, that this is the main cause of the current discussion. I hardly believe that this activity can be done without at least creating a completely new branch. пт, 13 нояб. 2020 г. в 11:12, Nikolay Izhikov : > My suggestion: > > 1.

Re: IEP-61 Technical discussion

ous size. But, on other side, Go has different model for concurrency and porting probably will not be so straightforward. чт, 19 нояб. 2020 г. в 13:48, Ivan Daschinsky : > I'd suggest to discuss this IEP and technical details in open ZOOM > meeting. > > чт, 19 нояб. 2020 г. в 13:47,

Fwd: IEP-61 Technical discussion

-- Forwarded message - От: Ivan Daschinsky Date: чт, 19 нояб. 2020 г. в 13:02 Subject: Re: IEP-61 Technical discussion To: Alexey Goncharuk Alexey, let's arise another question. Specifically, how nodes initially find each other (discovery) and how they detect failures. I

Re: IEP-61 Technical discussion

I'd suggest to discuss this IEP and technical details in open ZOOM meeting. чт, 19 нояб. 2020 г. в 13:47, Ivan Daschinsky : > > > -- Forwarded message ----- > От: Ivan Daschinsky > Date: чт, 19 нояб. 2020 г. в 13:02 > Subject: Re: IEP-61 Technical discussion >

Re: IEP-61 Technical discussion

Rust port, it seems fairly straightforward. Will be happy to > discuss this and other alternatives on the call as well. > > чт, 19 нояб. 2020 г. в 14:41, Ivan Daschinsky : > > > > Any existing library that can be used to avoid re-implementing the > > protocol ourselves? P

Re: 2.9.1 release scope and dates

4, Yaroslav Molochkov > wrote: > > > > Ivan, thanks! > > > > Added it to the list. > > > >> On 8 Nov 2020, at 14:13, Ivan Daschinsky wrote: > >> > >> Yaroslav, there is another bug for 2.9.1 release > >> https://issues.a

Re: [DISCUSS] Use GridNioServer in Java thin client

I suppose that the best variant -- ability to switch to netty if this lib is in classpath пн, 9 нояб. 2020 г. в 15:58, Igor Sapego : > Sounds like a good idea to me. > > Best Regards, > Igor > > > On Mon, Nov 9, 2020 at 3:32 PM Alex Plehanov > wrote: > > > +1 for using GridNioServer as java

Re: IEP-61 Technical discussion

serf) 4 -- https://github.com/scalecube/scalecube-cluster -- (Java implementation of SWIM) чт, 19 нояб. 2020 г. в 16:35, Ivan Daschinsky : > >> Friday, Nov 27th work for you? If ok, let's have an open call then. > Yes, great > >> As for the protocol port - w

Re: Why WAL archives enabled by default?

gt; > > Dmitriy Pavlov > > > > > > вт, 10 нояб. 2020 г. в 09:57, ткаленко кирилл : > > > > > > > Hello guys again! > > > > > > > > Does anyone know why we are doing any calculation here > > > > IgniteUtils#adjustedWalHi

Re: [DISCUSS] Disable socket linger by default in TCP discovery SPI.

e good news that 1.2- also were > > fixed. > > so, > > -- brand new TLS with any linger > > -- plain old TLS with linger>0 > > > > On Fri, Oct 30, 2020 at 3:10 PM Ivan Daschinsky > > wrote: > > > > > Ilya, Anton.

Re: Incorrect failure handler exceptions

There is not a big problem to fix it. 1. Blocked thread is detected by another worker. Currently we take dump before printing it to log with zero depth. This can be easily fixed. 2. We should propagate BlockedThreadExceptiob to failureCtx with original stacktrace of blocked thread. StackFrames,

Re: [DISCUSS] Missed (non-suited) tests

the tickets are open? This will help to find > out > > > > tests that were forgiven in a recent time. > > > > > > > > Also I believe that this check must be automated. I didn't find a way > > how > > > > uncomment / unused tests are found in the ticket. If there is no any &g

Re: [DISCUSS] Missed (non-suited) tests

I suggests to mark these tests with @Ignore and file tickets to fix them. пт, 30 окт. 2020 г. в 16:26, Ivan Daschinsky : > Hi > > WalCompactionAfterRestartTest -- yes we need it. This test failed because > of race (test shold be rewritten a little bit) > > пт, 30 окт. 20

Re: [DISCUSS] Disable socket linger by default in TCP discovery SPI.

Hi! Vova, I agree with you, this default behaviour is quite confusing. Even if we want to workaround bug for old jdk's and SSL, it's strange idea to affect all other users by default. I think that we should add section in documentation how to workaround this issue, and disable socket linger on

Re: [DISCUSS] Disable socket linger by default in TCP discovery SPI.

Ilya, Anton. It means that not if TLS 1.3 is worked ok and with TLS < 1.2 is not ok. When TLS 1.3 is introduced, whole sun.security.ssl.SSLSocketImpl was rewritten. There is not any code anymore that could cause a deadlock. Therefore, in JDK, that supports TLS 1.3, this option is unnecessary,

Re: 2.9.1 release scope and dates

Hi. I'd suggest to add this issue. This is a usability improvement for zk discovery, and also this patch incorporates fixes for JMX metrics concurrency issues [1] -- https://issues.apache.org/jira/browse/IGNITE-13577 чт, 5 нояб. 2020 г., 16:20 Yaroslav Molochkov : > Igniters! > > I'd like to

Re: Why WAL archives enabled by default?

for recovery will remain and > there will be no data loss. > > 06.11.2020, 11:29, "Ivan Daschinsky" : > > Guys, fisrt of all, archiving is not for PITR at all, this is > optimization. > > If we disable archiving, every rollover we need to create new file. If we > > enable a

Re: Why WAL archives enabled by default?

is questionable, because it can cause some performance problems. But as an option, it can be used and should be switchable. пт, 6 нояб. 2020 г. в 12:36, Ivan Daschinsky : > Kirill, how your approach will help if user tuned a cluster to do > checkpoints rarely under load? > No way. > > пт, 6

Re: Why WAL archives enabled by default?

>> For example, when trying to move a segment to the archive. We cannot do this, we will lost data. We can truncate archived segment if and only if it is not required for recovery. If last checkpoint marker points to segment with lower index, we cannot delete any segment with higher index. So the

Re: Why WAL archives enabled by default?

> reservation / release of segments, thus we can know how many segments we > can delete right now. > > 06.11.2020, 09:53, "Ivan Daschinsky" : > >>> For example, when trying to move a segment to the archive. > > > > We cannot do this, we will lost data.

Re: Why WAL archives enabled by default?

you are talking about this feature. > > пт, 6 нояб. 2020 г. в 13:21, Ivan Daschinsky : > > > Kirill and I discussed privately proposed approach. As far as I > understand, > > Kirill suggests to implement some > > heuristic to do a force checkpoint in some cases if user

[DISCUSS] Python thin client development approach.

Hi folks! Since we already have a separate repo for thin-clients [1], [2] I'd like to propose some improvements in development process/ 1. We should simplify and automate unit tests run for different versions of python 2. We should add travis integration per commit and pr. Tests could be run

Re: Limiting number of active connection for thin client

>> However, sometimes it can create excessive load for cluster in use cases when there are a lot of thin clients. Could you please provide some figures? I suppose, that our NIO server can handle thousands connections easily, and problem is not in multiple connections. пт, 25 дек. 2020 г. в 11:33,

Re: [DISCUSS] Missed (non-suited) tests

gt; > > > such > > > > >> > test > > > > >> > > > and > > > > >> > > > > > move it to the right module. But I think this work will > > > take a > > > > >> lot > > > > >> > of > >

Re: [DISCUSS] Python thin client development approach.

r > > > On Fri, Dec 25, 2020 at 1:49 PM Nikolay Izhikov > wrote: > > > Hello, Ivan. > > > > I’m +1 for your proposal. > > > > > 25 дек. 2020 г., в 13:14, Ivan Daschinsky > > написал(а): > > > > > > Hi folks! > >

Re: Ignite website css not loading in local dev

l to run > the > > website in local? > > > > Also I have observed few additional lines commented in the index.html > like > > below > > > > > > > > I will check if uncommenting them addresses the issue. > > > > Regards, > > Saikat > >

Re: Ignite website css not loading in local dev

Hi, Saikat. Do you have https://issues.apache.org/jira/browse/IGNITE-13659 commit in yout local branch? In this patch, this issue was solved. Namely, docs/assets/css/docs.scss and docs/assets/css/styles.scss are corrected. Jekyll required that in custom stiles, first two lines contains this char

Re: Hard limit WAL archive size

As for me, correct approach is to trigger checkpoint when we are too close to WAL archive size limit. The main purpose of these mechanism is to provide durability, so we should think about not to fail node, nor to delete data voluntary, but prevent possible data loss. вт, 26 янв. 2021 г. в 19:13,

Re: Ignite website css not loading in local dev

html > > On Sunday, January 31, 2021, Ivan Daschinsky wrote: > > > Saikat, have you tried build and run locally docs using docker? I just > > tried latest master -- everything is working as expected. > > Checked this in chrome incognito mode. I usually check docs locally using

  1   2   3   4   5   >