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.
Investigate add/pin/gc locking · ipfs/kubo#3514 | Good First Issue