Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Oct 14 21:02
    Aaronontheweb synchronize #3975
  • Oct 14 21:02
    Aaronontheweb opened #3975
  • Oct 14 20:11
    IgorFedchenko commented #3973
  • Oct 14 20:10
    IgorFedchenko synchronize #3973
  • Oct 14 20:06
    IgorFedchenko synchronize #3973
  • Oct 14 20:06
    IgorFedchenko synchronize #3973
  • Oct 14 19:42
    IgorFedchenko edited #3973
  • Oct 14 18:08
    Aaronontheweb commented #3937
  • Oct 14 17:27
    Aaronontheweb commented #90
  • Oct 14 17:26
    Aaronontheweb commented #90
  • Oct 14 17:25
    Aaronontheweb assigned #90
  • Oct 14 17:16

    Aaronontheweb on dev

    Provide static GetRoutees.Insta… (compare)

  • Oct 14 17:16
    Aaronontheweb closed #3974
  • Oct 14 17:16
    Aaronontheweb milestoned #3974
  • Oct 14 16:05
    jackowild opened #90
  • Oct 14 15:08
    Aaronontheweb commented #3974
  • Oct 14 15:08
    Aaronontheweb commented #3974
  • Oct 13 14:40
    cptjazz synchronize #3974
  • Oct 13 14:07
    cptjazz opened #3974
  • Oct 13 08:30
    ismaelhamed commented #3937
Weston
@ronnyek
I've effectively got data coming in from different sources, sometimes polled, sometimes pulled, sometimes pushed in.
Ultimately I need to see what of that data a customer is looking for and notify them in the appropriate manner
so it woudlnt be like oh we processed this data, now send notification to 20k users at the same time
it'd be much more specific
I figure if I could have a pool of processors, and a pool of notifiers
because notifiers need to determine best method to notify client, and actually do the notification
I oculd just have a big mq, and a service hosted that just consumes work items off the queue
and notify accordingly, but seems like if the lifecycle of actors in akka made sense, this owuld be much better for being able to scale out resources
we're having a lot more processing consumption, increase resources there
Weston
@ronnyek
am I way off base? I know OF projects that use akka / akka.net, but I dont know what responsibilities akka serves there... or how it helps those projects scale.
also, are akka/akka.net really a major version or more behind, or do they just have diff versioning?
Timur Babyuk
@timba
Aaron Stannard
@Aaronontheweb
found a regression in Akka.Remote we introduced in v1.0.2
serialization problem with actor refs. Think it has to do with NoSender going over the network but I'm not 100% sure yet.
@ronnyek we have totally different versioning than they do
we started working on Akka.NET somewhere around Akka 2.1-2.2
Roger Johansson
@rogeralsing
@Aaronontheweb how does the regression manifest itself?
Roger Johansson
@rogeralsing
@Aaronontheweb btw. "RemoteDeploySpec" is wrong, it doesnt do anything remote. everything is just deployed locally
or am I missing the purpose of it ?
Roko Bobic
@rocco337
Hi, I need help with scheduller
Can I cancell scheduler from actor?
Boban
@bobanco
@rocco337 Yes you can cancel the scheduler, but you have to use Context.System.Scheduler.Advanced.ScheduleRepeatedlyCancelable which will return ICancelable and then you can call .Cancel() on that.
Bartosz Sypytkowski
@Horusiath
@rocco337 when you subscribe to scheduler you can pass ICancellable to it or receive cancellable object as a subscribe result
Roger Johansson
@rogeralsing
ScheduleTellRepeatedlyCancelable and ScheduleTellOnceCancelable are available directly on the standard scheduler
Roko Bobic
@rocco337
Tnx. I understand that you can cancel scheduler. But can you cancel scheduler from actor that is scheduled?
Basically I triggered repeated scheduler to send message on one actor
and than fro mthat actor I would like to cancel scheduler
Roger Johansson
@rogeralsing
oh, no, not unless you pass the ICancellable to it
Roko Bobic
@rocco337
aha yes I thought so. Maybe than it is not good idea to try to cancel itfro mthere :)
Roko Bobic
@rocco337
@rogeralsing just read your blog about serviceBus. It is jus what I needed.Tnx
Bartosz Sypytkowski
@Horusiath
ok @rogeralsing . I think I've covered #1067
Aaron Stannard
@Aaronontheweb
@rogeralsing an all-systems address confused the RemoteActorRefProvider and it tried to resolve a local address for an akka:// actor path
which is by definition, local
the remote deploy spec is testing the deployer, not the actual over-the-wire deployment mechanism
there's multi-node tests for Akka.Remote and the RemoteRouterSpec which actually do real remote deployments
I'm sorry - I'm thinking of RemoteDeployer spec
no idea what the RemoteDeploy spec was for
Aaron Stannard
@Aaronontheweb
going to send in a PR in a moment here that turns on multi-node tests for all builds
should be a good time ;)
Weston
@ronnyek
So being versioning is not in line... Does akka have pretty good persistence support and does distribution work reliably?
I think the distribution I speak of is what the java project called clustering
Aaron Stannard
@Aaronontheweb
@ronnyek ah, we're still working on porting over Clustering - we have several Akka.Persistence implementations too but those are still a bit early
here's the roadmap, if you're interested: https://petabridge.com/blog/akkadotnet-2015-roadmap/
Akka.Cluster, the core component of clustering, is the goal of the next release -we
we have people using it in production already and it's been out in some way, shape, or form since August of last year - but there's a lot of subtle stuff that has to be tuned with it
Akka.Cluster.Sharding, Akka.Cluster.Tools, and Akka.Cluster.Metrics are all in the works also
jweimann
@jweimann
Hey aaron, isn't the talk you're doing sat the Aamer as the last codecamp?
same
..
Aaron Stannard
@Aaronontheweb
yessir - more or less the same.