These are chat archives for akkadotnet/akka.net

18th
Jun 2015
Bartosz Sypytkowski
@Horusiath
Jun 18 2015 06:07
Lighthouse isn't available as nuget package? 0.o
tstojecki
@tstojecki
Jun 18 2015 07:31
it is a stand alone vs project that compiles to an .exe at the moment with a batch file that lets you run it as win service
tstojecki
@tstojecki
Jun 18 2015 07:37
i don't know that nuget would be the right fit, something like chocolatey might be a better one
Raymen Scholten
@raymens
Jun 18 2015 07:45
I also found that odd when I was trying to run a sample
Timur Babyuk
@timba
Jun 18 2015 08:09
I don't think that windows service should be thought as the only deployment option for Lighthouse. For Azure worker role is a better fit. Appharbor has its own background workers. Not to mention Mono/Linux. The key item in Lighthouse is lighthouse actors subsystem which should be configured and run wherever it is deployed. So it's a perfect candidate to add either to a separate nuget package or as a part of Akka cluster.
tstojecki
@tstojecki
Jun 18 2015 08:12
it seems like the project currently combines the two
the lighthouse actors subsystem embedded within a windows service
so this exercise would involve creating a nuget package for the lighthouse actors subsystem that then can be referenced inside of a container of chioce (win service, azure worker role, etc...)
is that what you're after @timba?
Timur Babyuk
@timba
Jun 18 2015 08:49
Discovery service seems to be a natural part of clustering. So I'd prefer to put it into Akka.Cluster package.
Roger Johansson
@rogeralsing
Jun 18 2015 09:30
Yes, but at the same time, creating a lighthouse service is literally 3 lines of code + a bit of config in its simplest form.. Petabridge Lighthouse does a little bit more, you can pass command line arguments and such to it..
But we also have to keep in mind the scope of the akka.net project, we are porting what exists in java Akka. everything else is pretty much out of scope and should be hosted elsewhere
Bartosz Sypytkowski
@Horusiath
Jun 18 2015 09:31
I think that Lighthouse as command-line program installed as chocolatey is good idea
Roger Johansson
@rogeralsing
Jun 18 2015 09:32
yes absolutely. but that can be managed by Petabridge
@Horusiath where is the 3 sec for akka.persistence tests specified?
the timeout that is.. hardcoded or in config?
Bartosz Sypytkowski
@Horusiath
Jun 18 2015 09:36
@rogeralsing are you talking about Akka.Persistence.TestKit specs?
Roger Johansson
@rogeralsing
Jun 18 2015 09:40
yes
Bartosz Sypytkowski
@Horusiath
Jun 18 2015 09:44
AsyncWriteProxy has hardcoded timeout (marked as TODO in both .NET and JVM ;) ) on replay but it's not 3sec ;) If I'm correct this is a TestProbe.ExpectMsg timeout
Roger Johansson
@rogeralsing
Jun 18 2015 09:52
Ah oki
Roger Johansson
@rogeralsing
Jun 18 2015 12:09
Pretty impressive with an Akka Transport on Akka IO :)
The framework builds itself :D
Timur Babyuk
@timba
Jun 18 2015 13:26
@rogeralsing I see you point about leaving Akka.NET clear and following inherited Akka model. But 3 lines of code is potentially 3 bugs. So having reusable piece of code even such small piece of code won't hurt anyone I believe. It's possible to put discovery service to a separate package as @tstojecki mentioned and I think such package will appear in form of community contribs to the project.
Aaron Stannard
@Aaronontheweb
Jun 18 2015 15:58
@Horusiath that is a good idea
I'll see about making that happen
Aaron Stannard
@Aaronontheweb
Jun 18 2015 16:36
@timba I'm going to make lighthouse more user-friendly, for sure
Aaron Stannard
@Aaronontheweb
Jun 18 2015 16:41
@rogeralsing is there a new XUnit plugin for ReSharper or VS that runs XUnit 2?
I miss being able to run our tests in debug mode :p
also, I'm not a fan of the latest changes to Gitter - seems like they don't show which messages have been read or not any more
Aaron Stannard
@Aaronontheweb
Jun 18 2015 17:07
for anyone who's been wondering about Microservices with Akka.Cluster, here's a great story from theJVM: http://tech.iheart.com/post/121599571574/why-we-picked-akka-cluster-as-our-microservice
iHeartRadio is one of the most popular apps in the US
Roger Johansson
@rogeralsing
Jun 18 2015 17:14
@Aaronontheweb I use the built in testrunner in vs for xunit2 (i think.. it works, and I can debug, thats enough for me :) )
Aaron Stannard
@Aaronontheweb
Jun 18 2015 17:14
got a link for that?
Roger Johansson
@rogeralsing
Jun 18 2015 17:18
its the one built into vs. I havnt installed anything (that I remember)
Chris Martin
@trbngr
Jun 18 2015 17:21
Great article @Aaronontheweb! Do you have a list of Akka-based blogs? Jvm and .net.
Aaron Stannard
@Aaronontheweb
Jun 18 2015 17:24
oh really? so it gets picked up by VS without an extension?
that's basically everything from the core Akka.NET team :p
Chris Martin
@trbngr
Jun 18 2015 17:26
But I already subbed to those :P
Aaron Stannard
@Aaronontheweb
Jun 18 2015 17:26
haha
Bartosz Sypytkowski
@Horusiath
Jun 18 2015 17:26
you've forgot Hakan
Aaron Stannard
@Aaronontheweb
Jun 18 2015 17:27
oh yeah, he has good stuff on the TestKit
Bartosz Sypytkowski
@Horusiath
Jun 18 2015 17:27
is pretty good
Chris Martin
@trbngr
Jun 18 2015 17:28
nice
tstojecki
@tstojecki
Jun 18 2015 17:57
@Aaronontheweb good article, have you actually used akka.net cluster in prod with good success? ... would love to that, but those intermittent tcp errors are not giving me a warm and fuzzy feeling
i have looked at the comments and issues today, looks like others are running to some of those as well
This message was deleted
Aaron Stannard
@Aaronontheweb
Jun 18 2015 18:23
@tstojecki senor @annymsMthd has. You have to bear in mind that a lot of the issues that come up with Akka.Cluster when you're initially launching it have to do with two nodes racing to connect with each other, dropping the connection attempt when they realize that two are occurring at once (which is illegal,) and then waiting at random intervals to attempt to connect again.
Cassandra, Riak, and other clustered DB systems run into the same issue
and it's something that comes up more often in dev and test than production
that being said, eliminating intermittent TCP connection errors is something that we're still working on
1.0.2 resolved a lot of that
but there's still a lot more work to do
I'm just about done with the R&D I had to do to develop Petabridge's training courses (gotta pay the bills,) shifting back to full-time R&D on Akka.Cluster and Helios next week
I've personally used Akka.Remote in production under what I would consider to be very heavy workloads
tstojecki
@tstojecki
Jun 18 2015 18:26
great to hear you guys are aware and on top of that
Aaron Stannard
@Aaronontheweb
Jun 18 2015 18:27
yeah, I'm anal about the quality control on Akka.Cluster - but a lot of the issues are really subtle
i.e. we realized that running the heartbeat system on top of the TPL had devastating consequences under even light loads
moved that to the dedicated scheduler and resolved a lot of heartbeat issues
and I'm pretty sure there are still some issues inside the EndpointManager