Vitastor 0.6.4 released
- Implement a basic Kubernetes CSI driver
- Minor fixes for vitastor-nbd
- Fix build without RDMA broken in 0.6.3
2021-05-16 Continue reading →
Posts up to 2021-05-16
Vitastor 0.6.3 released
- RDMA support
- Client performance optimisations (4k randread ~120k -> ~180k on 1 core)
- JSON configuration file (/etc/vitastor/vitastor.conf) support
- Bug fixes
2021-05-01 Continue reading →
Vitastor 0.6.2 released
- Fix a possible crash during SYNC when journal fsyncs are enabled
- Fix a memory leak in the chained read implementation
2021-04-15 Continue reading →
Vitastor 0.6.1 released
A bugfix for the new “chained read from snapshot” feature
2021-04-14 Continue reading →
Vitastor 0.6.0 released
Warning: upgrading from 0.5.x is currently not supported! Please create an issue if you really need upgrade capability.
2021-04-11 Continue reading →
Vitastor 0.5.11 released
Another bunch of fixes, including important ones. Now OSDs are stable in SSD+HDD configurations and everything is mostly ready for the merge of master branch.
2021-04-08 Continue reading →
Vitastor 0.5.10 released
The version seems to be stable after this bunch of fixes :)
- Fix delete & write operation ordering during rebalance to not lose objects in the immediate_commit=off mode
- Fix a possible crash caused by very high iodepths
- Re-distribute PG primaries over OSDs that come up after a short downtime
- Allow to specify etcd URLs for OSDs with http://, do not die with a strange error if -etcd option is missing for fio
- Fix a journal flushing deadlock which sometimes occurred in the immediate_commit=off mode
- Fix a bug where OSDs could hang if the data device filled up
- Fix an allocator bug where it was unable to allocate up to last (n%64) data device blocks
- Fix monitor crash that occurred on removal of some etcd keys
- Fix a bug where PGs could remain incomplete due to incorrect PG history with just zeroes in osd_sets
2021-03-16 Continue reading →
Vitastor 0.5.9 released
- Fix two monitor bugs which led to objects being “logically lost” (physically present on some secondary OSDs while primary doesn’t know about it) after multiple interrupted rebalancings
- Implement “no_recovery” and “no_rebalance” flags
2021-03-11 Continue reading →