Skip to content

v2.1.3

Choose a tag to compare

View all tags
@github-actions github-actions released this 31 Dec 09:50
· 178 commits to master since this release
v2.1.3
3b24dab

Changelog

  • 3b24dab Optimize LockKey hash algorithm
  • 80f5df5 Corrected variable naming
  • 3c050f9 Revert "Using the murmur hash algorithm"
  • 1093f02 Merge pull request #3 from snower/feature/murmur3
  • c9e4e32 update github action
  • d5dc3df Using the murmur hash algorithm
  • aa64e4d Fixed: You should first shut down the DB to stop clearing the timeout queue, then shut down the AOF and replication synchronization to ensure that all data can be flushed to disk.
  • f93773c The optimization does not use parameters marked with _
  • 106db63 Optimize the shutdown order to ensure that all data is processed
  • 043a8d8 Optimize GetOrNewLockManager
  • 0d1b8a9 Optimize active master node switching to ensure that all executing and background execution commands are completed
  • b78fd75 Optimizing when Lock Update, if the lock needs to be updated and the current Lock has a LockCommand waiting to be executed, it will be cleared so that it can be overwritten with the new LockCommand.
  • 1e517cf Fixed the issue where a background command that acquires a LockManager and locks it may release the normally acquired LockManager.
  • 8966f99 remove github action build-test golang version 1.24
  • 9b0e83f update github action build-test golang version
  • 1c83be2 Optimize initNewLockManager
  • d9d9dca Optimize the background command execution settings to activate low priority locks for non-system busy activation without counting usage counts
  • 4031051 Optimize the logic of acquiring or releasing LockManager from the FreeLockManager queue
  • 724fa19 Optimize the management of command status information, high and low priority locks, and background execution pool related information
  • 9707e1d fix management command output status information
  • 1abee47 Optimize the background execution command to start two coroutines for each concurrent queue
  • 8cb016d Optimize and add background execution commands to the corresponding concurrent lock queue
  • 2d76b52 change version to 2.1.3
  • 6d71ede Fix the exception of judging whether refCount is zero when RemoveLockManager
  • 1f6bba4 Optimize the lock-free concurrency control logic of GetOrNewLockManager and RemoveLockManager
  • 50977ae Optimize LockData to include LockCommand execution and add LowSetPriority to execute before subsequent commands to ensure consistency
  • 80f436d Optimize low-priority locks to distinguish different application settings in different scenarios
  • 408ea51 Corrected the problem of handling the LockData being the Lock command and judging that it must be the same dbid exception
Assets 11
Loading