Dmitry,
additional BLT related logging is already added. I hope it will help
users to understand BLT better.
On Tue, May 8, 2018 at 3:36 PM, Dmitriy Setrakyan wrote:
> Completely support the decision to move any BLT behavior changes to 2.6.
> However, in 2.5 we need to add usability log messages
Completely support the decision to move any BLT behavior changes to 2.6.
However, in 2.5 we need to add usability log messages, which I believe we
already have.
D.
On Tue, May 8, 2018 at 2:15 PM, Andrey Gura wrote:
> Igniters,
>
> I believe BLT is serious usability problem but rush isn't good i
Igniters,
I believe BLT is serious usability problem but rush isn't good idea
because can lead to new bugs. As release manager I think that we
should move BLT fix to Apache Ignite 2.6 release and focus on issues
included to the AI 2.5 release scope.
I also want inform you that code freeze is plann
Hi Dmitriy,
As far as I understand manual activation will not be required for in-memory
mode (same for persistence). Change means we will change node state from
'joined-inactive' to 'joined-active' according to that user defined in
policy (cluster grow policy).
Default will be allow to rebalance
Can someone explain what is the before and after effect for this change
from the usability standpoint. If we are changing BLT for the in-memory
mode, which is the default, then we must think through all the usability
consequences ahead of time. Otherwise, the perception will be that the
product sto
I'm backing up Vladimir's proposal to fix the behavior in 2.5 if it's not
time-consuming. To give you a bit more context on the subj, here is why we
should have the fix to be delivered in 2.5:
http://apache-ignite-users.70518.x6.nabble.com/Problems-
with-persistence-and-partitioned-cache-in-2-4-0-t
I like AI 2.5 now, but then release AI 2.6 with (BL)AT fix. Probably we
will find some more changes to be delivered to users.
сб, 28 апр. 2018 г. в 17:56, Vladimir Ozerov :
> Yakov,
>
> Messages would help users understand what is wrong earlier, but will not
> protect them from additional mainten
Yakov,
Messages would help users understand what is wrong earlier, but will not
protect them from additional maintenance which is required in AI 2.4 and is
supposed to be removed in next AI releases.
Please note that in IEP-4 topic I proposed alternative solution - release
AI 2.5 now, but then rel
Guys, how about we release 2.5 in the nearest future after adding proper
usability log messages that will explain user what to do and also output
link to readme.io with the first BLT related message during node uptime.
This should not take much time and we can use the same messages when we
have (BL
Ok, I understand process now. Thank you for clarification.
сб, 28 апр. 2018 г. в 17:41, Vladimir Ozerov :
> Dmitry,
>
> I think that developer convenience is of much smaller priority here than
> user experience. Moreover, we are not going to unfreeze AI 2.5 scope
> completely. Instead, we propose
Dmitry,
I think that developer convenience is of much smaller priority here than
user experience. Moreover, we are not going to unfreeze AI 2.5 scope
completely. Instead, we propose to add BLT fix to AI 2.5, but disallow
anything else. This way most contributors will continue working with master
a
-0.9 from me, because I want users get performance fix
https://issues.apache.org/jira/browse/IGNITE-7638 and 2 related fixes
faster.
сб, 28 апр. 2018 г. в 17:35, Dmitry Pavlov :
> Hi Vladimir,
>
> The fact that we will postpone the release will somehow allow users to
> receive fixes faster? What
Hi Vladimir,
The fact that we will postpone the release will somehow allow users to
receive fixes faster? What if we will fix (BL)AT it in 2.6 instead?
It will be additional issue for all developers to maintain 2.5 & master
branches.
Sincerely,
Dmitriy Pavlov
сб, 28 апр. 2018 г. в 17:28, Vladim
Igniters, we have a problem.
Baseline topology was introduced in AI 2.4. Looks like it have two serious
flaws which confuse our users a lot:
1) No automatic rebalance by default
2) Topology misalignment between persistent and in-memory caches
These are really *critical* problems which severely af
14 matches
Mail list logo
