LoggerThread should limit the number of characters used to log error messages
containing sql queries
----------------------------------------------------------------------------------------------------
Key: SEQUOIA-1113
URL: https://forge.continuent.org/jira/browse/SEQUOIA-1113
Project: Sequoia
Type: Improvement
Versions: sequoia 2.10.10
Reporter: Stephane Giron
Assigned to: Stephane Giron
Fix For: sequoia 2.10.11
If such an error occurs, such as :
com.mysql.jdbc.PacketTooBigException: Packet for query is too large (4622325 >
1048576). You can change this value on the server by setting the
max_allowed_packet' variable.
at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:2655)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1604)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1715)
at com.mysql.jdbc.Connection.execSQL(Connection.java:3249)
at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1268)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1541)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1455)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1440)
at
org.continuent.sequoia.controller.recoverylog.events.LogRequestEvent.execute(LogRequestEvent.java:104)
at
org.continuent.sequoia.controller.recoverylog.LoggerThread.run(LoggerThread.java:678)
the full request is logged into full_cluster.log. This is not very convenient
with 4 MB queries, for example. The number of logged characters for the query
should be limited, for example with the sqlDumpLength size from the virtual
database.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
