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

Sergey Chugunov updated IGNITE-17002:
-------------------------------------
    Description: 
Now Ignite supports entering Maintenance Mode after index corruption 
automatically - this was implemented in linked issue.

But there are use-cases when user needs to request rebuilding specific indexes 
in MM, so we need to provide a control.sh API to make these requests.

Also for better integration with monitoring tools it is nice to provide an API 
to check status of rebuilding task and print message to logs when each task is 
finished and all tasks are finished.

  was:
Now Ignite supports entering Maintenance Mode after index corruption 
automatically.

 

But there are use-cases when user needs to request rebuilding specific indexes 
in MM, so we need to provide a control.sh API to make these requests.

 

Also for better integration with monitoring tools it is nice to provide an API 
to check status of rebuilding task and print message to logs when each task is 
finished and all tasks are finished.


> Indexes rebuild in Maintenance Mode
> -----------------------------------
>
>                 Key: IGNITE-17002
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17002
>             Project: Ignite
>          Issue Type: Improvement
>          Components: control.sh, persistence
>            Reporter: Sergey Chugunov
>            Priority: Major
>             Fix For: 2.14
>
>
> Now Ignite supports entering Maintenance Mode after index corruption 
> automatically - this was implemented in linked issue.
> But there are use-cases when user needs to request rebuilding specific 
> indexes in MM, so we need to provide a control.sh API to make these requests.
> Also for better integration with monitoring tools it is nice to provide an 
> API to check status of rebuilding task and print message to logs when each 
> task is finished and all tasks are finished.



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

Reply via email to