-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
fatal error: concurrent map iteration and map write #6418
Comments
Not sure why this didn't show up sooner. fixes #6418
@Stebalien - seeing this on several nodes on 0.4.22, with the following stack trace:
is there anything we can do to prevent encountering this scenario? |
This is a different issue that was fixed in libp2p/go-libp2p-swarm#134. This change was not included in go-ipfs 0.4.22, you'll have to either cherry-pick this change, use go-ipfs master, or wait for go-ipfs 0.5.0 (which should be released by the new year). |
Fixes a concurrent map access issue: #6418. The fix for this somehow didn't make it into 0.4.22 either.
Fixes a concurrent map access issue: ipfs#6418. The fix for this somehow didn't make it into 0.4.22 either.
Fixes a concurrent map access issue: ipfs#6418. The fix for this somehow didn't make it into 0.4.22 either.
Fixes a concurrent map access issue: ipfs#6418. The fix for this somehow didn't make it into 0.4.22 either.
Hey, Version details
|
@0xsarvesh this is a known issue, please update to 0.17 |
Version information:
Description:
Regular operation of an IPFS node crashed due to what would appear to be a data race?
Output from the logs can be viewed on IPFS via Qmb39D6U7YWx49kNSTVFb8iXpZ5zAT8qfdiF2bRraEo9eC
The text was updated successfully, but these errors were encountered: