-
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Operation Stopped - January 2022 #62
Comments
Hey @rpodgorny, yeah sorry for not creating a tracking issue earlier. I know some people rely on this service, like me as well. It would be nice to get it more stable. However, this is still limited by the pre-production status of go-ipfs. What happened:
While a So I removed the block storage and started a reimport. After 3 days (way longer than a full import usually takes) I've noticed that the IO had completely stopped, while IPFS was using 1.6-1.8 cores continuously. The script was waiting several minutes on simple I've sent two dumps to @aschmahmann and tried to find the culprit, to no avail atm. The dumps are
So as long these performance issues are not fixed I can't do a reimport on 0.12rc1. Still undecided if I should roll back and retry or do a git bisect to find the commit(s) which introduced the issue. |
Just for reference, that's the conversation with @@aschmahmann yesterday (from my timezone's perspective):
|
@aschmahmann I'm now running the import offline |
I've posted the issue with the import now at ipfs/go-ipfs: ipfs/kubo#8694 |
The offline import has finished. Not sure about the performance though - haven't observed it. |
does this mean it's supposed to be publicly available by now? i'm unable to even get listing as of now... |
@rpodgorny nope, not yet. While the Archlinux part was imported, the Manjaro portion did throw an ipfs error on a I'll retry this one more time, and if this fails I think I'll just roll the version back. 0.12 is just not mature enough. 🤷 |
I've tried again. It will just stop at random locations:
Since a repeat of this command is successful this looks like a race condition to me, @aschmahmann. So I'll just roll back to 0.11. |
0.11 has the same issue. |
heh, sounds like ipfs team has some bisecting to do... ;-) ...is there any upstream ticket to track this? |
@rpodgorny yeah, have a look: |
...maybe you meant this one? -> ipfs/kubo#8694 |
Well, that's what I referenced in my comment ;D |
I've installed 0.9.1 on the server and the import worked flawlessly. So it's up and running again (currently catching up a day or so). Switching to the IPFS mirror should be safe in an hour or two since you would otherwise get "downgraded package" messages or not receive updates. :) |
hello,
i'm taking to the liberty to create this issue to track the progress of the current import issue (as of 2022-01-22). regurarly checking the status page and/or matrix proved to be too cumbersome - at least for me.
that being said, what is the current state, @RubenKelevra ? is there any way i (or anyone else) can help?
thanks!
The text was updated successfully, but these errors were encountered: