These are chat archives for atomix/atomix

27th
Sep 2018
Alex Robin
@alexrobin
Sep 27 2018 07:30
@kuujo no problem, I read bout your toddler after i posted the message. I hope he is ok.
So like I said what I'm trying to implement is a datastore primitive with custom indexing and more search capabilities that a typical map. This primitive needs to persist its own state (i.e. the indexed data) and I will be using the primitive-backup protocol or even direct client to backup communications for low latency / high throughput reads.
Alex Robin
@alexrobin
Sep 27 2018 07:35
The only reason I need the primitive name and memberID is because I want to make sure I create a uniquely named folder in case multiple instances of Atomix and/or of the primitive are run on the same machine. Thanks for pointing me to the getServiceName() method, I forgot that service name and primitive name are the same indeed (I saw that in the code after)
Alex Robin
@alexrobin
Sep 27 2018 07:42
I guess the other way (for that particular use case) would be that the server context provides the path to a "data directory" to the service and let us configure this path at the member level perhaps, much like what is done for the Raft protocol. What do you think?
Jordan Halterman
@kuujo
Sep 27 2018 20:57
@alexrobin indexing does seem like a legit use case. That makes sense. I say go for it! We probably just need to have a warning in the Javadoc to avoid exposing it to the client in any way
Luca Burgazzoli
@lburgazzoli
Sep 27 2018 20:59
hey I'm trying to create a new component for apache camel for atomix v3 (ve do already have the v1) but I'm not able to create a simple single node 'cluster' for testing purpose
what happens is that invoking Atomix.start() never completes so the process is locked at Atomix.start().join()
Jordan Halterman
@kuujo
Sep 27 2018 21:05

FYI I know we’ve had conversations about Kubernetes recently here @mmanco

Kubernetes!

Atomix now has Helm charts for Kubernetes:
https://github.com/atomix/atomix-k8s

The chart should be officially released next week, but I wanted to share it for anyone that wants to help out. Keep in mind the chart is based on the Docker image built from several PRs that have yet to be merged.

The chart defines a StatefulSet that circumvents the DNS bootstrapping issue using the publishNotReayAddresses option. It supports arbitrary Atomix configurations and uses an init container to construct the configuration used in pods on an emptyDir volume shared with the Atomix pods.

I’m hoping to get all the relevant PRs merged and a new release out this week so we can publish the Helm chart next week.

Luca Burgazzoli
@lburgazzoli
Sep 27 2018 21:12
@kuujo that's nice
@kuujo do you have any spare time to look at my problem porting the apache camel component to the atomix v3 ?
Luca Burgazzoli
@lburgazzoli
Sep 27 2018 21:39
I think I found it, it was a problem of wrong guava version being on the classpath
Jordan Halterman
@kuujo
Sep 27 2018 21:40
I hate the Guava dependency
for this reason
we need to make an effort to remove it for 3.1