Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 08:19
    ismaelhamed synchronize #4097
  • 02:22
    kimbyungeun opened #4098
  • Dec 15 19:47

    Aaronontheweb on dev

    TypeExtensions.TypeQualifiedNam… (compare)

  • Dec 15 19:47
    Aaronontheweb closed #4071
  • Dec 15 19:47
    Aaronontheweb closed #3767
  • Dec 15 19:47
    Aaronontheweb labeled #3767
  • Dec 15 19:47
    Aaronontheweb labeled #3767
  • Dec 15 19:47
    Aaronontheweb milestoned #3767
  • Dec 15 19:44
    Aaronontheweb labeled #4097
  • Dec 15 19:44
    Aaronontheweb milestoned #4097
  • Dec 15 13:23
    Aaronontheweb commented #4096
  • Dec 15 13:22
    Aaronontheweb commented #4093
  • Dec 15 13:16
    ismaelhamed commented #4093
  • Dec 15 13:04
    ismaelhamed edited #4097
  • Dec 15 13:04
    ismaelhamed opened #4097
  • Dec 15 12:50
    ismaelhamed commented #4096
  • Dec 15 12:48
    ismaelhamed commented #4096
  • Dec 15 12:05
    Aaronontheweb commented #4096
  • Dec 15 11:43
    ismaelhamed commented #4096
  • Dec 14 19:13
    hwanders commented #4096
Kevin McFarlane
@kevinmcfarlane
I'm having difficulty getting a simple persistence example to work based on the first example in the Petabridge blog post. I'm using SqlServer. I don't get any errors but otoh nothing gets written to the journal and snapshot tables. This is using Akka 1.0.6 with Persistence 1.0.6.17 and Persistence SqlServer 1.0.6.3. I'm on Sql Server 2008 R2, so I don't know whether that's an issue? Can someone take a peek if I post it up to my GitHub, unless they can think of an obvious gotcha to check in the meantime?
Toshko Andreev
@Ravenheart
suppose i'm writing the client side actors
do i have to specify my actor path as if its gonna be remote
like akka.tcp://MySystem@127.0.0.1:1234/user/someActor
or can i specify it like a normal in-app path: akka://MySystem/user/someActor
Dave Sansum
@dave-sansum
I'm currently using a child per entity model and after getting this running locally I'm starting to look into the remoting/clustering elements. In seems the clustering is really geared towards actors that are functional rather than entity based and I'm struggling to any documentation on dynamic systems. What I'm looking to do is have location transparency so if an entity A lives on node A, if node A fails the entity can be brought up seamlessly on node B ? It seems cluster sharding is the right (only) thing for this but it doesn't seem that mature at the moment. Any advice would be much appreciated?
Marc Piechura
@marcpiechura
@Ravenheart you only need the Akka.tcp path if you want to communicate with a remote actor
Toshko Andreev
@Ravenheart
also i've noticed that in some of the tutorials when you override say PostStop() you call the base method
while in some others you don't
do i always call the base method or
Kevin McFarlane
@kevinmcfarlane
@Ravenheart I wondered that as well! But IIRC I think base PostStop() curently does nothing?
Toshko Andreev
@Ravenheart
hello kevin
might i ask how long you've been using akka.net?
Marc Piechura
@marcpiechura
@Ravenheart @kevinmcfarlane the comment of the methods give you information weather you could skip the base call. PreStart and PostStop do nothing, rest does something
Kevin McFarlane
@kevinmcfarlane
@Ravenheart so far I've just tried it as a learning exercise on a home utility application I wrote to do backups to cloud storage. I wrote it conventionally and then thought I'd redo it using Akka. I tweak it from time to time once I think of some ideas or oversights.
Aaron Stannard
@Aaronontheweb
akkadotnet/akka.net#1911 - sorry for the delay on this @Horusiath
but that's all staged and ready to go - going to let the build server do its little dance
Aaron Stannard
@Aaronontheweb
alright, Akka.NET v1.0.8 is on its way to NuGet now
very minor patch - mostly just changes the configuration for Akka.Persistence back to the way it was
to11mtm
@to11mtm

Stupid question.... Context.ActorOf() inside an actor will create a child
So if I have inside my actor code pathed at
/user/SomeActor
{
Context.ActorOf(Props.Create(new S3SingleBucketFileOperationActor(params),"child")));
}

That will create it under /user/SomeActor/child/ , right?

Arjen Smits
@Danthar
yes
Maxim Cherednik
@maxcherednik
Hi @Danthar I asked a question before, but no one answered. Could you please comment on this:
Hi guys got a q. I know I've already asked similar one, but I didn't quite get the answer.
Here are a few facts:
  1. Cluster is still in beta
  2. There are online courses from the Petabridge about akka.net including Clustering
    So having these 2, I would assume that the cluster module can be used already. Even though it's still in Beta, there could be a limited number of bugs for some edge cases, but it should work in the most cases.
    Is this correct? @Silv3rcircl3 @Danthar @Aaronontheweb
Aaron Stannard
@Aaronontheweb
yep
getting Akka.Cluster out of beta is my number one priority at the moment
suspended work on just about everything else to finish it
throwing the kitchen sink at this fucker
but overall, you should be able to start using it
we've had people running it in production for years already
Maxim Cherednik
@maxcherednik
yeah, ok then. Some time ago you were advising me to take the course. Which I am planing to do, but I wasn't sure about the status of the clustering and how soon I can use it in Prod
Aaron Stannard
@Aaronontheweb
just got off the phone and told someone end of May / early June
who asked me the same question, another Akka.NET user
I'm committed to making that happen
Maxim Cherednik
@maxcherednik
Cool. Yet I still wonder about the cluster. I wanted to try an empty cluster without any real actor in there. Very simple setup - it was working more or less on local(when all the nodes are on the same machine). Then when you clarified that the port should be the same and of course auto-down is off. I decided to roll out several virtual machines in azure so that to try it. Doesn't work. No matter what I do. If I restart the node hard(as if it died), seed node start acting up with lots of exceptions.
So basically cluster formed, but actual failover cases I didn't manage to try...
Aaron Stannard
@Aaronontheweb
If I restart the node hard(as if it died), seed node start acting up with lots of exceptions.
the stuff I'm working on now should address that
the socket server sitting underneath Akka.Cluster has a bunch of fun issues that had never been properly classified until recently
race conditions at startup
spent the past two weeks working on an update to that
on top of that, latest release today includes a patch I made to the EndpointRegistry in Akka.Remote
which also caused issues that occurred on node restart
I'm working those issues from the bottom up
dealing with the socket server first, then Akka.Remote's endpoint system, and then finally dealing with things like the cluster daemon
Vladyslav Pyshnenko
@Pisha91
Hi , @Aaronontheweb , we using Akka.Cluster in our project hosted on Azure Cloud service and very often one of node on worker role is not starting after deploy or reboot. In logs we could see next error "Failed to startup Cluster. You can try to increase 'akka.actor.creation-timeout'.". Does this issue related to all that you described before?
Aaron Stannard
@Aaronontheweb
I've seen that issue before - that's unrelated
how many cores are you running those nodes on?
Vladyslav Pyshnenko
@Pisha91
8
Aaron Stannard
@Aaronontheweb
ok, you should be good there