ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Konstantinov (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (IGNITE-737) ClusterGroup.forDataNodes() returns empty cluster group for daemon node
Date Mon, 20 Apr 2015 04:06:58 GMT

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

Pavel Konstantinov edited comment on IGNITE-737 at 4/20/15 4:06 AM:
--------------------------------------------------------------------

1. Cache configuration is empty for nodes started after visor


was (Author: pkonstantinov):
Cache configuration is empty for nodes started after visor

> ClusterGroup.forDataNodes() returns empty cluster group for daemon node
> -----------------------------------------------------------------------
>
>                 Key: IGNITE-737
>                 URL: https://issues.apache.org/jira/browse/IGNITE-737
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: sprint-3
>            Reporter: Alexey Kuznetsov
>            Assignee: Pavel Konstantinov
>             Fix For: sprint-4
>
>         Attachments: ignite-737-test.patch, ignite-737.patch
>
>
> To reproduce:
> Start one ore several nodes with cache "A".
> Start daemon node.
> On daemon node execute ignite.cluster.forDataNodes("A").
> Returned projection should contain remote nodes with cache "A".
> Appropriate tests should also be added.
> Also it will be useful to check all cluster.forXXX() methods on daemon node.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message