Closed mialbu closed 1 year ago
Seems to be a node issue to me, but let's have it there for now.
In fact, this looks a lot like nspcc-dev/neofs-node#2155 and may be fixed by nspcc-dev/neofs-node#2176.
Please retry now with new NeoFS node (after #50).
Please retry now with new NeoFS node (after #50).
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 74b925abde8a96ea22882d73b1ad797d30d7d5fb where you changed the docker-compose to just use one image, but I run into the following error with commit da7afa705e4ab4351061a663eeceda631b8aad70:
I get the same error when using the latest commit (f6c31d6c33917817d2741356efb1a0462d824608).
I've cleared the local cache as mentioned in the README but that did not help.
Ah, it's just missing from the Docker Hub. If you're to make
it first, it'll be OK, but let's upload it to the Hub as well...
We've got 0.37.0 version now, please check.
We've got 0.37.0 version now, please check.
Hey @roman-khimov, it works with 0.37.0, awesome! Sorry for the late response.
With the latest to provide neofs-aio in one single image (commit 74b925abde8a96ea22882d73b1ad797d30d7d5fb) 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 (fd041257f7ab74b2e81eeb1a409ce9ce84676c13).
I start up the neofs-aio container successfully and run
tick.epoch
before 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
ObjectWriter
callsClose()
here. The exact error that is returned is type*apistatus.ServerInternal
with 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