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

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *New test failure in master IgniteStartStopTest.TestStartDefault https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-863164702742609335=%3Cdefault%3E=testDetails

[jira] [Created] (IGNITE-13295) Expiration of cache entries, which relate to a non-persistent data region in the persistent cluster, results in AssertionError

Vyacheslav Koptilin created IGNITE-13295: Summary: Expiration of cache entries, which relate to a non-persistent data region in the persistent cluster, results in AssertionError Key: IGNITE-13295 URL:

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

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to

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

Thanks, Pavel! Anton, Alex, we're in agreement to merge the changes in Ignite 2.9. Please go ahead removing the Hadoop/IGFS modules from both the master and 2.9 branches. - Denis On Thu, Jul 23, 2020 at 8:14 AM Pavel Tupitsyn wrote: > Denis, > > Thanks for the explanation, I don't have any

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

Denis, Thanks for the explanation, I don't have any objections anymore. On Wed, Jul 22, 2020 at 7:46 PM Denis Magda wrote: > Hi, > > Send an email to this address: dev-unsubscr...@ignite.apache.org > > - > Denis > > > On Wed, Jul 22, 2020 at 9:28 AM C Ravikiran > wrote: > > > Hi, > > > >

Re: PDS suites fail with exit code 137

> > About "jemalloc" - 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? :) Yes, if you want to use

Re: PDS suites fail with exit code 137

> > glibc allocator uses arenas for minimize contention between threads I understand it the same way. I did testing with running of Indexing suite locally and periodically executing "pmap ", it showed that the number of 64mb arenas grows constantly and never shrinks. By the middle of the suite

[jira] [Created] (IGNITE-13294) Page write throttling can park threads for too long

Aleksey Plekhanov created IGNITE-13294: -- Summary: Page write throttling can park threads for too long Key: IGNITE-13294 URL: https://issues.apache.org/jira/browse/IGNITE-13294 Project: Ignite

Re: PDS suites fail with exit code 137

AFAIK, glibc allocator uses arenas for minimize contention between threads when they trying to access or free preallocated bit of memory. But seems that we use -XX:+AlwaysPreTouch, so heap is allocated and committed at start time. We allocate memory for durable memory in one thread. So I think

Re: PDS suites fail with exit code 137

Hello Ivan, It feels like the problem is more about new starting threads rather than the allocation of offheap regions. Plus I'd like to see results soon, 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

[jira] [Created] (IGNITE-13293) .NET: Enum serialization is slow

Pavel Tupitsyn created IGNITE-13293: --- Summary: .NET: Enum serialization is slow Key: IGNITE-13293 URL: https://issues.apache.org/jira/browse/IGNITE-13293 Project: Ignite Issue Type: Bug

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? чт,

PDS suites fail with exit code 137

Hello Igniters, I'd like to discuss the current issue with "out of memory" fails on TeamCity. Particularly suites [1] and [2], they have quite a lot of "Exit code 137" failures. I investigated the "PDS (Indexing)" suite under [3]. There's another similar issue as well: [4]. I came to the

[jira] [Created] (IGNITE-13292) Remove unneeded ZkPinger from ZookeeperDiscovery

Ivan Daschinskiy created IGNITE-13292: - Summary: Remove unneeded ZkPinger from ZookeeperDiscovery Key: IGNITE-13292 URL: https://issues.apache.org/jira/browse/IGNITE-13292 Project: Ignite

[jira] [Created] (IGNITE-13291) Remove unnecessary dependency to curator-client from ZookeeperDiscoverySpi

Ivan Daschinskiy created IGNITE-13291: - Summary: Remove unnecessary dependency to curator-client from ZookeeperDiscoverySpi Key: IGNITE-13291 URL: https://issues.apache.org/jira/browse/IGNITE-13291

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

Alex, Denis Issue with moving of Web Console to separate repository is merged to master. See: https://issues.apache.org/jira/browse/IGNITE-13038 Please, consider to cherry-pick to ignite-2.9 --- Alexey Kuznetsov

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

Hi guys, considering Denis's question: [1] ("inverse TCP connection establishment") is already in master. I think we should port it in 2.9, would be a good thing. "Serverless functions" [2] support is code complete in a private branch, it's safe to say that the issue will be completed next week