[jira] [Updated] (IGNITE-13901) [IEP-39] Management API to remove metastore key.

["Nikolay Izhikov (Jira)" <ji...@apache.org>]

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

Nikolay Izhikov updated IGNITE-13901:
-------------------------------------
    Description: 
Ignite provides metastore for internal components or plugins to store some information.
There is some scenario when by-hand removal from metastore required.

  1. Blocker bug - we delete some class that was written to metastore from the new version.
  2. Migration between custom Ignite distributions where one of them has a custom class and the other doesn’t.


We should provide to the cluster administrator the ability to remove any key from the metastore.
JMX beans to remove metastore key should be introduced:

In the scope of IEP-35 System view API introduced.
A new API should use the same identifier that is used in the corresponding System View(metastore, distributed_metastore).

  was:
Ignite provides many API to deploy and execute user-provided code on the server nodes inside the same JVM as the Ignite process runs.
Ignite has many APIs that allocate many resources on the server nodes, also. 
In case of some buggy code that consumes many system resources(CPU, RAM, flood network) or heavy query the whole cluster can become unstable.

We should provide to the cluster administrator the ability to stop any user deployed task.

JMX beans to cancel listed tasks should be introduced:

* SQL queries.

In the scope of IEP-35 System view API introduced.
A new API should use the same identifier that is used in corresponding System View.


> [IEP-39] Management API to remove metastore key.
> ------------------------------------------------
>
>                 Key: IGNITE-13901
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13901
>             Project: Ignite
>          Issue Type: Sub-task
>            Reporter: Nikolay Izhikov
>            Assignee: Nikolay Izhikov
>            Priority: Major
>              Labels: IEP-39
>             Fix For: 2.9
>
>
> Ignite provides metastore for internal components or plugins to store some information.
> There is some scenario when by-hand removal from metastore required.
>   1. Blocker bug - we delete some class that was written to metastore from the new version.
>   2. Migration between custom Ignite distributions where one of them has a custom class and the other doesn’t.
> We should provide to the cluster administrator the ability to remove any key from the metastore.
> JMX beans to remove metastore key should be introduced:
> In the scope of IEP-35 System view API introduced.
> A new API should use the same identifier that is used in the corresponding System View(metastore, distributed_metastore).



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