Pace2Car opened a new issue, #24861: URL: https://github.com/apache/shardingsphere/issues/24861
## Bug Report **For English only**, other languages will not accept. Before report a bug, make sure you have: - Searched open and closed [GitHub issues](https://github.com/apache/shardingsphere/issues). - Read documentation: [ShardingSphere Doc](https://shardingsphere.apache.org/document/current/en/overview). Please pay attention on issues you submitted, because we maybe need more details. If no response anymore and we cannot reproduce it on current information, we will **close it**. Please answer these questions before submitting your issue. Thanks! ### Which version of ShardingSphere did you use? master a593ad9 ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? Both ### Expected behavior Configured props `system_log_level` in the configuration file `server.yaml` ```YAML props: system-log-level: DEBUG ``` After startup, expect to see debug logs, but only output info Excute: SET DIST VARIABLE system_log_level = 'DEBUG'; then, the debug log is output. ### Actual behavior `system_log_level` is not in effect ### Reason analyze (If you can) The log level is not refreshed in propeties refresh logic -- 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]
