Maxim, Folks, hi.
The approach looks reasonable to me, +1
As an additional user notification, we might use even/odd number
strategy. User could be sure that even (as an example) major release
doesn’t break backward compatibility. Crucial API changes might be
collected only in odd releases
Ilya, hi.
+1 from me. We should not worry about weird user actions. Direct calling
of GC looks unusual today. Suggestion of forced disabling manual
System.gc() looks useless.
14.05.2021 15:06, Ilya Korol пишет:
Hi, everyone.
There is a proposal to remove suggestion that user should disable
Hi all.
Let's add simple and useful thin-client-pool monitoring in 2.12:
https://issues.apache.org/jira/browse/IGNITE-15183
https://github.com/apache/ignite/pull/9525
19.11.2021 09:50, Maksim Timonin пишет:
Hi, I want to add to 2.12 a fix [1] of a bug [2]. It affects users of
metric
Dmitry, hi.
Here is the ticket [1] and PR [2]. Looks trivial. Waiting for the test
completed.
[1] https://issues.apache.org/jira/browse/IGNITE-13194
[2] https://github.com/apache/ignite/pull/7969
29.06.2020 03:43, dpavlov.ta...@gmail.com пишет:
Hi Igniters,
I've detected some new issue
*
Hi, Igniters.
We’ve found that enabled by default socket linger causes unexpected
delay in detection of node failure.
Moreover, long closing of socket works as Thread.sleep() within
algorithms of failure detection and connection recovery in TCP
discovery. These time gaps lead to hardly p
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,
y.
Do we need to do except the following?
zero linger as default + warning on SSL enabled on JVM before the fix +
warning at documentation + migration notes
On Tue, Nov 3, 2020 at 2:38 PM Steshin Vladimir wrote:
Ilya, hi.
Of course: /TcpDiscoverySpi.setSoLinger(int)/ property. A
Yaroslav, Hi.
I suggest to merge minor fix of javadoc: [1]. It should have appeared in
2.9. Commits in master:
d3e5b7c11ed037670700eea75851e619d5d1b6b1
and
1654e9fac61842424c08d26a08ef67569f74746a
[1] https://github.com/apache/ignite/pull/8448
19.11.2020 17:15, Ivan Daschinsky пишет:
bit behind the schedule
On 26 Nov 2020, at 21:14, Maxim Muzafarov <
mmu...@apache.org
wrote:
Yaroslav,
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 <
vlads...@gmail.
(3db17612d7c433ddfbb404f92eebca6dd2f4fefe)
Перенаправленное сообщение
Тема: Re: 2.9.1 release scope and dates
Дата: Wed, 2 Dec 2020 13:06:42 +0300
От: Steshin Vladimir
Кому: dev@ignite.apache.org
Yaroslav, Hi.
I propose [1] and [2] to pick up into 2.9.1.
[1] is important. It
10 matches
Mail list logo
