Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 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
  • Dec 11 07:52
    dependabot-preview[bot] synchronize #104
  • Dec 11 07:52

    dependabot-preview[bot] on nuget

    Bump MongoDB.Driver from 2.9.1 … (compare)

  • Dec 11 07:52
    dependabot-preview[bot] edited #104
  • Dec 11 07:51
    dependabot-preview[bot] edited #104
feanor41
@feanor41
Thank you all in advance.
@Horusiath If I want to contribute in cluster tools and cluster sharding, where will be in the code a good start for reading and getting the sense of it?
Bartosz Sypytkowski
@Horusiath
@feanor41 your case can be solved by cluster sharding, but in general it's the case of some third service actor, that both actors use to establish the connection with each other
Bartosz Sypytkowski
@Horusiath
concerning Akka.Cluster.Tools and Akka.Cluster.Sharding - most (if not all) of the code is already ported, but I need to make multinode test runner specs working. If you want to help a little, I can try to find something, that could interest you. Just give me a while to reorganize the code ;)
feanor41
@feanor41
@Horusiath Thanks, no rush. I was looking at Cluster Sharding documentation available and arrived myself to cluster sharding path. Thanks for confirm it.
Aaron Stannard
@Aaronontheweb
blob
@Horusiath #1455 should fix it - proof above
merge it
Bartosz Sypytkowski
@Horusiath
if you say so ;)
merged
Bartosz Sypytkowski
@Horusiath
akka.net spec suite have so many races and it's so resource consuming, that I want to tell xUnit guys to build their test runner on top of akka.net, so that their runner will finally stop failing from pressure we generate
Kelly
@kcliffe
Anybody else running on Windows using Akka.Remoting having runtime exception where specific google.protobuf ver 521 is required? (nuget restores latest - 555)? Works at home under mono. Just breaks at work...
Bartosz Sypytkowski
@Horusiath
@feanor41 if you want to play a little with the Akka.Cluster.Tools, take a look at PR #1408 - under Examples/Cluster/ClusterTools you can find projects with samples for each of the 3 major features:
  • cluster singletons
  • cluster distributed pub/sub mechanim
  • cluster client -> this one to be better visible will require to set .Node project actor ref provider to RemoteActorRefProvider, while keeping .Seed actor ref provider to ClusterActorRefProvider (the purpose is to show that non-cluster actor system is able to call cluster itself)
@kelly-cliffe you can manage this using assembly bindings in your app.config file
Kelly
@kcliffe
@Horusiath Yes thanks. That's what I've done. Just wondered if everybody else was currently taking that approach, or if i was alone and something sinister was happening on my dev machine.
Bartosz Sypytkowski
@Horusiath
yeah, ultimately I think that we should be able to cover those cases automagically
feanor41
@feanor41
@Horusiath Excellent, I'll take a look at this as your suggestion!
Tom Rathbone
@chillitom
@Horusiath could Akkling IActorRef<'Msg> use flexible types? If I make an actor of type obj then I have to downcast every message to :> obj
Tom Rathbone
@chillitom
been playing with Akkling, trying to understand how to handle more event types than the those declared in the Eventsourced<> type parameter
Christian Duhard
@cduhard
How far off might 1.05 be?
Aaron Stannard
@Aaronontheweb
@Horusiath all the packages in the nightly MyGet feed have their binaries now by the looks of it https://www.myget.org/feed/Packages/akkadotnet
@cduhard we're trying to get it out ASAP - @Horusiath needs to do a bit of integration testing with some of the Akka.Persistence plugin implementations first before we ship
Christian Duhard
@cduhard
k, is there a pre build available?
Aaron Stannard
@Aaronontheweb
yessir, on the nightly feed I just linked
Christian Duhard
@cduhard
cool, thanks
Aaron Stannard
@Aaronontheweb
step-by-step docs for setting that up within NuGet
Chris G. Stevens
@cgstevens
I have a 2 websites that are part of my cluster. Sometimes one websites will become unreachable and my logic for all of the other members determine that after 120 seconds they should do a Cluster.Down(ThatWebsiteAddress). I can see that all of the members get a MemberRemoved for that website and then it is reported as Down.
My problem is that when my other service detects that this website is down and has been removed from the cluster it tries restarts that website. I can see see it trying to join and I get this message: [[akka://MyService/system/cluster/core/daemon]] - New incarnation of existing member [UniqueAddress: (akka.tcp://My@1.1.9.2:57771, 303375918)] is trying to join. Existing will be removed from the cluster and then new member will be allowed to join.
But it never gets removed from the cluster so the member never is able to join. I can try to have a member .Leave(ThatWebAddress) and do another .Down(ThatWebAddress) but it never gets removed. Basically I have a ClusterStatus actor that monitors the status of the cluster from its view and determines if it needs to restart itself or if a member has been unreachable for x seconds to down it. If so it shuts that service down and logs to the event log for Solarwinds to determine if the service or website needs to be started back up.
Aaron Stannard
@Aaronontheweb
@cgstevens I'll give you a full answer when I get into the office, but the short answer is that nodes have to be manually issued a Cluster.Down command to remove them from the cluster
node being disconnected != node leaving the cluster
Akka.Cluster achieves partition tolerance by treating unexpected disconnects as transient failures, and for now relies on humans to manually tell the cluster when a disconnect is a permanent failure or not
definitely do not recommend turning auto-down on in HOCON config, which it sounds like might be the case here
you'll end up with a split brain most of the time
Chris G. Stevens
@cgstevens
right I was using that but that killed my cluster.
so I created my own ClusterStatus to down per our business rules..
Aaron Stannard
@Aaronontheweb
ah, very cool - so are you sure the right node is being downed when that happens?
I see in the message it looks like a node definitely gets removed
but the same node can't join again?
Chris G. Stevens
@cgstevens
no.. I just get that message
I can see in the Member list that is Down
Aaron Stannard
@Aaronontheweb
ok, sounds like that might be a bug - would you mind logging an issue for it?
we have a multi-node spec that covers this but I don't know if it's been ported yet
Chris G. Stevens
@cgstevens
Sure can and will.
Aaron Stannard
@Aaronontheweb
thanks!@
Chris G. Stevens
@cgstevens
No problem... I can feel I am getting closer and closer and as our system comes together using Angular, SignalR (sql backplane), MVC5, Akka, Log4Net and TopShelf...
Just love a can send a Message from multiple services to a webpage and don't have to refresh the page...
Thanks for your help!
Bartosz Sypytkowski
@Horusiath
@chillitom there is a retype function, which returns new IActorRef<> responding on new generic type. Type is actually infered.
Bartosz Sypytkowski
@Horusiath
so using your example, you could just do something like that:
let a = retype p
a <! Inc
a <! Dec
a <? GetState |> Async.RunSynchronously |> printfn "State: %d"
Aaron Stannard
@Aaronontheweb
@Horusiath what do we need to be able to ship our 1.0.5 releasE?
I want to get it out ASAP