Split object stuck in GC cycle #1523

New issue

Closed

opened 2025-12-28 17:35:43 +00:00 by sami · 0 comments

sami commented

2025-12-28 17:35:43 +00:00

Owner

Originally created by @roman-khimov on GitHub (Oct 20, 2025).

Originally assigned to: @End-rey on GitHub.

Expected Behavior

Objects deleted and never returning again.

Current Behavior

Oct 20 20:20:55 metis1 neofs-node[2740175]: error        engine/inhume.go:159        inhuming root object but no link object is found        {"linkAddr": "HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/3fLGesRxQuCwVPH1aBJ4EWdkqqYtMdv1i8Xh1i6ZuHwi", "addrBeingInhumed": "HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/PfHyJiXB9AshvvKmp1eKvGNYWNG8sRELXkMULs8rXRC", "error": "status: code = 2049 message = object not found"}
Oct 20 20:20:55 metis1 neofs-node[2740175]: error        engine/inhume.go:159        inhuming root object but no link object is found        {"linkAddr": "HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/3DVHf4Nmkc41NiHXx1YmJiRCCmoFeLPLNuXvsyS7DtKr", "addrBeingInhumed": "HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/jPPUX7xHJkoLmPFdM74WgQrmgLxAG7b3byi6NkgWnmJ", "error": "status: code = 2049 message = object not found"}
Oct 20 20:20:55 metis1 neofs-node[2740175]: error        engine/inhume.go:159        inhuming root object but no link object is found        {"linkAddr": "HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/58oAuA2naNiaJMdTtnYaWpMVtFNaXbw387yS6teQJDeE", "addrBeingInhumed": "HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/HZnpp3Aiv6EPdYUPiq6BbQJu4RZuNXJHVYi51w9xJ4zf", "error": "status: code = 2049 message = object not found"}

Possible Solution

Fix something

Steps to Reproduce (for bugs)

Not really known.

Context

Mainnet.

Regression

Kinda. #3633 fixed a similar thing, but it looks like the case of completely missing data can still be improved by just dropping the big object from the DB.

Your Environment

Version used: 0.49.1
Server setup and configuration: mainnet
Operating System and version (uname -a): Debian bookworm

Originally created by @roman-khimov on GitHub (Oct 20, 2025). Originally assigned to: @End-rey on GitHub. ## Expected Behavior Objects deleted and never returning again. ## Current Behavior ``` Oct 20 20:20:55 metis1 neofs-node[2740175]: error engine/inhume.go:159 inhuming root object but no link object is found {"linkAddr": "HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/3fLGesRxQuCwVPH1aBJ4EWdkqqYtMdv1i8Xh1i6ZuHwi", "addrBeingInhumed": "HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/PfHyJiXB9AshvvKmp1eKvGNYWNG8sRELXkMULs8rXRC", "error": "status: code = 2049 message = object not found"} Oct 20 20:20:55 metis1 neofs-node[2740175]: error engine/inhume.go:159 inhuming root object but no link object is found {"linkAddr": "HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/3DVHf4Nmkc41NiHXx1YmJiRCCmoFeLPLNuXvsyS7DtKr", "addrBeingInhumed": "HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/jPPUX7xHJkoLmPFdM74WgQrmgLxAG7b3byi6NkgWnmJ", "error": "status: code = 2049 message = object not found"} Oct 20 20:20:55 metis1 neofs-node[2740175]: error engine/inhume.go:159 inhuming root object but no link object is found {"linkAddr": "HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/58oAuA2naNiaJMdTtnYaWpMVtFNaXbw387yS6teQJDeE", "addrBeingInhumed": "HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/HZnpp3Aiv6EPdYUPiq6BbQJu4RZuNXJHVYi51w9xJ4zf", "error": "status: code = 2049 message = object not found"} ``` ## Possible Solution Fix something ## Steps to Reproduce (for bugs) Not really known. ## Context Mainnet. ## Regression Kinda. #3633 fixed a similar thing, but it looks like the case of completely missing data can still be improved by just dropping the big object from the DB. ## Your Environment * Version used: 0.49.1 * Server setup and configuration: mainnet * Operating System and version (`uname -a`): Debian bookworm