Vladislav Pyatkov created IGNITE-12671:
--
Summary: Update of partition's states can stuck when rebalance
completed during exchange
Key: IGNITE-12671
URL: https://issues.apache.org/jira/browse/IGNITE-12671
Hi Saikat,
I left a couple of comments in pr:
https://github.com/apache/ignite-extensions/pull/4#pullrequestreview-357891629.
Please tell me what do you think about it.
Best Regards,
Evgenii
вт, 11 февр. 2020 г. в 17:15, Saikat Maitra :
> Hi,
>
> Can someone please help in review for these foll
Hi Maxim,
Do you have any understanding in regards to documentation readiness? I do
remember Nikolay was creating a page for the new metrics framework and
Artem stepped in as a reviewer. But not sure if that supposedly the largest
item is completed and if the other pages need to be updated.
-
Den
Pavel Tupitsyn created IGNITE-12670:
---
Summary: .NET: Calculate IAffinity.GetPartition locally for
default affinity
Key: IGNITE-12670
URL: https://issues.apache.org/jira/browse/IGNITE-12670
Project:
Maxim Muzafarov created IGNITE-12669:
Summary: Remove not used rebalanceDelay from production code
Key: IGNITE-12669
URL: https://issues.apache.org/jira/browse/IGNITE-12669
Project: Ignite
-1 Prohibit:
My justification builds solely on the possibility to encourage a user to
switch to an API that will be changed and later break the compilation.
Maxim,
rebalanceDelay was introduced before the BLT appear in the product to solve
scenarios which are now solved by BLT.
It's pointless for me having it in the product since BLT was introduced.
I do not think delaying rebalancing per cache group has any meaning. I
cannot image any reason for it
Yes, you are right. Missed resources, I'll remove them tomorrow
ср, 12 февр. 2020 г. в 16:23, Stepan Pilschikov :
> With mnist_tf_model in same directory
> All others looks right
>
> ср, 12 февр. 2020 г. в 16:21, Stepan Pilschikov >:
>
>> Hmm, interesting, got it
>> Also found
>> apache-ignite-2
With mnist_tf_model in same directory
All others looks right
ср, 12 февр. 2020 г. в 16:21, Stepan Pilschikov :
> Hmm, interesting, got it
> Also found apache-ignite-2.8.0-bin/examples/src/main/resources/models/mleap
> I think its also should be removed then
>
> ср, 12 февр. 2020 г. в 16:11, Alexe
Hmm, interesting, got it
Also found apache-ignite-2.8.0-bin/examples/src/main/resources/models/mleap
I think its also should be removed then
ср, 12 февр. 2020 г. в 16:11, Alexey Zinoviev :
> Please, have a look to the next ticket
> https://issues.apache.org/jira/browse/IGNITE-12659
> Also tensorf
Alexey,
Why do you think delaying of historical rebalance (on BLT node join)
for particular cache groups is not the real world use case? Probably
the same topic may be started on user-list to collect more use cases
from real users.
In general, I support reducing the number of available rebalance
Please, have a look to the next ticket
https://issues.apache.org/jira/browse/IGNITE-12659
Also tensorflow packages are blockers for IGFS deprecation and removal.
ср, 12 февр. 2020 г. в 15:58, Alexey Zinoviev :
> They are not lost, they are removed from release branch due to a lot of
> bugs, cves
They are not lost, they are removed from release branch due to a lot of
bugs, cves and so on, don't worry about that.
ср, 12 февр. 2020 г., 14:31 Stepan Pilschikov :
> Also lost ignite-ml-tensorflow-model-parser and ignite-tensorflow in
> libs/optional
>
>
> ср, 12 февр. 2020 г. в 14:25, Stepan P
Maxim,
In general rebalanceDelay is used to delay/disable rebalance then topology
is changed.
Right now we have BLT to avoid unnecesary rebalancing when topology is
changed.
If a node left from cluster topology no rebalancing happens until the node
explicitly removed from baseline topology.
I wou
Andrey N. Gura created IGNITE-12668:
---
Summary: Extend test coverage for plugin providers configuration
Key: IGNITE-12668
URL: https://issues.apache.org/jira/browse/IGNITE-12668
Project: Ignite
Alexey,
> All scenarios where rebalanceDelay has meaning are handled by baseline
> topology now.
Can you, please, provide more details here e.g. the whole list of
scenarios where rebalanceDelay is used and how these handled by
baseline topology?
Actually, I doubt that it covers exactly all the
Andrey N. Gura created IGNITE-12667:
---
Summary: Falky test
FailureProcessorThreadDumpThrottlingTest.testThrottlingPerFailureType
Key: IGNITE-12667
URL: https://issues.apache.org/jira/browse/IGNITE-12667
Also lost ignite-ml-tensorflow-model-parser and ignite-tensorflow in
libs/optional
ср, 12 февр. 2020 г. в 14:25, Stepan Pilschikov :
> But now have new problems
> I build ignite-2.8 build on TC
> https://ci.ignite.apache.org/buildConfiguration/Releases_ApacheIgniteMain_ReleaseBuild/5043672
> Pre
But now have new problems
I build ignite-2.8 build on TC
https://ci.ignite.apache.org/buildConfiguration/Releases_ApacheIgniteMain_ReleaseBuild/5043672
Previous
https://ci.ignite.apache.org/buildConfiguration/Releases_ApacheIgniteMain_ReleaseBuild/4988324
New build much lighter
Previous: 5.7 Gb
Cu
Amelchev Nikita created IGNITE-12666:
Summary: Provide cluster performance profiling tool
Key: IGNITE-12666
URL: https://issues.apache.org/jira/browse/IGNITE-12666
Project: Ignite
Issue T
Thanks for fix
Duplicated examples deleted and tutorial works on real (1+ node) cluster now
I think ticket can be closed, have no power here
вт, 11 февр. 2020 г. в 20:44, Alexey Zinoviev :
> Sorry, for that, but I it touches ML-related stuff only and doesn't
> influence on any another module.
> I
Andrey Mashenkov created IGNITE-12665:
-
Summary: SQL: Potential race on MapResult close.
Key: IGNITE-12665
URL: https://issues.apache.org/jira/browse/IGNITE-12665
Project: Ignite
Issue Ty
-1 Prohibit.
To me as a developer the situation when old but stable API is deprecated
with only experimental (thus unstable/unfinished) alternative is very far
from comfortable.
And from outside folks it may look like as a sign of immature processes
inside Ignite community (which is definitely not
I've meant baseline topology.
ср, 12 февр. 2020 г. в 12:41, Alexei Scherbakov <
alexey.scherbak...@gmail.com>:
>
> V.Pyatkov
>
> Doesn't rebalance topology solves it ?
>
> ср, 12 февр. 2020 г. в 12:31, V.Pyatkov :
>
>> Hi,
>>
>> I am sure we can to reduce this ability, but do not completely.
>> W
Ivan Pavlukhin created IGNITE-12664:
---
Summary: Failed to dump debug information. Failed to create string
representation of binary object.
Key: IGNITE-12664
URL: https://issues.apache.org/jira/browse/IGNITE-12664
V.Pyatkov
Doesn't rebalance topology solves it ?
ср, 12 февр. 2020 г. в 12:31, V.Pyatkov :
> Hi,
>
> I am sure we can to reduce this ability, but do not completely.
> We can use rebalance delay for disable it until manually triggered.
>
> CacheConfiguration#setRebalanceDelay(-1)
>
> It may helpf
How can i understand it from documentation ?
If Ignite persistence is enabled, Ignite enforces the baseline topology
concept which represents a set of server nodes in the cluster that will persist
data on disk.
>No, baseline is supported for im-memory caches as well.
>
>ср, 12 февр. 2020
Hi,
I am sure we can to reduce this ability, but do not completely.
We can use rebalance delay for disable it until manually triggered.
CacheConfiguration#setRebalanceDelay(-1)
It may helpful for cluster where can not allow performance drop from
rebalance at any time.
--
Sent from: http://apa
No, baseline is supported for im-memory caches as well.
ср, 12 февр. 2020 г. в 12:18, Zhenya Stanilovsky :
>
>
> But baseline, it`s about persistence [1] isn`t it? I wrote about
> pure inmemory case.
>
> [1] https://apacheignite.readme.io/docs/baseline-topology
> >Vyacheslav, Evgeny,
> >
> >All s
But baseline, it`s about persistence [1] isn`t it? I wrote about pure inmemory
case.
[1] https://apacheignite.readme.io/docs/baseline-topology
>Vyacheslav, Evgeny,
>
>All scenarios where rebalanceDelay has meaning are handled by baseline
>topology now.
>
>ср, 12 февр. 2020 г. в 12:00, Alexei S
Vyacheslav, Evgeny,
All scenarios where rebalanceDelay has meaning are handled by baseline
topology now.
ср, 12 февр. 2020 г. в 12:00, Alexei Scherbakov <
alexey.scherbak...@gmail.com>:
> Sergey,
>
> The ticket looks outdated.
> In fact this is already implemented.
>
> ср, 12 февр. 2020 г. в 11:
Classification: Public
Alexey,
then I don't have objections.
-Original Message-
From: Alexei Scherbakov [mailto:alexey.scherbak...@gmail.com]
Sent: 12 February 2020 12:01
To: dev
Subject: Re: [DISCUSSION] Deprecation of obsolete rebalancing functionality
Sergey,
The ticket looks outdat
Ilya Kasnacheev created IGNITE-12663:
Summary: Let's limit all thread pools' sizes to 3 in tests
Key: IGNITE-12663
URL: https://issues.apache.org/jira/browse/IGNITE-12663
Project: Ignite
Sergey,
The ticket looks outdated.
In fact this is already implemented.
ср, 12 февр. 2020 г. в 11:58, Sergey-A Kosarev :
> Classification: Public
>
> Hi, Alexey.
> I believe it can't be done until in-memory caches will use baseline
> topology [1].
> In our case we are using rebalanceDelay for in
Hi, Alexei!
CacheConfiguration#getRebalanceDelay was extremely useful for the
caches backed by @CacheLocalStore to prevent rebalancing during full
cluster startup/shutdown.
But @CacheLocalStore annotation is deprecated also.
I think "rebalancing delay" stuff might be useful for replicated
cached
Classification: Public
Hi, Alexey.
I believe it can't be done until in-memory caches will use baseline topology
[1].
In our case we are using rebalanceDelay for in-memory caches.
[1] https://issues.apache.org/jira/browse/IGNITE-8414
Kind regards,
Sergey Kosarev
-Original Message-
From
I know guys who use this setting (may be erroneously) = MAX_INT for real
rebalance delaying (very small sla) grid without persistence. But i don`t know
further algo, may be if backup nodes become extremely small they creates the
same cluster near it. Can ignite simple disable rebalance?
>F
Folks,
I want to deprecate some obsolete functionality related to rebalancing.
Details in [1]
Any objections ?
[1] https://issues.apache.org/jira/browse/IGNITE-12662
--
Best regards,
Alexei Scherbakov
Alexey Scherbakov created IGNITE-12662:
--
Summary: Get rid of CacheConfiguration#getRebalanceDelay and
related functionality.
Key: IGNITE-12662
URL: https://issues.apache.org/jira/browse/IGNITE-12662
39 matches
Mail list logo
