XZX369 commented on issue #22884:
URL:
https://github.com/apache/shardingsphere/issues/22884#issuecomment-1374344524
shardingsphere 5.1.2, database connection pool maxPoolSize: 500 minPoolSize:
50, but sharding often freezes, resulting in connection anomalies. This is a
big risk for online use, and what configurations can be optimized to handle a
large number of connections without failing unexpectedly
shardingsphere 5.1.2, 数据库连接池 maxPoolSize: 500 minPoolSize: 50,
但是sharding还是会经常卡死，导致连接异常.这样对于线上使用有很大的风险,有哪些配置可以优化到能处理大量连接不会异常挂掉呢
走路太骚扭到小腰?
***@***.***
------------------ 原始邮件 ------------------
发件人:
"apache/shardingsphere"
***@***.***>;
发送时间: 2022年12月16日(星期五) 下午5:12
***@***.***>;
***@***.******@***.***>;
主题: Re: [apache/shardingsphere] The table generated by time fragments
does not conform to the configuration logic (Issue #22884)
@XZX369
Simply put, you need to replace readwrite_ds.test_log_$->{202206..202406}
with readwrite_ds.test_log$->2023$->{01..12},
readwrite_ds.test_log$->{[2022 , 2024]}1$->{06..12}.
If you're dynamically changing this value via something like DistSQL, you
should tend to use
readwrite_ds.test_log$->{[202206,202207,202208,202209,202210,202211,202212,202301,202302]},
something like this It is more convenient to generate a more readable string
expression.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
