Severity Code Description Project File Line
Error The command ""D:\Repositories\olympus\akka.net.paket\paket.exe" restore --references-files "D:\Repositories\olympus\akka.net\src\contrib\dependencyInjection\Akka.DI.Ninject.Tests\paket.references"" exited with code 1. Akka.DI.Ninject.Tests
happens about half the time during a normal build
like, why does anything need to restore when all I did was update some of my own source?
@stefansedich looks like akkadotnet/akka.net#1434 passes now
Hey guys, in a simple clustering scenario -- how do I go about creating a singleton actor? (like only create it on one single node, and then, how do the other cluster members get an IActorRef/ActorSelection to it?)
Is there an established pattern / example of it?
merged
testing my "install.sh" script again then getting onto getting unit tests running under mono.
Looking at http://getakka.net/docs/clustering/cluster-extension#when-to-work-with-gossip-directly -- it says "Cluster Singletons" can't be done through a router (and needs to be done via monitoring gossip, somehow?) -- Is there an example or a pattern for this anywhere?
This message was deleted
This message was deleted
This message was deleted
oops
fresh VM to build under Mono 4.3 is not just a script away!
hopefully I have as much luck with the tests this time around.
As discussed, here you go, Andrew--this one is the issue about using alternative config formats besides HOCON: akkadotnet/akka.net#1450
@BrainSlugs83 we'll have cluster singletons as part of Akka.Cluster.Tools plugin. Most of it is already done (including cluster singleton), we just need to write the rest of test specs for them.
ok. as soon as i specify any kind of akka.loggers in my test class the EventFilter assertion stuff breaks. even if i specify Akka.Event.StandardOutLogger
anyone know what's up with that?
Implemented a retrying-exponentialbackoff-supervisor. Not meant to be a one-size-fits-all solution. But might be interesting to some ppl nonetheless. https://gist.github.com/Danthar/82e89eff01ba1eb1d4c3
sending Update() to a PersistentView doesn't appear to have any effect.. could I be doing something wrong? Looking through the source of PersistentView I can't find anywhere where it handles this message type.
does it run under mono to your knowledge
:+1: tell us how you get on, would be interested to hear how it goes.
I think stefansedich is working on getting 4.3 to work.
Hi, is it possible if i send text file (133KB) from akka server to client Akka ?. i have try but client is not respond
public class HelloActor : UntypedActor
{
public HelloActor()
{
}
protected override void OnReceive(object request)
{
var data = System.IO.File.ReadAllText(AppDomain.CurrentDomain.BaseDirectory+"myfile.txt");
Sender.Forward(data);
}
}
var actor = System.ActorSelection("HelloActor");
return await actor.Ask<string>(null, TimeSpan.FromHours(1));
is it to large for 133 KB txt file ?
and this is my config hocon at server
remote {
log-sent-messages = on
log-received-messages = on
maximum-frame-size = 10MB
Hi guys. Anyone know a link for a good tutorial for a akkadotnet FSM? I have only seen the official documentation but it is quite poor...
@chillitom Update on PersistentView triggers it to send ReplayMessages message to the journal. In result it replays events that happened from the last replayed message received
Guys. Anyone can explain about large message ? is it to large for 133 KB txt file
???
@tru3d3v 10mb isn't a valid value for that setting
it's expressed as "total bytes"
public long? GetByteSize()
{
var res = GetString();
if (res.EndsWith("b"))
{
var v = res.Substring(0, res.Length - 1);
return long.Parse(v);
}
return long.Parse(res);
}
bah, stupid markdown
10 * 1024 * 1024
@BrainSlugs83 another hack I've seen for doing this is pinning your "singleton" to the Akka.Cluster leader
you can use gossip messages to tell if a given node is the leader
and when leader == self then create singleton
otherwise have everyone else look for it
there's only 1 leader in the cluster at any time
and leaders change only when the previous leader was gracefully terminated or forcibly removed by a human
which is why that hack works pretty well
kicking one off
@ronnyek @GraemeBradbury I am working on getting it to build and run tests which is a nightmare, for one it won't even build under mono 4.2 as some methods used in the IO stuff is not even in mono 4.2 and was only added a month ago.
would be scary to run it without knowing it builds and all tests pass as who knows what is missing at runtime.
@Horusiath, thanks for the heads up -- @Aaronontheweb -- double thanks, that seems like it will work well -- especially with a persistent actor (new singleton comes up and will get the last committed state) -- I'm thinking if a node gets a message that it's no longer the leader it should stop the singleton actor too...
Is there anyway to specify that certain roles cannot be the leader? (I have some roles in my cluster that are transient.)
(Or the opposite of that, to declare: "only these roles can be the leader?" -- black-list or white-list works for me, just need to keep the transients from becoming leaders.)
heh, that's a good question - no, there isn't at the moment
typically though, one of your seed nodes will almost always be your leader
so just boot the non-transient ones first
the other thing you can do... just thinking about this
is have the leader, whoever it is
it can be any type of node
use a clustered router to deploy your "singleton" actor onto a specific type of role
like instead of having that actor run on the leader itself
the leader instead just becomes responsible for 1. checking if that actor has already been deployed and then 2. deploying it onto a specific role if it hasn't
Oh not a bad idea -- have the leader run the clustered router...
Right -- have to check if it's already been deployed, that makes sense...
yeah, that's a small bit of "consistency" price you have to pay in exchange for decoupling :p
How would I detect if it's gone down? -- will a deathwatch on the actor itself work, or should I deathwatch on the node itself? (can the router tell me what node it deployed it the "singleton" to?)
if the router is configured to only deploy a single routee
which is easy to do
you can use
router.Tell(new Identify("are you a singleton?"))
and the routee will reply back with
ActorIdentity
and then you can Deathwatch the routee
sigh so I just chucked a simple console app at my mono dev VM, and that segfaulted just running.
meaning that all actors will automatically reply to it
then it ran after a while, something must be fucked with this vm.
I need another laptop
@Aaronontheweb thanks -- sometimes Akka makes me feel like, I have a hammer, and all these nails -- and for some reason, I'm looking for the screw driver anyway. XD
or if you want to run the entire test suite,
./build.cmd all
as for re-running it on the build server, I'll need to give you an account
@Aaronontheweb this will be more complicated - for some reason when I'm updating nuget packages in persistence plugin projects, references get kicked out of the csproj
ok, I see now - when you usually get nuget package, you should have a separate dir create for it, with *.nupkg file and lib sub-directory
now when I'm downloading nightlies I don't have lib sub-dir, only
[Content_Types].xml file
as you can see there, all of the NUKPGs I produced when I ran it yesterday definitely have binaries in them
based on the file sizes
ah, my bad!
those are the symbol pkgs
the true NuGet packages are screwed up
I can see that
so something must not have been updated in the FAKE script when paket was introduced
probably in the output copying step
let me check
we use XUnit 2
I'm pretty sure that's been updated to work with the VS Test Runner
@Aaronontheweb with the hack about monitoring gossip and having the singleton live on the cluster lead, would this work if you had Lighthouse as your seed nodes?
couldn't use it OOB
it's definitely a hack
Cool, yeh just wanted to understand that - sounds like proper cluster singleton isn't too far away anyhow