akkadotnet/akka.net

Port of Akka actors for .NET

Weston

@ronnyek

maybe I'll take a crack at it

does it run under mono to your knowledge

Graeme Bradbury

@GraemeBradbury

:+1: tell us how you get on, would be interested to hear how it goes.

I think stefansedich is working on getting 4.3 to work.

tru3d3v

@tru3d3v

Hi, is it possible if i send text file (133KB) from akka server to client Akka ?. i have try but client is not respond

public class HelloActor : UntypedActor
{
public HelloActor()
{
}

protected override void OnReceive(object request)
{
var data = System.IO.File.ReadAllText(AppDomain.CurrentDomain.BaseDirectory+"myfile.txt");
Sender.Forward(data);
}

}
var actor = System.ActorSelection("HelloActor");
return await actor.Ask<string>(null, TimeSpan.FromHours(1));
is it to large for 133 KB txt file ?
and this is my config hocon at server
remote {

    log-sent-messages = on
    log-received-messages = on
    maximum-frame-size = 10MB

thedarkdestructor

@thedarkdestructor

Hi guys. Anyone know a link for a good tutorial for a akkadotnet FSM? I have only seen the official documentation but it is quite poor...

Bartosz Sypytkowski

@Horusiath

@chillitom Update on PersistentView triggers it to send ReplayMessages message to the journal. In result it replays events that happened from the last replayed message received

tru3d3v

@tru3d3v

Guys. Anyone can explain about large message ? is it to large for 133 KB txt file

???

Aaron Stannard

@Aaronontheweb

@forki thanks! this was on VS build

@tru3d3v 10mb isn't a valid value for that setting

it's expressed as "total bytes"

public long? GetByteSize()
        {
            var res = GetString();
            if (res.EndsWith("b"))
            {
                var v = res.Substring(0, res.Length - 1);
                return long.Parse(v);
            }

            return long.Parse(res);
        }

Aaron Stannard

@Aaronontheweb

so you need to multiply 10 1024 1024 to get 10mb :p

bah, stupid markdown

10 * 1024 * 1024

Stefan Sedich

@stefansedich

or be greedy and go for 1000

Aaron Stannard

@Aaronontheweb

@BrainSlugs83 another hack I've seen for doing this is pinning your "singleton" to the Akka.Cluster leader

you can use gossip messages to tell if a given node is the leader

and when leader == self then create singleton

otherwise have everyone else look for it

there's only 1 leader in the cluster at any time

and leaders change only when the previous leader was gracefully terminated or forcibly removed by a human

which is why that hack works pretty well

Aaron Stannard

@Aaronontheweb

@Horusiath nightlies should be working again now

kicking one off

Stefan Sedich

@stefansedich

@ronnyek @GraemeBradbury I am working on getting it to build and run tests which is a nightmare, for one it won't even build under mono 4.2 as some methods used in the IO stuff is not even in mono 4.2 and was only added a month ago.

would be scary to run it without knowing it builds and all tests pass as who knows what is missing at runtime.

Mikey

@BrainSlugs83

@Horusiath, thanks for the heads up -- @Aaronontheweb -- double thanks, that seems like it will work well -- especially with a persistent actor (new singleton comes up and will get the last committed state) -- I'm thinking if a node gets a message that it's no longer the leader it should stop the singleton actor too...

Is there anyway to specify that certain roles cannot be the leader? (I have some roles in my cluster that are transient.)

(Or the opposite of that, to declare: "only these roles can be the leader?" -- black-list or white-list works for me, just need to keep the transients from becoming leaders.)

Aaron Stannard

@Aaronontheweb

heh, that's a good question - no, there isn't at the moment

typically though, one of your seed nodes will almost always be your leader

so just boot the non-transient ones first

the other thing you can do... just thinking about this

is have the leader, whoever it is

it can be any type of node

use a clustered router to deploy your "singleton" actor onto a specific type of role

like instead of having that actor run on the leader itself

the leader instead just becomes responsible for 1. checking if that actor has already been deployed and then 2. deploying it onto a specific role if it hasn't

Mikey

@BrainSlugs83

Oh not a bad idea -- have the leader run the clustered router...

Right -- have to check if it's already been deployed, that makes sense...

Aaron Stannard

@Aaronontheweb

yeah, that's a small bit of "consistency" price you have to pay in exchange for decoupling :p

Mikey

@BrainSlugs83

How would I detect if it's gone down? -- will a deathwatch on the actor itself work, or should I deathwatch on the node itself? (can the router tell me what node it deployed it the "singleton" to?)

Aaron Stannard

@Aaronontheweb

if the router is configured to only deploy a single routee

which is easy to do

you can use router.Tell(new Identify("are you a singleton?"))

and the routee will reply back with ActorIdentity

and then you can Deathwatch the routee

Stefan Sedich

@stefansedich

sigh so I just chucked a simple console app at my mono dev VM, and that segfaulted just running.

Aaron Stannard

@Aaronontheweb

Identify is an auto-received message

Where communities thrive

People

Repo info

Activity