beardedeagle/mnesiac

Issues

• 2 nodes, store gets cleared when one (specific one) goes down

  #96 opened 3 months ago by mxgrn
  1

• Any examples of this working in a k8s environment?

  #93 opened a year ago by eliasdarruda
  5

• Running into :mnesia is listed both as a regular application and as an included application from deps whenbuilding release

  #95 opened a year ago by benonymus
  2

• Remote tables detection not working properly

  #84 opened 2 years ago by fabiosuarez-sumup
  6

• Add ability to use Gossip strategy

  #59 opened 4 years ago by KamilLelonek
  9

• Replication factor

  #9 opened 6 years ago by madshargreave
  8

• 0.4.0 checklist

  #53 opened 4 years ago by beardedeagle
  1

• Mnesia crashes and recovers on secondary nodes in clustered configuration

  #2 opened 6 years ago by beardedeagle
  1

• Schemas constantly aren't connected which causes aborted errors

  #22 opened 5 years ago by MikaAK
  1

• Providing record_name option for table, disables its distribution

  #20 opened 5 years ago by aby2503
  1

• How to use with libcluster Kubernetes DNS clustering strategy

  #7 opened 6 years ago by athal7
  4

• Multiple table names for single store creates multiple entries

  #14 opened 6 years ago by beardedeagle
  2

• Inspect remote Mnesia tables before performing copy

  #8 opened 6 years ago by beardedeagle
  8