Change Log
[wesql-server:8.0.35-0.1.0_beta4.38] - 2024-12-23
New Feature
- Replication: WeSQL replication is designed as a cloud-native replication solution that uses object storage as a medium for binlog copying between one WeSQL Source database and one or more other Replica databases. WeSQL replication uses asynchronous replication, periodically detecting changes in the binlog in the Source object storage to replicate data to the local Replica Server and replay it. The feature is controlled by the parameter
binlog_archive_replica
, and it is only enabled when set tobinlog_archive_replica=true
. More information, refer to Replication.
Improvements
-
Object Storage
- Improve time accuracy of waiting object storage lease lock to reduce startup time. Change the object storage lease lock timeout from 12s to 8s.
- Add parameter
objectstore_lease_lock_timeout
for object storage lease lock. If 0, lease lock is disabled. The default value is 8s.
-
Clone Instance
Adjust the source object storage parameter names when cloning instances to facilitate the use of these parameters in WeSQL Replication.
- Rename parameter
initialize_from_objectstore
toinitialize_from_source_objectstore
. - Rename parameter
initialize_objectstore_provider
tosource_objectstore_provider
. - Rename parameter
initialize_objectstore_region
tosource_objectstore_region
. - Rename parameter
initialize_objectstore_endpoint
tosource_objectstore_endpoint
. - Rename parameter
initialize_objectstore_use_https
tosource_objectstore_use_https
. - Rename parameter
source_objectstore_bucket
tosource_objectstore_bucket
. - Rename parameter
initialize_repo_objectstore_id
tosource_objectstore_repo_id
. - Rename parameter
initialize_branch_objectstore_id
tosource_objectstore_branch_id
. - Rename parameter
initialize_smartengine_objectstore_data
tosource_objectstore_smartengine_data
.
Bugs Fixed
- Snapshot
- When clone an new instance, if the bucket parameter
source_objectstore_bucket
of the source instance is different from theobjectstore_bucket
parameter of the cloned instance, the initialization will fail.
- When clone an new instance, if the bucket parameter
- Smartengine
- Fix uneven data writes cause wal checkpoint stalls. Subtables with empty memtable do not advance their recovery points causing the WAL checkpoint to stall while waiting for all subtables to align at a consistent WAL position.
- Binlog
- Fix the local binlog to be unable to be purged that has been persisted, When executing purge binlog(auto purge or manual purge).