Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Dec 07 11:49
    IgorFedchenko commented #4085
  • Dec 07 10:31
    IgorFedchenko commented #4085
  • Dec 07 08:36
    IgorFedchenko commented #4085
  • Dec 06 20:57
    IgorFedchenko commented #4085
  • Dec 06 20:32
    IgorFedchenko commented #4085
  • Dec 06 20:01
    IgorFedchenko commented #4085
  • Dec 06 19:55
    IgorFedchenko commented #4085
  • Dec 06 16:22
    Aaronontheweb labeled #3997
  • Dec 06 16:22
    Aaronontheweb closed #3997
  • Dec 06 16:20
    IgorFedchenko commented #3997
  • Dec 06 16:08
    IgorFedchenko commented #4085
  • Dec 06 15:50
    Aaronontheweb assigned #4085
  • Dec 06 15:50
    Aaronontheweb labeled #4085
  • Dec 06 15:50
    Aaronontheweb labeled #4085
  • Dec 06 15:49
    Aaronontheweb closed #4032
  • Dec 06 14:58
    IgorFedchenko commented #4032
  • Dec 06 14:57
    IgorFedchenko opened #4085
  • Dec 05 17:21
    Aaronontheweb synchronize #4079
  • Dec 05 17:20
    Aaronontheweb labeled #4084
  • Dec 05 17:20
    Aaronontheweb labeled #4084
Alex Valuyskiy
@alexvaluyskiy
waiting for akkadotnet/akka.net#2405
Weston
@ronnyek
io is high performance network transports and things like http endpoints and what not?
webeoutrascoisas
@webeoutrascoisas
Hi!
There's a way to test if my ActorSelection received a message? Something like ActorSelectionProbe?
Chris G. Stevens
@cgstevens
@webeoutrascoisas I am returning a ACK in cases where I need to guarantee delivery.
Nick Chamberlain
@heynickc
@webeoutrascoisas are you able to create a TestProbe at that specific path? That test probe could then forward, if needed.
webeoutrascoisas
@webeoutrascoisas
i'll try it @heynickc
webeoutrascoisas
@webeoutrascoisas
TestProbe ExpectMsg still not working
I'm passing Ref.Path to Context.ActorSelection
Jeff Pang
@jeff-pang
can someone point me in the right direction on how to get Akka on .net core? The information i got from google all seems to be dated. those I found uses project.json
webeoutrascoisas
@webeoutrascoisas
@jeff-pang there's no .net core version yet
Jeff Pang
@jeff-pang

@webeoutrascoisas thanks. I understand that officially not from nuget but based on some article you are able to get an "unofficial" version to work since 1.2.0-alpha1 ? Or am I mistaken?

I read it from here https://medium.com/@FurryMogwai/building-a-basket-micro-service-using-asp-net-core-and-akka-net-ea2a32ca59d5

Marc Piechura
@marcpiechura
@webeoutrascoisas @jeff-pang it's available via myget , link is somewhere in #2153
Jeff Pang
@jeff-pang
@Silv3rcircl3 awesome! Thanks!
Deniz ─░rgin
@Blind-Striker

@Silv3rcircl3 i couldnt find akka core library in myget. So i download @alexvaluyskiy https://github.com/alexvaluyskiy/akka.net/tree/coreclr_final branch and compile it myself for todays meetup. Because of Google.ProtocolBuffers library i couldnt compile cluster and remote to .net core but Akka.Core local actor system can work on .net core.

I made an example repo ;

https://github.com/CodeFiction/AkkaDotNetCoreDemo

Deniz ─░rgin
@Blind-Striker
I think I convinced most of the developers who participated in today's meeting to use Akka.Net :)
Sean Gilliam
@sean-gilliam
nice :+1:
Jeff Pang
@jeff-pang
@Blind-Striker Yeah, same, I can't find akka core in myget. Thanks for the branch. I'll do my own compilation too
Nick Chamberlain
@heynickc
@webeoutrascoisas so are you having issues using ActorSelection to get to the TestProbe? Here's what I was thinking:
[Fact]
public void Should_probe_replace_actor_selection_and_forward()
{
    var testProbe = CreateTestProbe("FindMeWithSelectionProbe");
    var actor = Sys.ActorOf(Props.Create(() => new FindMeWithSelectionActor()), "FindMeWithSelection");
    var selection = Sys.ActorSelection(testProbe.Ref.Path);
    selection.Tell("Hi!");
    testProbe.ExpectMsg("Hi!");
    testProbe.Forward(actor);
}
Franky Ostyn
@FOstyn

Hi all,
a NLog question: with NLog is it possible to define 2 or more different logfiles.
<rules>
<logger name="AkkaLog" minlevel="Debug" writeTo="logfile1" />
<logger name="myLogFile" minlevel="Debug" writeTo="logfile2" />
</rules>

Using the same config file for Akka doesn't work, nothing is logged from Akka, I think Akka expects the name = "" like:
<rules>
<logger name="
" minlevel="Debug" writeTo="logfile1" />
</rules>

Is it possible to define in HOCON the name of the logfile for Akka ?

Great, the "" must be "*"
Jose Carlos Marquez
@oeaoaueaa
Is there any limit in the amount of nodes a cluster can have? when I deploy my services there is only one being left out, permanently joining (we have 21 nodes in the test environment)
Aaron Stannard
@Aaronontheweb
@oeaoaueaa no limit that I know of
Jose Carlos Marquez
@oeaoaueaa
ok, any logging line or configuration I should look at?
Aaron Stannard
@Aaronontheweb
just sent you a private message asking for some logs from the affected node
that would be super helpful if you could send those my way
Bartosz Sypytkowski
@Horusiath
@oeaoaueaa lower bound doesn't exists, however it's always better to have 2-3 nodes just in case. Upper bound: hard to tell, I guess no one tested this on .NET platform. On JVM they reached 2400 node cluster, but that test was couple years ago and probably now they can do better
Jose Carlos Marquez
@oeaoaueaa
21 should be nothing then, I was thinking that it could be something related to configuration because there are two services in the same machine that is always the last to be deployed and is one of those two that gets stuck joining
Bartosz Sypytkowski
@Horusiath
there may be many reasons, starting from configuration ending on the content of dlls and how many nodes at once you're trying to join
do you get any error messages?
i.e. by default no downing provider is configured so you may want to configure akka.cluster.auto-down-unreachable-after = <X>sec to be able to mark stale unreachable nodes to be marked as dead
Jose Carlos Marquez
@oeaoaueaa
no errors or warns
Jose Carlos Marquez
@oeaoaueaa
if the cluster is always meant to have the same number of nodes, and the services stop/leave the cluster when upgraded is there any need of downing provider?
Bartosz Sypytkowski
@Horusiath
if you're able to guarantee that neither your network nor your server will ever fail ;)
Jose Carlos Marquez
@oeaoaueaa
I know that is not a good solution, but worst case scenario, will need to restart lighthouse to "create" a new cluster right?
by they way, I have 3 instances of lighthouse, is that a bad practice?
Bartosz Sypytkowski
@Horusiath
no, lighthouse is just ordinary actor system. if you turn it down, your cluster will live anyway
and having 3 of them is fine
Jose Carlos Marquez
@oeaoaueaa
what I have notice is that when lighthouse services are restarted they create a new cluster and then the other nodes have to be restarted too for them to join
Bartosz Sypytkowski
@Horusiath
yes, because in order to join the cluster, a node must know another node, that is already part of it. Since your lighthouse nodes are down (and probably other nodes have dynamic addresses) you cannot simply join the cluster, as known endpoints are lost. When lighthouse nodes will go up again, they don't know that cluster lives somewhere out there, so they will join the nodes they know about - themselves - forming a new cluster. Joining to self address is equivalent of establishing new cluster
Jose Carlos Marquez
@oeaoaueaa
mmm, the addresses are static, should I pace the deployment of lighthouses in a way they could rejoin the same cluster instance?
Bartosz Sypytkowski
@Horusiath
if you don't throw down all lighthouse nodes, this shouldn't be a problem - this is a reason, why it's good to have more than one node working as lighthouse, so in the case if it goes down for some reason, there is a still replacement with known address
Jose Carlos Marquez
@oeaoaueaa
just realized that if I restart one of the lighthouse nodes it tries to join but gets stuck rejoining too
Bartosz Sypytkowski
@Horusiath
try setup auto-down, also AFAIK issue may be an order in which seed nodes are defined. @Aaronontheweb any ideas?
Jose Carlos Marquez
@oeaoaueaa
is it wrong to have "self" in the seed nodes?
Bartosz Sypytkowski
@Horusiath
no, it should be ok. But the problem with hanging join may be caused by some of the unreachable nodes not being marked as down, but @Aaronontheweb would need to confirm that
Aaron Stannard
@Aaronontheweb
after taking a look at the cluster code
think I found an issue
gotta confirm a behavioral thing real quick
it's an easy fix if it is what I think it is