ipfs/kubo

Investigate add/pin/gc locking

Open

#3,514 创建于 2016年12月16日

在 GitHub 查看
 (1 评论) (1 反应) (0 负责人)Go (13,906 star) (2,725 fork)batch import
help wantedkind/testtopic/commands:addtopic/repo

描述

While looking into #3470 and #3436, I found that the locks around adding/pinning/GC look really wonky and inconsistent.

This issue is a reminder that we need to:

  • Look very closely at which locks are in play
  • Document in detail how these locks work
  • Write stress tests which make sure we don't end deadlock ourselves

贡献者指南

技术栈
go
领域
backend
议题类型
research
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
over 1 week
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
needs investigation
前置要求
Go concurrencyIPFS internals
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
15
研究方向
Investigate the locking mechanisms around add/pin/GC operations in the IPFS Go implementation (kubo). Start by examining the code referenced in issues #3470 and #3436. Document the current lock usage, identify inconsistencies, and propose a consistent locking strategy. Finally, write stress tests to ensure deadlock free operation.