Level/party

Issues

• Can level-party be used with RocksDB?

  #47 opened a year ago by maxlath
  2

• Add support for db.sublevel(prefix)?

  #41 opened 2 years ago by qpwo
  1

• Install master-specific modules.

  #1 opened 2 years ago by mcollina
  2

• level-party leader process holding memory

  #36 opened 2 years ago by maxlath
  11

• Does the leader need to go through socket?

  #28 opened 2 years ago by ronag
  4

• Error: Connection to leader lost

  #8 opened 3 years ago by binarykitchen
  7

• Cannot successfully access same database with two different system users

  #13 opened 8 years ago by medikoo
  4

• Can't use level party with aws efs

  #30 opened 3 years ago by saadshahd
  0

• Always use worker for server?

  #27 opened 3 years ago by ronag
  2

• Using accountdown with level-party causes hangup

  #12 opened 4 years ago
  2

• Node 10

  #17 opened 5 years ago by trisys3
  13

• Add changelog

  #21 opened 5 years ago by vweevers
  0

• When client becomes the "leader" no operations execute against the database

  #11 opened 5 years ago by doowb
  1

• Issue when two processes are accessing same level db instance (same folder name during level party setup)

  #10 opened 5 years ago by jaggukaka
  0

• Errors not propagating?

  #6 opened 5 years ago by vespakoen
  1

• lev and level-party

  #9 opened 5 years ago by mattstyles
  3

• Level-party upgrade for Node 11+ ?

  #18 opened 5 years ago by MongoExpUser
  1

• Broken on node v6.0?

  #14 opened 5 years ago by binarykitchen
  1

• Wrapping level-party breaks it

  #16 opened 5 years ago by eslachance
  1

• No level.destroy() ?

  #15 opened 7 years ago by eslachance
  10

• Why level-prebuilt?

  #7 opened 9 years ago by binarykitchen
  5

• Doesn't always connect

  #5 opened 9 years ago by doowb
  3

• Expected errors different between level-up and level-party

  #3 opened 9 years ago by marsaud
  1

• Chained batch feature broken

  #4 opened 9 years ago by marsaud
  2