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

Make Nuxeo startup fail when another node has the same clustering id

    XMLWordPrintable

    Details

    • Release Notes Summary:
      Nuxeo startup fails when another node has the same clustering id
    • Backlog priority:
      700
    • Upgrade notes:
      Hide

      If a node is started when a node with the same repository.clustering.id already exists (or crashed, maybe the same node), an exception will be thrown at startup:

      ERROR [RegistrationInfoImpl] Component service:org.nuxeo.ecm.core.repository.RepositoryServiceComponent notification of application started failed:
      Failed to initialize clustering for repository: default,
      Duplicate cluster node with id: 1234 (a crashed node must be cleaned up, or the repository.clustering.id configuration fixed)

      Show
      If a node is started when a node with the same repository.clustering.id already exists (or crashed, maybe the same node), an exception will be thrown at startup: ERROR [RegistrationInfoImpl] Component service:org.nuxeo.ecm.core.repository.RepositoryServiceComponent notification of application started failed: Failed to initialize clustering for repository: default, Duplicate cluster node with id: 1234 (a crashed node must be cleaned up, or the repository.clustering.id configuration fixed)
    • Sprint:
      nxcore 9.3.9
    • Story Points:
      2

      Description

      Having two or more nodes configured with the same value for the property repository.clustering.id is an important configuration mistake which should make the startup fail, because the propagation of the invalidations is not guaranteed any more.

      Adding a primary key on the nodeid column of cluster_nodes table could be a solution.

      If possible, the solution should take into account tow to apply this change on an existing database?

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 3 hours
                  3h

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.