mirror of
https://github.com/nspcc-dev/neofs-aio.git
synced 2026-03-01 04:28:53 +00:00
Cannot create object right after container start up #17
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mialbu on GitHub (Jan 23, 2023).
With the latest to provide neofs-aio in one single image (commit
74b925abde) I've run into problems when creating an object within ~2 minutes of neofs-aio container start up (after some time passes the object creation workes as expected). I haven't run into that problem with the second to last commit (fd041257f7).I start up the neofs-aio container successfully and run
tick.epochbefore any other code is running. While I have issues with object creation, every other interaction works just fine. This includes the following methods of the Golang client:I am using neofs-sdk-go in a shared library. Specifically, the error appears when the
ObjectWritercallsClose()here. The exact error that is returned is type*apistatus.ServerInternalwith valuestatus: code = 1024 message = not enough nodes to SELECT from.For completeness, the container I try to store the object to has a policy with 1 replica and a backupfactor of 0. The complete container information is the following by using neofs-api-java:
Using that container for all object related integration tests I've written have worked fine with the former commit in neofs-aio and imho should not have had any affect on this issue.
Finally, the logs I get from
docker logs neofs-aio:@roman-khimov
@roman-khimov commented on GitHub (Jan 23, 2023):
Seems to be a node issue to me, but let's have it there for now.
@roman-khimov commented on GitHub (Jan 23, 2023):
In fact, this looks a lot like nspcc-dev/neofs-node#2155 and may be fixed by nspcc-dev/neofs-node#2176.
@roman-khimov commented on GitHub (Apr 17, 2023):
Please retry now with new NeoFS node (after #50).
@mialbu commented on GitHub (Apr 18, 2023):
Hey @roman-khimov I've just tried to use neofs-aio on the latest commit, but I can't start the container. It works with commit
74b925abdewhere you changed the docker-compose to just use one image, but I run into the following error with commitda7afa705e:I get the same error when using the latest commit (
f6c31d6c33).I've cleared the local cache as mentioned in the README but that did not help.
@roman-khimov commented on GitHub (Apr 18, 2023):
Ah, it's just missing from the Docker Hub. If you're to
makeit first, it'll be OK, but let's upload it to the Hub as well...@roman-khimov commented on GitHub (Apr 18, 2023):
Should be OK now either way: https://hub.docker.com/layers/nspccdev/neofs-aio/0.36.0/images/sha256-4cd2fef8eda536daa5525508dfde2888ff730d68dc89ff90cc20765c77dd3750?context=explore
@roman-khimov commented on GitHub (Jun 21, 2023):
We've got 0.37.0 version now, please check.
@mialbu commented on GitHub (Jun 22, 2023):
Hey @roman-khimov, it works with 0.37.0, awesome! Sorry for the late response.