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

Devesh Kumar Singh updated HDDS-12062:
--------------------------------------
    Description: 
Each background task in Recon should be able to restart back if it crashes for 
some unexpected error. Sometimes a workaround or data correction will fix the 
error, but Recon SCM tasks are not able to recover on their own once they 
encountered any run time error. System should be able to recover tasks on its 
own if error has been subsided.

 

cc: [~kkasawa] 

  was:
Each background task in Recon should be able to restart back if it crashes for 
some unexpected error. Sometimes a workaround or data correction will fix the 
error, but Recon SCM tasks are able to recover on their own once they 
encountered any run time error. System should be able to recover tasks on its 
own if error has been subsided.

 

cc: [~kkasawa] 


> Recon - Each background task in Recon should be able to restart back and 
> retried
> --------------------------------------------------------------------------------
>
>                 Key: HDDS-12062
>                 URL: https://issues.apache.org/jira/browse/HDDS-12062
>             Project: Apache Ozone
>          Issue Type: Task
>          Components: Ozone Recon
>    Affects Versions: 1.4.0
>            Reporter: Devesh Kumar Singh
>            Assignee: Devesh Kumar Singh
>            Priority: Major
>
> Each background task in Recon should be able to restart back if it crashes 
> for some unexpected error. Sometimes a workaround or data correction will fix 
> the error, but Recon SCM tasks are not able to recover on their own once they 
> encountered any run time error. System should be able to recover tasks on its 
> own if error has been subsided.
>  
> cc: [~kkasawa] 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to