If I have 2+ nodes (cluster sharding) running, and I start sending messages, none are getting processed, once I drop down to 1, processing starts on that node, then I can later add additional nodes and they will sometimes pick up the load.. Is this by design?
am I missing another config?
beta60
that we're trying to ship in 1.3.6
my bad on the delay on the 1.3.6 release
when do you think that the cluster sharding stuff will be out of beta?
Awesome, I don't know why it didn't work before my upgrade, perhaps cleaning everything out and reinstalling the old version fixed something. Every message came through near instantly on 0.4.6.
glad to hear it
after moving to nightlys, I am getting this error:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.MissingMethodException: Method not found: 'Void Hyperion.SerializerOptions..ctor(Boolean, Boolean, System.Collections.Generic.IEnumerable
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.MissingMethodException: Method not found: 'Void Hyperion.SerializerOptions..ctor(Boolean, Boolean, System.Collections.Generic.IEnumerable
1<Hyperion.Surrogate>, System.Collections.Generic.IEnumerable1<Hyperion.SerializerFactories.ValueSerializerFactory>, System.Collections.Generic.IEnumerable`1<System.Type>)'.
I suspect
^^^
I didnt have a reference to it at all
thanks again for the help
one question, what triggers a rebalance?
i am having an issue using UnboundedStash
below is a cut-down actor implementation that i am using
public class ClassName : ReceiveActor, IWithUnboundedStash
{
public IStash Stash { get; set; }
public ClassName()
{
ReceiveAny(_ => Stash.Stash());
}
void BecomeLoaded()
{
Stash.UnstashAll();
}
}
the problem i am having is that when BecomeLoaded() is called, i am getting a null pointer exception on Stash
i have not tried sending a message to it to see if one is also thrown on ReceiveAny
any thoughts on this? i can obviously do a null check before calling UnstashAll, but concerned that its not actually working
Upgrading to 1.3.5 from 1.2.3, and I'm starting to see some random serialization exceptions upon restarting some nodes:
Cannot find serializer with id [7]. The most probable reason is that the configuration entry 'akka.actor.serializers' is not in sync between the two systems.
which is weird because that's Akka's persistence serializer, which is loaded automatically
@ismaelhamed have you specified persistence config as fallback explicitly? If I remember correctly, after 1.3 there were some problems with loading configurations - because we started supporting .net standard - i.e. app.config were no longer used due to lack of ConfigurationManager API.