Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Nov 28 20:14
    to11mtm synchronize #4642
  • Nov 28 19:46
    to11mtm synchronize #4642
  • Nov 28 19:29
    motmot80 synchronize #4643
  • Nov 28 19:23
    motmot80 edited #4643
  • Nov 28 19:01
    motmot80 opened #4643
  • Nov 28 18:43
    to11mtm synchronize #4642
  • Nov 28 18:11
    motmot80 commented #4641
  • Nov 28 17:48
    to11mtm synchronize #4642
  • Nov 28 16:43
    to11mtm opened #4642
  • Nov 27 23:37
    motmot80 edited #4641
  • Nov 27 23:35
    motmot80 commented #4641
  • Nov 27 23:26
    motmot80 opened #4641
  • Nov 27 07:30
    to11mtm synchronize #4581
  • Nov 27 06:37
    tesgu commented #4639
  • Nov 26 17:31
    razvangoga commented #4215
  • Nov 26 17:28
    razvangoga commented #4215
  • Nov 26 17:18
    Aaronontheweb commented #4215
  • Nov 26 17:16

    Aaronontheweb on 1.4.12

    (compare)

  • Nov 26 17:15

    Aaronontheweb on master

    Bump AkkaVersion from 1.4.5 to … Bump Microsoft.NET.Test.Sdk fro… Bump MongoDB.Driver from 2.10.4… and 10 more (compare)

  • Nov 26 17:15
    Aaronontheweb closed #163
eyantiful
@eyantiful
@Horusiath we should support 15k concurrent msgs in under 100ms.
When you say resolving do you mean ActorSelection?
Jeff Cyr
@JeffCyr
@eyantiful Are you able to batch messages? Akka.Remote cannot handle 150K msg/sec
We are working on increasing the performance of Akka.Remote in v1.5
eyantiful
@eyantiful
@JeffCyr are you talking from single node? the figures are for the cluster as a whole.
@JeffCyr Im currently POC to see how far can we go with minimum nodes in order to asses cluster size...
Jeff Cyr
@JeffCyr
@eyantiful Yes I meant for a single node, I made a benchmark with two nodes on the same machine on loopback, I could get ~6K msg/sec
On v1.5 we were at 100K msg/sec for the same test, and there were still room for improvements
eyantiful
@eyantiful
@JeffCyr Default serializer change ?
Bartosz Sypytkowski
@Horusiath
@eyantiful actor system on a single machine (8 cores) can serve around 20-27mln msg/sec - this can be ofc slowed significantly by things such as persistence, but it also points how important local affinity of actors is
Bartosz Sypytkowski
@Horusiath
also for communication between nodes, take a look at Wire - it supports everything, default akka serializer should support and has quite good performance - you can see some comparison here
Vagif Abilov
@object
I get exception while executing TakeSnapshot command for persistence actors implemented in F#:
"Unable to cast object of type 'Akka.Serialization.WireSerializer' to type 'Akka.Serialization.NewtonSoftJsonSerializer'."
System.InvalidCastException: Unable to cast object of type 'Akka.Serialization.WireSerializer' to type 'Akka.Serialization.NewtonSoftJsonSerializer'.
at Akka.Persistence.FSharp.FunPersistentActor`3.OnCommand(Object msg)
at Akka.Persistence.UntypedPersistentActor.ReceiveCommand(Object message)
at Akka.Persistence.UntypedPersistentActor.Receive(Object message)
at Akka.Actor.ActorBase.AroundReceive(Receive receive, Object message)
at Akka.Persistence.Eventsourced.<ProcessingCommands>b__90_0(Receive receive, Object message)
at Akka.Persistence.Eventsourced.AroundReceive(Receive receive, Object message)
at Akka.Actor.ActorCell.ReceiveMessage(Object message)
at Akka.Actor.ActorCell.Invoke(Envelope envelope)
I inspected Akka code and apparently this line fails:
let serializer = UntypedActor.Context.System.Serialization.FindSerializerForType typeof<obj> :?> Akka.Serialization.NewtonSoftJsonSerializer
Bartosz Sypytkowski
@Horusiath
@object which version of Akka.FSharp are you using?
Vagif Abilov
@object
1.0.7
Jeff Cyr
@JeffCyr
@eyantiful Yes I was using Wire
Bartosz Sypytkowski
@Horusiath
ok, this is a bug
Vagif Abilov
@object
I have configured Wire as serializer, and as you can see that it casts to Newtonsoft.Json
Bartosz Sypytkowski
@Horusiath
I thought, we removed that line some time ago
Vagif Abilov
@object
So the workaround is to get rid of this line and compile from sources?
Zetanova
@Zetanova
This GC Collections test of PerfUtil for Gen0-2 looks interesting
Bartosz Sypytkowski
@Horusiath
@object yes, cause this line was part of workaround, we've made for json.net not being able to properly deserialize some of the f# types
Vagif Abilov
@object
I see. Should I create an issue for that or you will take care of this?
Bartosz Sypytkowski
@Horusiath
please set an issue, I have a limited time for last few months and I could forget that
Vagif Abilov
@object
OK. Should I submit a PR if this is only about removing the line? (If the fix requires a bigger effort, I am afraid I am too new to internals to handle it quickly).
Bartosz Sypytkowski
@Horusiath
as you'll see this is not only a single line
but you could play with it anyway
Vagif Abilov
@object
Yes I already see it's not a single line. But I'll see what I can do.
Bartosz Sypytkowski
@Horusiath
Akka.FSharp API is small, and part of responsible for serialization hack is even smaller
Vagif Abilov
@object
Further investigating F#/Wire persistence problem. It's not only Akka.Persistence.FSharp but also Akka.FSharp that has expectations about JSON.NET as the serializer.
And there is tryDeserializeJObject that is dependent on Newtonsoft.Json.Linq.JObject etc.
But I am not able to provoke an error if I get rid of this stuff and replace with general Akka.Serializer type and FromBinary method call.
So if you are aware of some test that shows necessity for tryDeserializeJObject let me know. As for now, I got rid of this function and its calls and my persistent actors seem to work (I also tested them with the F# persistence example included in Akka solution).
to11mtm
@to11mtm

Hey folks, I have a question about the Simple.Cluster.Transformation sample. I Attempted to set it up such that I have the 'backends' and the frontend running on a second computer (server) , and the client computer is just running a frontend. If I shut down the client, I get some complaints that it is unreachable on the server, but eventually the auto-down-unreachable downs them. If I bring the client back up, everything's back to normal.

However, if I shut the SERVER down, The client can never talk to the server again, even if I bring the server back up... Any ideas as to what I'm doing wrong?

My HOCON looks like this:

akka {
            actor {
              provider = "Akka.Cluster.ClusterActorRefProvider, Akka.Cluster"
            }

            remote {
              log-remote-lifecycle-events = DEBUG
              helios.tcp {
                hostname = "NODE" //CLIENT, or SERVER, depending on where it is run
                port = 65530
              }
            }

            cluster {
              seed-nodes = [
                "akka.tcp://ClusterSystem@SERVER:2551",
                "akka.tcp://ClusterSystem@SERVER:2552"]

              auto-down-unreachable-after = 2s
            }
          }
Bartosz Sypytkowski
@Horusiath
@to11mtm in order to join the cluster, node must know at least one other node being part of it already. Quite probably in your example, server is the node which establishes a cluster, while client is the one which tries to join it. Since node cannot join to cluster, because it's connection is unreachable (server if down), it's marking it as a failing endpoint
Kamil Wojciechowski
@aph5nt
huston... I decided to create new project and use akka1.0.7 + F#. I have created a dummy persistance actor ( https://gist.github.com/aph5nt/8616368185202fcc58808faa82e0fb41) and I got the following error
System.MissingMethodException : Method not found: 'Void Aggregate3..ctor(!2, Microsoft.FSharp.Core.FSharpFunc2<Eventsourced`3<!0,!1,!2>,Microsoft.FSharp.Core.FSharpFunc2<!2,Microsoft.FSharp.Core.FSharpFunc2<!1,!2>>>, Microsoft.FSharp.Core.FSharpFunc2<Eventsourced3<!0,!1,!2>,Microsoft.FSharp.Core.FSharpFunc2<!2,Microsoft.FSharp.Core.FSharpFunc2<!0,Microsoft.FSharp.Core.Unit>>>)'.
at CryptoGames.Game.Mines.Actors.Runa
I have also tried with 'normal' functions declarations ( eg. let execute mailbox state command = () )
did anyone have the same problem ???
Bartosz Sypytkowski
@Horusiath
@aph5nt this sounds like some versioning problem on the F# side (like most of the F# MissingMethodException do)
Kamil Wojciechowski
@aph5nt
@Horusiath runtime is set to 4.4.0.0 and im targeting framework 4.5.2 + referenced fsharp.core from packages (instead of program files)
ok, i will create new standalone console proj
and check it again
to11mtm
@to11mtm
@Horusiath Is there a way to attempt to 're-join' without restarting the entire actorsystem?
Bartosz Sypytkowski
@Horusiath
you need to know the list of nodes, that will be used to join/create the cluster
Kamil Wojciechowski
@aph5nt
@Horusiath ok, in f# console app it works
Bartosz Sypytkowski
@Horusiath
one of the common patterns is to have at least single node that is serves only as connection endpoint with well known address. It doesn't need to perform any work out there, it just needs to be present (see lighthouse project)
to11mtm
@to11mtm
@Horusiath : I will give that a try. As I'm learning the clustering pieces and moving forward, I'm continually reminded of your blog post comment about monads =)
to11mtm
@to11mtm
@Horusiath : THANK YOU! Lighthouse as the middleman does the trick like a charm
Kamil Wojciechowski
@aph5nt
@Horusiath it was R# issue :(
ilhadad
@ilhadad

Guys I am having an issue with with an ask. This is the code making the ask. This code resides in one node:

SupervisorRegistryGetListRequest request = new SupervisorRegistryGetListRequest(Self);
            //Make the ask
            _SupervisorRegistry.Ask<SupervisorRegistryGetListResponse>(request).ContinueWith<SupervisorRegistryGetListEvent>(taskResponse =>
            {
                SupervisorRegistryGetListResponse r = taskResponse.Result as SupervisorRegistryGetListResponse;
                if (taskResponse.IsFaulted)
                {
                    return new SupervisorRegistryGetListEvent(request, r, false);
                }
                return new SupervisorRegistryGetListEvent(request, r, true);
            }).PipeTo(Self);

and the config is:

akka {
                    # here we are configuring log levels
                    log-config-on-start = off
                    stdout-loglevel = DEBUG
                    loglevel = DEBUG

          // Define an Nlog logger for the Akka system
          loggers = ["Akka.Logger.NLog.NLogLogger, Akka.Logger.NLog"]

            actor {
              provider = "Akka.Cluster.ClusterActorRefProvider, Akka.Cluster"
            }

            remote {
                            log-remote-lifecycle-events = DEBUG
                            log-received-messages = on

            helios.tcp {
                                transport-class = "Akka.Remote.Transport.Helios.HeliosTcpTransport, Akka.Remote"
                                applied-adapters = []
                                transport-protocol = tcp
                                #will be populated with a dynamic host-name at runtime if left uncommented
                                #public-hostname = "POPULATE STATIC IP HERE"
                                hostname = "127.0.0.1"
                                port = 8777
              }
            }
}

and this is the code replying to the ask resides on a different node:

            Receive<SupervisorRegistryGetListRequest>(r => HandleGetListRequest(r));
... more code here...
 private void HandleGetListRequest(SupervisorRegistryGetListRequest r)
        {
            ImmutableDictionary<MicroServices.Area,IActorRef> immutableDictOfSupervisorsActors = 
                _KnownSupervisorsActors.ToImmutableDictionary(kvp => kvp.Key, kvp => kvp.Value.SupervisorActorReference);

            r.Requestor.Tell(new SupervisorRegistryGetListResponse(r.Requestor,immutableDictOfSupervisorsActors,r));

        }

and it's config is:

akka {
                    # here we are configuring log levels
                    log-config-on-start = off
                    stdout-loglevel = DEBUG
                    loglevel = DEBUG

          // Define an Nlog logger for the Akka system
          loggers = ["Akka.Logger.NLog.NLogLogger, Akka.Logger.NLog"]

          // Enables connectivity to the remote ActorSystemBridge
          actor {
            provider = "Akka.Cluster.ClusterActorRefProvider, Akka.Cluster"
            debug {
              receive = on
              autoreceive = on
              lifecycle = on
              event-stream = on
              unhandled = on
            }

          }

          remote {
            log-remote-lifecycle-events = DEBUG
            helios.tcp {
                transport-class = "Akka.Remote.Transport.Helios.HeliosTcpTransport, Akka.Remote"
                transport-protocol = tcp
                port = 8888
                hostname = "127.0.0.1"
            }
          }
}

The receive is being triggered, however, the message never gets back to the ask. Not sure what's wrong. How can I check what is happening with the reply?