Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-20418

nuxeoctl start should be in strict mode by default

    XMLWordPrintable

    Details

    • Epic Link:
    • Tags:
    • Backlog priority:
      100
    • Upgrade notes:
      Hide

      nuxeoctl now starts a Nuxeo server in strict mode by default.

      --force and --strict have no impact.

      To start a Nuxeo server but aborting in error the start command when a component cannot be activated or if a server is already running, use the --lenient option.

      $ nuxeoctl start --lenient
      Show
      nuxeoctl now starts a Nuxeo server in strict mode by default. --force and --strict have no impact. To start a Nuxeo server but aborting in error the start command when a component cannot be activated or if a server is already running, use the --lenient option. $ nuxeoctl start --lenient
    • Team:
      PLATFORM
    • Sprint:
      nxplatform 11.1.20
    • Story Points:
      2

      Description

      Allowing a Nuxeo instance to start with undeployed component can be risky, especially in cluster mode.
      For instance if you start a new instance to share a big load of async jobs, if for any reasons the repository fails to deploy the instance will drain the job queue without being able to execute any jobs.

        Attachments

          Issue Links

          depends on

          Improvement - An improvement or enhancement to an existing feature or task. NXP-17707 Add a way to report warning on nuxeoctl status

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          is duplicated by

          New Feature - A new feature of the product, which has yet to be developed. NXP-19331 Improve Runtime Contributions Error/Debug/Test management

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. NXP-16490 Tighten Nuxeo Runtime

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Sub-task - The sub-task of the issue NXP-16641 adapt the distribution for running in strict mode

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. NXP-28678 nuxeoctl shouldn't hang in strict mode

          • Major - Major loss of function.
          • Resolved
          is required by

          Bug - A problem which impairs or prevents the functions of the product. NXP-28020 Nuxeo still starts when ChronicleLogTailer fails to start

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 5 hours
                  5h