thx all clear now !!!
On Sunday, August 7, 2016 at 3:10:18 PM UTC-4, Henry Mai wrote:
>
> > What is testActor ? There is no variable of that name? what does it
> represent ?
>
> testActor in the example is just some arbitrary actor that is created in
> the test code (not shown in the docs).
>
Hi,
I have been trying to Log things within my scalaTest as such:
class ChangeSetActorTest extends
PersistenceSpec(ActorSystem("Persistent-test-System")) with PersistenceCleanup {
val log = Logging(system, this)
Basically let's just say that ChansetActorTest inherit from TestKit(system
> What is testActor ? There is no variable of that name? what does it
represent ?
testActor in the example is just some arbitrary actor that is created in
the test code (not shown in the docs).
It refers to the B actor in this sentence:
"This code can be used to forward messages, e.g. in a ch
Great, thanks for the update.
sön 7 aug. 2016 kl. 20:08 skrev Eric Swenson :
> Thanks, Patrik. That is precisely what happened. I had been using
> auto-down-unreachable-after, and while this appeared to work fine in the
> normal "rolling update" mode of deploying nodes to our cluster, it had the
Thanks, Patrik. That is precisely what happened. I had been using
auto-down-unreachable-after, and while this appeared to work fine in the
normal "rolling update" mode of deploying nodes to our cluster, it had the
split-brain effects when there were transient cases of unreachability. I
have s
It's typically caused by multiple persistent actors with the same
persistenceId running at the same time. E.g. because there were a network
split and your cluster was split into two separate clusters and thereby
starting multiple persistent actors. That is why we so strongly recommend
against using
This is by design. See discussion in
https://github.com/akka/akka/issues/18050. It should be done in the plugin
implementations where the necessary information is available. I have create
a feature request in the Cassandra plugin.
https://github.com/akka/akka/issues/18050
On Fri, Jul 29, 2016 at 2
The last link should have been
https://github.com/akka/akka-persistence-cassandra/issues/116
On Sun, Aug 7, 2016 at 6:34 PM, Patrik Nordwall
wrote:
> This is by design. See discussion in https://github.com/akka/
> akka/issues/18050. It should be done in the plugin implementations where
> the nec
On Wed, Jul 27, 2016 at 8:12 PM, Muthukumaran Kothandaraman <
muthu.kmk2...@gmail.com> wrote:
> Hi,
>
> I would like to understand the possible degree of parallelism in Cassandra
> persistence plugin with Cassandra 3.4.0.
>
> For my usecase, I would be having around 3K distinct peristent actors
>
As far as I can see the PersistencePluginProxy can only be used with the
default journal plugin and then you would
use PersistencePluginProxy.start(system).
I hope you need this for testing. PersistencePluginProxy is not intended
for production usage.
Regards,
Patrik
On Sat, Aug 6, 2016 at 12:46
Thanks.
On Friday, August 5, 2016 at 7:32:54 AM UTC-4, murtuza chhil wrote:
>
>
> Hi Gitted,
>
> I am a newbie and not much of a scala guy
>
> The example referenced is for producing the largest of the 3 numbers input.
>
> zip1's zipwith is using 2 of the 3 numbers as input and producing one
Yes, that is documented behavior. The reason for the special first seed
node is also documented. What is your question?
Regards,
Patrik
tors 4 aug. 2016 kl. 04:33 skrev Yutao Shuai :
> In a 3-node cluster, all of nodes are seed nodes, if first node start
> failed, the whole cluster can't start su
That is documented behavior.
reference.conf have substitutions resolved first, without application.conf
in the stack, so the reference stack has to be self-contained.
One way to solve it is to do the concatenation of the base url and the
method suffix in code instead.
/Patrik
tors 4 aug. 2016 kl
13 matches
Mail list logo
