Where communities thrive

Join over 1.5M+ people
Join over 100K+ communities
Free without limits
Create your own community

Explore more communities

akkadotnet/akka.net

Port of Akka actors for .NET

People

Repo info

Activity

Apr 08 23:26

Arkatufus synchronize #4372
Apr 08 23:15

Arkatufus synchronize #4372
Apr 08 23:15

Arkatufus synchronize #4372
Apr 08 22:51

Aaronontheweb synchronize #4373
Apr 08 22:51

Aaronontheweb on 1.4.5-release-notes

(compare)
Apr 08 22:51

Aaronontheweb on dev

v1.4.5 release_notes.md placeho… (compare)
Apr 08 22:51

Aaronontheweb closed #4374
Apr 08 22:47

Aaronontheweb opened #4374
Apr 08 22:43

Aaronontheweb synchronize #4373
Apr 08 22:41

Aaronontheweb on 1.4.5-release-notes

v1.4.5 release_notes.md placeho… (compare)
Apr 08 22:40

Aaronontheweb synchronize #4373
Apr 08 22:04

Aaronontheweb labeled #4373
Apr 08 22:04

Aaronontheweb labeled #4373
Apr 08 22:04

Aaronontheweb opened #4373
Apr 08 21:04

Arkatufus commented #4372
Apr 08 21:01

Arkatufus synchronize #4372
Apr 08 20:52

Arkatufus synchronize #4372
Apr 08 20:36

Arkatufus synchronize #4372
Apr 08 20:33

Arkatufus commented #4372
Apr 08 20:33

Arkatufus opened #4372

Aaron Stannard

@Aaronontheweb

but this looks really clearly like a DotNetty issue

Ryan Anthony

@ryandanthony_twitter

Can you use a Lighthouse type of solution with Akka.Cluster.Sharding?

Aaron Stannard

@Aaronontheweb

https://petabridge.com/blog/cluster-sharding-technical-overview-akkadotnet/ - scroll to the bottom

Ryan Anthony

@ryandanthony_twitter

ok let me try that

thanks

Jesse Connor

@jesseconnr

Ah well, I would try, but using nuget from within visual studio to downgrade was apparently a bad idea, everything is wonderfully jacked now. :)

Aaron Stannard

@Aaronontheweb

lol

well, got some answers from the DotNetty crew that make some sense

due to some issues with .NET Core, it's possible that the byte buffer pools DotNetty uses can be released early

by the socket itself

especially true on Linux

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.