Investigate and document all possible disk errors that shoud count in shard error counter #838

New issue

Open

opened 2025-12-28 17:20:51 +00:00 by sami · 1 comment

sami commented

2025-12-28 17:20:51 +00:00

Owner

Originally created by @fyrchik on GitHub (Oct 25, 2022).

As an example we have recently encountered too many open files error because of wrong system configuration.
Should we count them in the shard error counter?

Currently we count all errors from Open/Write as "physical" errors. Maybe we should behave differently in some situations.

Originally created by @fyrchik on GitHub (Oct 25, 2022). As an example we have recently encountered `too many open files` error because of wrong system configuration. Should we count them in the shard error counter? Currently we count all errors from `Open`/`Write` as "physical" errors. Maybe we should behave differently in some situations.

sami added the

neofs-storage

discussion

labels

2025-12-28 17:20:51 +00:00

sami commented

2025-12-28 17:20:51 +00:00

Author

Owner

@fyrchik commented on GitHub (Oct 26, 2022):

As a first step towards this goal I propose to define custom error type with IsLogical method. The engine can then simply call IsLogical and increase error counter if not.

@fyrchik commented on GitHub (Oct 26, 2022): As a first step towards this goal I propose to define custom error type with `IsLogical` method. The engine can then simply call `IsLogical` and increase error counter if not.

sami referenced this issue

2025-12-28 17:21:00 +00:00

Complex object sometimes can't be fetched from certain nodes when bearer token is attached #875

sami referenced this issue

2025-12-28 17:21:41 +00:00

Complex object is not readable through non-container node #1069