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 06 22:45

Aaronontheweb on dev

sharding - release shard lease … (compare)
Apr 06 22:45

Aaronontheweb closed #4369
Apr 06 22:45

Aaronontheweb milestoned #4369
Apr 06 22:45

Aaronontheweb labeled #4369
Apr 06 22:45

Aaronontheweb commented #4363
Apr 06 22:31

yesh-nadella commented #4363
Apr 06 22:05

Arkatufus commented #4368
Apr 06 19:55

zbynek001 opened #4369
Apr 06 17:38

Aaronontheweb assigned #4368
Apr 06 17:38

Aaronontheweb labeled #4368
Apr 06 17:37

Aaronontheweb milestoned #4368
Apr 06 17:37

Aaronontheweb labeled #4368
Apr 06 15:07

PiotrJustyna opened #4368
Apr 03 22:24

huzaifak opened #4367
Apr 03 21:45

Aaronontheweb commented #4344
Apr 03 05:55

Lutando commented #4344
Apr 02 17:23

huzaifak commented #4303
Apr 02 17:23

huzaifak closed #4303
Apr 02 02:13

ShawnYun commented #4366
Apr 01 17:18

huzaifak commented #4303

Jesse Connor

@jesseconnr

Would having an old 1.3.0 version of Akka.Serialization.Hyperion possibly have an effect?

I just realized that when everything else was updated, that wasn't because I didn't check the prerelease in visual studio.

Aaron Stannard

@Aaronontheweb

try an upgrade and see what happens

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?