You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2020/07/10 12:05:34 UTC

[GitHub] [shardingsphere] Simbafa opened a new issue #6324: ShardingSphere-Proxy stop working

Simbafa opened a new issue #6324:
URL: https://github.com/apache/shardingsphere/issues/6324


   ### Which version of ShardingSphere did you use?
   Shardingsphere-ui-4.1.1
   Previous version 4.0.0-RC1 also has the same issue.
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   ShardingSphere-Proxy
   ### Expected behavior
   ShardingSphere-Proxy can receive connection and process sql statements.
   ### Actual behavior
   ShardingSphere-Proxy continues to receive connections, and the connections all logined successfully.
   But it stops here. It doesn't process the following sql statements.
   
   Following is part of the outputs(We modified according our purpose). 
   ```
   [INFO ] 19:49:41.596 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xd66b03e6, L:/0.0.0.0:3307] READ: [id: 0x60558169, L:/192.168.1.46:3307 - R:/192.168.1.46:44510]
   [INFO ] 19:49:41.597 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xd66b03e6, L:/0.0.0.0:3307] READ COMPLETE
   [INFO ] 19:49:41.601 [epollEventLoopGroup-3-2] o.a.s.s.f.m.a.MySQLAuthenticationEngine - ===Username: amRiYzpteXNxbDovLzE5Mi4xNjguMC4xMDg6MzMwNi90ZXN0P3VzZXI9cm9vdCZwYXNzd29yZD10ZXN0JnNlcnZlclRpbWV6b25lPVVUQyZ1c2VTU0w9ZmFsc2U=
   [INFO ] 19:49:41.601 [epollEventLoopGroup-3-2] o.a.s.s.f.m.a.MySQLAuthenticationEngine - ===Auth  connection url=jdbc:mysql://192.168.0.108:3306/test?user=root&password=test&serverTimezone=UTC&useSSL=false
   [INFO ] 19:49:41.602 [epollEventLoopGroup-3-2] o.a.s.s.f.m.a.MySQLAuthenticationEngine - ===Login succeed
   [INFO ] 19:49:44.597 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xd66b03e6, L:/0.0.0.0:3307] READ: [id: 0xafd94de4, L:/192.168.1.46:3307 - R:/192.168.1.46:44512]
   [INFO ] 19:49:44.597 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xd66b03e6, L:/0.0.0.0:3307] READ COMPLETE
   [INFO ] 19:49:44.601 [epollEventLoopGroup-3-3] o.a.s.s.f.m.a.MySQLAuthenticationEngine - ===Username: amRiYzpteXNxbDovLzE5Mi4xNjguMC4xMDg6MzMwNi90ZXN0P3VzZXI9cm9vdCZwYXNzd29yZD10ZXN0JnNlcnZlclRpbWV6b25lPVVUQyZ1c2VTU0w9ZmFsc2U=
   [INFO ] 19:49:44.602 [epollEventLoopGroup-3-3] o.a.s.s.f.m.a.MySQLAuthenticationEngine - ===Auth  connection url=jdbc:mysql://192.168.0.108:3306/test?user=root&password=test&serverTimezone=UTC&useSSL=false
   [INFO ] 19:49:44.602 [epollEventLoopGroup-3-3] o.a.s.s.f.m.a.MySQLAuthenticationEngine - ===Login succeed
   ```
   After the client application is killed. The blocked sql statement will be processed.
   ```
   [INFO ] 19:50:06.662 [ShardingSphere-Command-1] o.a.s.s.b.c.j.w.StatementExecutorWrapperJustep - ===Modified Sql:SELECT * FROM sa_taskrelation
   [INFO ] 19:50:06.662 [ShardingSphere-Command-2] o.a.s.s.f.m.c.MySQLCommandExecutorFactory - Execute packet type: COM_QUERY, value: MySQLComQueryPacket(sql=select * from sa_sign)
   [INFO ] 19:50:06.662 [ShardingSphere-Command-2] o.a.s.s.b.c.j.w.StatementExecutorWrapperJustep - ===Modified Sql:SELECT * FROM sa_sign
   [INFO ] 19:50:06.662 [ShardingSphere-Command-0] o.a.s.s.f.m.c.MySQLCommandExecutorFactory - Execute packet type: COM_QUERY, value: MySQLComQueryPacket(sql=select * from document_subscriptions)
   [INFO ] 19:50:06.663 [ShardingSphere-Command-0] o.a.s.s.b.c.j.w.StatementExecutorWrapperJustep - ===Modified Sql:SELECT * FROM document_subscriptions
   [INFO ] 19:50:06.663 [ShardingSphere-Command-3] o.a.s.s.f.m.c.MySQLCommandExecutorFactory - Execute packet type: COM_QUERY, value: MySQLComQueryPacket(sql=select * from selectionlist_data)
   [INFO ] 19:50:06.664 [ShardingSphere-Command-1] o.a.s.s.f.m.c.MySQLCommandExecutorFactory - Execute packet type: COM_QUERY, value: MySQLComQueryPacket(sql=select * from sa_remindactionparameter)
   [INFO ] 19:50:06.664 [ShardingSphere-Command-3] o.a.s.s.b.c.j.w.StatementExecutorWrapperJustep - ===Modified Sql:SELECT * FROM selectionlist_data
   ```
   
   ### Reason analyze (If you can)
   
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
   The test client application is a multi-thread application.
   In a thread, it does following work.
   1. connection to shardingsphere-proxy
   2. get all table names of the database.
   3. for each table, executeQuery("select * from " + tablename) and print the result set, sleep 2 seconds.
   4. close the connection
   5. goto 1
   
   100 threads are created to test.
   when shardingsphere-proxy is blocked, part of the client outputs:
   ```
   Fri Jul 10 19:49:27 CST 2020 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
   ```
   It seems client is connecting to server, but cannot get response.
   ### Example codes for reproduce this issue (such as a github link).
   


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [shardingsphere] Simbafa commented on issue #6324: ShardingSphere-Proxy stop working

Posted by GitBox <gi...@apache.org>.
Simbafa commented on issue #6324:
URL: https://github.com/apache/shardingsphere/issues/6324#issuecomment-658127189


   > Can you help to do a test using proxy.frontend.flush.threshold: 2 ? If water mark didn't take effect, this case will block the proxy.
   
   I run the test application with 150 threads, Sharding-Proxy works well.


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [shardingsphere] Simbafa commented on issue #6324: ShardingSphere-Proxy stop working

Posted by GitBox <gi...@apache.org>.
Simbafa commented on issue #6324:
URL: https://github.com/apache/shardingsphere/issues/6324#issuecomment-657516488


   ![20200713194357](https://user-images.githubusercontent.com/37646009/87301752-b5648a80-c542-11ea-8f1a-f5cfc1c501f2.png)
   


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [shardingsphere] tuohai666 commented on issue #6324: ShardingSphere-Proxy stop working

Posted by GitBox <gi...@apache.org>.
tuohai666 commented on issue #6324:
URL: https://github.com/apache/shardingsphere/issues/6324#issuecomment-657513553


   OK. Can you provide the log with the property sql.show: true of querying big blob data?


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [shardingsphere] Simbafa commented on issue #6324: ShardingSphere-Proxy stop working

Posted by GitBox <gi...@apache.org>.
Simbafa commented on issue #6324:
URL: https://github.com/apache/shardingsphere/issues/6324#issuecomment-657999154


   Hi @tuohai666 ,
   
   when sharding-proxy stops response, backconnection is waiting something.
   
   ![LOCK](https://user-images.githubusercontent.com/37646009/87392676-851ef980-c5df-11ea-801d-857bf2f870d8.jpg)
   


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [shardingsphere] tuohai666 commented on issue #6324: ShardingSphere-Proxy will be blocked when query big blob data

Posted by GitBox <gi...@apache.org>.
tuohai666 commented on issue #6324:
URL: https://github.com/apache/shardingsphere/issues/6324#issuecomment-658211334


   @Simbafa Thanks for your analysis and all the test.
   The root cause of this problem is due to unreached notify to proxy.
   
   Codes in MySQLCommandExecuteEngine:
   ```
   1     context.flush();
   2     backendConnection.getResourceSynchronizer().doAwait();
   ```
   Proxy might be starting to **begin** notify() after the 1st line ended before wait(). The notify will be back before or after the 2nd line.
   If after the 2nd line, everything goes well. Otherwise, the thread will never be awakened by notify.
   I have submitted a pr to resolve this problem by adding a timer to wait.
   


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [shardingsphere] tuohai666 commented on issue #6324: ShardingSphere-Proxy stop working

Posted by GitBox <gi...@apache.org>.
tuohai666 commented on issue #6324:
URL: https://github.com/apache/shardingsphere/issues/6324#issuecomment-658109825


   @Simbafa 
   
   > When the blob data size is small, everything is Ok.
   > But When I increased the blob data size to 900K+, Sharding-Proxy will stop response soonly.
   
   When you increased the blob data size to 900K, all of the client threads will query this table right? But Sharding-Proxy will not stop immediately but stopped soonly?
   
   Can you help to use 1 client thread to query this table with 900K size column? I want to make sure whether proxy will stop for every query.


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [shardingsphere] Simbafa commented on issue #6324: ShardingSphere-Proxy stop working

Posted by GitBox <gi...@apache.org>.
Simbafa commented on issue #6324:
URL: https://github.com/apache/shardingsphere/issues/6324#issuecomment-656643302


   Correct process log output like this:
   
   ```
   [INFO ] 20:09:31.298 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0x1fbb6b60] REGISTERED
   [INFO ] 20:09:31.305 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0x1fbb6b60] BIND: 0.0.0.0/0.0.0.0:3307
   [INFO ] 20:09:31.309 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0x1fbb6b60, L:/0.0.0.0:3307] ACTIVE
   [INFO ] 20:09:36.153 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0x1fbb6b60, L:/0.0.0.0:3307] READ: [id: 0x2007074d, L:/192.168.1.46:3307 - R:/192.168.1.46:44530]
   [INFO ] 20:09:36.157 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0x1fbb6b60, L:/0.0.0.0:3307] READ COMPLETE
   [INFO ] 20:09:36.543 [epollEventLoopGroup-3-1] o.a.s.s.f.m.a.MySQLAuthenticationEngine - ===Username: amRiYzpteXNxbDovLzE5Mi4xNjguMC4xMDg6MzMwNi90ZXN0P3VzZXI9cm9vdCZwYXNzd29yZD10ZXN0JnNlcnZlclRpbWV6b25lPVVUQyZ1c2VTU0w9ZmFsc2U=
   [INFO ] 20:09:36.666 [epollEventLoopGroup-3-1] o.a.s.s.f.m.a.MySQLAuthenticationEngine - ===Auth  connection url=jdbc:mysql://192.168.0.108:3306/test?user=root&password=test&serverTimezone=UTC&useSSL=false
   [INFO ] 20:09:36.668 [epollEventLoopGroup-3-1] o.a.s.s.f.m.a.MySQLAuthenticationEngine - ===Create schema of database=test for 8d232dd2081bf9758e9a40659b84efe7
   [INFO ] 20:09:36.910 [epollEventLoopGroup-3-1] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
   [INFO ] 20:09:37.446 [epollEventLoopGroup-3-1] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
   [INFO ] 20:09:37.472 [epollEventLoopGroup-3-1] ShardingSphere-metadata - Get all table names
   [INFO ] 20:09:37.562 [epollEventLoopGroup-3-1] o.a.s.s.f.m.a.MySQLAuthenticationEngine - ===Login succeed
   [INFO ] 20:09:37.646 [ShardingSphere-Command-0] o.a.s.s.f.m.c.MySQLCommandExecutorFactory - Execute packet type: COM_QUERY, value: MySQLComQueryPacket(sql=/* mysql-connector-java-5.1.47 ( Revision: fe1903b1ecb4a96a917f7ed3190d80c049b1de29 ) */SELECT  @@session.auto_increment_increment AS auto_increment_increment, @@character_set_client AS character_set_client, @@character_set_connection AS character_set_connection, @@character_set_results AS character_set_results, @@character_set_server AS character_set_server, @@collation_server AS collation_server, @@collation_connection AS collation_connection, @@init_connect AS init_connect, @@interactive_timeout AS interactive_timeout, @@license AS license, @@lower_case_table_names AS lower_case_table_names, @@max_allowed_packet AS max_allowed_packet, @@net_buffer_length AS net_buffer_length, @@net_write_timeout AS net_write_timeout, @@sql_mode AS sql_mode, @@system_time_zone AS system_time_zone, @@time_zone AS time_zone, @@transaction_isolation AS transaction_isolation, @@wait_timeout AS wait_timeout)
   [INFO ] 20:09:38.650 [ShardingSphere-Command-0] o.a.s.s.b.c.j.w.StatementExecutorWrapperJustep - ===Modified Sql:SELECT '1' AS auto_increment_increment, 'utf8' AS character_set_client, 'utf8' AS character_set_connection, 'utf8' AS character_set_results, 'utf8' AS character_set_server , 'latin_swedish_ci' AS collation_server, 'utf8_general_ci' AS collation_connection, NULL AS init_connect, 28800 AS interactive_timeout, 'GPL' AS license , 0 AS lower_case_table_names, 67108864 AS max_allowed_packet, 16384 AS net_buffer_length, 60 AS net_write_timeout, 'ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION' AS sql_mode , 'UTC' AS system_time_zone, 'SYSTEM' AS time_zone, 'REPEATABLE-READ' AS transaction_isolation, 28800 AS wait_timeout
   [INFO ] 20:09:38.737 [ShardingSphere-Command-1] o.a.s.s.f.m.c.MySQLCommandExecutorFactory - Execute packet type: COM_QUERY, value: MySQLComQueryPacket(sql=SET character_set_results = NULL)
   [INFO ] 20:09:38.755 [ShardingSphere-Command-1] o.a.s.s.b.c.j.w.StatementExecutorWrapperJustep - ===Modified Sql:SELECT 'x'
   [INFO ] 20:09:38.769 [ShardingSphere-Command-2] o.a.s.s.f.m.c.MySQLCommandExecutorFactory - Execute packet type: COM_QUERY, value: MySQLComQueryPacket(sql=SET autocommit=1)
   [INFO ] 20:09:38.783 [ShardingSphere-Command-2] o.a.s.t.s.ShardingTransactionManagerJustep - ===MyAddress: 192.168.1.46:3307
   [INFO ] 20:09:38.790 [ShardingSphere-Command-3] o.a.s.s.f.m.c.MySQLCommandExecutorFactory - Execute packet type: COM_QUERY, value: MySQLComQueryPacket(sql=SELECT table_name FROM information_schema.tables WHERE table_schema=database())
   [INFO ] 20:09:38.847 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0x1fbb6b60, L:/0.0.0.0:3307] READ: [id: 0x3bc18f6f, L:/192.168.1.46:3307 - R:/192.168.1.46:44534]
   [INFO ] 20:09:38.855 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0x1fbb6b60, L:/0.0.0.0:3307] READ COMPLETE
   [INFO ] 20:09:38.863 [epollEventLoopGroup-3-2] o.a.s.s.f.m.a.MySQLAuthenticationEngine - ===Username: amRiYzpteXNxbDovLzE5Mi4xNjguMC4xMDg6MzMwNi90ZXN0P3VzZXI9cm9vdCZwYXNzd29yZD10ZXN0JnNlcnZlclRpbWV6b25lPVVUQyZ1c2VTU0w9ZmFsc2U=
   [INFO ] 20:09:38.864 [epollEventLoopGroup-3-2] o.a.s.s.f.m.a.MySQLAuthenticationEngine - ===Auth  connection url=jdbc:mysql://192.168.0.108:3306/test?user=root&password=test&serverTimezone=UTC&useSSL=false
   [INFO ] 20:09:38.864 [epollEventLoopGroup-3-2] o.a.s.s.f.m.a.MySQLAuthenticationEngine - ===Login succeed
   [INFO ] 20:09:38.865 [ShardingSphere-Command-0] o.a.s.s.f.m.c.MySQLCommandExecutorFactory - Execute packet type: COM_QUERY, value: MySQLComQueryPacket(sql=/* mysql-connector-java-5.1.47 ( Revision: fe1903b1ecb4a96a917f7ed3190d80c049b1de29 ) */SELECT  @@session.auto_increment_increment AS auto_increment_increment, @@character_set_client AS character_set_client, @@character_set_connection AS character_set_connection, @@character_set_results AS character_set_results, @@character_set_server AS character_set_server, @@collation_server AS collation_server, @@collation_connection AS collation_connection, @@init_connect AS init_connect, @@interactive_timeout AS interactive_timeout, @@license AS license, @@lower_case_table_names AS lower_case_table_names, @@max_allowed_packet AS max_allowed_packet, @@net_buffer_length AS net_buffer_length, @@net_write_timeout AS net_write_timeout, @@sql_mode AS sql_mode, @@system_time_zone AS system_time_zone, @@time_zone AS time_zone, @@transaction_isolation AS transaction_isolation, @@wait_timeout AS wait_timeout)
   [INFO ] 20:09:38.876 [ShardingSphere-Command-0] o.a.s.s.b.c.j.w.StatementExecutorWrapperJustep - ===Modified Sql:SELECT '1' AS auto_increment_increment, 'utf8' AS character_set_client, 'utf8' AS character_set_connection, 'utf8' AS character_set_results, 'utf8' AS character_set_server , 'latin_swedish_ci' AS collation_server, 'utf8_general_ci' AS collation_connection, NULL AS init_connect, 28800 AS interactive_timeout, 'GPL' AS license , 0 AS lower_case_table_names, 67108864 AS max_allowed_packet, 16384 AS net_buffer_length, 60 AS net_write_timeout, 'ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION' AS sql_mode , 'UTC' AS system_time_zone, 'SYSTEM' AS time_zone, 'REPEATABLE-READ' AS transaction_isolation, 28800 AS wait_timeout
   [INFO ] 20:09:38.883 [ShardingSphere-Command-1] o.a.s.s.f.m.c.MySQLCommandExecutorFactory - Execute packet type: COM_QUERY, value: MySQLComQueryPacket(sql=SET character_set_results = NULL)
   [INFO ] 20:09:38.884 [ShardingSphere-Command-1] o.a.s.s.b.c.j.w.StatementExecutorWrapperJustep - ===Modified Sql:SELECT 'x'
   [INFO ] 20:09:38.887 [ShardingSphere-Command-2] o.a.s.s.f.m.c.MySQLCommandExecutorFactory - Execute packet type: COM_QUERY, value: MySQLComQueryPacket(sql=SET autocommit=1)
   [INFO ] 20:09:38.888 [ShardingSphere-Command-0] o.a.s.s.f.m.c.MySQLCommandExecutorFactory - Execute packet type: COM_QUERY, value: MySQLComQueryPacket(sql=SELECT table_name FROM information_schema.tables WHERE table_schema=database())
   [INFO ] 20:09:38.892 [ShardingSphere-Command-3] o.a.s.s.b.c.j.w.StatementExecutorWrapperJustep - ===Modified Sql:SELECT table_name FROM information_schema.tables WHERE table_schema = DATABASE()
   [INFO ] 20:09:38.892 [ShardingSphere-Command-0] o.a.s.s.b.c.j.w.StatementExecutorWrapperJustep - ===Modified Sql:SELECT table_name FROM information_schema.tables WHERE table_schema = DATABASE()
   [INFO ] 20:09:38.937 [ShardingSphere-Command-1] o.a.s.s.f.m.c.MySQLCommandExecutorFactory - Execute packet type: COM_QUERY, value: MySQLComQueryPacket(sql=select * from acls)
   [INFO ] 20:09:38.939 [ShardingSphere-Command-2] o.a.s.s.f.m.c.MySQLCommandExecutorFactory - Execute packet type: COM_QUERY, value: MySQLComQueryPacket(sql=select * from acls)
   [INFO ] 20:09:38.941 [ShardingSphere-Command-2] o.a.s.s.b.c.j.w.StatementExecutorWrapperJustep - ===Modified Sql:SELECT * FROM acls
   [INFO ] 20:09:38.944 [ShardingSphere-Command-1] o.a.s.s.b.c.j.w.StatementExecutorWrapperJustep - ===Modified Sql:SELECT * FROM acls
   ```


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [shardingsphere] tuohai666 commented on issue #6324: ShardingSphere-Proxy stop working

Posted by GitBox <gi...@apache.org>.
tuohai666 commented on issue #6324:
URL: https://github.com/apache/shardingsphere/issues/6324#issuecomment-657418410


   Hi @Simbafa , you provided very detail report. But I still have to ask does the test work if your application connect to an MySQL server instead of Sharding-Proxy. Please response after test not after think.


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [shardingsphere] Simbafa commented on issue #6324: ShardingSphere-Proxy stop working

Posted by GitBox <gi...@apache.org>.
Simbafa commented on issue #6324:
URL: https://github.com/apache/shardingsphere/issues/6324#issuecomment-657521192


   ```main_dbtable``` is one of the tables which include blob data in the test database. It has 5 records.
   
   ![table_structor](https://user-images.githubusercontent.com/37646009/87302476-0f198480-c544-11ea-8ce7-945ee08a9af1.png)
   ![table_size](https://user-images.githubusercontent.com/37646009/87302506-1a6cb000-c544-11ea-98cd-ea1a8733f3d9.png)
   
   


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [shardingsphere] yu199195 closed issue #6324: ShardingSphere-Proxy will be blocked when query big blob data

Posted by GitBox <gi...@apache.org>.
yu199195 closed issue #6324:
URL: https://github.com/apache/shardingsphere/issues/6324


   


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [shardingsphere] Simbafa commented on issue #6324: ShardingSphere-Proxy stop working

Posted by GitBox <gi...@apache.org>.
Simbafa commented on issue #6324:
URL: https://github.com/apache/shardingsphere/issues/6324#issuecomment-657336020


   Hi @tristaZero,
   Thanks for your quickly feedback.
   1.  In my test database, there are about 90 tables. None table rows exceed 20. But there is one table that includes blob data, one record size bigger than 50K bytes.
   2. I haven't tested ```select a from tableName where id=1```. Later I will try it.


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [shardingsphere] Simbafa commented on issue #6324: ShardingSphere-Proxy stop working

Posted by GitBox <gi...@apache.org>.
Simbafa commented on issue #6324:
URL: https://github.com/apache/shardingsphere/issues/6324#issuecomment-657511001


   Hi @tuohai666 ,
   Firstly, I confirmed that test application connects to MySql server directly is OK.
   After some tests, I found the issue is caused by BIG CLOB data.
   When the blob data size is small, everything is Ok.
   But When I increased the blob data size to 900K+, Sharding-Proxy will stop response soonly.


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [shardingsphere] Simbafa commented on issue #6324: ShardingSphere-Proxy stop working

Posted by GitBox <gi...@apache.org>.
Simbafa commented on issue #6324:
URL: https://github.com/apache/shardingsphere/issues/6324#issuecomment-658119192


   Hi @tuohai666 ,
   > When you increased the blob data size to 900K, all of the client threads will query this table right? But Sharding-Proxy will not stop immediately but stopped soonly?
   
   You are right. Sharding-Proxy will not sotp immediately. After some time, it stops.
   
   > Can you help to use 1 client thread to query this table with 900K size column? I want to make sure whether proxy will stop for every query.
   
   I run the test application with 1 thread, 2 threads, 3 threads, Sharding-Proxy works well.
   But when the threads increased to 5, Sharding-Proxy stops.
   
   


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [shardingsphere] tuohai666 commented on issue #6324: ShardingSphere-Proxy stop working

Posted by GitBox <gi...@apache.org>.
tuohai666 commented on issue #6324:
URL: https://github.com/apache/shardingsphere/issues/6324#issuecomment-657447821


   Please close debug level for log, and set sql.show: true .


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [shardingsphere] tristaZero commented on issue #6324: ShardingSphere-Proxy stop working

Posted by GitBox <gi...@apache.org>.
tristaZero commented on issue #6324:
URL: https://github.com/apache/shardingsphere/issues/6324#issuecomment-657333462


   Hi @Simbafa 
   Thanks for your detailed feedback. 
   
   At first, I want to figure out this issue is more likely to be a function bug or a performance one. So could you give us some feedback on the following questions?
   1. How many rows roughly of those test tables? You know all your test SQLs are all routing and full volume queries.
   2. What will happen if you do pressure tests using SQLs with sharding columns, like `select a from tableName where id = 1` (Suppousing id is sharding key)


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [shardingsphere] tuohai666 commented on issue #6324: ShardingSphere-Proxy stop working

Posted by GitBox <gi...@apache.org>.
tuohai666 commented on issue #6324:
URL: https://github.com/apache/shardingsphere/issues/6324#issuecomment-658095692


   Good.
   But still strange to me. I set WriteBufferWaterMark = 16MB before, but it seems like not take effect.
   Can you help to do a test using proxy.frontend.flush.threshold: 2 ? If water mark didn't take effect, this case will block the proxy.


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [shardingsphere] Simbafa commented on issue #6324: ShardingSphere-Proxy stop working

Posted by GitBox <gi...@apache.org>.
Simbafa commented on issue #6324:
URL: https://github.com/apache/shardingsphere/issues/6324#issuecomment-658090366


   @tuohai666 
   Sharding-Proxy does not stop if proxy.frontend.flush.threshold is 1.
   And performance effect is not obvious.


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [shardingsphere] tuohai666 commented on issue #6324: ShardingSphere-Proxy stop working

Posted by GitBox <gi...@apache.org>.
tuohai666 commented on issue #6324:
URL: https://github.com/apache/shardingsphere/issues/6324#issuecomment-658016143


   @Simbafa This issue might relate with WriteBufferWaterMark.
   
   You can set property proxy.frontend.flush.threshold: 1 and have a try.


----------------------------------------------------------------
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:
users@infra.apache.org