Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in
Toggle navigation
Menu
Open sidebar
eos
QuarkDB
Commits
9602aeb0
Commit
9602aeb0
authored
Apr 24, 2019
by
Georgios Bitzes
Browse files
Update release notes for 0.3.7
parent
b2910dcc
Pipeline
#829702
failed with stages
in 30 minutes and 56 seconds
Changes
1
Pipelines
8
Hide whitespace changes
Inline
Side-by-side
CHANGELOG.md
View file @
9602aeb0
# Changelog
# Changelog
All notable changes to this project will be documented in this file.
All notable changes to this project will be documented in this file.
## Unreleased
## 0.3.7 (2019-04-24)
-
Heavy use of lease commands could cause performance degradation and latency
spikes, due to accumulation of long-lived deletion tombstones on expiration
events. Starting from this release, such tombstones should disappear much
more quickly without accumulating.
-
Fixed regression introduced in 0.3.6, which made it impossible to create new
-
Fixed regression introduced in 0.3.6, which made it impossible to create new
bulkload nodes. (Note: to workaround, delete directory
``/path/to/bulkload/current/state-machine``
bulkload nodes. (Note: to workaround, delete directory
``/path/to/bulkload/current/state-machine``
right after running
``quarkdb-create``
)
right after running
``quarkdb-create``
)
-
Addition of
``LEASE-GET-PENDING-EXPIRATION-EVENTS``
command to list all
pending lease expiration events, and
``RAW-SCAN-TOMBSTONES``
to inspect tombstones
as an aid in debugging.
-
Expanding a cluster is now easier, no need to pass
``--nodes``
to quarkdb-create
when creating a new node for an established cluster.
## 0.3.6 (2019-03-21)
## 0.3.6 (2019-03-21)
-
Improved memory management and recycling, putting less pressure on the global
-
Improved memory management and recycling, putting less pressure on the global
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment