Alibaba CORBA timeout

00:32:26, 258 warn [thread = Processor1-E15, class = serverconnection, host = 10.1.1.91, Port = 2441, schema = facebook_onlinegame_db] global_new.default {show full tables like 'probablynot '}
Java. util. Concurrent. timeoutexception
At java. util. Concurrent. futuretask $ sync. innerget (futuretask. Java: 228)
At java. util. Concurrent. futuretask. Get (futuretask. Java: 91)
At com. Alibaba. Cobar. server. node. mysqlchannel. Connect (mysqlchannel. Java: 185)
At com. Alibaba. Cobar. server. node. mysqldatasource. getchannel (mysqldatasource. Java: 156)
At com. Alibaba. Cobar. server. node. mysqldatanode. getchannel (mysqldatanode. Java: 115)
At com. Alibaba. Cobar. server. node. mysqldatanode. getchannel (mysqldatanode. Java: 107)
At com.alibaba.cobar.server.exe cutor. multinodeexecutor $ 3.run( multinodeexecutor. Java: 206)
At java. util. Concurrent. threadpoolexecutor $ worker. runtask (threadpoolexecutor. Java: 886)
At java. util. Concurrent. threadpoolexecutor $ worker. Run (threadpoolexecutor. Java: 908)
At java. Lang. thread. Run (thread. Java: 662)

Recently, we found that the stout. sometimes warning-level logs appear to be time out exceptions when a network link is created. Therefore, the source code of checkout CORBA traces the corresponding code lines and finds that it is indeed an exception caused by timeout, the corresponding parameters provided by CORBA are configured for this time. Therefore, the Time Out is set to 60 seconds. The original value of this parameter is 10 seconds. Further analysis, I think the reason may be that the company uses VPN, and the connection to the database is also through VPN. Due to the unstable network, the new connection times out.

The corresponding timeout settings of CORBA. In schema. XML, the datanode node waittimeout attribute

<! -- The data node consists of the master and slave data sources, heartbeat, connection pool, and other configurations. --> <Datanode name = "dn_shards"> <property name = "datasource"> <! -- The first line of datasourceref indicates the primary data source --> <! -- The primary data sources of the three data nodes can be separated by commas (,). The abbreviation $1-3 is supported, indicating ds_shard_master [1], ds_shard_master [2], ds_shard_master [3] --> <datasourceref> facebook_onlinegame_ds_shards [0], facebook_onlinegame_ds_shards $1-3 </datasourceref> <! -- The second row of datasourceref indicates the backup data source --> <! -- <Datasourceref> ds_single_slave </datasourceref> --> <! -- If you need one master node and multiple slave nodes, you can configure the second backup data source in the third row, and so on --> <! -- <Datasourceref> ds_single_slave2 </datasourceref> --> </property> <! -- Cobar and backend data source connection pool size settings --> <property name = "poolsize"> 16 </property> <! -- Cobar uses heartbeat to implement the ha of the backend data source. Once the heartbeat of the primary data source fails, it switches to the backup data source to work. --> <! -- Cobar heartbeat is an SQL statement executed to the backend data source, determine the running status of the data source based on the returned results of this statement --> <property name = "Heartbeat"> select 1 </property> <property name = "waittimeout"> 60000 </property> </datanode>