You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (JIRA)" <ji...@apache.org> on 2019/04/03 15:44:00 UTC
[jira] [Commented] (IGNITE-11188) Optimize baseline autoadjustment
for in-memory clusters with zero timeout
[ https://issues.apache.org/jira/browse/IGNITE-11188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16808854#comment-16808854 ]
Ignite TC Bot commented on IGNITE-11188:
----------------------------------------
{panel:title=--> Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3488515&buildTypeId=IgniteTests24Java8_RunAll]
> Optimize baseline autoadjustment for in-memory clusters with zero timeout
> -------------------------------------------------------------------------
>
> Key: IGNITE-11188
> URL: https://issues.apache.org/jira/browse/IGNITE-11188
> Project: Ignite
> Issue Type: Improvement
> Reporter: Ivan Bessonov
> Assignee: Ivan Bessonov
> Priority: Major
> Labels: IEP-4, Phase-2
> Fix For: 2.8
>
>
> In current implementation (IGNITE-8571) zero-timeout case initiates two partition map exchanges on join/leave node events. This could be improved so that baseline is updated at the same time as join/leave event processing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)