Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 16:07
    spankr commented #3921
  • 15:55
    Aaronontheweb labeled #3765
  • 15:54
    Aaronontheweb labeled #3765
  • 15:54
    Aaronontheweb milestoned #3765
  • 15:53
    Aaronontheweb closed #3902
  • 15:23
    Aaronontheweb commented #3921
  • 15:11
    spankr commented #3921
  • 15:05
    Aaronontheweb commented #3973
  • 15:05
    Aaronontheweb commented #3973
  • 15:02
    Aaronontheweb commented #4000
  • 15:02
    Aaronontheweb milestoned #4000
  • 15:02
    Aaronontheweb assigned #4000
  • 15:01
    Aaronontheweb commented #3889
  • 14:55
    sean-gilliam commented #3889
  • 14:35
    IgorFedchenko commented #3973
  • 13:10
    zbynek001 opened #4000
  • 11:20
    IgorFedchenko commented #3973
  • 11:20
    IgorFedchenko commented #3973
  • 11:18
    IgorFedchenko commented #3973
  • 10:47
    IgorFedchenko synchronize #3973
edwinparker
@edwinparker
@leo12chandu Yes we have referenced the actor code in the remote node (using a shared library) and the actorsystem name is the same. I read in the comments here from a couple years ago that this might not be possible but I'm wondering if that has changed.
Aaron Stannard
@Aaronontheweb
@gemr142388 what error is that?
@edwinparker there's a way to use DI when remotely deploying an actor
but you kind of have to decouple the steps
remotely deploy a parent actor that doesn't use DI at all
and then have the parent locally deploy a child that does use DI
that will allow you to use the container definitions that are defined in the remote process
to inject all of the settings into the remote actor
edwinparker
@edwinparker
Thanks @Aaronontheweb that makes sense...we will give that a try
Gustavo Eduardo Mendoza Ramírez
@gemr142388
@Aaronontheweb The ciruit breaker is open, but I got the following error

``"System.InvalidOperationException: There were not enough free threads in the ThreadPool to complete the operation. at System.Net.HttpWebRequest.BeginGetResponse(AsyncCallback callback, Object state) at System.Net.Http.HttpClientHandler.StartGettingResponse(RequestState state) at System.Net.Http.HttpClientHandler.StartRequest(Object obj) --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter1.GetResult()
at Core.HttpWebUtilImpl.<SendRequest>d__9.MoveNext()"

"Akka.Pattern.OpenCircuitException: Circuit Breaker is open; calls are failing fast
at Akka.Pattern.HalfOpen.<Invoke>d4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Akka.Pattern.CircuitBreaker.<WithCircuitBreaker>d
33.MoveNext()"```

Aaron Stannard
@Aaronontheweb
funnily enough, we merged a pull request that fixed this bug this morning
akkadotnet/akka.net#3505
should be included in our latest nightlies
let me see if they've run yet today... might be too early still
ok yeah, nightlies don't run yet for another four hours
I just manually kicked off a nightly build now though
should be online sometime within the hour
give that a try until we release Akka.NET v1.3.9
Gustavo Eduardo Mendoza Ramírez
@gemr142388
@Aaronontheweb Thanks, I will update version and test, thanks a lot
nathvi
@nathvi
Aaron Stannard
@Aaronontheweb
:+1: :clap:
onward and upward
Stéphane Erbrech
@serbrech
Hello community :)
I was wondering if there is any reference on running akka.net cluster on top of a kubernetes cluster
@Aaronontheweb I see you have some plans for this? I'd be interested to know more
also, hello @paulinfrancis :D
DaKaLKa
@DaKaLKa
@serbrech We run a show case application with akka.net cluster on top of a two node kubernetes cluster in the IBM Cloud. We use stateful sets for the seed nodes, so that the addresses don't change (currently fixed two seed nodes - but scaling is workding quite fine). Currently the application is running for about 2 Month (24/7) without any problems. The amount of messages is not so high (about 10msg/s).
Stéphane Erbrech
@serbrech
thanks @DaKaLKa that's what I thought, nothing special except stateful set for the seed nodes then
Sebastien Bacquet
@sbacquet
@Aaronontheweb
Hello Aaron
I can see the Akka.DistributedData.Tests.MultiNode tests are all skipped.
Do you know when the DistributedData feature is planned to be official (not beta) ?
Thank you and sorry if the question has already been asked !
me-slove
@me-slove
@Aaronontheweb Good cluster article but it did leave one interesting question unanswered (unless I missed it). How do routers handle these comings and goings? It seems that your handler example would work very well for a "roll your own" controller/router
Aaron Stannard
@Aaronontheweb
I think I mentioned how the built-in routers handle it in passing
let me see if I can dig that up real quick
it was only a sentence
or so
Other tools, like clustered routers, deal with network partitions by simply not routing new messages to unreachable nodes. If an unreachable node comes back, the routers will add those nodes back to the routing table and resume delivering messages.
so I actually have a series of "proper care and feeding of Akka.NET Cluster" posts stubbed out
me-slove
@me-slove
thank you for finding it. more coffee when reading I guess :)
Aaron Stannard
@Aaronontheweb
I pulled that first one and published it because my original post was getting pretty large
other topics I plan on addressing: Starting and Killing Nodes Gracefully
cluster planning and design - understanding how the connectivity model of Akka.Remote and Akka.Cluster works
so that one is drilling into things like "don't use load balancers" and such
and later in the summer I want to get into some DevOps type stuff with the cluster
monitoring and deployment
me-slove
@me-slove
If you are looking for a priority vote, I vote for design and planning. specific why and why not use certain architectures and their trade offs.
Aaron Stannard
@Aaronontheweb
yeah I can do something more general too
mostly I started writing these posts not because the underlying technology is complicated
me-slove
@me-slove
For me, that's the hardest part right now. Deciding whether to use a cluster or not or just remoting
Aaron Stannard
@Aaronontheweb
but rather because using that technology requires developers to approach the problems in ways that are pretty novel compared to good, old-fashioned web applications