Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.9
    • None
    • Docs Required, Release Notes Required

    Description

      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:

      • Compute task

      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.

      Attachments

        Issue Links

          Activity

            People

              nizhikov Nikolay Izhikov
              nizhikov Nikolay Izhikov
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m