etolabo/kumofs

Issues

• Potential error(e.g., resource leak, deadlock) due to the unreleased lock (logpack_lock(lpk)

  #28 opened 3 years ago by jenny-cheung
  1

• kumo server and manager are binding to too many IPs

  #8 opened 5 years ago by lukenowak
  0

• internal compiler error: in extract_insn

  #27 opened 9 years ago by ferseiti
  1

• Documentation on the replication partitioning scheme

  #26 opened 10 years ago by timoc
  0

• kumofs memcache protocol not compatible with dalli memchache client

  #7 opened 14 years ago by nikwest
  1

• Feature Request: Server preference tag for operations

  #23 opened 12 years ago by whardier
  1

• only 1st kumo-server in a cluster gets GET requests

  #6 opened 14 years ago by astro
  4

• kumofs-gateway: potential memory leaks

  #4 opened 14 years ago by astro
  6

• kumo-gateway memcache_binary responds with code 4 (invalid arguments)

  #5 opened 14 years ago by astro
  1

• memcache_text.cc response_get_multi() always prints a CAS of 0

  #2 opened 14 years ago by astro
  2

• Concurrency Control

  #1 opened 14 years ago by astro
  6

• kumo-manager: auto-attach feature?

  #3 opened 14 years ago by astro
  2