Re: [akka-user] CRDT gossip implementation - replication flow

2017-02-02 Thread Patrik Nordwall
Hopefully we can have a release candidate of 2.5.0 out within a month. The more people that help out with the remaining tasks the quicker we can get it done. See issues on github milestone 2.5.0. We can also release another milestone if needed. /Patrik tors 2 feb. 2017 kl. 06:07 skrev Vadim Punski

Re: [akka-user] CRDT gossip implementation - replication flow

2017-02-02 Thread Vadim Punski
What is the road map and timeline? > -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/faq.html >> Search the archives: https://groups.google.com/group/akka-user --- You received this me

Re: [akka-user] CRDT gossip implementation - replication flow

2017-01-31 Thread Patrik Nordwall
On Tue, Jan 31, 2017 at 7:26 AM, Vadim Punski wrote: > > > On Tuesday, January 31, 2017 at 4:02:51 PM UTC+2, Patrik Nordwall wrote: >> >> >> >> On Tue, Jan 31, 2017 at 6:42 AM, Vadim Punski wrote: >> >>> >>> >>> On Monday, January 30, 2017 at 4:29:13 PM UTC+2, Patrik Nordwall wrote: >>

Re: [akka-user] CRDT gossip implementation - replication flow

2017-01-31 Thread Vadim Punski
On Tuesday, January 31, 2017 at 4:02:51 PM UTC+2, Patrik Nordwall wrote: > > > > On Tue, Jan 31, 2017 at 6:42 AM, Vadim Punski > wrote: > >> >> >> On Monday, January 30, 2017 at 4:29:13 PM UTC+2, Patrik Nordwall wrote: >>> >>> >>> It's sent to one random node per tick, not all nodes. >>> >> >>

Re: [akka-user] CRDT gossip implementation - replication flow

2017-01-31 Thread Patrik Nordwall
On Tue, Jan 31, 2017 at 6:42 AM, Vadim Punski wrote: > > > On Monday, January 30, 2017 at 4:29:13 PM UTC+2, Patrik Nordwall wrote: >> >> >> It's sent to one random node per tick, not all nodes. >> > > Node per tick, you're right ... > > >> The reason for sending all digests is to be able to find

Re: [akka-user] CRDT gossip implementation - replication flow

2017-01-31 Thread Vadim Punski
On Monday, January 30, 2017 at 4:29:13 PM UTC+2, Patrik Nordwall wrote: > > > It's sent to one random node per tick, not all nodes. > Node per tick, you're right ... > The reason for sending all digests is to be able to find entries that are > not the same. Remember that message delivery is

Re: [akka-user] CRDT gossip implementation - replication flow

2017-01-30 Thread Patrik Nordwall
On Sun, Jan 29, 2017 at 3:04 AM, Vadim Punski wrote: > Hi, > > I'm new to Akka and CRDT, so take the below with a grain of salt. > I'm trying to implement the application requirements with thousands of > LWW-Maps, not related to each other. > The implementation itself is not the main issue I have

[akka-user] CRDT gossip implementation - replication flow

2017-01-29 Thread Vadim Punski
Hi, I'm new to Akka and CRDT, so take the below with a grain of salt. I'm trying to implement the application requirements with thousands of LWW-Maps, not related to each other. The implementation itself is not the main issue I have, but the internal "distributed data" gossip protocol implementa