[MAGNOLIA-2913] MySQL "max-packet-size" causes corrupt nodes Created: 29/Oct/09 Updated: 29/Oct/09 Resolved: 29/Oct/09 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 4.1.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Rainer Blumenthal | Assignee: | Jan Haderka |
| Resolution: | Not an issue | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
If you upload e.g. a PDF that is 9 MB with a "max_allowed_packet" of 8 MB you get nodes that you cant delete anymore - all in all you get a corrupted repository. The Rollback fails... (we didn't use InnoDB in our case - maybe that helps) Maybe this is not a magnolia issue - but i am not completely sure. |
| Comments |
| Comment by Jan Haderka [ 29/Oct/09 ] |
|
Hi Rainer, Regarding the corruption of the node caused by too small packet size, I suspect you are using MySQL with the MyISAM instead of InnoDB, is that so? |