Re: How to know memory used by a cache or a set

+ dev list Ignite developers, Seems that the present solution for memory calculation doesn't work (check the thread): https://apacheignite.readme.io/v2.5/docs/memory-metrics#section-memory-usage-calculation Was it really broken? -- Denis Magda

Re: Signing off Ignite for export beyond the U.S.

Dmitriy, I think that it's required to enlist all of the publicly released Ignite versions (available for download from the website). It means that the XML should have the following controlled sources grouped by Ignite versions' ranges. - Ignite 1.0.0 - Ignite 1.5.0-b1: ASF, Oracle, The Eclips

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

+1 to Denis, Near caches are on-heap, as well, so I guess we need it. BTW, TeamCity Bot uses Guava on-heap caching above Ignite (Durable Memory). This is because keeping the same instance of Java object cached brings a visible performance boost for really hot code points. At least, it reduces GC p

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

Ivan, I believe that, yes, those caches are still extremely useful for low-latency use cases. Companies are ready to allocate more RAM in favor of lower latencies because off-heap access is still slower than the on-heap one. There are not that many use case of this kind, but I can recall several c

Re: [DISCUSSION] Complete Discontinuation of IGFS and Hadoop Accelerator

Dmitriy, I like the first approach with applying Maxim's idea of creating a branch > named -igfs-Hadoop (not release, but current master state). +1 for this approach. Any other opinions before we finalize this discussion? - Denis On Tue, Jun 18, 2019 at 11:28 AM Dmitriy Pavlov wrote: > Hi D

Re: Thin client test suites failure

Hi Ivan, Can these failures be related to Java version? Java home is set randomly by TC Bot. Dmitriy Pavlov вт, 18 июн. 2019 г. в 22:11, Павлухин Иван : > Hi igniters, > > Does anyone know why python, php and nodejs [1, 2, 3] suites fail so > frequently on TC? Is there any activity to deal with

Thin client test suites failure

Hi igniters, Does anyone know why python, php and nodejs [1, 2, 3] suites fail so frequently on TC? Is there any activity to deal with it? [1] https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_ThinClientPython&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv

Re: Ignite 2.7.5 c# client Nuget package

Hi Dmitriy, Yes, I see it there. Thanks! Raymond. On Wed, Jun 19, 2019 at 2:09 AM Dmitriy Pavlov wrote: > Hi Raymond, > > Please check, NuGet Packages were published > https://www.nuget.org/packages/Apache.Ignite/ > > Sincerely > Dmitriy Pavlov > > вт, 18 июн. 2019 г. в 13:21, Raymond Wilson :

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

Do we still need onheap caches? вт, 18 июн. 2019 г. в 21:30, Denis Magda : > > +1 > > Thick (aka. standard clients) provide comprehensive compute APIs with > peer-class-loading. That's a huge differentiator for Ignite. Until thin > clients support compute and ML API at the same level as the standa

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

+1 Thick (aka. standard clients) provide comprehensive compute APIs with peer-class-loading. That's a huge differentiator for Ignite. Until thin clients support compute and ML API at the same level as the standard client does, I would not consider the standard clients' discontinuation. Plus, as Al

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

Denis, here is the link: https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0+Wishlist вт, 18 июн. 2019 г. в 21:28, Denis Magda : > Alex, > > I've separated all to-be-removed points from existing > > Ignite 3.0 wishlist [1] to a dedicated block and also added a few more > > things

Re: [DISCUSSION] Complete Discontinuation of IGFS and Hadoop Accelerator

Hi Denis, I like the first approach with applying Maxim's idea of creating a branch named -igfs-Hadoop (not release, but current master state). 2nd) 3rd party repo can be Apache repo just like ignite-release. But it's true it is time-consuming to move code. 3rd) Attic is for projects, I hope no on

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

Alex, I've separated all to-be-removed points from existing > Ignite 3.0 wishlist [1] to a dedicated block and also added a few more > things that look right to be dropped. Could you please share a reference to the wishlist? It's not in your original email nor anywhere else in the discussion. G

Re: [DISCUSSION] Complete Discontinuation of IGFS and Hadoop Accelerator

Igniters, Thanks a lot for sharing your opinion. As I see, there is a consensus that IGFS and Hadoop Accelerator are to be discontinued and no longer supported by the community. As for the source code, if the community prefers moving the source code to another repository rather than removing it,

Re: Release process wiki update

Dmitriy, Thanks for keeping us in the loop. Let us know once the final steps are over. If any help is needed, call for it. - Denis On Tue, Jun 18, 2019 at 7:07 AM Dmitriy Pavlov wrote: > Hi Ignite developers, > > Thanks to Pavel T. for providing an initial description on how to upload > NuGet

[jira] [Created] (IGNITE-11935) Checkstyle must support NewlineAtEndOfFile rule

Maxim Muzafarov created IGNITE-11935: Summary: Checkstyle must support NewlineAtEndOfFile rule Key: IGNITE-11935 URL: https://issues.apache.org/jira/browse/IGNITE-11935 Project: Ignite Is

[jira] [Created] (IGNITE-11934) Bugs & tests fixes

Dmitriy Govorukhin created IGNITE-11934: --- Summary: Bugs & tests fixes Key: IGNITE-11934 URL: https://issues.apache.org/jira/browse/IGNITE-11934 Project: Ignite Issue Type: Bug

Re: [DISCUSSION] Complete Discontinuation of IGFS and Hadoop Accelerator

Folks, +1 to reduce the number of supported features. Probably, the best solution will be removing IGFS from core module and making it as an Ignite plugin (will require some efforts to do this). I've also think we can move IGFS to the separate branch (from the master one) if someone will decide m

Re: Ignite 2.7.5 c# client Nuget package

Hi Raymond, Please check, NuGet Packages were published https://www.nuget.org/packages/Apache.Ignite/ Sincerely Dmitriy Pavlov вт, 18 июн. 2019 г. в 13:21, Raymond Wilson : > Great! > > Thanks, > Raymond > > On Tue, Jun 18, 2019 at 9:51 PM Dmitriy Pavlov wrote: > > > Hi Raymond, > > > > I'm go

Re: Release process wiki update

Hi Ignite developers, Thanks to Pavel T. for providing an initial description on how to upload NuGet packages. I've added details about how to set it up: https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-6.3.13.UploadNuGetpackagestonuget.org Thanks also to Alexand

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

We found an issue, we never set up group access before: now committers (wiki group: ignite) can edit and create pages, and PMC members (wiki group: ignite-pmc) are admins. Andrey, could you confirm you can edit now? вт, 18 июн. 2019 г. в 13:33, Dmitriy Pavlov : > Hi Ivan, thank you for this b

Re: Signing off Ignite for export beyond the U.S.

Igniters, please review crypto notice in https://github.com/apache/ignite/pull/6616/files#diff-26fd799ea07494916e9da9b91b2aac64R29 Only 2 open questions: about declaring released versions, and about declaring .NET versions (.NET Core & . NET Classic). By default, I propose to keep both. Sincerel

Re: [DISCUSSION] Mirroring Teamcity settings in a GitHub repository

Hello, Dmitriy. Thanks, for starting this discussion. I think almost all of community members don't know the difference between two options. I vote for the simplest solution with the human readable format. В Пн, 17/06/2019 в 21:07 +0300, Dmitriy Pavlov пишет: > Hi Igniters, > > During prepari

Re: Contibutor permissions for Apache Ignite Jira tickets

Hi Madhusudan, Thank you for interest in Apache Ignite, and welcome to the community. I've added your account to JIRA contributors group, now you can assign an issue to yourself. Let me share introduction how to contribute: https://github.com/apache/ignite/blob/master/CONTRIBUTING.md#contributing

Re: Access to Apache Ignite JIRA

Hi Evgeniy, Welcome on board! I've added your account to JIRA contributors group, now you can assign an issue to yourself. Let me share introduction how to contribute: https://github.com/apache/ignite/blob/master/CONTRIBUTING.md#contributing-to-apache-ignite and full guide https://cwiki.apache.or

[jira] [Created] (IGNITE-11933) Build scalar scaladoc only if javadoc profile is active

Ivan Pavlukhin created IGNITE-11933: --- Summary: Build scalar scaladoc only if javadoc profile is active Key: IGNITE-11933 URL: https://issues.apache.org/jira/browse/IGNITE-11933 Project: Ignite

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

Hi Ivan, thank you for this bit of information. We seem to be on the same page about a removal, and it would not happen in 3.0. My concern related to public API and users. If we internally redesign thick clients and remove counter-intuitive use cases (e.g. caches on a client, excepting near caches)

Re: Ignite 2.7.5 c# client Nuget package

Great! Thanks, Raymond On Tue, Jun 18, 2019 at 9:51 PM Dmitriy Pavlov wrote: > Hi Raymond, > > I'm going to upload it today or tomorrow. > > Best Regards > Dmitriy Pavlov > > вт, 18 июн. 2019 г., 12:42 Raymond Wilson : > > > Hi, > > > > When will the 2.7.5 Nuget package be available? > > > > We

Re: Ignite 2.7.5 c# client Nuget package

Hi Raymond, I'm going to upload it today or tomorrow. Best Regards Dmitriy Pavlov вт, 18 июн. 2019 г., 12:42 Raymond Wilson : > Hi, > > When will the 2.7.5 Nuget package be available? > > We are getting notifications from running Ignite services that 2.7.5 is > available. > > Thanks, > Raymond.

Ignite 2.7.5 c# client Nuget package

Hi, When will the 2.7.5 Nuget package be available? We are getting notifications from running Ignite services that 2.7.5 is available. Thanks, Raymond.

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

Nikolay, Dmitriy, Should we have a separate thread devoted to client nodes? Also, my cent here is from a Hazelcast history. Once they removed their thick client (called LiteMember), but after a while they brought it back. I think we need to learn this lesson in more details. вт, 18 июн. 2019 г.

Re: IGNITE-7285 Add default query timeout

Hi Saikat, Thank you for driving it. I left my comments [1]. [1] https://issues.apache.org/jira/browse/IGNITE-7285 сб, 15 июн. 2019 г. в 20:48, Saikat Maitra : > > Hi Ivan, > > Thank you for your email. I have updated the PR to use default query > timeout. > > Please take a look. > > https://git

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

Also, * Get rid of old services. * Make system cache non-persistent or even more - drop it. Discussion on dev list [1]. I have no permissions to edit wiki page and would glad if someone add all thoughts from this thread. [1] http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-System-

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

Folks, May I ask you to add the mentioned points to the wishlist to keep them in one place for convenience? вт, 18 июн. 2019 г. в 00:19, Alex Plehanov : > Remove "force server mode" for client nodes (already was discussed on dev > list earlier [1]). > > [1] : > > http://apache-ignite-developers.