Hi Alexey,
Sorry for the confusion. I mixed up how this works. Do you think we should
add another method to start the target?
def startJournalPlugin(system: ActorSystem, journalPluginId: String): Unit
def startSnapshotStorePlugin(system: ActorSystem, snapshotPluginId: String
): Unit
It could
>
>> The problem with the PersistencePluginProxy.start(system) is that AFAIU
>> it checks the actual actor system config before it decides how exactly to
>> start the plugin, and if in the config it say "start-target-journal=false"
>> (as in my case) it won't start the underlying journal.
>>
>
> No
On Mon, Aug 8, 2016 at 9:13 PM, oleksiys wrote:
> Hi Patrik,
>
> no, it's not for production, but during testing we'd like to be able to
> shutdown cluster nodes to make sure the app behaves properly.
> In the proxy journal config file I set the "start-target-..." property to
> false for all the
Hi Patrik,
no, it's not for production, but during testing we'd like to be able to
shutdown cluster nodes to make sure the app behaves properly.
In the proxy journal config file I set the "start-target-..." property to
false for all the nodes and I want to start the target journal only on the
o
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
Hi,
I have a usecase, where I'd like to be able to move the proxied journal
from one cluster node to another.
Looks like I can redirect all the journal clients using:
*PersistencePluginProxy.setTargetLocation(someNewLocation)*
But now on the cluster node, that has to host the journal I need to