Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-10154

Critical worker liveness check configuration is non-trivial and inconsistent

    XMLWordPrintableJSON

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.7
    • Fix Version/s: 2.7
    • Component/s: None
    • Labels:
    • Ignite Flags:
      Docs Required

      Description

      The way the critical thread liveness check is configured has a number of usability issues.

      1) By default, the liveness check is disabled (i.e. if no failure handler is specified in the configuration). However, if you specify any handler (including the default one), liveness check gets enabled (which is something the users may not want) unless you disable it explicitly.

      2) Users that use Ignite 2.6 with a configured failure handler will get this check enabled after migrating to Ignite 2.7.

      In the two cases above, the functionality changes in a non-trivial way. Ideally, we need an option that enables this functionality explicitly. A possible example would be to keep liveness check disabled until the user sets the systemWorkerBlockedTimeout to a positive value. (Or the other way around: enable liveness check by default until the user explicitly disables it).

        Attachments

          Activity

            People

            • Assignee:
              agura Andrey N. Gura
              Reporter:
              Artem Budnikov Artem Budnikov
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: