Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 15:02
    Arkatufus opened #4375
  • 07:34
    ismaelhamed synchronize #4350
  • Apr 08 23:26
    Arkatufus synchronize #4372
  • Apr 08 23:15
    Arkatufus synchronize #4372
  • Apr 08 23:15
    Arkatufus synchronize #4372
  • Apr 08 22:51
    Aaronontheweb synchronize #4373
  • Apr 08 22:51

    Aaronontheweb on 1.4.5-release-notes

    (compare)

  • Apr 08 22:51

    Aaronontheweb on dev

    v1.4.5 release_notes.md placeho… (compare)

  • Apr 08 22:51
    Aaronontheweb closed #4374
  • Apr 08 22:47
    Aaronontheweb opened #4374
  • Apr 08 22:43
    Aaronontheweb synchronize #4373
  • Apr 08 22:41

    Aaronontheweb on 1.4.5-release-notes

    v1.4.5 release_notes.md placeho… (compare)

  • Apr 08 22:40
    Aaronontheweb synchronize #4373
  • Apr 08 22:04
    Aaronontheweb labeled #4373
  • Apr 08 22:04
    Aaronontheweb labeled #4373
  • Apr 08 22:04
    Aaronontheweb opened #4373
  • Apr 08 21:04
    Arkatufus commented #4372
  • Apr 08 21:01
    Arkatufus synchronize #4372
  • Apr 08 20:52
    Arkatufus synchronize #4372
  • Apr 08 20:36
    Arkatufus synchronize #4372
Vagif Abilov
@object
@Silv3rcircl3 thanks!
qwoz
@qwoz
I'd like to send messages to actors on a schedule and I'd also like to persist this between system restarts. Has anybody come up with a clever solution to do that, taking into account when things were last run, when they're due to run again, etc.?
I'm aware of schedule tell... this is more about the restartable persistence aspect of it.
qwoz
@qwoz
The scenario if it helps: I'm building a reminder kind of service that anybody can use to remind them to do something and there could end up being tens of thousands of reminders at any time. The reminders might be for one message 20 minutes from now, might be every 5 minutes, might be every day at 8:03 AM, might be every last Friday of every second month at midnight. Accuracy isn't too important so if something is off by some number of seconds or minutes that's okay. But outages, restarts, etc. must not cause a reminder to be missed. Basically some kind of reliable cron daemon for actors.
Boban
@bobanco
@qwoz you can use Quartz.Net and Akka.NET to achieve that, as you said you could persist the incoming messages which will come to the actor manager, after message is persisted you could put into the quartz and you're done, now at the other side when you will do a recovery from restarts you could simply put back the reminders to the quartz or you can also achieve the same without akka persistence, but you will need to create your mechanism for storing the reminders to the disks or to the DB when they are created, and on restart you could overwrite the PreStart() method and start the recovery of the reminders yourself, basicly its really easy to achieve these kind of things with akka with writing just couple of lines code. :smile:
qwoz
@qwoz
Thanks @bobanco ... if I understand it correctly, you're suggesting that upon a system restart, I would need to explicitly recreate instances of all the reminder actors, and have each reminder actor be responsible for loading up Quartz with its own schedule? I looked into Quartz briefly and it seems to have its own persistence mechanism for schedules (to a DB, rather than its RAM-based store). Perhaps it's possible to hook into that mechanism to recreate an instance of the specific reminder actor whose schedule has triggered rather than going through what I assume would be a relatively expensive operation of iterating over every single instance just to load up Quartz again. Or am I misunderstanding?
Boban
@bobanco
@qwoz yes you can use quartz persistence as well, i haven't used quartz persistence so i can not give any info regarding how good is it, btw in this case you will just need a tiny wrapper on the quartz scheduler into single actor, you could even use akka cluster singleton tool and you can make sure that only 1 isntance is running trough the cluster if you are going on that way. Also quartz has support for clustering as well but based on my experience it doesn't work well, so if i were you i would go with akka cluster and quartz, so you will get the benefits of both worlds. But to summarize i would say it depends mostly on your requirements etc.
Maxim Cherednik
@maxcherednik

Hi guys,
updated recently to 1.0.7 and now I see quite strange behaviour from the cluster:

  1. There is a seed node and a worker node
  2. When worker node joins the cluster, I see this kind of logs on the seed node:
    [INFO][4/24/2016 12:22:21 PM][Thread 0016][[akka://riskengine/system/cluster/core/daemon]] Node [akka.tcp://riskengine@10.0.0.10:4053] is JOINING, roles [riskenginewidget]
    [INFO][4/24/2016 12:22:21 PM][Thread 0014][[akka://riskengine/system/cluster/core/daemon]] Leader is moving node [akka.tcp://riskengine@10.0.0.10:4053] to [Up]
    [INFO][4/24/2016 12:22:22 PM][Thread 0015][[akka://riskengine/system/cluster/core/daemon]] Leader is moving node [akka.tcp://riskengine@10.0.0.10:4053] to [Up]

This line: Leader is moving node... Sometimes I see it twice, sometimes 3 times. Is this expected?

Hyungho Ko
@hhko
Hi. I want to use Akka.Hocon nuget package for my project's config.
My project is also using Akka.NET nuget package.
Akka.Hocon is using the same namespaces and class names with Akka.NET.
so, Compiler generates ambiguous reference errors.
How to solve it? ]
Marc Piechura
@marcpiechura
@hhko if you use Akka you don't need the hocon package yet, we have an issue for this #1419
Hyungho Ko
@hhko
@Silv3rcircl3 Thank you for good information.
Section name is fixed on 'akka' in both Akka.NET and Akka.Hocon.
I think if it is not fixed, Akka.Hocon can be more flexible library.
Vladimir Sergienko
@vss1001
Hi gents, I have spent some time reviewing the options out there I am settled on using Akka.NET on my next project.
The one area that I have a question on at the moment relates to the security of over-the-web remoting.
Due to the nature of the application each client company's app instance will be running on its own VM with its own DB persistence for data that it is the "sole point of truth" however it will need to share parts of this data in real-time with an arbitrary and dynamically changing list of other company's app instances. I have to ensure that the communication between these app instances is secure but due to the dynamic interconnection I can't have predefined VPNs as suggested on http://getakka.net/docs/remoting/security . I am planning on deploying the app instances on ASP.NET Core RC1 on Ubuntu docker containers, is Akka.NET port to .net Core anywhere close to reliable or should I target Mono/ some other key recommendations?
Any suggestions on how I can ensure communication encryption / security for remote messages? Is it possible or viable at the moment to use DotNetty with Akka.NET instead of Helios to take advantage of TLS?
Toshko Andreev
@Ravenheart
greetings guys
how do i remove Json.NET as the defaul serializer
i'm following the bootcamp tutorials
and everything works OK, but theres a warning that json.net will be removed as default serialzier soon
Marc Piechura
@marcpiechura
@Ravenheart it's explained in the docs here
Marc Piechura
@marcpiechura
@vss1001 we have an issue for .net core #992, @Aaronontheweb is working on replacing Helios with dotnetty, don't know what's the actual status is but until then the current solution is, as far as I know, to keep your ActorSystem secured behind a web api that supports your security concerns
Dave Sansum
@dave-sansum

I have a question around dependency injection. In the akka.net docs it has the following "When scoping actor type dependencies using your DI container, only TransientLifestyle or InstancePerDependency like scopes are supported. This is due to the fact that Akka explicitly manages the lifecycle of its actors. So any scope which interferes with that is not supported."

What I want to figure out is why when akka manages the lifecycle of the actors does it also needs to do the same for dependencies? We're currently starting out with Akka in a hybrid environment so are injecting current components in to the actors. We've been hitting issues where singleton components are forced to instances (in the Ninject DI library specifically via BeginBlock) so we're ending up with say multiple db connections rather than using the singleton pool?

We can implement our own DI resolver to solve this which is fine but we're intrigued to know why this is the case in the first place as it's surely not a responsibility of the Akka framework to manage it's dependencies?

Thanks in advance

Toshko Andreev
@Ravenheart
must I call base.PostStop() in override PostStop?
Arjen Smits
@Danthar
@dave-sansum The discussion in here should be illuminating: akkadotnet/akka.net#1139
Note that it is abit older. But afaik not much has been improved since.
Toshko Andreev
@Ravenheart
also there appears to be an ebook about akka.net (its referred to in Unit 2's start page) whats it called and where can i buy it from
Arjen Smits
@Danthar
There are plenty of akka related books. And the theory is easily applicable to akka.net. http://getakka.net/docs/Books
as for .net specific books. I know there is one currently being written. But i keep forgetting the link: @bruinbrown is the author
Toshko Andreev
@Ravenheart
alright thanks
Arjen Smits
@Danthar
@dave-sansum In short. Singleton scopes should be supported. If it does not, its a bug in the DI plugin. imho
We know there are a few - bugs in the di plugins
I dont use DI i.c.w akka alot. But when i do its Autofac. And i know that one works properly in all cases.
I noticed that the more i use Akka in my projects, the less i use DI. Because eventually you realise having an actor manage those resources, is a better model. In an actor based world that is.
We do have some changes planned for the DI api. Im guessing that will also be the time some of those issues will be adressed.
when that is, i cannot say. Will probably be a while.
Dave Sansum
@dave-sansum
@Danthar had a look through that link but couldn't find the answer. Even at this early stage we can see having an actor manage those resources is the right way but our hands are tied as we try and make it there! We're pretty convinced it's a bug with the Ninject DI library. If you read around Ninject 'BeginBlock' it's essentially discouraged as it ignores all life cycles set on the container and always creates a new instance everytime. We think this is just an unrequired step and even without the need for lots of DI forcing a change of lifecycle without anyone knowing just feels wrong. Happy to do a PR for the Ninject repo if it'd get merged sooner?
Arjen Smits
@Danthar
@dave-sansum the link was intended to give you abit of background on the state of the DI plugins.
hence my followup above
And your right about it being a bug.
PR's are most welcome
We recently moved the plugins out of core repo
CI still needs to be setup. but that will also happen soon.
Dave Sansum
@dave-sansum
Great. Will submit the PR this afternoon. Thanks for teh advice
Carlos Torrecillas
@CarlosTorrecillas
Unfortunately our changes don't seem to be fully working and we are facing issues with the Release method in Ninject and the dependencies aren't being released for some reason. If we get to the bottom of it we will submit the PR
Arjen Smits
@Danthar
:+1:
Justin Merth
@jdmerth
Hi all, when using cluster sharding, how are entities removed from a shard when they're no longer needed?
Maxim Cherednik
@maxcherednik
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
Toshko Andreev
@Ravenheart
hey guys assuming i've got computers behind a NAT
is it at all possible to communicate with them
if say i have a central server thats all good network wise
Maxim Cherednik
@maxcherednik
@Ravenheart if you wish to have a bottleneck, you can. Akka assumes peer-to-peer connection