These are chat archives for atomix/atomix

20th
Jun 2018
william.z
@zwillim
Jun 20 2018 05:50
management-group:
type: raft
name: system
partitions: 1
data-directory: target/test-logs/system
members:
- node1
- node2
- node3
the name system is needed
FKrack
@FKrack
Jun 20 2018 06:38
Thank you for your answer. But that does not change anything. I still get the exception.
Johno Crawford
@johnou
Jun 20 2018 07:26
what config are you using now and has the exception changed
FKrack
@FKrack
Jun 20 2018 07:35
cluster {
  name: test
  members.1 {
    id: node1
    address: "localhost:5001"
  }
  members.2 {
    id: node2
    address: "localhost:5002"
  }
  members.3 {
    id: node3
    address: "localhost:5003"
  }
}

managementGroup {
  name: system
  type: raft
  partitions: 1
  dataDirectory: target/test-logs/system
  members: [node1, node2, node3]
}

partitionGroups.raft {
  type: raft
  storageLevel: memory
  partitions: 7
  partitionSize: 3
  dataDirectory: target/test-logs/raft
  members: [node1, node2, node3]
}

partitionGroups.data {
  type: primary-backup
  partitions: 7
}

primitives.test {
  type: map
  cacheEnabled: true
  protocol {
    type: multi-raft
    group: raft
  }
}
java -cp bin/* io.atomix.agent.AtomixAgent "-c d:\atomixServer3.0\atomix.conf" node1@localhost:5001
FKrack
@FKrack
Jun 20 2018 08:57
I made it work by copying the conf file to a jar in the classpath.
name: system is not necessary!
A conf file with path in -c parameter does not work.
Jordan Halterman
@kuujo
Jun 20 2018 09:04
Yeah that’s because of the change to the configuration format. Just add atomix.conf to the classpath now. Doesn’t have to be inside a jar
We have to add an additional method to take a File in the Atomix factories to make sure paths work correctly because Typesafe Config only tries to search the classpath if you don’t explicitly parse a file
Should open a bug for that
FKrack
@FKrack
Jun 20 2018 09:18
Ok! I write a bug.