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

Alexander Lapin updated IGNITE-15161:
-------------------------------------
    Description: 
During the work on https://issues.apache.org/jira/browse/IGNITE-15278, the 
general flow of the components start and stop was introduced.

It is needed to implement a stop mechanism for every component. 

The main points that should be considered during the implementation of 
component's stop: 
* All threads should be stopped properly
* All Executors should be shutdown
* All public methods should be guarded by read lock, stop should be done using 
write lock.

  was:
During the work on https://issues.apache.org/jira/browse/IGNITE-15278, the 
general flow of the components start and stop was introduced.

It is needed to implement a stop mechanism for every component. 

The main points that should be considered during the implementation of 
component's stop: 
* All threads should be stopped properly
* All Executors should be shutdown
* All public methods should be guarded by read lock, stop should be done using 
write lock.

A


> Implement component's stop
> --------------------------
>
>                 Key: IGNITE-15161
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15161
>             Project: Ignite
>          Issue Type: Epic
>            Reporter: Alexander Lapin
>            Assignee: Alexander Lapin
>            Priority: Major
>              Labels: ignite-3
>   Original Estimate: 120h
>          Time Spent: 10m
>  Remaining Estimate: 119h 50m
>
> During the work on https://issues.apache.org/jira/browse/IGNITE-15278, the 
> general flow of the components start and stop was introduced.
> It is needed to implement a stop mechanism for every component. 
> The main points that should be considered during the implementation of 
> component's stop: 
> * All threads should be stopped properly
> * All Executors should be shutdown
> * All public methods should be guarded by read lock, stop should be done 
> using write lock.



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

Reply via email to