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: Custom Affinity Functions proposed for removal?

If I have a primary key vector like this , where & can have varying values for , and I want all keys with the same and to reside in the same partition for processing colocation requirements then I can't use the standard Ignite mapping to do this, I need to use a custom mapper than uses just

[jira] [Created] (IGNITE-13670) Omit nullmap where possible

Alexey Goncharuk created IGNITE-13670: - Summary: Omit nullmap where possible Key: IGNITE-13670 URL: https://issues.apache.org/jira/browse/IGNITE-13670 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-13669) Implement date native types

Alexey Goncharuk created IGNITE-13669: - Summary: Implement date native types Key: IGNITE-13669 URL: https://issues.apache.org/jira/browse/IGNITE-13669 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-13668) Implement Number(n) and Decimal native types

Alexey Goncharuk created IGNITE-13668: - Summary: Implement Number(n) and Decimal native types Key: IGNITE-13668 URL: https://issues.apache.org/jira/browse/IGNITE-13668 Project: Ignite

[jira] [Created] (IGNITE-13667) Add schema columns relocation table to map from user order to system order

Alexey Goncharuk created IGNITE-13667: - Summary: Add schema columns relocation table to map from user order to system order Key: IGNITE-13667 URL: https://issues.apache.org/jira/browse/IGNITE-13667

Incorrect failure handler exceptions

Hello! https://issues.apache.org/jira/browse/IGNITE-13665 The notorious problem with failure handler's thread dump, which nobody has bothered to investigate, until now. "IgnitionEx$IgniteNamedInstance$2.apply" If anybody knows how to fix it, please suggest. Regards, -- Ilya Kasnacheev

[jira] [Created] (IGNITE-13665) Useless failure trace "IgnitionEx$IgniteNamedInstance$2.apply"

Ilya Kasnacheev created IGNITE-13665: Summary: Useless failure trace "IgnitionEx$IgniteNamedInstance$2.apply" Key: IGNITE-13665 URL: https://issues.apache.org/jira/browse/IGNITE-13665 Project:

Re: delete is too slow, sometimes even causes OOM

Hi Frank, Thanks for starting this discussion. Our contributors with SQL experience should step in. Generally, I came across this performance issue a week or so ago while doing training about Ignite. In my case, a simple DELETE was running for a minute over a table of negligible size. - Denis

delete is too slow, sometimes even causes OOM

Current code logic for DELETE is as follows: if WHERE clause contains a condition as "key=xxx", it uses fastUpdate which remove the related item directly. else do select for update; for each row, call closure code "RMV" to remove it. 1. As "executeSelectForDml" get _KEY and _VAL columns

[jira] [Created] (IGNITE-13664) GridCommandHandlerTest.testPersistenceCleanCorruptedCachesCommand fails on Windows platform

Vyacheslav Koptilin created IGNITE-13664: Summary: GridCommandHandlerTest.testPersistenceCleanCorruptedCachesCommand fails on Windows platform Key: IGNITE-13664 URL:

Re: 2.9.1 release proposal

Nikolay, hi! Done. On Tue, Nov 3, 2020 at 10:48 AM Nikolay Izhikov wrote: > Hello, Yaroslav. > > Looks like we have fixVersion 2.9.1 in Jira. > Let’s mark all tickets with label «2.9.1-rc1» with fixVersion=2.9.1 and > use fixVersion instead of label further. > > >

[jira] [Created] (IGNITE-13663) Represent in the documenttion affection of several node addresses on failure detection v2.

Vladimir Steshin created IGNITE-13663: - Summary: Represent in the documenttion affection of several node addresses on failure detection v2. Key: IGNITE-13663 URL:

Re: Interoperable Ignite.NET Dates

Pavel, Thank you for your positive feedback! I will create an IEP. вт, 3 нояб. 2020 г. в 15:48, Pavel Tupitsyn : > Alexey, > > The proposal looks good to me. > > Usually I would try to avoid extra dependencies in the core assembly, > but NodaTime seems to be worth it. > > Would you like to

[jira] [Created] (IGNITE-13662) Discribe soLinger setting in TCP Discovery and SSL issues.

Vladimir Steshin created IGNITE-13662: - Summary: Discribe soLinger setting in TCP Discovery and SSL issues. Key: IGNITE-13662 URL: https://issues.apache.org/jira/browse/IGNITE-13662 Project:

Re: Interoperable Ignite.NET Dates

Alexey, The proposal looks good to me. Usually I would try to avoid extra dependencies in the core assembly, but NodaTime seems to be worth it. Would you like to prepare an IEP? Thanks, Pavel On Tue, Nov 3, 2020 at 3:15 PM Alexey Kukushkin wrote: > We already created tickets and tested

Re: Custom Affinity Functions proposed for removal?

Raymond, Thanks for the details. So it sounds like you have a custom affinity mapper, not affinity function. This makes things simpler, but I'm still failing to understand why standard mechanisms for collocation [1] didn't work for you. Could you please clarify? [1]

Re: [DISCUSS] Ignite 3.0 development approach

Ksenia, thanks for scheduling this on such short notice! As for the original topic, I do support Alexey's idea. We're not going to rewrite anything from scratch, as most of the components are going to be moved as-is or with minimal modifications. However, the changes that are proposed imply

[jira] [Created] (IGNITE-13661) Example for transactions in thin clients

Stepan Pilschikov created IGNITE-13661: -- Summary: Example for transactions in thin clients Key: IGNITE-13661 URL: https://issues.apache.org/jira/browse/IGNITE-13661 Project: Ignite

Re: Interoperable Ignite.NET Dates

We already created tickets and tested the proposed solution with our applications (already in PROD) and an internal fork of Ignite. This discussion is a proposal to donate this change to open source Apache Ignite is the community accepts it: - IGNITE-12824 .NET: Write DateTime in interoperable

Re: usage analytics

Makes sense to me. I would love to know which components/APIs are used more than others. Obviously, we should make sure everything is anonymous and we don't collect any private user data, but I believe this is already guaranteed by Google Analytics. -Val On Tue, Nov 3, 2020 at 3:59 AM Alexey

Re: Interoperable Ignite.NET Dates

Cool, makes sense to me then. Please feel free to create a ticket and mark it with the "ignite-3" label. -Val On Tue, Nov 3, 2020 at 4:03 AM Alexey Kukushkin wrote: > Val, absolutely - our proposal affects .NET API only. > > вт, 3 нояб. 2020 г. в 15:00, Valentin Kulichenko < >

Re: Interoperable Ignite.NET Dates

Val, absolutely - our proposal affects .NET API only. вт, 3 нояб. 2020 г. в 15:00, Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Got it. So it only affects the .NET side, correct? > > -Val > > On Tue, Nov 3, 2020 at 3:52 AM Alexey Kukushkin > > wrote: > > > Hi Val, > > > > Our

Re: Interoperable Ignite.NET Dates

Got it. So it only affects the .NET side, correct? -Val On Tue, Nov 3, 2020 at 3:52 AM Alexey Kukushkin wrote: > Hi Val, > > Our proposal does not overlap with IEP-54 > < > https://cwiki.apache.org/confluence/display/IGNITE/IEP-54%3A+Schema-first+Approach > >, > which proposes changing Ignite

Re: usage analytics

Folks, I want to bump up this discussion and slightly change the format suggested by Nikita. I dot think it is correct to gather any information related to the user environment. However, can we collect just the fact of some of the Ignite APIs/subsystems being used with no user information

Re: Interoperable Ignite.NET Dates

Hi Val, Our proposal does not overlap with IEP-54 , which proposes changing Ignite date storage format. Our proposal is enhancing Ignite to handle .NET dates in a truly portable way instead of requiring the

[jira] [Created] (IGNITE-13660) Unexpected NODE_LEFT on graceful stop (at ducktests)

Anton Vinogradov created IGNITE-13660: - Summary: Unexpected NODE_LEFT on graceful stop (at ducktests) Key: IGNITE-13660 URL: https://issues.apache.org/jira/browse/IGNITE-13660 Project: Ignite

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

    Ilya, hi.     Of course: /TcpDiscoverySpi.setSoLinger(int)/ property. Always been. 02.11.2020 20:14, Ilya Kasnacheev пишет: Hello! Is there any option to re-enable linger on SSL sockets? Telling people to re-configure does not help if they can't. Regards,

Re: [DISCUSS] Ignite 3.0 development approach

Pavel, all the interesting points will be anyway published here in English (as the principal "if it's not on devlist it doesn't happened" is still relevant). This is just a quick call for a group of developers. Later we can do a separate presentation of idea and discussion in English as we did for

Re: [DISCUSS] Ignite 3.0 development approach

Kseniya, Thanks for scheduling this call. Do you think we can switch to English if non-Russian speaking community members decide to join? On Tue, Nov 3, 2020 at 1:32 PM Kseniya Romanova wrote: > Let's do this community discussion open. Here's the link on zoom call in > Russian for Friday 6 PM:

Re: [DISCUSS] Ignite 3.0 development approach

Let's do this community discussion open. Here's the link on zoom call in Russian for Friday 6 PM: https://www.meetup.com/Moscow-Apache-Ignite-Meetup/events/274360378/ вт, 3 нояб. 2020 г. в 12:49, Nikolay Izhikov : > Time works for me. > > > 3 нояб. 2020 г., в 12:40, Alexey Goncharuk >

Re: [DISCUSS] Ignite 3.0 development approach

Time works for me. > 3 нояб. 2020 г., в 12:40, Alexey Goncharuk > написал(а): > > Nikolay, > > I am up for the call. I will try to explain my reasoning in greater detail > and will be glad to hear the concerns. Will this Friday, Nov 6th, work? > > вт, 3 нояб. 2020 г. в 10:09, Nikolay Izhikov

Re: [DISCUSS] Ignite 3.0 development approach

Nikolay, I am up for the call. I will try to explain my reasoning in greater detail and will be glad to hear the concerns. Will this Friday, Nov 6th, work? вт, 3 нояб. 2020 г. в 10:09, Nikolay Izhikov : > Igniters, should we have a call for this topic? > > > 2 нояб. 2020 г., в 18:53, Pavel

[jira] [Created] (IGNITE-13659) TDE - Phase 3. Documentation

Pavel Pereslegin created IGNITE-13659: - Summary: TDE - Phase 3. Documentation Key: IGNITE-13659 URL: https://issues.apache.org/jira/browse/IGNITE-13659 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-13658) Volatile cache writes to persistent storage.

Stanilovsky Evgeny created IGNITE-13658: --- Summary: Volatile cache writes to persistent storage. Key: IGNITE-13658 URL: https://issues.apache.org/jira/browse/IGNITE-13658 Project: Ignite

Re: Custom Affinity Functions proposed for removal?

In terms of Key -> Partition -> Node mapping, we provide customer affinity mappers for the Key -> Partition stage an allow Ignite to map partitions to nodes. Our keys are structs with multiple fields forming a composite primary key, parts of which are spatially identifying and parts contain other

Re: Custom Affinity Functions proposed for removal?

Moti, Raymond, Could you please describe your use cases in more detail? What are the types used as cache keys? What is the custom logic that you use for affinity mapping? What was the exact reason to customize versus using built-in collocation mechanisms? Ultimately, I'm sure that custom

Re: Interoperable Ignite.NET Dates

Hi Alexey, The IEP-54 [1] describes the data layout proposed for Ignite 3.0, it includes various date/time types. Can you please take a look and check if this addresses your concerns? We can then discuss further if needed.

Re: Interoperable Ignite.NET Dates

Pavel, We propose changing public API so this is for Ignite 3.0. Thanks! вт, 3 нояб. 2020 г. в 02:17, Pavel Tupitsyn : > Alexey, > > Just to clarify before we start the discussion: > this proposal seems to introduce some breaking changes, so we are talking > about Ignite 3.0, correct? > >

[jira] [Created] (IGNITE-13657) Flaky test TxOptimisticDeadlockDetectionCrossCacheTest

Aleksey Plekhanov created IGNITE-13657: -- Summary: Flaky test TxOptimisticDeadlockDetectionCrossCacheTest Key: IGNITE-13657 URL: https://issues.apache.org/jira/browse/IGNITE-13657 Project: Ignite