You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Pavel Tupitsyn (Jira)" <ji...@apache.org> on 2022/04/15 07:13:00 UTC

[jira] [Updated] (IGNITE-16823) .NET: Thin 3.0: Compute cluster awareness

     [ https://issues.apache.org/jira/browse/IGNITE-16823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Tupitsyn updated IGNITE-16823:
------------------------------------
    Ignite Flags: Release Notes Required  (was: Docs Required,Release Notes Required)

> .NET: Thin 3.0: Compute cluster awareness
> -----------------------------------------
>
>                 Key: IGNITE-16823
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16823
>             Project: Ignite
>          Issue Type: Improvement
>          Components: platforms, thin client
>    Affects Versions: 3.0.0-alpha5
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-alpha5
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently, all Compute operations go through the default node. Improve client compute with cluster awareness:
> * Correspond client connections with node id (extend handshake)
> * *Compute.Execute*: match specified set of nodes against active connections. If there are matches, pick random. Otherwise, use default connection and let the server handle node mapping.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)