Problem/Motivation

If a big string is inserted into a MySQL / Maria DB BLOB field that exceeds 10% of the the innodb_log_file_size setting you get this error message:

The size of BLOB/TEXT data inserted in one transaction is greater than 10% of redo log size.

Like in #972528: dblog fails to log MAX_ALLOWED_PACKET errors because they're longer than MAX_ALLOWED_PACKET the complete error message contains the complete query itself that caused the error. Therefore it is impossible to succeed to log that exception in a MySQL dblog.

Proposed resolution

Like in #972528: dblog fails to log MAX_ALLOWED_PACKET errors because they're longer than MAX_ALLOWED_PACKET the error message needs to be truncated before written to dblog.

Remaining tasks

none

User interface changes

none

API changes

none

Data model changes

none

CommentFileSizeAuthor
#17 interdiff-15-17.txt2.65 KBgease
#17 2833100_50percent-17.patch6.17 KBgease
#15 interdiff-13-15.txt758 bytesgease
#15 2833100_50percent-15.patch5.3 KBgease
#13 2833100_50percent-13.patch4.85 KBgease
#4 2833100_50percent.patch4.92 KBmkalkbrenner
#2 2833100.patch4.92 KBmkalkbrenner
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mkalkbrenner created an issue. See original summary.

mkalkbrenner’s picture

mkalkbrenner
Primary language German
Location 🇩🇪
CreditAttribution: mkalkbrenner at bio.logis Genetic Information Management GmbH for OSCE: Organization for Security and Co-operation in Europe commented
Status: Active » Needs review
FileSize
2833100.patch4.92 KB

Status: Needs review » Needs work

The last submitted patch, 2: 2833100.patch, failed testing.

mkalkbrenner’s picture

mkalkbrenner
Primary language German
Location 🇩🇪
CreditAttribution: mkalkbrenner at bio.logis Genetic Information Management GmbH for OSCE: Organization for Security and Co-operation in Europe commented
Status: Needs work » Needs review
FileSize
2833100_50percent.patch4.92 KB

Status: Needs review » Needs work

The last submitted patch, 4: 2833100_50percent.patch, failed testing.

mkalkbrenner’s picture

mkalkbrenner
Primary language German
Location 🇩🇪
CreditAttribution: mkalkbrenner at bio.logis Genetic Information Management GmbH for OSCE: Organization for Security and Co-operation in Europe commented
Status: Needs work » Needs review

I have no idea, why the test doesn't force the exception on CI. In my local test environment it works.
Is it acceptable to provide such a trivial patch without a test?

As you can see in https://www.drupal.org/node/1679344#comment-11838038 the patch would be helpful.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

gease’s picture

gease
he/him
Primary language Russian
Location Praha
CreditAttribution: gease at bio.logis Genetic Information Management GmbH commented
FileSize
2833100_50percent-13.patch4.85 KB

Rerolled patch from #4 against 8.9.x .

Status: Needs review » Needs work

The last submitted patch, 13: 2833100_50percent-13.patch, failed testing. View results
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.

gease’s picture

gease
he/him
Primary language Russian
Location Praha
CreditAttribution: gease at bio.logis Genetic Information Management GmbH commented
FileSize
2833100_50percent-15.patch5.3 KB
interdiff-13-15.txt758 bytes

Fixed tests.

daffie’s picture

daffie CreditAttribution: daffie commented

@gease: Could you move the added test to its own method. I would like to help to get this issue fixed.

gease’s picture

gease
he/him
Primary language Russian
Location Praha
CreditAttribution: gease at bio.logis Genetic Information Management GmbH commented
Status: Needs work » Needs review
FileSize
2833100_50percent-17.patch6.17 KB
interdiff-15-17.txt2.65 KB

As per #16, moved innodb_max_log_size test into separate method. Not that I would understand clearly why we need to close connection and get it again at certain point, but otherwise the test hangs.

Status: Needs review » Needs work

The last submitted patch, 17: 2833100_50percent-17.patch, failed testing. View results
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.