djession edited a comment on issue #9087:
URL: https://github.com/apache/shardingsphere/issues/9087#issuecomment-767389449


   this is my server.yaml
   
   > governance:
   >   name: governance_ds
   >   registryCenter:
   >     type: etcd
   >     serverLists: http://192.168.183.132:2379
   >     props:
   >       retryIntervalMilliseconds: 500
   >       timeToLiveSeconds: 60
   >       maxRetries: 3
   >       operationTimeoutMilliseconds: 500
   >   overwrite: false
   > 
   > authentication:
   >   users:
   >     root:
   >       password: root
   >     sharding:
   >       password: sharding
   >       authorizedSchemas: sharding_db
   > 
   > props:
   >   max-connections-size-per-query: 1
   >   acceptor-size: 16  # The default value is available processors count * 2.
   >   executor-size: 16  # Infinite by default.
   >   proxy-frontend-flush-threshold: 128  # The default value is 128.
   >   proxy-transaction-type: LOCAL
   >   proxy-opentracing-enabled: false
   >   proxy-hint-enabled: false
   >   query-with-cipher-column: true
   >   sql-show: true
   >   check-table-metadata-enabled: false
   
   **hi,when i didn't used governance also get the same error**
   
   server.yaml
   > authentication:
   >   users:
   >     root:
   >       password: root
   >     sharding:
   >       password: sharding
   >       authorizedSchemas: sharding_db
   > 
   > props:
   >   max-connections-size-per-query: 1
   >   acceptor-size: 16  # The default value is available processors count * 2.
   >   executor-size: 16  # Infinite by default.
   >   proxy-frontend-flush-threshold: 128  # The default value is 128.
   >   proxy-transaction-type: LOCAL
   >   proxy-opentracing-enabled: false
   >   proxy-hint-enabled: false
   >   query-with-cipher-column: true
   >   sql-show: true
   >   check-table-metadata-enabled: false
   
   
   > mysql> show tables;
   > ERROR 2013 (HY000): Lost connection to MySQL server during query
   
   **this is my test procedure:**
   **_1.nitialize the table_**
   
   > mysql> show databases;
   > +---------------------+
   > | Database            |
   > +---------------------+
   > | replica_sharding_db |
   > +---------------------+
   > 1 row in set (0.01 sec)
   > 
   > mysql> use replica_sharding_db;
   > Database changed
   > mysql> create table t_order(user_id int not null,order_id bigint not null 
auto_increment primary key,status varchar(50))engine=innodb default 
charset=utf8;
   > Query OK, 0 rows affected (0.34 sec)
   > 
   > mysql> show tables;
   > +---------------------+
   > | Tables_in_demo_ds_0 |
   > +---------------------+
   > | t_order             |
   > +---------------------+
   > 1 row in set (0.01 sec)
   > 
   > mysql> insert into t_order(user_id,status) values(1,"sdf");
   > Query OK, 1 row affected (0.12 sec)
   > 
   > mysql> exit
   > Bye
   
   
   **_2.then reconnect the shardingproxy_**
   
   >  mysql -P3307 -h192.168.183.132 -uroot -p
   > Enter password:
   > Welcome to the MySQL monitor.  Commands end with ; or \g.
   > Your MySQL connection id is 2
   > Server version: 8.0.22-0ubuntu0.20.04.3-ShardingSphere-Proxy 5.0.0-RC1
   > 
   > Copyright (c) 2000, 2020, Oracle and/or its affiliates. All rights 
reserved.
   > 
   > Oracle is a registered trademark of Oracle Corporation and/or its
   > affiliates. Other names may be trademarks of their respective
   > owners.
   > 
   > Type 'help;' or '\h' for help. Type '\c' to clear the current input 
statement.
   > 
   > mysql> show databases;
   > +---------------------+
   > | Database            |
   > +---------------------+
   > | replica_sharding_db |
   > +---------------------+
   > 1 row in set (0.00 sec)
   > 
   > mysql> use replica_sharding_db;
   > Reading table information for completion of table and column names
   > You can turn off this feature to get a quicker startup with -A
   > 
   > Database changed
   > mysql> show tables;
   > ERROR 2013 (HY000): Lost connection to MySQL server during query
   > mysql>
   
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to