search

michelya / tungsten-replicator

Automatically exported from code.google.com/p/tungsten-replicator
0 stars 0 forks source link

WARNING from running trepctl services #30

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. run trepctl services
2. Check log file

What is the expected output? What do you see instead?
Nothing. Warning below complaining about wait_timeout.

What version of the product are you using? On what operating system?
2.0.2, CentOS 5.5, MySQL 5.1.56

Please provide any additional information below.

INFO   | jvm 1    | 2011/04/22 12:54:26 | 2011-04-22 12:54:25,985 INFO  
replicator.conf.PropertiesManager Reading static properties file: 
/opt/tungsten-replicator-2.0.2/cluster-home/bin/../../tungsten-replicator/conf/s
tatic-alpha.properties
INFO   | jvm 1    | 2011/04/22 12:54:26 | 2011-04-22 12:54:25,986 INFO  
replicator.conf.PropertiesManager Reading static properties file: 
/opt/tungsten-replicator-2.0.2/cluster-home/bin/../../tungsten-replicator/conf/s
tatic-beta.properties
INFO   | jvm 1    | 2011/04/22 12:54:26 | 2011-04-22 12:54:25,987 INFO  
replicator.conf.PropertiesManager Reading static properties file: 
/opt/tungsten-replicator-2.0.2/cluster-home/bin/../../tungsten-replicator/conf/s
tatic-charlie.properties
INFO   | jvm 1    | 2011/04/22 12:54:26 | 2011-04-22 12:54:25,989 INFO  
replicator.conf.PropertiesManager Reading static properties file: 
/opt/tungsten-replicator-2.0.2/cluster-home/bin/../../tungsten-replicator/conf/s
tatic-delta.properties
INFO   | jvm 1    | 2011/04/22 12:54:26 | Apr 22, 2011 12:54:26 PM 
org.drizzle.jdbc.internal.mysql.MySQLProtocol executeQuery
INFO   | jvm 1    | 2011/04/22 12:54:26 | WARNING: Could not execute query 
org.drizzle.jdbc.internal.common.query.DrizzleQuery@674009d2: Variable 
'wait_timeout' can't be set to the value of '99999999'

Original issue reported on code.google.com by t...@tslls.com on 22 Apr 2011 at 4:56

GoogleCodeExporter commented 9 years ago 
Max value of wait_timeout for linux is 31536000 and you have 99999999, I think 
that is the issue.

Original comment by t...@tslls.com on 22 Apr 2011 at 7:00

GoogleCodeExporter commented 9 years ago 
This value is strangely variable on different platforms.  I am going to set 
this to what appears to be the minimum common value, namely 2147483, according 
to published documentation from Oracle.  
(http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html#sysvar_wait
_timeout)

A better long-term fix would be to refresh connections after disuse.  This is 
somewhat more involved than one would think.  The replicator does not implement 
connection pooling in a way that would allow us to refresh or discard idle 
connections easily prior to next use.

Original comment by berkeley...@gmail.com on 23 Apr 2011 at 6:38

GoogleCodeExporter commented 9 years ago

Original comment by berkeley...@gmail.com on 23 Apr 2011 at 6:39

GoogleCodeExporter commented 9 years ago 
Value is now set to the minimum Windows value.  Passes tests and warnings are 
not seen on lab hosts.

Original comment by berkeley...@gmail.com on 26 Apr 2011 at 5:17