Release preparation v1.145

Product Discussions STORJLINGS
1

After some break we going to release new v1.145

Changelog

Satellite

  • cfa0ec6 web/satellite: resolve some build warnings
  • d49ed20 satellite/{console,web}: show product shortname in more places
  • b087bcb web/satellite: move usage graphs off main dashboard
  • 1ee8d37 satellite/metabase/avrometabase: refactor parser to use error accumulation pattern
  • 3092f6b satellite/metabase/avrometabase: refactor parser to use errs.Combine pattern
  • d41c5e6 satellite/metabase/avrometabase: add objects iterator
  • cbf67b7 satellite/console: avoid using console.Config as a global variable
  • ea61983 satellite/metabase: change spanner.Insert to spanner.InsertMap
  • 6b7cd61 satellite/metabase/changestream: fix flaky TestDeleteChangeStream
  • 7ac55e6 satellite/metabase: fix test context in TestListObjectsPendingDuplicates
  • ad9c94e satellite/payments: remove partner-specific billing logic
  • 7af72bd satellite/metainfo: switch logging to use public project id
  • 0f2dde7 satellite/accounting: remove unused method
  • 46a7f01 satellite/metainfo: add comprehensive doc.go for AI agents
  • 9ed2c7f satellite/metabase: fix flaky tests
  • c4ae04a satellite/eventing/eventingconfig: project-level gating config
  • 4118d0f satellite/metabase/avrometabase: add node aliases parsing
  • ac2658d satellite/eventing: add event type validation
  • aa324df satellite/eventing: add test event support
  • 15cb5fc satellite/metainfo: add bucket eventing config API endpoints
  • 2ca7e71 satellite/metainfo: add metadata size restriction to BeginObject
  • cd7abcd satellite/analytics: send tenant ID to Hubspot
  • c848f47 web/satellite: re-open create project dialog after member account conversion
  • ec4cada satellite/admin/back-office: cascade user agent and placement update
  • 06fe87d satellite/admin/back-office: treat user agent as string
  • 7381f59 satellite/admin: reorganize code
  • 91b4d91 satellite: whitelabel email system
  • 2fabdff satellite/admin/back-office: update user default placement
  • 4f1f0c8 satellite/admin-ui: update user default placement
  • 27075ff satellite/admin-ui: clean up head/rate limit display
  • e230a46 satellite/{console,payments}: add pricing endpoint
  • 2f4c453 web/satellite: hide satellite selector for white labeled satellite
  • a87d759 satellite/eventing: add Redis cache for bucket notification configs
  • 1a952c8 satellite/{console,payments}: Add config to require address
  • 8492b67 satellite/eventing: add event type and filter matching utilities
  • 2a4f889 satellite/metainfo: use Redis cache for bucket eventing
  • ad304fe satellite/eventing: use Redis cache in the eventing service
  • 61abebc web/satellite: small compute UI updates
  • ea3d4e5 web/satellite: move compute dialogs to a dedicated folder
  • d2bfe19 web/satellite: added start/stop compute instance
  • 7e0c2b8 web/satellite: add restart instance functionality
  • 96b22c3 satellite/satellitedb: add remainder_bytes column to bucket_storage_tallies
  • fa7d311 satellite/repair/repairer: add RPC connection pool
  • a6d5b83 satellite/metabase: fix swapped Spanner tags in precommitUnversionedObjectFull
  • 6cce3ba satellite/console: simplify whitelabel smpt password
  • 34a6b84 satellite/satellitedb: simplify migration for bucket_storage_tallies table

Storagenode

  • 0b13733 storagenode: enable nodestats.Cache for select runner
  • cd68e34 cmd/storagenode-updater: avoid using tag for binary

Test

  • 6c1ec16 {Jenkinsfile/testsuite}: bump postgres to v17

General

  • b502a76 shared/modular: debug flag to print out current / all components
  • 7927201 scripts: move go scripts to separate folder
  • 9e49dd7 shared/dbutil/spannerutil: fix test failing for production Spanner
  • 5368782 shared/modular/cli: fix typo in file name
3 Likes
2

If this version deploys cleanly: will you slowly start migration of old data to hashstore?

1 Like
3

github show that there is also

  • 3aea9a5 storagenode: adjusting used/available space calculation

is there something wrong?

4

Is the rollout of version 1.141.2 stopped? I haven’t seen any progress of cursor/seed on https://version.storj.io/

5

In 1.144 was introduced in SNO API reclaimable, but it show 0 all the time, when it will start to work?

1 Like
6

Hopefully in 1.146 (:crossed_fingers:) There are multiple patches related to space calculation can be expected.

8 Likes
7

When we will see updates? today we are stack at 1.142

9

The team is working on the release

1 Like
10

Is there any timeline for this?

11

The release is in progress, with a small delay in order to include an important bug fix.

4 Likes
12

I created an account on the forum to inform you of something that could cause a problem with your calculation metrics. I didn’t spend much time looking into it, and a developer on your team will be able to quickly tell whether or not it’s relevant and whether it’s correct or not.

I was thinking about the time zone, because it seems to me (but I may be wrong) that the graph on the left shows the time zone of your server and the one on the right shows the time zone of my server (node) UTC+1. So the values are not quite aligned.

image
image899×475 35 KB

If it’s just for this display, it’s not too much of a problem, but it could probably cause more serious issues if the times are not aligned.

But maybe I’m wrong.

14

Your assumption is partially correct, the graph on the left side uses a UTC 0 timezone (not a server timezone), however, these two values have a different source:

  1. The graph is based on what’s registered on the satellite using values from the signed work orders sent by your node
  2. The donut is based on a local calculation on the node’s side. How is it calculated depends on many factors (what’s backend - piecestore or hashstore, did the filewalker finish its job in case of piecestore, did the node compaction in case of hashstore, did the node receive a bloom filter to move deleted data to the trash, etc.).

In many cases a usage reported by the satellite will slightly differ from the usage reported by the node. Please also note - both are estimations anyway, because actually storage is accounted in GBh (like kWth), and it’s used to account for the payout. These displayed numbers just estimations and they are not accurate.
The accurate numbers are in the Payout history, so you can see an actual usage only for previous months.

15

v1.146.5 still shows 0 in reclaimable:

"diskSpace": {
    "used": 495166327896,
    "available": 504833672104,
    "overused": 0,
    "allocated": 1000000000000,
    "trash": 84834105152,
    "reclaimable": 0
  },
16

even if patch is made, not always possible to add it, it depends on lot of factors.

1 Like