Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-18032

MDEV-15611 apparently still occuring with MariaDB 10.2.16

Details

    Description

      Still seen on a MariaDB 10.2.16 instance, although it was supposed to be fixed with 10.2.15

      "Could not execute Delete_rows_v1 event on table ...; Cannot delete or update a parent row: a foreign key constraint fails"

      and node being shut down after four failed retries.

      Attachments

        Issue Links

          Activity

            I could not yet repeat the issue so I would need some additional information from the customer.

            (1) galera configuration
            (2) show create table bamboo-gs.VCS_LOCATION;
            (3) REFERENCES VCS_LOCATION (`VCS_LOCATION_ID`)) looks like a self reference is that true ?
            (4) When this problem happened did user check from effected node
            database is there really offending row that would cause delete to fail ?
            (6) what is value of wsrep_sync_wait configuration variable ?

            jplindst Jan Lindström (Inactive) added a comment - I could not yet repeat the issue so I would need some additional information from the customer. (1) galera configuration (2) show create table bamboo-gs.VCS_LOCATION; (3) REFERENCES VCS_LOCATION (`VCS_LOCATION_ID`)) looks like a self reference is that true ? (4) When this problem happened did user check from effected node database is there really offending row that would cause delete to fail ? (6) what is value of wsrep_sync_wait configuration variable ?

            People

              jplindst Jan Lindström (Inactive)
              hholzgra Hartmut Holzgraefe
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.