Yes, it will be fixed. I don't think it will cause any critical problems.
It's only when you do updates at a high rate and then the delta messages
will be dropped. Delivery of deltas are not mandatory for correct end
result. Make sure you use latest version, though. 2.5.2.
If it's annoying you
Hello Patrik,
Will this bug be fixed? Can you suggest me some quick work around?
Thanks,
Mainak
On Wed, May 24, 2017 at 8:24 AM, Patrik Nordwall
wrote:
> That's interesting. I see the same problem when running that example. It
> shouldn't be much data involved
That's interesting. I see the same problem when running that example. It
shouldn't be much data involved there. I have created issue
https://github.com/akka/akka-samples/issues/25 and will look into it.
/Patrik
On Tue, May 23, 2017 at 7:25 PM, Mainak Ghosh
wrote:
> Hey
Hey Patrick,
I might have pasted the wrong log. Here is the correct one:
[JVM-1] [INFO] [05/22/2017 16:31:25.245] [ScalaTest-main]
[akka.remote.Remoting] Starting remoting
[JVM-3] [INFO] [05/22/2017 16:31:25.245] [ScalaTest-main]
[akka.remote.Remoting] Starting remoting
[JVM-2] [INFO]
I can't see that error in the log messages you included, but in general:
http://doc.akka.io/docs/akka/2.5/scala/distributed-data.html#Limitations
You can sometimes split one data entry into several, e.g. instead of having
one huge ORSet you can use 10 ORSet at the top level and pick the right one
Hello,
I am trying to run the akka distributed data sample in Java using Akka 2.5.
I am getting the following error:
[JVM-3] [INFO] [05/22/2017 16:31:12.845] [ScalaTest-main]
[akka.remote.Remoting] Starting remoting
[JVM-1] [INFO] [05/22/2017 16:31:12.861] [ScalaTest-main]