ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignite TC Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-10983) Check that persistenceEnabled is consistent on all nodes
Date Mon, 29 Apr 2019 14:54:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-10983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16829321#comment-16829321

Ignite TC Bot commented on IGNITE-10983:

{panel:title=--&gt; Run :: All: Possible Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}JDBC Driver{color} [[tests 0 TIMEOUT , Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=3712054]]

{color:#d04437}Platform .NET (Core Linux){color} [[tests 0 Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=3712056]]

[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3702897&amp;buildTypeId=IgniteTests24Java8_RunAll]

> Check that persistenceEnabled is consistent on all nodes
> --------------------------------------------------------
>                 Key: IGNITE-10983
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10983
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Stanislav Lukyanov
>            Assignee: Stepachev Maksim
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
> Currently it is possible to have a cluster where the same data region is persistent on
some nodes and not persistent on others. This use case doesn't have enough testing, so it's
better to deny it for now by adding a check for that and not allowing a node with a different
persistenceEnabled value to join the cluster.

This message was sent by Atlassian JIRA

View raw message