by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Sep 17 17:14
    briansain commented #4567
  • Sep 17 16:59
    briansain synchronize #4568
  • Sep 17 16:27
    VaclavK closed #51
  • Sep 17 16:27
    VaclavK closed #50
  • Sep 15 14:57
    BartHuls closed #4569
  • Sep 15 14:18
    Aaronontheweb commented #4563
  • Sep 15 13:53
    Zetanova commented #4563
  • Sep 15 13:41
    Aaronontheweb commented #4563
  • Sep 15 13:38
    Zetanova commented #4563
  • Sep 15 13:28
    Zetanova commented #4563
  • Sep 15 13:15
    Aaronontheweb commented #4567
  • Sep 15 13:11
    Aaronontheweb commented #4569
  • Sep 15 09:59
    BartHuls commented #4569
  • Sep 13 16:51
    to11mtm commented #4568
  • Sep 11 18:45
    briansain synchronize #4568
  • Sep 11 16:18
    briansain commented #4567
  • Sep 11 15:50
    briansain commented #4567
  • Sep 11 15:37
    ismaelhamed commented #4567
  • Sep 11 15:24
    dependabot-preview[bot] synchronize #146
  • Sep 11 15:24

    dependabot-preview[bot] on nuget

    Bump AkkaVersion from 1.4.9 to … (compare)

Jared Lobberecht
@Jared314
@schepersk I am also using 1.0.8, but I also need to start using the query api to build out some historical reporting and file export features
Alex Valuyskiy
@alexvaluyskiy
@Jared314 @schepersk we are planning to release it today
Ralf
@Ralf1108
@ZoolWay why not use a guid instead of a counter?
@Silv3rcircl3 so it's still an unresolved problem?
Marc Piechura
@marcpiechura
@Ralf1108 yes, you shouldn't use Akka.Streams with remote actors
Noel
@nanderto
@ @alexvaluyskiy do you mean a separate repository under my account? I don't imagine that I have access under Akka.net
Alex Valuyskiy
@alexvaluyskiy
Yes, under your account
Noel
@nanderto
ok no problem I will get it done today
Ralf
@Ralf1108
@Silv3rcircl3 sad to hear that. Thought that was the point in "Akka Streams".... to distribute stream processing over many machines. WIthout that it is only a Streams implementation with local actors.
Marc Piechura
@marcpiechura
@alexvaluyskiy btw I'm done with the adapter for azure if you want to take a look
William Austin
@wyldebill
i want to use akka.net actors in a simple domain as such - you find interesting places and submit their lat/long to the system. the system catalogs it and makes it available for others to search/query. would each place be a separate actor?
Vagif Abilov
@object
@wyldebill do these places need to perform actions by responding to messages? Do they have state? If so, they are good candidates for actors.
Erik Lagerholm
@stabface
Does anyone have a code example of a decorator pattern implementation to use with Akka actors?
Noel
@nanderto
Marc Piechura
@marcpiechura
@nanderto why haven't you forked the existing repository ? https://github.com/akkadotnet/Akka.Persistence.ServiceFabric
Noel
@nanderto
@Silv3rcircl3 the implementation is different from the previous one at that location and when I asked on this gitter if there was interest in my alternative, @alexvaluyskiy suggested that I create a new repository for it under my account.
Daniel Söderberg
@raskolnikoov
Hello! I would like some help with my akka cluster. I wont get it to work when I try to call an actor in the cluster. Dead letters all the time. Im swedish so If you want to help me in swedish you can do that.
Alex Valuyskiy
@alexvaluyskiy
@nanderto why are you using Wire for serialization? Wire is designed for ... wire. For remoting and clustering. But not for persistent. You should choose the closest serializer to your storage. In many cases it is JSON. You also could use serializers like Protobuf in this cases. Maybe @rogeralsing is not agree with me
Noel
@nanderto
@alexvaluyskiy I thought I would try it out, the standard Service Fabric way of serializing does not work at least, and it seemed like a good alternative for Akka, I am not sure I understand your objection, but I assumed that at some point it would be configurable, and users could choose there own.
Peter Bergman
@peter-bannerflow
@raskolnikoov I'm swedish so you can PM me in swedish if u want to and I'll see if I can help
Arsene
@Tochemey

Hello How long does it take ActorSystem to properly shutdown? because I got this in my log and I have not received any successful shutdown confirmation.

[DEBUG][16:08:02 09:15:45][ActorSystemImpl] System shutdown initiated

However I am running it inside Owin.

Arjen Smits
@Danthar
@Tochemey normally its pretty quick, since there is no real way to block system shutdown.
It does need to spin down all your actors, so if you have alot, it might take abit longer, but even then it should be a few seconds at most
(and by alot i mean a few million :P)
Arsene
@Tochemey
@Danthar Is there a proper way to implement the shutdown?
Arjen Smits
@Danthar
there is not a one size fits all solution
it depends on what your actors are doing
normal shutdown is simply calling Terminate on the actor system and Wait() or await on WhenTerminated (or the terminate task itself)
but actor shutdown is asynchronous and non-deterministic
(granted it starts with the userguardians children, meaning, your actor)
So if you need to you could implement some kind of ordered termination
Arsene
@Tochemey
ok
Arjen Smits
@Danthar
what tend to do for non-trivial applications is:
  • Don't call Terminate on the ActorSystem directly, but let your actor call Context.Shutdown once all work has been done (if applicable)
  • Intercept application shutdown and send a message into your actor system to start shutting down, and send a response back when its ready to be terminated
Alex Valuyskiy
@alexvaluyskiy
Just released an updated version of MongoDb plugin for Persistence
https://www.nuget.org/packages/Akka.Persistence.MongoDb/1.1.0.3-beta
Arjen Smits
@Danthar
What the easiest way to handle this is, if work comes in from another actor system via remoting or clustering, use retry mechanisms for your work, so if you kill your actor system, even though any work will have been lost, it will simply be processed elsewhere (a different node) or presented again once you start up your actorsystem again.
Arsene
@Tochemey
@Danthar Please can you provide some code snippets?
This message was deleted
Arsene
@Tochemey
Hello can someone show me how to properly shutdown the actor system? I have stopped all the child actors created using the actors system. I want to know how to use WhenTerminated. Thank you
Marc Piechura
@marcpiechura
@Tochemey what exactly do you want to do with WhenTerminated?
Arsene
@Tochemey
I want to be able to display an termination logging info for instance.
Marc Piechura
@marcpiechura
Then I would register a callback with RegisterOnTerminationwhere you write the log entry
that is automatically called once the system is terminated
Arsene
@Tochemey

Hello How long does it take ActorSystem to properly shutdown? because I got this in my log and I have not received any successful shutdown confirmation.

[DEBUG][16:08:02 09:15:45][ActorSystemImpl] System shutdown initiated

However I am running it inside Owin.

@Silv3rcircl3 Please this what I am observing.
Arjen Smits
@Danthar
@Tochemey So your calling ActorSystem.Terminate() and it never terminates ?
Arsene
@Tochemey
@Danthar I have figured it out. I started a new thread that got executed before the ActorSystem.Terminate calling thread. Sorry for the false alert.
Vagif Abilov
@object
A question about message serializability. Sure properly designed messages should be small and serializable, and for persistent and remote actors they must be serializable. But I have a scenario with a helper actor that just sends HTTP requests. It uses 3rd party library types to represent requests, and sometimes such request contains binary stream (for multipart forms). The stream processing doesn't happen until the actor starts generating the HTTP payload so it's just a unprocessed stream reference that is sent in a message to the HTTP request actor. I tested the implementation and it works fine. But since an instance of Stream type is obviously not meant to be used in actor messages, I wonder if this can lead to bad consequences even if in-proc scenario.
Arjen Smits
@Danthar
@object if that message never leaves the local actorsystem, then its not a problem. There is nothing wrong with using non-serializable messages between a 'manager-actor' and its 'worker'. As long as you are aware of the drawbacks and limitations it imposes.
on a local actorsystem level. Akka could not care less. Its in the remoting, clustering and persistence scenario's that it becomes a problem