Release preparation v1.136

Product Discussions
1

Release candidate v1.136 is already deployed on QA environment and ready for testing

Changelog

General

Satellite

  • 9b1f65b satellite/satellitedb: do ArchiveRollups in a transaction
  • 8248203 satellite/satellitedb: GetProjectDailyUsageByDateRange, always call rows.Close on error
  • 803186c satellite/nodeselection: delay checks initialization for reduce selector
  • 7f29a61 satellite/nodeselection: atleast should count the number of groups
  • 3b9de15 satellite/metainfo: include cipher information with ETag and ETagOrCustom
  • c1b757b satellite/{payments,console,web}: fixes for ‘pay upfront to upgrade’
  • 4db048f web/satellite: update share icons (#7573)
  • 6247330 satellite/metainfo: add name for single upload limiter cache
  • 086556d satellite/{accountfreeze,admin}: remove trial freeze on user kind change
  • 21a05a5 satellite/satellitedb: add method to query total project member count by project ID
  • 02d48fc satellite/console: return members count with project config
  • ec4e94d web/satellite: add creator column to buckets table
  • 4950a7f web/satellite: extended API keys table to also show key creator’s email
  • baf57b6 web/satellite: add ‘cannot delete key/bucket’ dialog
  • 246630a satellite/nodeselection: late evaluation of atleast parameter
  • ebdf746 satellite/metabase: copy segments (CopyObject) outside tx
  • 0f1e90b satellite/metabase: CopyObject add intermediate pending stage
  • 3aebf8a satellite/console: support storing announcement status in user_settings
  • 4b5b4e6 web/satellite: added generic announcement banner
  • 60af254 satellite/metabase: reduce contention from DeletePendingObject
  • 6c02aa3 satellite/metabase: DeletePendingObject use Update instead of Query
  • 7091262 satellite/db: fix duplicate usage report rows
  • e1a8997 satellite/metabase: reduce DB lock times form deleteObjectLastCommittedPlain
  • 7d3334c satellite/console: fix usage report test
  • fa78f91 satellite/console, private/web: implemented add credit card rate limit
  • 7ff8788 satellite/console: do not allow regular project members to query invite links
  • 09d88ca satellite/console: do not allow generating 2FA secret if 2FA is already enabled
  • a79f9c7 satellite/mailservice: include email Subject in Error/Info logs
  • 94dfb07 satellite/{console,satellitedb}: always update status_updated_at on user status update
  • ebac322 satellite/{console,payments}: add max credit card count restriction
  • b61d9ad satellite/admin: update project limits as part of kind update (#7578)
  • 5d774a8 web/satellite: add refresh button to browser
  • f5ca234 satellite/mailservice: added config for the new hubspot email sending service

Storagenode

  • 25717b8 storagenode: register webui for modular storagenode
  • a170e50 storagenode: support setup subcommand with modular storagenode
  • ea39842 storagenode: register hashstore related features

Test

  • a4173bc ci,testsuite/wasm: fixed verify build
4 Likes
2

what it modular storagenode?

3

Probably for SELECT operators since they like to manage their load and resources.

4

TLDR; a long-term plan, to refactor some invisible internals of our services.

Our microservices (satellite, storagenode, version control etc.) have many internal small services (like piece walker, or piece store).

The way how we initialize these services are very static, and hard to maintain. We introduced an experimental modular framework (such for mud in storj/storj), which can make this wiring more dynamic.

  1. It make it easier to develop new components, or ad-hoc helpers and cli tools
  2. It makes it easier to run more lightweight unit test (without DB dependency, or mocked DB).
  3. Also, it can make the unit test more cache friendly
  4. It can make it easier to explain required configuration for microservices (can show which configuration is used)

Current phase:

  1. we have dedicated storagenode-modular and satellite-modular satellite. Same logic, same behavior, different initialization logic
  2. Yes, select uses this binary
  3. Eventually, we are planning to use this initialization mechanism for all containers, but it’s a long-term effort and low priority
3 Likes
5

1.136 version windows GUI
Nodes stops for unknown reason, no error log about stop.
several nodes, different servers.

6

What windows version? No problems with Windows Server 2022 + 1.136.4 here.

7

windows 10, interesting that no error in logs

Screenshot 2025-09-05 152914
Screenshot 2025-09-05 152914550×514 33.9 KB

No info in logs, this mean that something very fast kill node
How can I help to investigate this problem?

8

First now i turned to info log level.
I see massive content canceled amount, bot i do not see download start at all.
it generates around 200mb in several h.

9

Do you have 1.135 nodes and are they running without issues?

10

I do not have 1.135 any more, not all nodes making issues, some more some less.
one node made more problems, so i try to check disk also here.

11

Also no errors in the nodes log?

12

not, any fatal errors. download canceled mostly

13

I found one problem why it could be main problem on one server.
First i thoud than 1 on NVME that was in and not used, may be makes problem.
So i watched inside. And I see that cpu cooler not spinning on I7-7700, So cpu worked slow, that why there was so many canceled uploads. i will monitor it.

But it not resolve problem why node not show on info level start of download.
it show only canceled or downloaded/uploaded

14

My nodes don’t show start messages either. I remember this was removed long ago in order to reduce the number of log entries.

1 Like
15

Thank you for info, then it is not a problem.

16

node sill turn itself off without any log entry.

17

Even on DEBUG log level, no error in log, why it go off.

18

Maybe something in the Windows journals?

19

Do you mean Event Viewer?

20

Yes. Please check the event details, maybe there is something in it or right before it.