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

Posted to issues@ignite.apache.org by "Sergey Chugunov (Jira)" <ji...@apache.org> on 2022/06/03 05:04:00 UTC

[jira] [Updated] (IGNITE-16636) Use busy-lock approach to guard stopping RestComponent

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

Sergey Chugunov updated IGNITE-16636:
-------------------------------------
    Fix Version/s: 3.0.0-alpha6
                       (was: 3.0.0-alpha5)

> Use busy-lock approach to guard stopping RestComponent
> ------------------------------------------------------
>
>                 Key: IGNITE-16636
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16636
>             Project: Ignite
>          Issue Type: Improvement
>          Components: rest
>            Reporter: Roman Puchkovskiy
>            Assignee: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-alpha6
>
>
> We usually use a lock to make sure that
>  # A stop request does not interfere with the component service requests started before the stop request
>  # When a stop request starts being executed, no service request can be executed anymore
> It probably makes sense to implement the same logic in RestComponent as well.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)