Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 12:04
    nagytech synchronize #4092
  • 11:53
    nagytech synchronize #4092
  • 11:49
    nagytech edited #4092
  • 11:40
    nagytech opened #4092
  • 11:32
    nagytech edited #4091
  • 11:32
    nagytech opened #4091
  • 10:13
    nagytech commented #3954
  • 05:29
    nagytech commented #4090
  • 05:29
    nagytech opened #4090
  • Dec 11 23:52
    scptre commented #4082
  • Dec 11 14:26
    nagytech commented #3954
  • Dec 11 11:18
    nagytech edited #4089
  • Dec 11 11:17
    nagytech opened #4089
  • Dec 11 11:00
    nagytech commented #4083
  • Dec 11 08:34
    jiyeongj commented #4083
  • Dec 11 08:33
    jiyeongj commented #4083
  • Dec 11 08:33
    jiyeongj commented #4083
  • Dec 11 07:57

    dependabot-preview[bot] on nuget

    (compare)

  • Dec 11 07:57

    dependabot-preview[bot] on dev

    Bump MongoDB.Driver from 2.9.1 … (compare)

  • Dec 11 07:57
    dependabot-preview[bot] closed #104
Aaron Stannard
@Aaronontheweb
June 30th
Chris G. Stevens
@cgstevens
woot!
:)
Jordan S. Jones
@jordansjones
Can anyone point to a snippet of code or documentation about the recommended way to “properly” shutdown the ActorSystem while gracefully leaving the cluster?
I know I have seen somethings in here, but I am failing at searching
wdspider
@wdspider
Is there a way to get an exception when the akka hocon is not parse-able rather than simply failing silently?
Ivan R. Perez
@irperez
@Aaronontheweb when you get a chance, take a look at this issue. Wanted to get your thoughts. akkadotnet/akka.net#2115
Aaron Stannard
@Aaronontheweb
so I've seen people ask for something like that before
needing to guarantee that at least 1 subscriber handles a published message
my suggestion to them was to have an AtLeastOnceDeliveryActor publish the message to DistributedPubSub
as long as you don't care about multiple subscribers handling it
that way you can guarantee that at least one actor handled it when they send an ACK back
an out of the box atleastoncedelviery actor may not be the best candidate
since it relies on the ActorPath to cache its sender, which can be a bit ephemeral in DistributedPubSub
i.e. probably won't work across restarts
the other scenario you'd have to cover is what if there are no subscribers for that topic
Aaron Stannard
@Aaronontheweb
it's a common problem - so coming up with a canonical solution would be a good idea. I think it's going to be something inherent in the actor on either end of the pub/sub relationship though, rather than a modification of the DistributedPubSub system itself
since the only way to realistically guarantee processing of a message is using an acknowledgement protocol
which means both sender and receiver need to be aware of it
Vagif Abilov
@object
@corneliutusnea thanks for publishing your Visualizer on GitHub.
Stanley Goldman
@StanleyGoldman
@object can you send a screenshot
i haven't seen any yet
and i haven't set it up for myself yet
Aaron Stannard
@Aaronontheweb
I'd be curious to see it also
Jordan S. Jones
@jordansjones
:+1:
Vagif Abilov
@object
I am far from my work pc right now. But will make a screenshot when I am back to work from my short vacation. It's an alpha state but looks promising.
Aaron Stannard
@Aaronontheweb
in today's public service announcement
Tail Recursion and C#: natural enemies
testing various parts of the actor dispatching system
for performance issues
came up with a test where I can pre-fill an actor's mailbox with 500000 messages
and none of them will be processed until I send that actor a Tell
instant stack overflow exception
Aaron Stannard
@Aaronontheweb
interesting - looks like it takes about 3x as long to put a message in an actor's mailbox vs. how long it takes the dispatcher to dequeue that message and push it into the actor's cell
feng3245
@feng3245
Does anyone know a reliable way of distinguishing if an actor is available from an actorSelection. IE no actor is at that address
Aaron Stannard
@Aaronontheweb
ActorSelection.ResolveOne
is one way - you'll get an exception if the actor can't be resolved
if you want to do it without an exception, do this
ActorSelection.Ask<ActorIdentity>(new Identify(null))
ActorIdentity.Subject will be null
feng3245
@feng3245
The interesting part is that I've used ResolveOne and it never returned control back to the current thread. Not even with an exception
Aaron Stannard
@Aaronontheweb
did you specify a timeout on it?
feng3245
@feng3245
I specified a 3 second timeout
Aaron Stannard
@Aaronontheweb
should work - our source is open; give it a look
might also be an issue, if you're doing this over Akka.Remote, that we've fixed in 1.1
made a lot of changes related to that
feng3245
@feng3245
The current release for akka.net is at 1.08 from nuget. Is it out yet?
Aaron Stannard
@Aaronontheweb
1.1 is due out in a week
timeline is on the readme
feng3245
@feng3245
Ok good to know