Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 13:05
    IgorFedchenko commented #4085
  • 03:08
    hhko commented #4094
  • Dec 13 21:37
    Aaronontheweb commented #4085
  • Dec 13 20:28
    IgorFedchenko commented #4085
  • Dec 13 20:27
    IgorFedchenko commented #4085
  • Dec 13 15:38
    Aaronontheweb labeled #4096
  • Dec 13 15:38
    Aaronontheweb milestoned #4096
  • Dec 13 15:38
    Aaronontheweb labeled #4096
  • Dec 13 15:38
    Aaronontheweb opened #4096
  • Dec 13 10:41
    peirens-bart opened #4095
  • Dec 13 08:37
    Aaronontheweb synchronize #4071
  • Dec 13 08:13
    jiyeongj opened #4094
  • Dec 12 15:42
    Aaronontheweb synchronize #4086
  • Dec 12 15:42
    Aaronontheweb closed #4083
  • Dec 12 15:42

    Aaronontheweb on dev

    Fix #4083 - Endpoint receive bu… (compare)

  • Dec 12 15:42
    Aaronontheweb closed #4089
  • Dec 12 15:42
    Aaronontheweb labeled #4093
  • Dec 12 15:42
    Aaronontheweb labeled #4093
  • Dec 12 15:42
    Aaronontheweb labeled #4093
  • Dec 12 15:42
    Aaronontheweb opened #4093
Arjen Smits
@Danthar
:D
haven't seen @Horusiath around for a while, so no idea how up to date he is ^^
but our main blocker for akka persistence are the CI build images
the core team is currently working to resolve that by moving to docker images which we can host on an azure environment
that eliminates @Aaronontheweb as the bottleneck since he would be the person to normally build the build-agent images
This will really help in making it easier for contributors to help in keeping the persistence plugins up to date, and even introduce new integrations
So these are some of the steps we are taking to improve the speed at which we can keep the persistence plugins updated
Kris Schepers
@schepersk
awesome!
Arjen Smits
@Danthar
@slc if you can post your configs in a gist, i can take a look
slc
@slc
Will do
Arjen Smits
@Danthar
(or upload the solution somewhere)
solution upload is tricky for IP reasons
thats the two configs
super simple configs AFAIK
Arjen Smits
@Danthar
hmm, could you try adding the public-hostname = "127.0.0.1" to the helios.tcp segment
slc
@slc
will do now...
Ralf
@Ralf1108
hi all, I checked out the new Akka.net Streams feature and I think its very goog. One questions was left open. If I create a processing flow how can I distribute it across different machines. Are there any examples how to start?
Arjen Smits
@Danthar
not sure if its still needed.
slc
@slc
public-hostname = "127.0.0.1" Added.
No change. Still errors.
do I need to configure IIS Express in any special way?
The weird thing is that I can send the message from the web actor to the service actor with no problems
Marc Piechura
@marcpiechura
@Ralf1108 that's not possible out of the box. But what you can do is to have an actor that distributes "job" messages to different machines and have a stream on every machine.
Arjen Smits
@Danthar
@slc no.
slc
@slc
I just cant Tell() back to the web actor from the service actor
James Farrer
@jamesfarrer
thanks @cgstevens and @qwoz . most helpful
Arjen Smits
@Danthar
@slc what if you reduce it to its bare minimum. So send a message containing nothing more then a string, and use Sender.Tell to echo it back
slc
@slc
I think I'm going to have to
Arjen Smits
@Danthar
that would eliminate possible serialization issues
slc
@slc
I was wondering if that was the case
Marc Piechura
@marcpiechura
@Ralf1108 here is some documentation about this topic http://getakka.net/docs/streams/integration#integrating-with-actors also @Aaronontheweb is currently rewriting the webcrawler sample to implement exactly the behavior you described
slc
@slc
I will try sending a string instead, or perhaps a bool
Ricky Blankenaufulland
@ZoolWay
@slc I have not followed the whole conversation but because I falled into the trap this week when messages have been swallowed: You are not creating one of the actors in an async method?
slc
@slc
nope, all syncronous
Ricky Blankenaufulland
@ZoolWay
ok
then check for the string/bool
slc
@slc
no async/await anywhere
yup, just about to try that
cannot Tell(true) either
:(
I guess that somewhat rules out serialisation/deserialisation issues
Im going to pull out an example from my solution and see if I can replicate in isolation
Ralf
@Ralf1108
@Silv3rcircl3 ok thx for the hints!
slc
@slc
@ZoolWay @Danthar - Found it! Serialization problem with the message being passed back. Message had a private constructor and I assume JSON.NET couldnt deserialise.
So annoying that the error message is a little elusive, nevermind
Jeff
@jpierson
Greetings all, just learning Akka.NET and I'll have some questions concerning Clustering, Routing, and Sharding. Is this the best place to ask those questions?
Jeff
@jpierson
In the examples I've seen with Cluster Routing it appears that the routing actor is created via ActorSystem.ActorOf on the same node where messages are being dispatched. Is this the general pattern or are there other options or reasons for having the router itself somewhere else in the cluster? If so is using an actor singleton the way to reach that router?
Peter Rosconi
@prosconi
Anyone know when cluster metrics events are expected to be completed?
Noel
@nanderto
Hi, I created a new implementation of Akka.Persistence.ServiceFabric, It uses ServiceFabric reliable collections that are embedded in the actor instead of calling a service like the old version did. I know its not on the road map for Akka.net and the old version has not seen any updates for some time. DOes anyone know if there is any interest in this implementation? its located here https://github.com/nanderto/akka.net/tree/ServiceFabric/src/contrib/persistence
Valeriy Reutskiy
@vvreutskiy
Hello!
I am trying to set up cluster client and I got stumbled over this comment in ClusterToolsExample.Node.Program.RunClusterClient method:
//NOTE: to properly run cluster client set up actor ref provider for nodes on provider = "Akka.Remote.RemoteActorRefProvider, Akka.Remote"
But if I change provider to RemoteActorRefProvider, how will nodes connect to each other in the cluster?