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 2020/06/02 13:36:00 UTC

[jira] [Commented] (IGNITE-13106) Java thin client: Race between response and notification for compute tasks

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

Ignite TC Bot commented on IGNITE-13106:
----------------------------------------

{panel:title=Branch: [pull/7885/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--&gt; Run :: Basic Tests* Results|https://ci.ignite.apache.org/viewLog.html?buildId=5357718&amp;buildTypeId=IgniteTests24Java8_RunBasicTests]

> Java thin client: Race between response and notification for compute tasks 
> ---------------------------------------------------------------------------
>
>                 Key: IGNITE-13106
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13106
>             Project: Ignite
>          Issue Type: Bug
>          Components: thin client
>    Affects Versions: 2.9
>            Reporter: Aleksey Plekhanov
>            Assignee: Aleksey Plekhanov
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Java thin client {{ClientCompute.execute()}} methodĀ can hang due to race between processing of COMPUTE_TASK_EXECUTE responseĀ and COMPUTE_TASK_FINISHED notification.
> These messages are strongly ordered on the server-side. But on the client-side response and notification are processed by different threads. If notification will be processed before response, task future will never be completed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)