Simple-Coder commented on issue #731:
URL:
https://github.com/apache/shardingsphere-elastic-job-lite/issues/731#issuecomment-638562286
测试中kill -9杀死springboot项目，没有优雅停止，导致后续与zk之间信息未更新，导致重启一直处于分片。
This is an automated message
DKodak commented on issue #729:
URL:
https://github.com/apache/shardingsphere-elastic-job-lite/issues/729#issuecomment-638562362
> 您能否提供更多详细信息？
Of course, the situation we met at that time was as follows: five timing
tasks were triggered at 10:30, but it was found that another
lovepoem opened a new issue #738:
URL: https://github.com/apache/shardingsphere-elastic-job-lite/issues/738
Upload the xml schema to official website and change domain name
Now the domain is `dangdang.com`
This is
lovepoem opened a new issue #737:
URL: https://github.com/apache/shardingsphere-elastic-job-lite/issues/737
Since the elastic-job-lite is transferred here , we should change the base
package , maven group and maven artifactId
Hi All,
We have lots of rule about sharding, encrypt, master-slave, shadow,
replica, and maybe add more in future.
The current rule configurations are inconsist and scattered. I plan to
define the rule configuration level of them and to help user easy to
understand it.
The 1st level is rule,
hi
we think the count query from 16databases , in the end ,it seems every
database result to sum by sharding-proxy in memory ,we think it so fast.
for example , db0 count query cost 5s, by the sharding-proxy count
query cost 25s with 16databases, to deal with the count result need 20s
Hi:
before i send last email ,i didn't add this props,
after I add props in server.yml , by the config like this:
max.connections.size.per.query: 64
acceptor.size: 64
executor.size: 64
the count query sql cost 25s
I changed props ,increase to 128 or 256 ,the count query sql cost still between
In server.yaml, followling props effect the concurrency, you can have a try.
max.connections.size.per.query: 64
acceptor.size: 64
executor.size: 64
--
Zhang Yonglun
Apache ShardingSphere
Kai Yu 于2020年6月3日周三 下午3:16写道：
> Hi ALL :
> we have a project used 16 databases (db0 ...db15)，we used
Hi ALL :
we have a project used 16 databases (db0 ...db15)，we used sharding-proxy
4.0.0-RC2 ,
and config the sharding.xml like this:
schemaName: ty-basic-member
dataSources:
db0:
url: jdbc:mysql://xxx:3306/db0?useSSL=false
username: root
password: root
