Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 13:23
    Aaronontheweb commented #4096
  • 13:22
    Aaronontheweb commented #4093
  • 13:16
    ismaelhamed commented #4093
  • 13:04
    ismaelhamed edited #4097
  • 13:04
    ismaelhamed opened #4097
  • 12:50
    ismaelhamed commented #4096
  • 12:48
    ismaelhamed commented #4096
  • 12:05
    Aaronontheweb commented #4096
  • 11:43
    ismaelhamed commented #4096
  • Dec 14 19:13
    hwanders commented #4096
  • Dec 14 13:05
    IgorFedchenko commented #4085
  • Dec 14 03:08
    hhko commented #4094
  • Dec 13 21:37
    Aaronontheweb commented #4085
  • Dec 13 20:28
    IgorFedchenko commented #4085
  • Dec 13 20:27
    IgorFedchenko commented #4085
  • Dec 13 15:38
    Aaronontheweb labeled #4096
  • Dec 13 15:38
    Aaronontheweb milestoned #4096
  • Dec 13 15:38
    Aaronontheweb labeled #4096
  • Dec 13 15:38
    Aaronontheweb opened #4096
  • Dec 13 10:41
    peirens-bart opened #4095
Aaron Stannard
@Aaronontheweb
@mmisztal1980 I need to update it to 1.1.2 Akka
that should fix it
DNS / IPv6 stuff
Daniel D'Agostino
@dandago2_twitter
hey guys, from http://getakka.net/docs/clustering/cluster-overview I read: "NOTE: Akka.Cluster is currently a pre-release nuget package, so you'll need to set the pre flag when you install it into your applications. Akka.Cluster will be considered "fully released" once Akka.NET v1.1 ships." -- I thought both Akka .NET 1.1 and Akka.Cluster were already out, so is this just a case of outdated documentation? :)
Arjen Smits
@Danthar
yes.
You are more then welcome to do a PR :)
Daniel D'Agostino
@dandago2_twitter
I'm not sure what workflow you use for these updates :)
Arjen Smits
@Danthar
Simple. Fork the getakka.net repo. Make the changes in the .md file as needed.
Make a commit to your fork, and do a PR from there
Daniel D'Agostino
@dandago2_twitter
oh, PR works across repos on github?
I'll give it a try later, thanks :)
Arjen Smits
@Danthar
And in general this doc applies: http://getakka.net/docs/Contributing%20to%20Akka
But yeah if you fork from a repo. Github tracks that your repo is a Fork, and that it has an upstream repository linked to it. It then allows you to make a PR to that upstream repo.
Daniel D'Agostino
@dandago2_twitter
I'm reading up on clustering, and was just wondering whether it's possible to assign roles dynamically, rather than fixed from config
e.g. have something that tells a node that it needs to adopt a certain role, according to arbitrary demands
Damian Reeves
@DamianReeves

So I'm working on an application that will have Aggregate Roots like in DDD. I currently see the need to have an actor that given a message, figures out the target entity type and then "activate" the persistent actor for that given entity (by id).

In doing research I came across this statement in the Akka.Cluster.Sharding module:

Cluster sharding is useful in cases when you want to contact with cluster actors using their logical id's, but don't want to care about their physical location inside the cluster or manage their creation. Moreover it's able to rebalance them, as nodes join/leave the cluster. It's often used to represent i.e. Aggregate Roots in Domain Driven Design terminology.

Is my use a canonical example for using cluster sharding? What if I have usages of this pattern that aren't clustered but only have 1 node?

Bartosz Sypytkowski
@Horusiath
@DamianReeves you can use cluster sharding for only 1 node
Damian Reeves
@DamianReeves
Cool, does my description of my usecase fit sharding?
Bartosz Sypytkowski
@Horusiath
yes ;)
Damian Reeves
@DamianReeves
:+1:
Do you have any usage examples?
Bartosz Sypytkowski
@Horusiath
There is an example in the core repo. I think it's missing use case of passivation
but this one is present in docs
Damian Reeves
@DamianReeves
cool... thanks again
Daniel D'Agostino
@dandago2_twitter
hey guys, I'm trying a really bare-bones test of Akka.Cluster based on the documentation here: http://getakka.net/docs/clustering/cluster-overview
akka {
    actor.provider = "Akka.Cluster.ClusterActorRefProvider, Akka.Cluster"
    remote {
        helios.tcp {
            port = 8081
            hostname = localhost
        }
    }
    cluster {
        seed-nodes = ["akka.tcp://ClusterSystem@127.0.0.1:8081"]
    }
}
This doesn't actually work
but if I change both host names to localhost, or both to 127.0.0.1, it works
it looks like Akka doesn't realise that they are actually the same thing
Daniel D'Agostino
@dandago2_twitter
Another thing: If I run a standalone node with itself configured as seed node, I see no errors. If I set up a non-seed node using the aforementioned node as seed node, I get the following error:
blob
Daniel D'Agostino
@dandago2_twitter
OK disregard the last error, had the wrong actorsystem name configured
Damian Reeves
@DamianReeves
For cluster sharding it would seem that I need to keep track of the ShardRegions I've created. If I call Start(...) or StarAsync(...) twice for the same type it throws and if I call ShardRegion(type) without previously starting a type it throws... am I missing something?
Bartosz Sypytkowski
@Horusiath
@DamianReeves shard region is singleton in actor system scope, if you're using one actor system for your application, you may set shard region as static property. Also there is other method ClusterSharding.ShardRegion(typeName) which will return shard region if it exists.
Damian Reeves
@DamianReeves
I get that, but lets say I have 2 AggregateRoots: Inventory and Customer it seems I'd have 2 regions and if I added Product it would be a third, is this the wrong approach?
I'm looking to do something like this:
        ReceiveAsync<AggregateCommandEnvelope>(async envelope =>
        {
            IActorRef shardRegion;
            var aggregateType = envelope.AggregateType;
            var aggregateTypeName = envelope.AggregateType.FullName; //TODO: May need to safe guard this in a different manner
            if(!_aggregateShardRegions.TryGetValue(aggregateTypeName, out shardRegion))
            {
                shardRegion =
                    await _sharding.StartAsync(
                        aggregateTypeName, 
                        Props.Create(aggregateType),
                        ClusterShardingSettings.Create(Context.System), 
                        new ShardingMessageExtractor(10)
                    );
            }
        });
Bartosz Sypytkowski
@Horusiath
yes
in general identifier of your entity (sharded actor) is something like (string typeName, string shardId, string entityId)
Damian Reeves
@DamianReeves
Ok, so in my example the typeName I pass to the sharding.Start is a broader concept like InventoryManagementSystem
Bartosz Sypytkowski
@Horusiath
ClusterSharding.ShardRegion(typeName) matches the ClusterSharding.Start(typeName: ...) parameter
Francis Paulin
@paulinfrancis

Hi all, I'm just getting into akka .net, and have a question I hope somebody can shed some light on. I've got an ASP .NET Core app, where I have wired SignalR and Akka together.

One of my actors parses some files, and tells my SignalR bridge to notify the clients with the resulting object.

I got an error:

The calling thread cannot access this object because a different thread owns

From json.net when it tried to serialize the object before SignalR sent it to the connected clients.

Without changing anything, the exception is no longer thrown, and everything works.

Am I experiencing issues with the dispatcher? If yes, what is the recommended configuration?

Thanks :)

Bartosz Sypytkowski
@Horusiath
@paulinfrancis how are you calling a signalr api?
Daniel D'Agostino
@dandago2_twitter
Where do I find the source for the Akka .NET documentation exactly?
Bartosz Sypytkowski
@Horusiath
@dandago2_twitter http://getakka.net/docs/ . You can also suplement it with docs for akka jvm in many situations
Daniel D'Agostino
@dandago2_twitter
I just want to edit it :)
Francis Paulin
@paulinfrancis

In my actor system init

public static void Create(IHubContext context, ISimulator simulator)
{
    _signalRSimulatorEventsPusher = new SignalRSimulatorEventsPusher(context);

    _actorSystem = ActorSystem.Create("SimulatorSystem");

    var signalRBridgeProps = Props.Create(() => new SignalRBridgeActor(_signalRSimulatorEventsPusher, ActorReferences.Simulator));
    ActorReferences.SignalRBridge = _actorSystem.ActorOf(signalRBridgeProps, "SignalRBridge");

    //Kosher?
    var simulatorProps = Props.Create(() => new SimulatorActor(simulator, ActorReferences.SignalRBridge));
    ActorReferences.Simulator = _actorSystem.ActorOf(simulatorProps, "Simulator");
}

In my SimulatorActor:

Receive<DiagramLoadedMessage>(message => signalRBridgeActor.Tell(message));

In SignalRBridgeActor. This is where it sometimes blows up.

Receive<DiagramLoadedMessage>(message =>
{
        _simulatorEventsPusher.NotifyLoadedDiagram(message.DiagramRootObject);
});
Daniel D'Agostino
@dandago2_twitter
@Horusiath what do you use to preview the markdown output when you edit the docs?
Bartosz Sypytkowski
@Horusiath
you've abstracted meat away ;) I was using signalr with actors by wrapping signalr hub/connection with an actor (like Props.Create(() => new SignalRActor(signalrHub)))
@dandago2_twitter vscode with markdown plugin
Francis Paulin
@paulinfrancis

I had a look here: http://getakka.net/docs/working-with-actors/Dispatchers, so I tried:

var signalRBridgeProps = Props.Create(() => new SignalRBridgeActor(_signalRSimulatorEventsPusher, ActorReferences.Simulator))
                                                                  .WithDispatcher("akka.actor.synchronized-dispatcher");

But it errors: "The current SynchronizationContext may not be used as a TaskScheduler."