Does anybody know what this error means: Missing cached payload in retry response.
It happened to me over the weekend when running a statement of the form:
INSERT INTO table1(fields) SELECT fields FROM table2 ON DUPLICATE KEY UPDATE f1=VALUES(f1)
This can be slow if there is a lot of data to move, but in this case, it couldn't have taken longer than about 400 seconds..... This was being done from a Java program using the cloud sql JDBC driver.
Has anybody else seen this error (it only appears in one distinct search result)?
Is there anything that I can do (apart from retrying) to make this go away?
Thanks, Philip
The full traceback is
Caused by: java.sql.SQLException: Missing cached payload in retry response.
#011at com.google.cloud.sql.jdbc.internal.Exceptions.newSqlException(Exceptions.java:129)
#011at com.google.cloud.sql.jdbc.internal.SqlProtoClient.toCachedExecResponse(SqlProtoClient.java:288)
#011at com.google.cloud.sql.jdbc.internal.SqlProtoClient.access$700(SqlProtoClient.java:34)
#011at com.google.cloud.sql.jdbc.internal.SqlProtoClient$ExecHelper.retry(SqlProtoClient.java:364)
#011at com.google.cloud.sql.jdbc.internal.SqlProtoClient$ExecHelper.run(SqlProtoClient.java:324)
#011at com.google.cloud.sql.jdbc.internal.SqlProtoClient.executeSql(SqlProtoClient.java:85)
#011at com.google.cloud.sql.jdbc.internal.SqlProtoClient.executeSql(SqlProtoClient.java:76)
#011at com.google.cloud.sql.jdbc.Connection.executeSql(Connection.java:520)
#011at com.google.cloud.sql.jdbc.Statement.executeSqlImpl(Statement.java:280)
#011at com.google.cloud.sql.jdbc.Statement.executeImpl(Statement.java:154)
#011at com.google.cloud.sql.jdbc.Statement.execute(Statement.java:142)