akkadotnet/akka.net

Port of Akka actors for .NET

Aaron Stannard

@Aaronontheweb

we use the default byte buffer allocator in our DotNetty transport, which uses pooling

this normally helps performance big time, because it eliminates allocations and keeps GC pressure down

guess I could expose some sort of setting to change the pooling strategy within Akka.Remote's DotNetty transport ("none" being an option)

but anyway, that issue is fixed in DotNetty v0.5.0 and they have one last PR they're trying to sort out before moving ahead with that

Ryan Anthony

@ryandanthony_twitter

@Aaronontheweb thanks for the help that did it. now onto the next problem.

If I have 2+ nodes (cluster sharding) running, and I start sending messages, none are getting processed, once I drop down to 1, processing starts on that node, then I can later add additional nodes and they will sometimes pick up the load.. Is this by design?

am I missing another config?

Aaron Stannard

@Aaronontheweb

oh man, this is running v1.3.5 right?

Ryan Anthony

@ryandanthony_twitter

yea

beta60

Aaron Stannard

@Aaronontheweb

sounds like this bug we fixed

that we're trying to ship in 1.3.6

Ryan Anthony

@ryandanthony_twitter

Aaron Stannard

@Aaronontheweb

if you try the nightlies that should work

Ryan Anthony

@ryandanthony_twitter

Aaron Stannard

@Aaronontheweb

http://getakka.net/community/getting-access-to-nightly-builds.html

my bad on the delay on the 1.3.6 release

Ryan Anthony

@ryandanthony_twitter

I understand

when do you think that the cluster sharding stuff will be out of beta?

Aaron Stannard

@Aaronontheweb

soon, hopefully - we just fixed the biggest bug with it in 1.3.6

Ryan Anthony

@ryandanthony_twitter

ok cool

Jesse Connor

@jesseconnr

Ah well it's good an update is coming. Almost got this downgrade worked out, hopefully it works, otherwise it seems my only option is going to be custom compiling dependencies to get this app live.

Awesome, I don't know why it didn't work before my upgrade, perhaps cleaning everything out and reinstalling the old version fixed something. Every message came through near instantly on 0.4.6.

Aaron Stannard

@Aaronontheweb

:+1:

glad to hear it

Ryan Anthony

@ryandanthony_twitter

after moving to nightlys, I am getting this error:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.MissingMethodException: Method not found: 'Void Hyperion.SerializerOptions..ctor(Boolean, Boolean, System.Collections.Generic.IEnumerable1<Hyperion.Surrogate>, System.Collections.Generic.IEnumerable1<Hyperion.SerializerFactories.ValueSerializerFactory>, System.Collections.Generic.IEnumerable`1<System.Type>)'.

Aaron Stannard

@Aaronontheweb

gotta upgrade the version of the Hyperion serializer too

I suspect

Ryan Anthony

@ryandanthony_twitter

Aaron Stannard

@Aaronontheweb

Akka.Serialization.Hyperion

^^^

Ryan Anthony

@ryandanthony_twitter

I didnt have a reference to it at all

Ryan Anthony

@ryandanthony_twitter

@Aaronontheweb ok nightly builds gave me much better results

thanks again for the help

one question, what triggers a rebalance?

Ryan Anthony

@ryandanthony_twitter

never mind, it looks like I just didnt have enough unique shardsIds in the dataset I was using.

nbparrell

@nbparrell

Can actor tell me its name inside of itself?

nbparrell

@nbparrell

Never mind I think I found what I need. Just to clarify I just need to use self.path.name to find the actors name.

Greatsamps

@Greatsamps

Hi guys

i am having an issue using UnboundedStash

below is a cut-down actor implementation that i am using

   public class ClassName : ReceiveActor, IWithUnboundedStash
   {
    public IStash Stash { get; set; }

    public ClassName()
    {
        ReceiveAny(_ => Stash.Stash());
    }

    void BecomeLoaded()
    {
        Stash.UnstashAll();
    }
    }

the problem i am having is that when BecomeLoaded() is called, i am getting a null pointer exception on Stash

i have not tried sending a message to it to see if one is also thrown on ReceiveAny

any thoughts on this? i can obviously do a null check before calling UnstashAll, but concerned that its not actually working

Bartosz Sypytkowski

@Horusiath

@Greatsamps where are you actually calling BecomeLoaded()?

Greatsamps

@Greatsamps

@Horusiath this is a cut-down implementation, in reality there is another method in the constructor under the ReceiveAny that does some work, then BecomesLoaded()

Ismael Hamed

@ismaelhamed

Upgrading to 1.3.5 from 1.2.3, and I'm starting to see some random serialization exceptions upon restarting some nodes:

Cannot find serializer with id [7]. The most probable reason is that the configuration entry 'akka.actor.serializers' is not in sync between the two systems.

which is weird because that's Akka's persistence serializer, which is loaded automatically

Where communities thrive

People

Repo info

Activity