@@ -3,6 +3,26 @@ Changelog for NeoFS Node
3
3
4
4
## [ Unreleased]
5
5
6
+ ### Added
7
+
8
+ ### Fixed
9
+
10
+ ### Changed
11
+
12
+ ### Removed
13
+
14
+ ### Updated
15
+
16
+ ### Updating from v0.45.0
17
+
18
+ ## [ 0.45.0] - 2025-02-27 - Sapsido
19
+
20
+ Unleashing the true scaling potential of NeoFS this release is the first one
21
+ to break the old ~ 320 node limit. It also brings a new powerful search API and
22
+ distributed settings management commands. Write cache received some care and
23
+ improved its efficiency. A number of other optimizations and fixes is included
24
+ as well.
25
+
6
26
### Added
7
27
- Initial support for meta-on-chain for objects (#2877 )
8
28
- First split-object part into the CLI output (#3064 )
@@ -17,7 +37,7 @@ Changelog for NeoFS Node
17
37
18
38
### Fixed
19
39
- ` neofs-cli object delete ` command output (#3056 )
20
- - Make the error message more clearer when validating IR configuration (#3072 )
40
+ - More clear error message when validating IR configuration (#3072 )
21
41
- Panic during shutdown if N3 client connection is lost (#3073 )
22
42
- The first object of the split object is not deleted (#3089 )
23
43
- The parent of the split object is not removed from the metabase (#3089 )
@@ -34,7 +54,7 @@ Changelog for NeoFS Node
34
54
### Changed
35
55
- Number of cuncurrenly handled notifications from the chain was increased from 10 to 300 for IR (#3068 )
36
56
- Write-cache size estimations (#3106 )
37
- - New network map support solving the limit of ~ 320 nodes per network
57
+ - New network map support solving the limit of ~ 320 nodes per network ( # 3088 )
38
58
- Calculation of VUB for zero hash (#3134 )
39
59
- More efficient block header subscription is used now instead of block-based one (#3163 )
40
60
- ` ObjectService.GetRange(Hash) ` ops now handle zero ranges as full payload (#3071 )
@@ -52,15 +72,15 @@ Changelog for NeoFS Node
52
72
- NeoGo to 0.108.0 (#3157 )
53
73
54
74
### Updating from v0.44.2
55
- Using public keys as a rule target in eACL tables was deprecated, and
56
- since this realese it is not supported to create new eACL table with keys,
57
- use addresses instead.
75
+ Using public keys as a rule target in eACL tables was deprecated, and
76
+ since this realese it is not supported to create new eACL table with keys,
77
+ use addresses instead.
58
78
For more information call ` neofs-cli acl extended create -h ` .
59
79
60
80
` small_object_size ` , ` workers_number ` , ` max_batch_size ` and ` max_batch_delay `
61
81
paramteters are removed from ` writecache ` config. These parameters are related
62
- to the BoltDB part of the write-cache, which is dropped from the code.
63
- Also, because of this, there will be automatic migration from BoltDB by flushing
82
+ to the BoltDB part of the write-cache, which is dropped from the code.
83
+ Also, because of this, there will be automatic migration from BoltDB by flushing
64
84
objects to the main storage and removing database file.
65
85
66
86
This version maintains two network map lists, the old one is used by default
@@ -2243,7 +2263,8 @@ NeoFS-API v2.0 support and updated brand-new storage node application.
2243
2263
2244
2264
First public review release.
2245
2265
2246
- [ Unreleased ] : https://github.com/nspcc-dev/neofs-node/compare/v0.44.2...master
2266
+ [ Unreleased ] : https://github.com/nspcc-dev/neofs-node/compare/v0.45.0...master
2267
+ [ 0.45.0 ] : https://github.com/nspcc-dev/neofs-node/compare/v0.44.2...v0.45.0
2247
2268
[ 0.44.2 ] : https://github.com/nspcc-dev/neofs-node/compare/v0.44.1...v0.44.2
2248
2269
[ 0.44.1 ] : https://github.com/nspcc-dev/neofs-node/compare/v0.44.0...v0.44.1
2249
2270
[ 0.44.0 ] : https://github.com/nspcc-dev/neofs-node/compare/v0.43.0...v0.44.0
0 commit comments