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

2022-04-14 Thread Pavel Tupitsyn (Jira)


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

Pavel Tupitsyn commented on IGNITE-16823:
-

Merged to main: 3ec4964003feafbf8f066dc4acac1f095c55f86c

> .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)


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

2022-04-13 Thread Igor Sapego (Jira)


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

Igor Sapego commented on IGNITE-16823:
--

[~ptupitsyn] looks good to me

> .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
>
>
> 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)