[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Haderka closed MAGNOLIA-2913.
---------------------------------
Resolution: Not an issue
Hi Rainer,
it is a known fact and the {{max_allowed_packet}} parameter settings is
mentioned in
http://wiki.magnolia-cms.com/display/WIKI/MySQL+Persistence?focusedCommentId=26804366#comment-26804366
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?
> MySQL "max-packet-size" causes corrupt nodes
> --------------------------------------------
>
> Key: MAGNOLIA-2913
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2913
> Project: Magnolia
> Issue Type: Bug
> Affects Versions: 4.1.1
> Reporter: Rainer Blumenthal
> Assignee: Boris Kraft
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
